How to answer: “Walk me through a difficult technical decision you made.”

What they’re actually asking

This is the engineering judgment question. Anyone can list technologies; they want to see you weigh options under constraints — time, money, team skill — and commit. The word they're listening for is 'because.'

How to structure your answer

Frame it as options, constraints, choice, result. Name the two or three real candidates, the constraint that decided it (deadline, team familiarity, ops burden — not hype), and what happened. Saying what would have changed your mind shows you decided with your eyes open.

Example answer

“We needed background jobs and the team wanted Kafka. I pushed for a Postgres-backed queue instead: we had two engineers, no ops experience with Kafka, and 200 jobs a minute, not 200,000. We shipped in a week on infrastructure we already knew how to debug at 2am. If we'd projected 50x growth in a year, I'd have chosen differently — we hit 5x, and the queue never blinked.”

What sinks people

• Choosing the resume-driven answer: the shiny tool with no constraint justifying it
• Presenting the decision as obvious — if it was obvious, it wasn't difficult
• No aftermath. A decision without a result is just an opinion.