Tech Lead interview question · Most asked
Tell me about a time you had to push back on a deadline or scope.
Summary
Describe the request, the evidence that it wasn't achievable (throughput, risks), how you presented options rather than a flat no, and the decision that resulted.
Longer Answer
Strong answers show data and partnership: "Based on our throughput the full scope was 85% likely in 14 weeks, not 8. I offered two options: ship card payments only by the date, or full scope two months later. Product chose the reduced scope; we shipped on time and added the rest in the next quarter." Mention how you kept the relationship constructive and how the forecast was tracked afterwards.
Key Points
- Evidence, not opinion
- Options that trade scope for time
- Outcome and relationship afterwards
Deep dive: Forecasting Delivery Honestly
Explanation
What interviewers look for
Constructive negotiation grounded in data, and business awareness.
Red flags
- 'I told them it was impossible'
- Accepting an impossible deadline and burning out the team
More most-asked Tech Lead questions
- Tell me about the most complex system you designed or led.
- How much should a tech lead code?
- Your team wants to rewrite a legacy service. How do you evaluate the proposal?
- 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.
- What does a tech lead do, and how is it different from an engineering manager?
- Two senior engineers have argued about an approach for weeks. What do you do?
- How do you keep code reviews fast without lowering quality?