Tell me about a time you had to choose between quality and speed.
Break down this behavioral question with a model STAR answer, the pitfalls that cost candidates points, and the follow-up questions worth rehearsing next.
A strong STAR example answer
The memo went out before any code did: here are the shortcuts we are about to take, here is the cleanup estimate, here is the date we pay it back, and here are the guardrails. My manager and our staff engineer signed it. Only then did we start building.
We had a six-week window to ship an onboarding experiment ahead of the quarter's traffic spike. The clean architecture needed the whole window; a direct implementation inside the legacy flow needed about half. I owned the call, and I chose speed — deliberately, on paper. The hacky path sat behind a single interface, covered by tests, so the risk stayed contained. We shipped well inside the window, the experiment lifted activation meaningfully, and the feature went permanent, which is exactly when debt turns dangerous. Because the memo carried a committed date, cleanup actually happened the following month instead of drifting forever, and the final design reused most of the experiment code. Every shortcut I have taken since starts the same way. If a tradeoff cannot survive being written down with a repayment date, it is not judgment. It is just debt.
How to structure your own answer
- Situation: Describe the delivery window and what each option cost.
- Task: State who owned the tradeoff decision and what the stakes were.
- Action: Show how you made the shortcut explicit, isolated, and time-boxed.
- Result: Give the business result and how the debt was actually repaid.
Common mistakes to avoid
- Claiming you always choose quality dodges the question — and so does always choosing speed.
- Never describe a shortcut with no repayment plan; that is negligence, not judgment.
- The tradeoff looks unilateral if you leave out who else signed off on it.
- Why did speed matter? Without the business result, the shortcut has no demonstrated value.
Follow-up questions to prepare for
Expect the interviewer to dig past your first answer. Common follow-ups for this question include:
- How do you decide which shortcuts are acceptable and which are not?
- Tell me about a time you chose quality over speed instead.
- How do you keep tech-debt promises from being deprioritized forever?
Related practice questions
Keep drilling with these, or browse the complete question bank.
Next up
Practice this question on the clock
Reading an answer and delivering one are different skills. Run a timed round and rate yourself.
Start a practice roundNext up
Interview coming up?
Have your post-interview follow-up email ready before you need it.
Follow-up email generator