Tell me about a major technical decision your team made while you led it. How did you weigh the options, and who did you involve?

What the interviewer is looking for

• This question tests technical judgement. Stays close enough to the technology to ask sharp questions and guide decisions while letting engineers own the solutions.
• Strong answers: A clear decision process, involving the right engineers, written proposals, considering cost and risk, and reviewing the result honestly.
• Likely follow-up: What would you do differently if you made that decision again?

Another way it may be asked: Maybe choosing a database or deciding to rebuild a system. How did the decision get made?

A structure to follow: Answer, explain, example, limits

1. Step 1

   Answer

   Give your direct answer in the first sentence so the interviewer knows where you are going.

2. Step 2

   Explain

   Say how it works or why you would do it that way, in plain words before jargon.

3. Step 3

   Example

   Anchor it in something you have actually done or seen, with the detail that shows hands-on experience.

4. Step 4

   Limits

   Say when your approach would not be the right one. It shows judgement.

This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.

Common slips

• Reciting a definition without showing you have applied it.
• Using terms you cannot explain if asked a level deeper.
• Claiming experience beyond what you can discuss in detail.

How to practise it

Say the answer in 90 seconds, then answer the follow-up as if it were a new question.

Related questions

• How do you stay technical enough to make good calls without becoming a bottleneck in code reviews or design decisions?
• If you were a new manager taking over a team, what would you do in your first month to get to know your people?
• Imagine your team's project is going to miss its deadline. How would you tell the stakeholders, and what would you include?
• Two engineers on your team strongly disagree about how to build something, and it's slowing things down. What would you do?
• How do you design an interview process that's fair and actually predicts who will do well on your team?

Browse all questions