Tell me about a time you had to explain a technical problem or trade-off to someone non-technical. How did you make it land?

What the interviewer is looking for

• This question tests communication. Explains technical ideas in terms the listener cares about, checks for understanding, and uses concrete examples rather than jargon.
• What to bring out: Framing in terms of the listener's goals, plain language and analogies, offering options with trade-offs, and checking they understood.
• Expect a follow-up like: How did you know your explanation worked?

Another way it may be asked: Say a product manager asks why a feature will take three weeks instead of three days. How would you explain it?

A structure to follow: STAR, with the weight on Action and Result

1. Step 1

   Situation

   One or two sentences: where, when and what was at stake. Pick a real example you were close to.

2. Step 2

   Task

   What you personally were responsible for. Say "I", not only "we", so the communication you showed is visible.

3. Step 3

   Action

   The two or three things you did and why you chose them over the alternatives. This should be about half your answer.

4. Step 4

   Result

   What changed, in your own measure of it, and what you would do differently. Only use numbers you can stand behind.

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

• Describing what the team did without saying what you did.
• Choosing an example with no clear outcome, or one you cannot answer detailed questions about.
• Ending on the action and skipping the result and what you learned.

How to practise it

Write two bullet points for each STAR letter, then say the answer aloud in about two minutes.

Related questions

• When would you pick a hash map over a list to store data, and what does that choice cost you?
• Imagine your code works on your laptop but fails in the test environment. Walk me through how you would start figuring out why.
• How do you usually use Git day to day, from starting a piece of work to getting it merged?
• How do you decide what to test in a new feature, and how do you balance unit tests against integration tests?
• Tell me about the trickiest bug you have tracked down. How did you find the root cause?

Browse all questions