BQ-042 · Technical judgment and decision quality
Describe reversing a technical decision after new evidence appeared.
Illustrative fictional example · Editorial draft, version 1. Use the structure and reasoning to prepare your own experience. Do not present this sample as your personal history.
What the interviewer may evaluate
These are general coaching criteria; interviewers and roles differ.
- Explain why the original decision was reasonable, which new evidence changed it, and how you migrated safely.
- Can you explain the evidence behind a staged summary migration verified against authoritative events?
- Can you describe revisiting explicit assumptions and migrating with evidence without overstating the outcome?
Before you start
- Explain why the original decision was reasonable, which new evidence changed it, and how you migrated safely.
- Separate personal actions from team outcomes.
Choose an experience that answers the prompt
Suitable examples
- Explain why the original decision was reasonable, which new evidence changed it, and how you migrated safely.
- An experience where you can distinguish your decision from the work owned by other people.
Examples to avoid
- I never change architecture decisions because that makes the original design look wrong.
- An example whose outcome you cannot distinguish from a plan or an assumption.
Gather your evidence
- Explain why the original decision was reasonable, which new evidence changed it, and how you migrated safely.
- Your decision, the alternative of defending read-time aggregation after the workload distribution changed, and the reason for the choice.
- The observations that support a staged summary migration verified against authoritative events and their limitations.
Build the answer
- Situation and responsibility. Explain why the original decision was reasonable, which new evidence changed it, and how you migrated safely.
- Actions and reasoning. Explain what you personally changed, who helped, and why you considered defending read-time aggregation after the workload distribution changed.
- Outcome and evidence. Report a staged summary migration verified against authoritative events. Distinguish observation from an assumption or future goal.
- Reflection and follow-through. Explain revisiting explicit assumptions and migrating with evidence. Name one limitation or remaining follow-up.
Full sample answer and paragraph explanations
Read aloud to check pacing. Expand the annotations to see why each paragraph matters and which detail belongs in a follow-up.
Reveal the full illustrative answer
Situation and responsibility
I initially chose read-time aggregation for a small activity summary because the access pattern was simple and updates were infrequent. I owned that API decision and documented the expected workload. Later usage introduced a few very active accounts, and their summaries required much more work than the average account. The new evidence was not merely that traffic increased; the distribution and required read behavior had changed enough to challenge the original choice.
Why this paragraph works
Evidence: An initially justified decision and changed distribution.
Why it matters: Identifies a relevant situation and your responsibility before describing the solution.
Prepare for a follow-up: Prepare this follow-up: Was the original decision a mistake?
Actions and reasoning
I examined request traces by account size and confirmed the expensive path with synthetic high-activity data. I proposed maintaining a derived summary for the affected access pattern, while keeping the underlying events authoritative. We compared that with query tuning and a short-lived cache. I documented the added freshness and rebuild responsibilities rather than present the new design as an obvious improvement with no cost. The team agreed on a staged path with comparison reads before switching consumers.
Why this paragraph works
Evidence: Evidence-driven alternatives with new costs.
Why it matters: Makes a decision and its reasoning visible rather than listing activities.
Prepare for a follow-up: Prepare this follow-up: What evidence changed the decision?
Outcome and evidence
We built the summary and tested updates, delayed processing, and reconstruction from source events. During the comparison stage, we investigated mismatches before making the derived value primary for display. The selected high-activity cases met the agreed read behavior, with freshness limitations visible in the contract. I would use actual production measurements for a latency claim. The design did not replace every query or eliminate the need to handle lag and correction.
Why this paragraph works
Evidence: Comparison and recovery verification.
Why it matters: Connects the claimed result to observations and acknowledges their limits.
Prepare for a follow-up: Prepare this follow-up: What new cost did you accept?
Reflection and follow-through
I learned to state architecture assumptions so that reversal can follow evidence rather than become a personal defense of a past choice. I did not describe the original decision as irrational given the earlier scope, but I owned revisiting it when the conditions changed. A safe reversal also required migration and recovery work; changing a diagram alone would not have protected consumers from inconsistent derived data.
Why this paragraph works
Evidence: Accountability without hindsight distortion.
Why it matters: Turns the experience into a concrete changed habit or mechanism.
Prepare for a follow-up: Prepare this follow-up: How did you migrate safely?
Reveal the concise version — roughly 60–90 seconds
I chose read-time activity summaries for an initially small workload. Later high-activity accounts changed the distribution and made that path expensive. I traced results by account size, reproduced the case, and proposed a derived summary with authoritative source events. We compared tuning and caching, then documented freshness and rebuild costs. A staged migration used comparison reads and tests for lag and reconstruction before switching the display. The selected cases met the agreed behavior, while remaining limits stayed explicit. I learned to make original assumptions visible and own a safe reversal when evidence changes, rather than defend a design or pretend it was always unreasonable.
Improve a weak answer
Weak excerpt
I never change architecture decisions because that makes the original design look wrong.
Improved excerpt
I examined request traces by account size and confirmed the expensive path with synthetic high-activity data. I proposed maintaining a derived summary for the affected access pattern, while keeping the underlying events authoritative. We compared that with query tuning and a short-lived cache. I documented the added freshness and rebuild responsibilities rather than present the new design as an obvious improvement with no cost. The team agreed on a staged path with comparison reads before switching consumers.
The improved excerpt explains a specific decision rather than the unsupported claim in the weak version. Complete it with a staged summary migration verified against authoritative events, and state the limits of what you observed.
Prepare for probing questions
Attempt each response before opening the guidance. Replace fictional details with your own evidence.
Was the original decision a mistake?
It was reasonable under the documented initial workload, though the answer should acknowledge any warning signs that were actually missed. New distribution evidence changed the trade-off; hindsight alone should not rewrite the earlier constraints.
What evidence changed the decision?
Work grouped by account size showed that a few high-activity accounts dominated aggregation. That mattered more than an overall traffic average and justified reproducing the outlier access pattern.
What new cost did you accept?
The derived summary could lag and needed rebuilding and correction behavior. I retained source events as authoritative and documented freshness instead of describing precomputation as free speed.
How did you migrate safely?
Comparison reads and mismatch investigation preceded the display switch. We also exercised lag and reconstruction. A new representation is not ready merely because it produces fast answers on one dataset.
How did you communicate ownership of the reversal?
I explained the original assumptions, new observations, alternatives, and migration cost. I owned the recommendation without pretending that everybody else should have predicted a requirement distribution that had not yet existed.
Adjust the evidence to your level
Early-career
Use a bounded project, internship, or volunteer example that demonstrates adaptability. Explain guidance you received rather than claiming senior authority.
Mid-level
Show independent responsibility for a defined outcome, including a staged summary migration verified against authoritative events. Name dependencies and when you sought help.
Senior
Explain trade-offs with affected colleagues, the verification plan, and revisiting explicit assumptions and migrating with evidence. Broader scope needs evidence rather than a larger job title.
Staff
Show a mechanism that changed decisions or capability across teams, including who adopted it and what remained outside your authority. Do not describe a local change as organization-wide influence.
Common mistakes
- Listing tasks without explaining why you considered defending read-time aggregation after the workload distribution changed.
- Claiming a staged summary migration verified against authoritative events without describing how you observed it.
- Claiming sole credit for decisions or work owned by collaborators.
- Treating a proposed follow-up as already completed.
Build your own answer
This worksheet stays in this page’s memory. It is not saved to your account or this device. Copy or download it before leaving or refreshing. Remove confidential details and use only experiences you can defend.
Self-review against observable evidence
This is a coaching checklist, not a company hiring score. Choose one rating per dimension.
Review each dimension to choose one concrete improvement for your next attempt.
Next exercise
Rehearse your own example, then ask a listener to identify a staged summary migration verified against authoritative events and the decision that led to it.
Prepare a follow-up on defending read-time aggregation after the workload distribution changed. Replace every fictional detail with your own facts and identify one claim that needs more evidence.