SDE behavioural interview (India product startup)
A behavioural round for a Software Development Engineer role at a fast-growing Indian product startup.
An advanced-level session of about 12 minutes. 4 questions, each answered out loud.
Engineers usually lose this round in the result. The situation gets three sentences, the task gets one, the action runs two minutes of implementation detail, and the story ends on 'and then we shipped it' — which tells the hiring manager nothing about whether it worked. Reverse the weight: one sentence of situation, one on what you specifically owned, a short action, and a result with something measurable in it — latency, incident count, the rollback that did not happen, the week the on-call rota went quiet. The friendly tone in this round is genuine and the follow-ups still are not soft. 'Tell me about a conflict' is followed by what the other person would say about it. 'A time you failed' is followed by what you changed in how you work. The second question is the interview.
Angles worth taking
- Say what your specific contribution was and then narrow it once more — the first version is almost always still the team's work.
- Tell the conflict story from the other engineer's side for one sentence before you tell it from yours.
- For a failure, name the decision that caused it. 'Requirements changed' is a circumstance, and the round is asking for ownership.
- End every story on a number or a state change: deploy time, error rate, a review step that exists now because of what happened.
- When a follow-up digs into a technical choice, answer at the level of the trade-off first and offer the detail only if they ask.
- If the best example comes from a college project or an internship rather than a job, say so at the top and tell it anyway.
Who is in the room
You play
A software engineering candidate
You speak with
A friendly hiring manager running a structured behavioural 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
4
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 behavioural questions using the STAR structure, grounded in real examples.
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.
More mock interview rounds
All mock interview rounds · Tech rounds · All speaking practice