In this article
The role and the title
For the manager side of the same loop, read the engineering manager interview guide. The questions here sit one step earlier: you lead a team's technical work, usually without owning its people process.
What does a tech lead do?
A tech lead is an engineer who guides the approach and execution of one team and partners closely with a manager. The work is scoping complex tasks, coordinating the team toward them, unblocking people along the way, and acting as a close partner to the team's product manager (Larson, Staff archetypes, June 2020).
Why it is asked: it shows whether you see the job as multiplying the team or as being its best coder. Source: Larson, Staff archetypes.
Is a tech lead a manager?
No. The tech lead partners with a manager, sometimes with two or three in a focused area. A Tech Lead Manager is a role on the engineering manager ladder that is similar to the tech lead but includes people management responsibilities, and only some companies have it (Larson, June 2020). Say which of the two you are interviewing for and what you expect to own.
Why it is asked: interviewers check that you know where technical direction ends and people management begins. Read the full explanation: the people management round.
Is "tech lead" a job title or a role?
Both, depending on the company: some use "tech lead" as a title and others as a role that an engineer holds alongside another title (Larson, June 2020). Ask early what the title means there: who you report to, whether people management is included, and how large the team is.
Why it is asked: a strong candidate clarifies the scope of the job before answering questions about it. Source: Larson, Staff archetypes.
Is a tech lead the same as a Staff engineer?
No. The tech lead is one Staff-engineer archetype, and Larson notes it is quite common to perform the role without the impact expected of a Staff-level engineer (Larson, June 2020). Do not claim seniority from the label; describe the scope and results of the team you led.
Why it is asked: it separates a title from demonstrated impact. Source: Larson, Staff archetypes.
How many tech leads does an organization need?
One author's rule of thumb is roughly one tech lead for every eight engineers, which makes the role far more common than other archetypes (Larson, June 2020). It is a rule of thumb, not a measured statistic. For an organization of 40 engineers it gives about 5 leads.1
Why it is asked: it tests whether you can reason about team structure with a stated assumption. Source: Larson, Staff archetypes.
How much should a tech lead still code?
Less over time. Larson says leads shrink their coding both to grow teammates and because the team's impact grows as the lead's coding blocks shrink (Larson, June 2020). No source gives a fixed split. A good answer takes work off the critical path and keeps enough hands-on contact to understand the architecture.
Why it is asked: it checks that you will delegate instead of hoarding the interesting work. Source: Larson, Staff archetypes.
Technical decisions and delivery
Fournier's Tech Lead 101 section names four parts: understanding the architecture, being a team player, leading technical decisions and communicating. The chapter also treats staying on the technical track or becoming a manager as a decision point (Fournier, chapter 3 headings, 2017). The answers below are advice built around these headings.
Text description of the diagram
- Fournier's Tech Lead 101 section names four parts: understanding the architecture, being a team player, leading technical decisions and communicating.
- The chapter also treats staying on the technical track or becoming a manager as a decision point.
How do you lead technical decisions?
State the problem, list the options with their costs, say who decides, decide, and write the decision and its reasons down so it can be revisited. A strong answer includes a decision you reversed when new facts arrived, and shows that you took the team's objections seriously before committing.
Why it is asked: it separates a lead who decides with the team from one who decides alone or avoids deciding. Source: Fournier, The Manager's Path, chapter 3.
How do you learn the architecture of a system you have just joined?
Read the existing design notes, trace one real request end to end, draw what you found, then check the drawing with the people who own each part. Note the fragile spots and the undocumented ones. Ask what changed recently and why, because the history explains most oddities.
Why it is asked: leads need an accurate picture of the system before they steer it. Read the full explanation: inheriting a team: the first 90 days.
How do you scope a complex task for the team?
Split it into pieces that can be built, reviewed and shipped separately, name the unknowns, and take the riskiest piece first so surprises arrive early. Agree on what "done" means for each piece before work starts. Scoping complex tasks is named in Larson's description of the role (Larson, June 2020).
Why it is asked: it shows whether you turn vague goals into work a team can pick up. Source: Larson, Staff archetypes.
What do you do when the project gets delayed?
Find out why before you react, size the slip, and tell your product manager and manager early with options: cut scope, move the date, or add help. Then update the plan so the new date has a reason behind it. A strong answer owns the estimate error instead of blaming the team.
Why it is asked: delays test honesty and calm under pressure. Read the full explanation: what to do when the project gets delayed.
How do you work with the product manager?
Treat the product manager as a close partner: Larson calls the tech lead the first person called when the roadmap needs to be shuffled (Larson, June 2020). Bring the cost and risk of each option, not just a yes or no, and agree on one story to tell the team.
Why it is asked: lead and product manager must share priorities, or the team gets mixed signals. Source: Larson, Staff archetypes.
How do you explain a technical decision to people who are not engineers?
Start with the outcome they care about, then the cost, the risk and the date, and leave the mechanism for questions. One accurate everyday comparison helps if you also say where it stops being true. Check understanding by asking what they would tell their own team.
Why it is asked: communicating is one of the four parts of the job in Fournier's chapter. Read the full explanation: getting people and teams to communicate better.
How do you balance technical debt against feature work?
Make the debt visible and priced: list the items, say what each costs the team in slowed work or incidents, and rank them. Agree with the product manager on a steady share of each cycle for the highest-cost items, and attach small fixes to nearby feature work. Decline cleanup that has no named benefit.
Why it is asked: it shows whether you trade long-term cost against delivery with evidence rather than taste.
How do you run code review and set engineering standards?
Write a short set of standards with the team: what a review must check, how quickly reviews happen, and what automated tools handle instead of people. Review for correctness, clarity and risk, give reasons, and separate must-fix comments from preferences. Hold your own code to the same standard, so the rule visibly applies to the lead too.
Why it is asked: it shows whether you raise the quality bar without becoming the bottleneck.
How do you lead the team through a production incident and the review after it?
During the incident, name one person to lead and one to communicate, restore service first and investigate later, and keep a timeline. Afterwards run a review that asks what allowed the failure, not who caused it, and finish with a few follow-up actions that each have an owner and a date. Report the outcome plainly.
Why it is asked: it tests calm under pressure, ownership and whether the team learns from failure.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →People and team
How do you unblock your team?
Ask what is slowing each person, in a stand-up or one-on-one, then remove the block yourself or escalate it with a clear request. Protect focus time by absorbing interruptions. Unblocking people is part of the role as Larson describes it (Larson, June 2020).
Why it is asked: it shows whether you make the team faster rather than only your own work. Source: Larson, Staff archetypes.
How do you handle a low performer on your team?
Give specific, early feedback about behavior and its effect, agree on what better looks like, and check in. Because a tech lead partners with a manager, share what you see with the manager, who often owns the formal process. Avoid surprising the person later.
Why it is asked: it tests candor and the line between guiding and managing. Read the full explanation: how to handle a low performer.
Two of your engineers can barely stand each other. What do you do?
Talk to each person separately, focus on work behavior instead of personality, then bring them together around a shared goal with clear working agreements. Do not take sides on facts you have not checked. If the conflict persists, involve the manager.
Why it is asked: leads often meet conflict first. Read the full explanation: two engineers who can barely stand each other.
How do you grow the engineers on your team?
Hand out work slightly beyond what each person has done, explain the reasoning behind your own choices, and give feedback soon after the work. Larson says leads delegate coding to grow their teammates (Larson, June 2020). Name a person who took over something you used to do.
Why it is asked: it shows whether you build others up or become a bottleneck. Read the full explanation: growing engineers.
How do you give hard feedback to a teammate?
Say it privately and promptly, describe what happened and its effect, ask for their view, and agree on one next step. Praise good work just as specifically, so feedback is not only bad news. A regular one-on-one makes hard messages easier to deliver.
Why it is asked: unsaid problems grow, and interviewers want evidence you say them. Read the full explanation: one-on-ones and hard feedback.
How do you measure the health of your team?
Watch several signals together rather than one number: whether work ships steadily, whether people raise problems early, whether knowledge is spread across more than one person, and whether people stay engaged. Ask the team directly and compare what they say with what you see.
Why it is asked: it shows whether you notice trouble before it becomes an exit. Read the full explanation: measuring team health.
How do you take part in hiring?
Agree on what the role needs before interviews start, ask each candidate comparable questions, write notes from evidence, and decide with the group in a debrief. Keep your own bias in check by separating what the candidate said from how you felt.
Why it is asked: tech leads often sit on the loop, and hiring shapes the team. Read the full explanation: hiring as an engineering manager.
What do you do when you disagree with your manager, architect or product manager on a technical call?
State your view privately first, with the evidence and the cost of each option, and ask what constraint they see that you do not. Keep the technical question apart from the relationship, agree on who makes the decision, and commit once it is made. If you still disagree on a high-risk point, write down your concern and escalate once, calmly.
Why it is asked: it shows whether you can hold a position without turning it into a fight.
Stack-specific tech lead interviews
People also search for Java, .NET (dot net), C#, Angular, React, iOS, Python, PHP (a server-side scripting language, short for PHP: Hypertext Preprocessor) and Salesforce tech lead questions. No public source covers them, so the entries below are advice: treat them as a technical depth check layered on the same lead competencies. Python, PHP and Salesforce rounds follow the same pattern.
What are Java tech lead interview questions like?
Expect depth on concurrency and thread safety in a service you own: shared state, locking choices and how you found a race. Expect questions on how you choose and upgrade Java and framework versions across a team, and how you set code-review standards for a Java Virtual Machine (JVM) codebase. Answer with one real service, the alternative you rejected and what the team learned.
Why it is asked: the interviewer wants to know whether your technical depth is current and your judgment sound.
What are .NET (dot net) tech lead interview questions like?
Prepare the same themes on .NET: thread safety and asynchronous code in a service you own, how you choose and upgrade framework versions across a team, and the code-review standards you set. Pick a real service, explain the trade-offs you weighed, and say how you taught the team the result.
Why it is asked: it checks depth on the platform and whether you steer upgrades without breaking delivery.
What are Angular and React tech lead interview questions like?
Expect decisions about state management and how a front end is split into modules, and how you would migrate a large front end without stopping feature work. Describe one real choice, the cost of changing course later and how you kept the team's code consistent. Frame the answer around a team outcome, not a feature list.
Why it is asked: a framework is the setting; the lead skill being checked is how you steer a team inside it.
What are iOS tech lead interview questions like?
Expect questions on app architecture choice, such as how you structure screens, data and navigation so several engineers work without colliding, and on release and rollback discipline: staged rollouts, feature flags and what you do when a bad build is live. A shipped build is hard to pull back quickly, so explain one release you owned.
Why it is asked: it shows whether you can make structure decisions and manage release risk on a mobile team.
Follow-up questions
What are the common tech lead interview questions and answers?
They fall into the four groups above: what the role is, how you lead technical decisions and delivery, how you work with people, and how deep your stack knowledge is. Practice the answers aloud with a real example from your own work for each.
What should I ask the interviewer about a tech lead role?
Ask whether "tech lead" is a title or a role there, who the partnering manager is, how large the team is, whether people management is included, and how much coding time the role expects (Larson, June 2020).
What if one of the two is your tech lead?
This is advice. You are the manager and one of the two engineers in conflict is your tech lead, so the case is unequal: the lead's behavior sets team norms, and the lead can shape the other engineer's work. Hold the lead to a higher standard in private coaching and protect the other engineer from any spill-over into reviews or assignments; if the lead cannot separate the conflict from technical decisions, move some of the lead's decision rights for a time. The general approach is in two engineers who can barely stand each other.
Do tech lead interviews include coding?
Some do, but the format varies by company and no source sets a standard. As advice, a code-level round for a lead typically probes reading and critiquing code and design at module level, so practice explaining what a change risks, how you would review it and how you would split it into modules. Ask the recruiter what each round covers.
- A tech lead guides one team's approach and execution and partners with a manager; a Tech Lead Manager is a different role.
- "Tech lead" is a title at some companies and a role at others, so ask which applies.
- The label does not make you Staff-level; describe your scope and impact.
- Answer with decisions, trade-offs and unblocking, not with how much you personally code.
- Stack questions are a depth check on top of the same lead skills.
Sources
- Staff archetypes: the Tech Lead (Will Larson, StaffEng) — StaffEng (Will Larson), 21 Jun 2020
- The Manager's Path, chapter 3 Tech Lead (Camille Fournier) — O'Reilly Media, 1 Mar 2017
- StaffEng: Guides to the Staff-plus engineer path (Will Larson) — StaffEng (Will Larson), 21 Jun 2020
