Interview Q&A · 38 questions · 17 answered publicly
Team Lead Interview Questions
Ordered by how often they're asked. Sign in free to see every answer, rate your confidence and run timed mock interviews.
-
Most asked What is the main job of a team lead?
Summary
To make the team effective: clear goals and priorities, a way of working that lets people focus and finish, feedback and growth for each person, and a healthy team environment. The team's results are the lead's results.
Longer Answer
A team lead shifts from personal output to team output. In practice that means: setting and protecting priorities with product; running planning and delivery so work flows; regular 1:1s and feedback; handling conflict and underperformance early; representing the team up and across. Depending on the company, a team lead may also be the tech lead, or may partner with an engineering manager who owns formal people processes.
Key Points
- Team output is the lead's output
- Priorities, flow, people and environment
- Role boundaries vary — clarify them
Deep dive: From Engineer to Team Lead
-
Most asked How do you run 1:1s with your team members?
Summary
Regularly (weekly or bi-weekly), 30 minutes, with a shared agenda the team member owns. The time is for their topics, blockers, feedback in both directions, growth and wellbeing — not status updates. I take notes and follow up on actions.
Longer Answer
I keep a shared document per person with recurring prompts: what's on your mind, what's in your way, one piece of feedback each way, progress on your growth goal, and monthly a quick 'how are you really doing' check. I reschedule rather than cancel. When someone says there's nothing to discuss, I use the time for career or feedback. Following through on actions is what makes 1:1s trusted.
Key Points
- Regular, report-owned agenda
- Blockers, feedback, growth, wellbeing — not status
- Notes and follow-through
Deep dive: Effective 1:1s
-
Most asked How do you give difficult feedback?
Summary
Early, privately and specifically: describe the situation, the observable behaviour and its impact (SBI), then ask for their perspective and agree a next step. Then notice and acknowledge improvement.
Longer Answer
Example: "In Tuesday's design review, you interrupted Ana three times while she presented; she stopped and we missed her concern until later. What was going on for you?" Avoid judgements about character ("you're dismissive"). Balance it with frequent, specific positive feedback so corrective feedback isn't the only kind people hear. Radical Candor frames the goal as caring personally and challenging directly at the same time.
Key Points
- Timely, private, specific (SBI)
- Ask for their view; agree a next step
- Frequent positive feedback too
Deep dive: Feedback That Lands
-
Most asked How do you measure your team's performance?
Summary
With team-level flow and outcome measures — throughput, cycle time percentiles, work in progress, work item age, plus quality and the outcomes our work is meant to move — never individual activity metrics.
Longer Answer
Story points or tickets per person get gamed and discourage reviewing and pairing. Flow metrics describe the system the lead can change, and percentiles (50th and 85th) set realistic expectations. Combine them with quality signals (incidents, escaped defects) and outcomes (conversion, latency, support load). Review them with the team and use outliers as retro topics.
Key Points
- Team flow metrics, not individual activity
- Percentiles and outliers
- Combine with quality and outcomes
Deep dive: Flow Metrics: Cycle Time and Throughput
-
Most asked How do you keep your team motivated?
Summary
By understanding each person — what energises and drains them, what they want to grow in — and shaping their work around it, connecting work to impact, recognising specifically, and removing friction.
Longer Answer
Motivation is individual. I ask directly in 1:1s, then use what I learn: stretch projects, ownership of an area, chances to present, less of the draining work. I share customer feedback and results. Gallup reports managers account for up to 70% of the variance in engagement — mostly through these everyday things. Pay matters when it's below market, but it rarely fixes boredom or lack of growth.
Key Points
- Individual: ask what energises and drains
- Growth, impact, recognition, less friction
- Pay is necessary but rarely sufficient
Deep dive: Motivation and Engagement
-
Most asked What is psychological safety, and how do you build it?
Summary
The belief that you can take interpersonal risks — admit mistakes, ask questions, challenge ideas — without being punished or embarrassed. You build it mostly through how you react: modelling fallibility, thanking people for bad news, inviting input structurally and addressing behaviour that undermines it.
Longer Answer
Google's Project Aristotle studied 180 teams and found how a team works together matters more than who is on it, with psychological safety the most important of five dynamics (then dependability, structure and clarity, meaning and impact). Practical moves: ask juniors first, silent writing before discussion, blameless postmortems, a quarterly pulse question like "if I make a mistake on this team, it is not held against me". Safety doesn't mean comfort — safe teams disagree more openly.
Key Points
- Taking interpersonal risks without fear
- Leaders' reactions teach safety
- Safety plus high standards
Deep dive: Psychological Safety
-
Most asked Two people on your team are in ongoing conflict. How do you handle it?
Summary
Act early: talk to each separately using specific observations, find the underlying cause (often unclear ownership, standards or working styles), then bring them together to agree concrete changes, write them down and follow up. Escalate to the manager if behaviour doesn't change.
Longer Answer
Focus on interests rather than positions: what does each person need to do good work? Common fixes are clear area ownership, a fast way to settle disagreements (e.g. the owner decides after one round of comments, or a 15-minute call instead of a long thread), and shared standards. Don't pick a side based on who complained first. Conflict about ideas is healthy; hostility isn't.
Key Points
- Separate conversations first
- Find the cause; interests over positions
- Agree, document, follow up; escalate if needed
Deep dive: Resolving Conflict Between Team Members
-
Most asked How do you handle an underperforming team member?
Summary
Raise it early and privately with specific examples, understand the cause, agree written expectations with support and a timeline, check in weekly, and involve the engineering manager early — formal processes are theirs and follow company policy.
Longer Answer
Common causes: unclear expectations, a skills gap, the wrong kind of work, personal circumstances or low motivation — each needs a different response. Covering for someone is unfair to them and to the team. Most cases improve with clarity and support; if not, the manager moves to a documented process. Recognise progress specifically along the way.
Key Points
- Early, private, specific
- Diagnose the cause; support accordingly
- Written expectations; involve the manager
Deep dive: Spotting and Coaching Underperformance Early
-
Most asked Stakeholders keep adding 'small' requests to your team's work. How do you handle it?
Summary
Keep one visible, prioritised list of commitments and answer every request with a trade-off — what gets delayed, or a smaller version — and let the priority owner decide. Protect a small buffer for genuinely urgent work.
Longer Answer
Individually small requests add up and silently push out the main goals. Saying yes reflexively leads to overtime and missed goals; saying no reflexively damages relationships. Offer alternatives: a manual workaround now and the real version later, or a reduced scope. Agree a size threshold below which engineers can simply help.
Key Points
- One visible, prioritised list
- Trade-offs and alternatives, not yes/no
- Priority owner decides; small buffer
Deep dive: Saying No and Negotiating Scope
-
Most asked Tell me about a time you helped someone on your team grow.
Summary
Describe the person and their goal, how you found the right opportunity, how you supported them (expectations, checkpoints, feedback) without taking over, and the result for them and the team.
Longer Answer
Strong answers are concrete: "Lee wanted to get better at system design. I gave him ownership of the payment-provider migration design, reviewed it with him in two rounds, and let him present it in the design review. Six months later he led the next migration on his own and was promoted." Show deliberate planning and specific feedback.
Key Points
- Specific goal and opportunity
- Support without taking over
- Measurable growth
Deep dive: Motivation and Engagement
-
Most asked Tell me about a time you gave feedback that was hard to deliver.
Summary
Choose a real, significant case; explain why it was hard, how you prepared, how you delivered it (specific, private, timely), how the person reacted, and what changed.
Longer Answer
Use SBI language in the story, show that you listened to their perspective, and include the follow-up — how you noticed improvement and acknowledged it, or how you handled it if it didn't improve. Reflect on what you'd do differently, e.g. raising it earlier.
Key Points
- Real stakes
- Specific, private, timely delivery
- Follow-up and outcome
Deep dive: Feedback That Lands
-
Most asked Tell me about a time your team missed a deadline. What did you do?
Summary
Describe the situation honestly, how and when you communicated the slip, how you re-planned with options, how you protected the team, and what you changed in planning afterwards.
Longer Answer
Good answers show early communication with a forecast and options, a blameless retro focused on causes (too much WIP, unplanned work, dependencies), and a concrete change — e.g. planning to real capacity or introducing a support rotation — with evidence it helped next time.
Key Points
- Early, honest communication
- Options and re-planning
- Systemic lesson applied
Deep dive: Planning That Holds
-
Most asked A high performer on your team is rude to colleagues. What do you do?
Summary
Address it quickly and privately with specific examples and their impact, make clear that how we work together is part of performance, agree a change, follow up, and involve the manager if it continues — regardless of their output.
Longer Answer
Tolerating it damages psychological safety for everyone and signals that results excuse behaviour. Use SBI ("in yesterday's review you called Ana's approach 'amateur'; she stopped contributing"), ask about their perspective, and agree concrete expectations. Recognise their strengths genuinely so the conversation is balanced — but don't trade behaviour for output.
Key Points
- Quick, private, specific
- Behaviour is part of performance
- Follow up; escalate if needed
Deep dive: Psychological Safety
-
Most asked What would you do in your first 30 days as a new team lead?
Summary
Listen and learn: 1:1s with each team member, the manager, product and key partners; review the team's metrics, incidents and backlog; observe the team's rituals; then share back what I heard and agree two or three priorities with my manager.
Longer Answer
I'd keep existing commitments moving, avoid big changes, and look for one quick, visible improvement the team wants. I'd also set up regular 1:1s and agree how I'll work with the tech lead and product manager. At day 30 I'd ask my manager and team for feedback on how I'm doing.
Key Points
- Structured listening
- Share back; agree priorities
- One quick win; feedback at day 30
Deep dive: From Engineer to Team Lead
-
Most asked Your team regularly finishes only about half of what it plans in a sprint. What do you do?
Summary
Plan from real capacity, not nominal capacity: subtract leave, support duty, meetings, reviews and an unplanned-work buffer based on data, plan to about 80% of what's left around a single sprint goal, and track planned vs done.
Longer Answer
Teams that plan 'people × days' typically have only around half of that available for planned work. Make support visible (the person on support takes no planned items), calculate capacity from the last few sprints, and commit to less. Reliable delivery rebuilds trust with product faster than ambitious plans that slip.
Key Points
- Real capacity from data
- Plan ~80%, one sprint goal
- Track planned vs done
Deep dive: Planning That Holds
-
Most asked Your team has many items in progress and everything takes weeks. How do you improve it?
Summary
Limit work in progress. By Little's law, average cycle time equals work in progress divided by throughput, so at the same throughput fewer items in progress means each finishes sooner. Set a team WIP limit, walk the board from the right in standup, and help finish before starting new work.
Longer Answer
Example: a team finishing 5 items a week with 14 in progress has an average cycle time of about 2.8 weeks; with 5 in progress it's about a week. Lower WIP also reduces context switching and review waits, which usually raises throughput too. Start the limit around the number of engineers and lower it gradually.
Key Points
- Little's law: WIP = throughput × cycle time
- Team WIP limit; stop starting, start finishing
- Swarm on the oldest items
Deep dive: Limiting Work in Progress
-
Most asked Your team is constantly interrupted by questions from other teams. What do you do?
Summary
Concentrate interruptions on one person through a weekly support rotation, with a single front door (form or channel), clear response times and written handovers — and turn repeated requests into documentation or self-service.
Longer Answer
When everyone answers, everyone works in fragments and the most helpful people burn out. The person on rotation takes no planned work. Track the load: if it's consistently above about 70% of one person's week, add capacity or reduce demand. Rotate fairly, including the lead.
Key Points
- One person on rotation, no planned work
- Single front door and service levels
- Measure load; automate repeats
Deep dive: Handling Interruptions and Support Rotations
- What was the hardest part of moving from engineer to team lead, and how did you handle it?
- How do you set up working agreements for a team?
- How do you make retrospectives useful?
- How do you onboard a new engineer to your team?
- How do you work with your own manager?
- How do you lead a team spread across locations and time zones?
- How do you work with product managers and designers?
- Tell me about a conflict in your team that you resolved.
- Tell me about a process change you introduced that made your team more effective.
- Tell me about a time someone on your team was struggling personally. How did you handle it?
- Tell me about a time you had to say no to a stakeholder.
- A team member asks for a promotion you don't think they're ready for. How do you respond?
- Your team is burning out after a long crunch. What do you do?
- You inherit a team with low trust and frequent complaints. Where do you start?
- Product asks you to commit to a date for a feature your team hasn't scoped yet. What do you say?
- How do you balance your own technical work with leading the team?
- How do you handle a team member who disagrees with a decision you made?
- What makes a team high-performing, in your view?
- A team member wants to work fully remote while the rest of the team is in the office. How do you make it work?
- How do you decide what to delegate as a team lead?
- How do you recognise good work on your team?