Product-startup SDE interview (India)
A mixed behavioural + technical round for a Software Development Engineer role at a fast-growing Indian product startup.
6 questions, each answered out loud.
There is no whiteboard in this one. The URL shortener question arrives inside a conversation and has to be built out loud, where the person listening only ever holds the last sentence you said. That changes the shape of a good answer: name the components first and say how many there are, then close each one off as you finish it, so the interviewer can follow a structure they cannot see. The behavioural questions run on the same clock, and with six questions there is no room to warm up into them. The achievement question — pick one and go deep, what exactly did YOU do — puts a great deal of weight on a single word. In a team story, the interviewer is listening for where your own work ended and somebody else's began.
Angles worth taking
- Ask what scale the shortener is for before designing; if that is left to you, say the assumption out loud and build to it.
- If you stall mid-design, say what you would check next and why — silence in a spoken design answer reads as a dead end.
- Answer the disagreement question with the decision that was actually taken and by whom; the conversation itself matters less.
- Drop the design register when a behavioural question follows; the two halves of this round reward very different speaking styles.
- Bring a number you can survive one more question about — an estimate you can derive beats a figure you memorised.
- If you have never built at the scale being discussed, say what you have built and reason outward from that instead.
Who is in the room
You play
The interview candidate
You speak with
A warm, professional interviewer running a structured round
Phrases to reach for
These are shown to you before the session starts. They are what you are asked to use, not a list the scorer is checking off.
Ready to speak?
Free to start. You need a TalkDrill account to speak — reading this page does not.
Browse all mock interview roundsThe format
Questions in this round
6
Modes
Learn (guided) · Mock (exam-real)
How a mock interview session works
Pick a round
HR, behavioural, or a role-specific set. Each one tells you how many questions it runs and roughly how long it takes.
Answer out loud
Questions come one at a time and you speak the answer. There is a clock, because a two-minute answer and a five-minute answer are different answers.
Take the follow-ups
Answers get followed up. A vague claim gets pressed on, which is what separates a rehearsed answer from a true one.
Read the report
Structure, evidence, filler and pace per answer, plus the one answer worth recording again before the real thing.
What you're scored on
Every round is assessed the same way, because interviewers are broadly consistent about what a good spoken answer contains.
Answer each question using the STAR structure, grounded in real, specific, quantified examples from your experience.
Structure
Whether the answer has a shape — situation, action, result — or arrives somewhere by accident after ninety seconds.
Evidence
Specifics over adjectives. "We cut it from six days to two" against "we improved the process significantly".
Relevance
Whether you answered the question asked, including the follow-up, rather than the question you prepared for.
Delivery
Pace, filler words, and whether the last third of the answer is as clear as the first.
