Tell me about a time new evidence caused you to change a technical decision.

Change a technical decision after new evidence

Demonstrates technical humility by changing direction when measurements invalidate an earlier decision.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I initially proposed adding a cache to reduce latency on a heavily used search endpoint. Before building it, I captured query plans and request traces and found that one unbounded projection was loading far more data than the response needed. We fixed the query shape and added the missing index, which met the latency target without introducing cache invalidation. I changed the design and explained the evidence behind the change.

Full answer below

Practice focus

Evidence-based judgment, adaptability, communication, sunk-cost resistance, and safe course correction.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Why this question matters
A credible answer shows why the first decision was reasonable, what evidence changed, and how the candidate corrected course without defensiveness.

Use this as an adaptable model, not a story to claim as your own. Replace the project, constraints, your actions, collaborators, outcome, evidence, and reflection with truthful details from your experience.
I initially proposed adding a cache to reduce latency on a heavily used search endpoint. Before building it, I captured query plans and request traces and found that one unbounded projection was loading far more data than the response needed. We fixed the query shape and added the missing index, which met the latency target without introducing cache invalidation. I changed the design and explained the evidence behind the change.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
The original idea was not irrational; repeated reads made caching plausible. The measurements showed that it was solving the wrong layer first. I shared the before-and-after plan and trace rather than quietly replacing the proposal, because the team needed to understand both the decision and why it changed. We kept a cache option documented, but only with a measurable threshold that would justify its consistency cost.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Making the first decision sound careless to make the correction look obvious.
Saying data changed the decision without naming the evidence.
Quietly switching approaches without aligning affected people.
Treating persistence as stronger than adapting.

Tell me about a time new evidence caused you to change a technical decision.

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Next interviewer turn

Try a variant

Skill areas

Suggest an improvement

Found this answer useful?