Practice a Disagreement With a More Senior Engineer
Practice discussing disagreement with a senior engineer using a concrete technical concern, relevant evidence and respect for decision authority.
TL;DR
- In this fictional senior engineer disagreement interview, a more experienced colleague recommends a design that you think will make a required recovery path difficult.
- Use the appropriate escalation path when necessary, with facts and context.
- Check whether you listened before challenging, made a specific concern inspectable and understood who could decide.
The practice prompt
In this fictional senior engineer disagreement interview, a more experienced colleague recommends a design that you think will make a required recovery path difficult. You have a specific concern but have not yet tested it.
The interviewer asks what you do. Avoid framing the answer as either unquestioning agreement or a contest to prove the senior person wrong.
Begin by checking your understanding of the proposed design and the constraint it is intended to solve. Your concern may be valid, or you may be missing important context.
Related reading: How to Prepare for a Senior Software Engineer Interview.
State the concern as a testable consequence
Replace “this design is bad” with a specific question about behavior. For example, ask how the workflow would recover after an interruption at a defined point.
Describe the assumption behind your concern and invite correction. This keeps the discussion focused on the system rather than the colleague's status or your confidence.
| Discussion step | Useful content |
|---|---|
| Restate | The objective and proposed approach |
| Concern | The specific failure or constraint you see |
| Evidence | Existing facts and what remains untested |
| Test | A bounded way to resolve the disagreement |
| Decision | The owner and accepted tradeoff |
The scenario does not require you to invent a benchmark. Propose the evidence you would gather.
Choose a proportionate test
Suggest a small example, design walkthrough or controlled experiment that addresses the disputed point. The test should be relevant to the decision and feasible within the available time.
If the concern is already resolved by an existing mechanism, acknowledge it. If the test supports your concern, explain the consequence and alternatives without treating the result as a personal victory.
Our system design frameworks guide can help you articulate requirements and tradeoffs during this rehearsal.
Respect authority without hiding material risk
Identify who is responsible for the final design decision. Once the relevant evidence is available, the owner may accept a tradeoff you would not personally choose.
Distinguish that situation from a request that crosses a clear organizational boundary or leaves a serious unresolved issue outside the owner's authority. Use the appropriate escalation path when necessary, with facts and context.
Do not make every technical preference an escalation. Explain why the consequence matters and what decision remains unresolved.
Practice the follow-up conversation
Have a partner say, “The senior engineer still disagrees.” Respond by checking whether the disagreement concerns facts, priorities or risk tolerance. Those differences require different next steps.
If it is factual, identify the evidence that could settle it. If it is a priority choice, make the tradeoff explicit for the decision owner. If the scenario involves a boundary, explain the responsible escalation.
Then reverse the result: the senior engineer demonstrates that your concern was based on a misunderstanding. Practice acknowledging that directly and incorporating the new information.
Debrief the answer
Check whether you listened before challenging, made a specific concern inspectable and understood who could decide. Avoid claiming that respect means silence or that confidence requires confrontation.
For a real behavioral answer, choose an actual disagreement and describe your role accurately. The fictional exercise should help structure your reasoning, not supply a fabricated story.
A strong response shows that you can challenge an idea constructively, update your view and support a clear decision while keeping consequential concerns visible.