HR interview questions
Common Urban Company HR questions, sample answer frames, and STAR tips.
Urban Company Interview Experiences
How Urban Company fresher interviews usually run, campus and off-campus. Patterns shift by year and role, so treat this as a prep map, not a script.
Urban Company placement process includes: 1. Online Assessment (90 minutes) - 2-3 coding problems, 2. Technical Interview Round 1 (45 minutes) - DSA problems and approach discussion, 3. Technical Interview Round 2 (45 minutes) - System design and detailed technical discussion, 4. Managerial Round (45 minutes) - Behavioral questions and project discussions, 5. HR Interview (30 minutes) - General discussion about compensation and role expectations. Total duration: 2-3 weeks from application to offer.
Eligibility (from student reports): 7.0+ CGPA in 10th, 12th, and graduation.
Fresher package ballpark (from student reports): ₹18-25 LPA. Confirm on your offer letter.
Round-wise process
Section titled “Round-wise process”| Round | Duration | What they test |
|---|---|---|
| Online Assessment | 90 min | 2-3 coding problems |
| Technical Round 1 | 45-60 min | DSA + project discussion |
| Technical Round 2 | 45-60 min | System design (orders / logistics) |
| HR | 20-30 min | Behavioural + culture fit |
Real interview experiences
Section titled “Real interview experiences”These are rewritten from public candidate write-ups, not invented composites. Details differ by campus and year.
Experience 1: SDE-1, on-campus (Day 0 offer)
Section titled “Experience 1: SDE-1, on-campus (Day 0 offer)”Source: Urban Company (formerly UrbanClap) Interview Experience for SDE 1 (On-Campus) - GeeksforGeeks
The drive opened with a pre-placement talk by the SVP of Engineering and the VP of Product, then one coding test and three hour-long interviews.
- Round 1 - Coding test (1.5 hours): 3 problems, medium to hard. The candidate solved two of three and still advanced.
- Round 2 - Low-level design (1 hour, with an SDE-II): design a task manager that can add tasks and delete the least frequently used ones. Solved with OOP plus set-backed structures. Note this is essentially an LFU-cache problem dressed as a product feature.
- Round 3 - Low-level design (1 hour, with an engineering manager): design an app for driverless cab booking against a given requirement list. Graded on class structure, data members and member functions - not on running code.
- Round 4 - Managerial (1 hour, with the VP of Engineering): resume walkthrough covering internships and a computer-vision project, then a DSA problem on finding pairs across multiple arrays, generalised to k arrays. The write-up flags that generalising your solution when the interviewer widens the problem was the thing being tested.
- Outcome: Offer on Day 0.
Experience 2: SDE, on-campus
Section titled “Experience 2: SDE, on-campus”Source: Urban Company Interview Experience for SDE (On-Campus) - GeeksforGeeks
- Round 1 - Online assessment (HackerEarth): 3 medium-to-hard problems. The candidate’s own advice was to prioritise dynamic programming in prep.
- Round 2 - Coding interview (1 hour): a single DP problem, live. Interviewer described as approachable and receptive to thinking out loud.
- Round 3 - Low-level design: design an Uber Carpool system - list requirements, then the classes and how they interact. Explicitly no working code required.
- Round 4 - Technical HR: resume-driven, plus what the candidate is actually interested in and where they want to go. Advice from the write-up: answer honestly rather than from a script, and know every line of your own resume.
- Outcome: Selected.
Common thread: Urban Company weights low-level / OOP design more heavily than most fresher loops - two of the four rounds in both accounts are design, and the prompts are consistently marketplace-shaped (cab booking, carpooling, task scheduling). Practising class-diagram-level design out loud matters at least as much as DSA volume here, and DP shows up repeatedly on the coding side.
Questions that come up often
Section titled “Questions that come up often”Coding / technical
Section titled “Coding / technical”- Top-K frequent elements. Usually expects heap / bucket sort
- Shortest path in a grid. Usually expects BFS
- Merge overlapping delivery slots. Usually expects interval merge
- Discussion on marketplace matching and partner allocation, bottlenecks, failure modes, simple APIs
- Detailed project discussion, architecture, hardest bug, what you would change
HR / behavioural
Section titled “HR / behavioural”- Why this product?
- Working with unclear requirements
- On-call or weekend comfort
- Relocation
Practical tips for Urban Company
Section titled “Practical tips for Urban Company”- Clear the screening round first. Timed practice beats last-minute topic hopping.
- For domain questions, explain marketplace matching in plain language, inputs, outputs, what breaks at scale.
- OOPs and SQL still open a lot of Urban Company panels. Do not skip fundamentals.
- HR answers should be concrete. One story with a result beats five slogans.
- If you do not know something, say so and outline how you would find out.
HR interview
Section titled “HR interview”After technical rounds, Urban Company usually closes with a short HR / hiring-manager conversation: motivation, location, notice period, and a couple of behavioural stories. Prepare those answers on the dedicated page rather than cramming them into this hub.