Software engineer interview questions

Six questions to practice out loud

Written by AI from software engineer job postings. Each one is the kind of question a software engineer interview asks, and each tests one of the five skills you are scored on.

1. QUESTION 1 · ROLE RELEVANCE

   Walk me through two pieces of software you built or changed that make you the right person for this role, in under two minutes.

   They are listening for: Two pieces of work, not your whole history.

   What a strong answer includes

   Two pieces of work, not your whole history. For each: what the system does, what you personally built or changed, and one result with a number, such as latency, defects or users. End on why this role. Weak answers recite languages and frameworks.

2. QUESTION 2 · ANSWER STRUCTURE

   Tell me about a production incident you helped resolve. How did you find the cause, and what did you change so it would not happen again?

   They are listening for: Give the timeline: when it started, when you knew, when it was fixed.

   What a strong answer includes

   Give the timeline: when it started, when you knew, when it was fixed. Name the signal that led you to the cause, such as a log line, a metric or a recent change. Then the corrective action and how you checked that it held. Weak answers stay at the level of the team and never say what you did.

3. QUESTION 3 · COMMUNICATION & PRESENCE

   Tell me about a code review where you and another engineer disagreed. What was the disagreement, how did it get settled, and what shipped?

   They are listening for: Name the change, the comment and the technical reason on each side.

   What a strong answer includes

   Name the change, the comment and the technical reason on each side. Say what you actually wrote or said, and whether you changed your mind. Finish with what shipped and how it held up. Weak answers make the other engineer the villain or skip the substance.

4. QUESTION 4 · JUDGMENT & PROBLEM-SOLVING

   Tell me about a time the design you wanted would not fit the deadline or the budget. What did you give up, and how did you decide?

   They are listening for: State the constraint first: the date, the budget or the size of the team.

   What a strong answer includes

   State the constraint first: the date, the budget or the size of the team. Name the option you dropped, what it would have bought you, and the risk you accepted instead. Say how you would know if the call was wrong. Weak answers describe the design they built and never the one they turned down.

5. QUESTION 5 · SPECIFICITY & EVIDENCE

   Tell me about a time you had to change code that nobody on the team fully understood. How did you work out what it was supposed to do before you changed it?

   They are listening for: Name the system, its age and what depended on it.

   What a strong answer includes

   Name the system, its age and what depended on it. Say exactly how you recovered what it was meant to do: tests you wrote first, logs, the people you asked. Give the change and one number that shows it worked. Weak answers say they refactored it with no evidence that behavior was preserved.

6. QUESTION 6 · ANSWER STRUCTURE

   Tell me about a time a user asked for one thing and needed something else. How did you find out, and what did you build?

   They are listening for: Quote the original request, then the moment you realized it was not the real need.

   What a strong answer includes

   Quote the original request, then the moment you realized it was not the real need. Say what you asked or watched to find the real one, and what you built instead. End with how the user responded and what it changed. Weak answers blame the user for not knowing what they wanted.