All jobs / Engineering manager / tech lead
People Management interview questions
People Management questions a Engineering manager / tech lead can be asked, from first job to senior. Open one to see the strongest answer and why it works.
What is a weekly 1:1 with a developer for?
The strongest answer: Their meeting — concerns, growth, what is in their way — with a running agenda they own; status lives on the board
Why it works: Exactly. The 1:1 belongs to the report, and status has other homes.
- The 1:1 is theirs.
- Running agenda, owned by the report.
- Status goes on the board, not here.
- Move it, never drop it.
A senior developer left sharp, dismissive comments on a junior’s pull request.
When and how do you raise it?
The strongest answer: Privately within a day or two: the specific comment, the effect on the junior, and a question about what they intended
Why it works: Exactly. Fast, private, specific, and curious about their side.
- Feedback is soon and private.
- Behaviour, impact, then their view.
- Do not queue it for the 1:1.
- Do not broadcast a hint.
A junior prefaces a question with “this might be stupid, but…”. What do you do?
The strongest answer: Thank them, answer properly, and keep asking my own basic questions in front of the team so asking is visibly normal
Why it works: Exactly. Safety is built by what you model, not by what you declare.
- Model asking, do not just permit it.
- Answer in the open.
- Slogans do not create safety.
- Never joke at the asker.
How do you recognise good work on the team?
The strongest answer: Specifically and soon — the behaviour and its effect — and I ask each person whether they prefer it public or private
Why it works: Exactly. Specific, timely, and in the form the person actually values.
- Specific and soon.
- Behaviour plus effect.
- Ask public or private.
- Do not reward late nights.
You were promoted from within and your friends now report to you. How do you handle it?
The strongest answer: I name the change openly in a 1:1 with each of them, and I hold everyone to the same expectations, including on who gets the interesting work
Why it works: Exactly. Acknowledge it, then be visibly consistent.
- Name the change out loud.
- Same expectations for all.
- Distribute interesting work fairly.
- Do not keep an inner circle.
What does a useful piece of feedback contain?
The strongest answer: The specific situation, what you observed them do, the impact it had, and an invitation to hear their view
Why it works: Exactly. Situation, behaviour, impact, then a real conversation.
- Situation, behaviour, impact.
- Invite their view.
- No sandwich.
- Never save it for the review.
One developer never speaks in meetings but their work is solid. What do you do?
The strongest answer: Ask in a 1:1 how they prefer to contribute, then create ways that fit — written input before meetings, design docs, smaller rooms
Why it works: Exactly. Contribution has many shapes; find theirs instead of forcing yours.
- Ask how they like to contribute.
- Offer written and small-room routes.
- Quiet is not a performance issue.
- Do not cold-call as a fix.
A developer has been missing expectations for two months. What is your first move?
The strongest answer: Work out why — unclear expectations, a skill gap, motivation, or something outside work — then set clear, written expectations with a short feedback loop
Why it works: Exactly. Diagnose, make expectations explicit, and give them a real chance with fast feedback.
- Diagnose before you act.
- Written expectations, short loop.
- Formal process is a later step.
- Do not manage by hoping.
An engineer asks what they need to do to be promoted. What do you tell them?
The strongest answer: Walk the ladder together, name the concrete gaps with examples, agree a plan with check-ins, and be honest that I cannot promise timing
Why it works: Exactly. Concrete gaps, a plan, and honesty about what you control.
- Use the ladder, with examples.
- Name the gaps concretely.
- Plan plus check-ins.
- Never promise a date you do not control.
Your strongest engineer resigns. What do you do?
The strongest answer: Listen properly to why, plan a clean handover, and look honestly at what the team and I should learn — a counter-offer is a considered choice, not a reflex
Why it works: Exactly. Learn, hand over well, and treat retention as a decision rather than a panic.
- Listen to the real reason.
- Plan the handover.
- Learn as a team.
- Counter-offer deliberately, if at all.
An engineer tells you they are underpaid. How do you respond?
The strongest answer: Listen, check their pay against the bands and the data I actually have, be honest about what I can and cannot do, and come back by a date
Why it works: Exactly. Take it seriously, check the facts, be honest about your power, and follow up.
- Listen and check the facts.
- Be honest about what you control.
- Follow up by a date.
- Never promise what you cannot deliver.
One engineer is consistently online late into the night. What do you do?
The strongest answer: Talk to them about sustainable pace, look at why the load falls on them, and make sure I am modelling boundaries myself
Why it works: Exactly. Treat it as a load and boundary problem, and check what you are modelling.
- Ask about the load.
- Talk about sustainable pace.
- Model boundaries yourself.
- Never make overtime the standard.
Coaching has not worked and you are moving to a formal performance process. What does doing it well look like?
The strongest answer: Written, specific expectations they could recognise as met or not, real support and check-ins, HR involved from the start, and honesty about where it can end
Why it works: Exactly. Clear, supported, documented, honest — and a genuine chance to succeed.
- Specific, written expectations.
- Support and check-ins are real.
- HR from the start.
- Never build a case in secret.
You have to let a team member go. How do you do it?
The strongest answer: Prepared and private, clear and brief about the decision, with next steps and support ready, and a team message afterwards that protects their dignity
Why it works: Exactly. Prepared, humane, clear, and dignified in front of the team.
- Prepare, and do it yourself.
- Clear, brief, humane.
- Next steps ready.
- Protect their dignity with the team.
Your strongest senior wants to grow but not into management. What do you offer?
The strongest answer: Scope beyond the team — a cross-team technical problem — sponsorship in the rooms where it is decided, and protected time to do it
Why it works: Exactly. Staff growth is scope, sponsorship, and time — not a title on a different track.
- Scope across teams.
- Sponsor them in the room.
- Protect their time.
- Management is not the only step.
You now manage a team lead for the first time. What changes?
The strongest answer: I coach them through their problems rather than solving them, agree what they should escalate, and I do not override their decisions with their team
Why it works: Exactly. Coach, agree escalation, and never undercut them in their own room.
- Coach, do not solve.
- Agree what escalates.
- Never override in their room.
- Let go of their engineers.
How do you use skip-level 1:1s?
The strongest answer: Regularly, to listen and learn what the org feels like from below, then share themes back with the lead without undermining them
Why it works: Exactly. Regular listening, themes shared back, lead kept whole.
- Regular, not reactive.
- Listen for themes.
- Share back with the lead.
- Never audit the lead through them.
How do you get ahead of attrition instead of reacting to it?
The strongest answer: Regular stay conversations: what keeps them, what would make them leave, what they want next — and then act on the growth pieces
Why it works: Exactly. Ask before they leave, and do something with the answers.
- Stay conversations, regularly.
- Know what would make them leave.
- Act on growth.
- Do not spy, ask.
How do you run performance calibration across teams?
The strongest answer: Compare evidence against the ladder across teams, look actively for bias in the pattern, and refuse a forced distribution
Why it works: Exactly. Evidence, consistency, bias checks, and no quota.
- Evidence against the ladder.
- Consistency across teams.
- Look for bias.
- No forced curve.
How do you evaluate the managers who report to you?
The strongest answer: Several signals together: their team’s health and retention, delivery outcomes, how their people grow, and how they handle the hard conversations
Why it works: Exactly. Outcomes, people growth, health, and courage — never one number.
- Multiple signals.
- Team health and growth.
- Delivery outcomes.
- Hard conversations count.
How should promotions be decided across an organisation?
The strongest answer: Against the ladder with written evidence, input from people who worked with the candidate, and calibration across teams so the same work earns the same level everywhere
Why it works: Exactly. Evidence, peer input, and cross-team consistency.
- Written evidence against the ladder.
- Input from those who worked with them.
- Calibrate across teams.
- Not tenure, not volume.
A report comes to you about harassment by a senior engineer. What do you do?
The strongest answer: Take it seriously immediately, bring HR in and follow the formal process, protect the person who reported from retaliation, and do not investigate it alone
Why it works: Exactly. Formal process, protection, and never a solo investigation.
- Immediately, seriously.
- HR and the formal process.
- Protect the reporter.
- Never trade it for the roadmap.