What Is the Udaan Interview Process Like? (Round by Round)

Candidates report three to four interview rounds at Udaan, and no separate algorithm round for experienced hires. The round reported most often is a machine coding round. You build a small working program in about 90 minutes, then explain it for about 30 minutes. A design round and a round on your past work follow.

Some reports add a hiring manager conversation and an HR round. Campus candidates report an online coding test on HackerEarth before any interview. Candidate reviews describe about four weeks from application to a final decision off campus.

Quick Overview

Reported lengths vary by role and by level, so treat these as ranges rather than fixed times.

Stage 1: Recruiter Contact

Most candidates report that a recruiter made the first contact, often after an online application. Expect questions about your current work, your reason for moving, and your notice period. A short recruiter step before the technical rounds is typical for companies of this size, though Udaan does not publish its process.

Stage 2: The Machine Coding Round

This round decides most outcomes at Udaan. A machine coding round is a timed session where you build a small working program, usually a console application or a pair of APIs. Candidates report about 90 minutes to build, then about 30 minutes to explain the result to an interviewer. Some reports describe a longer block: about 30 minutes for requirements, 90 minutes to build, and 30 minutes of review.

Reported problems include a news application that calls a public news API and parses the response, a deck of cards game, a parking lot system, a carpooling service, and a fitness booking service with two APIs. Candidates report submitting the code and a README file as a zip archive. Reviewers check that the program compiles, that every stated feature runs, and that the classes are separate enough to accept a new requirement. Several candidates state plainly that no data structure puzzles appear in this round.

Stage 3: The Design Round

Reported design rounds cover both textbook systems and your own work. Candidates report being asked to design Twitter, including trending topics. Frontend and application roles report a design shared on screen to build with React. Database questions appear here too, including relational schema design with optimization.

The full topic list is in What to expect in the Udaan system design interview.

Stage 4: The Past Work Round

Candidates report 30 to 50 minutes on one project from your resume. Interviewers ask what the problem was, what you decided, what was difficult, and what you learned. Choose a project where the key decisions were yours. Questions continue until the interviewer reaches the limit of your real involvement.

Stage 5: Hiring Manager and HR

Reports describe a conversation about your past work and your fit with the team, sometimes with design questions inside it. The HR round is mostly behavioral. Candidates report two questions almost every time: what do you know about Udaan, and why do you want to join. Prepare that answer using How to answer why Udaan.

How the Campus Process Differs

Campus candidates report two screening rounds before any interview. The first is an online technical assessment on HackerEarth of about two hours, with one application style problem. Reported examples are a calendar appointment system with four required functions, and a hotel management API with six. The second is a submission round of about 90 minutes, where you build two APIs and email the code with a README file.

Interviews follow: a case study round of about 40 to 50 minutes, often about a ride hailing or food delivery product, and then a project round. Each step removes most candidates, and reports describe only a few offers per drive.

Timeline and Decision

Campus drives run within a few days, and shortlists between rounds are announced the same day. Off-campus reports are slower. Candidate reviews describe about four weeks from application to a final decision. Silence after the machine coding submission is a common complaint, and some candidates report no reply at all.

The stage by stage waits are in how long it takes to hear back.

Questions to Ask Them

Every round ends with time for your questions, so prepare three. Good ones here are specific to a B2B marketplace. Ask how catalog, order and supply chain work is divided between teams. Ask how much of the team's work serves retailers, and how much serves sellers.

Ask what on-call duty involves during a peak sales period. A specific question also proves that you researched the product.

How to Prepare

• Practice building, not puzzling. Set a 90 minute timer and build a small console application with clean classes. Grokking the Object Oriented Design Interview teaches the class design this round grades.
• Prepare one project in depth. Write down the decisions, the alternatives you rejected, and the numbers, before the loop starts.
• Study marketplace systems. Grokking the System Design Interview covers the queues, caches and databases every order flow uses.
• Write the motivation answer early. The HR round asks what you know about Udaan in almost every report, so prepare that answer before the loop starts.