Software engineer interview questions (with what each one is testing)

The behavioural and technical-adjacent questions software engineers actually get asked, what each is testing, and the shape of an answer that scores. Plus how the loop is usually structured.

Software engineer6 questionsUpdated 2026-11-15

Engineering loops usually mix a coding screen, a system design round and a behavioural round. The behavioural round is where strong engineers lose offers: they answer with the team's story and no measurable outcome. These questions are the ones that repeat across employers.

Recruiter screenCoding screen (60–90 min)System designBehavioural / valuesHiring manager
Question 1

Walk me through a system you built and the trade-offs you chose.

What it is testing
Whether you can separate design from implementation, and defend a trade-off you did not get for free.
How to answer
Name the constraint first (latency, budget, team size), then the choice, then what you gave up. One diagram, two sentences of trade-off, and the outcome measured in numbers.
Question 2

Tell me about a bug that took you a long time to find.

What it is testing
Debugging method, and whether you can describe a hypothesis you formed and discarded.
How to answer
Structure it as: symptom, hypotheses, what eliminated each, the moment of the find, and the guard you added so it cannot recur.
Question 3

How do you decide between shipping now and shipping right?

What it is testing
Judgement about reversibility, not perfectionism versus speed.
How to answer
Anchor on reversibility: how expensive is it to be wrong, who is affected, what is the rollback. Then say what you actually shipped and what happened.
Question 4

Tell me about a code review where you disagreed with the reviewer.

What it is testing
Whether you can be wrong in public, and whether you argue with evidence or with volume.
How to answer
Describe the disagreement in one sentence, the evidence you brought, and how it ended — including the case where the reviewer was right.
Question 5

How do you handle a production incident?

What it is testing
Ownership under pressure and whether you separate mitigation from root cause.
How to answer
Mitigate first, communicate a timeline, then investigate. Say who you told and when, because that part is usually missing from candidates' stories.
Question 6

What technical decision are you proudest of?

What it is testing
Whether you have taste, and whether you can explain a decision without jargon.
How to answer
Pick something with a visible consequence — a migration, a decommissioning, a test strategy. Explain it so a non-engineer could follow the reason.

Questions people also ask

Do software engineers get behavioural interviews?

Almost always, usually as a separate round or folded into the hiring manager conversation. It is scored against the same competencies as any other role: ownership, conflict, ambiguity and delivery.

How technical should behavioural answers be?

Technical enough to be credible, simple enough to be followed. If the interviewer has to ask what the system did, the answer spent its time on detail instead of on your decision.

Practise this role

Run a software engineer mock interview.

Questions one at a time, a five-category score, and a rewrite of every answer. Free during the beta.

Start practising
Other roles