Tech Lead interview question · Most asked
Two senior engineers have argued about an approach for weeks. What do you do?
Summary
Check whether it's a reversible decision; make sure both positions are written down with their trade-offs; set a decision date; decide (or have the owner decide) and explain why; record the minority concern as a revisit trigger; and ask everyone to disagree and commit.
Longer Answer
Often the debate is about preferences, not risks — reframe it around the problems each option solves and what evidence would change the decision. If a small experiment can settle it within days, run it. Then close: "I'm choosing B for these reasons; Tom's concern about X is our revisit trigger." Follow up privately with the person who disagreed so they feel heard. Long stalemates cost more than most wrong two-way-door decisions.
Key Points
- Write both options and trade-offs
- Decide by a date, explain the reasoning
- Record the concern as a revisit trigger; disagree and commit
Deep dive: Decision Speed: One-Way and Two-Way Doors
Explanation
What interviewers look for
Ability to end stalemates respectfully and keep both engineers engaged.
Red flags
- Letting it run until someone gives up
- Deciding by seniority or volume
More most-asked Tech Lead questions
- Tell me about the most complex system you designed or led.
- How much should a tech lead code?
- You join as tech lead of an existing team. What do you do in the first 90 days?
- Tell me about a time you made a technical decision that turned out to be wrong.
- Tell me about a time you had to push back on a deadline or scope.
- What does a tech lead do, and how is it different from an engineering manager?
- How do you keep code reviews fast without lowering quality?
- How do you manage technical debt on a team that is always under delivery pressure?