All jobs / Engineering manager / tech lead
Leadership Skills interview questions
Leadership Skills 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.
The team asks you a technical question you cannot answer. What do you do?
The strongest answer: Say I do not know, pair with whoever knows or find out together, and come back with the answer
Why it works: Exactly. Admitting the gap and closing it in the open is what a lead models.
- Say you do not know.
- Find out together.
- Come back with the answer.
- Never bluff.
An engineer asks why the team is building this at all. What do you do?
The strongest answer: Give them the real reason — who asked for it, what problem it solves, how we will know it worked — and if I do not have that, say so and go and get it
Why it works: Exactly — context is part of the work, and “I do not know, I will find out” keeps it honest.
- Context is part of the work.
- Name who asked, and why.
- Say how success is measured.
- Admit when you do not know.
You have just become the lead of an existing team. What are your first weeks about?
The strongest answer: Listening: 1:1s with everyone, learning how the system and the people actually work, and one small visible fix before any bigger change
Why it works: Exactly. Learn first, earn trust with one small win, then change with the team.
- Listen before you change.
- 1:1 with everyone.
- One small visible win.
- No rewrites in month one.
Your team is fully remote across three time zones. What do you set up?
The strongest answer: Async-first written communication, a few agreed overlap hours, decisions documented where everyone can read them, and deliberate social time
Why it works: Exactly. Writing, overlap, documented decisions, and intentional connection.
- Async and written first.
- Agree overlap hours.
- Document decisions.
- Trust, not monitoring.
A designer and a developer are at odds over whether a design is feasible in time. What do you do?
The strongest answer: Get them in the same room early with the constraint on the table, prototype the contested part, and decide by the user outcome we are trying to reach
Why it works: Exactly. Bring them together, make it concrete, and decide on outcomes rather than on who is louder.
- Same room, early.
- Prototype the contested part.
- Decide by user outcome.
- Do not exclude a discipline.
Two engineers keep clashing in reviews and meetings. What do you do?
The strongest answer: Talk to each alone to understand it, then bring them together on the concrete issue and agree how they will work together from here
Why it works: Exactly. Understand both sides, then work the specific issue and the norms, together.
- Each alone, then together.
- Work the concrete issue.
- Agree working norms.
- Do not pick a side in public.
Your own manager keeps changing priorities on your teams. What do you do?
The strongest answer: Raise it privately with specific examples and the impact on delivery, and propose a way of handling changes that works for both of us
Why it works: Exactly. Specific, private, impact-focused, with a proposal.
- Private and specific.
- Lead with impact.
- Bring a proposal.
- Never vent to your team.
You are reorganising three teams into four. How do you communicate it?
The strongest answer: Explain why, be specific about what changes for each person, hold 1:1s within days, and be honest about what is not yet decided
Why it works: Exactly. Why, what changes for me, quickly, and honest about the gaps.
- Explain the why.
- What changes for each person.
- 1:1s within days.
- Honest about the unknowns.
Your team missed a date you personally defended to the leadership team. The monthly review is tomorrow.
What do you say in the room?
The strongest answer: That we missed it, what we know now that we did not know then, the new range, and what we have changed so the next forecast is better — as my miss, not the team’s
Why it works: Exactly — own it, say what you learned, give a new range, name what changed. That is what buys trust in the next forecast.
- Own it before you explain it.
- Say what you know now.
- Give a new range.
- Name what you changed.
Remote members of your hybrid team say they feel second-class. What do you change?
The strongest answer: Run meetings remote-first whenever anyone is remote, write decisions down where everyone can see them, and check that growth and promotions are not tracking office presence
Why it works: Exactly. Remote-first meetings, written decisions, and an honest look at who gets promoted.
- Remote-first when anyone is remote.
- Decisions in writing.
- Audit who gets promoted.
- Do not reward proximity.
You have been asked to reduce your organisation by a fifth of its roles.
How do you run it?
The strongest answer: Decide by role and business need with criteria I can explain, tell people quickly and directly with real support, and then rebuild trust honestly with the people who stay
Why it works: Exactly. Defensible criteria, direct and supported delivery, and honest work with the survivors.
- Explainable criteria.
- Direct, quick, supported.
- Never disguise the reason.
- Rebuild trust with the stayers.
How do you turn company strategy into an engineering direction?
The strongest answer: Translate it into a few engineering bets, say explicitly what we will not do, and repeat it until teams can connect their work to it
Why it works: Exactly. Few bets, explicit no-gos, repeated until it sticks.
- Few engineering bets.
- Say what you will not do.
- Repeat it constantly.
- Teams should see the link.
Leadership has cancelled the product your team has been building for two quarters. You hear on Thursday; it is public on Monday.
How do you handle it with the team?
The strongest answer: Tell them myself, early and face to face, with the real reason; let them be angry; say what happens to them and to the work; then decide together what is worth keeping
Why it works: Right — first-hand, honest, and followed by what happens to them. People remember how the news arrived for years.
- Tell them yourself, first.
- Give the real reason.
- Let them react.
- Then say what happens next.
You are asked to set the remote and hybrid policy for engineering. How do you approach it?
The strongest answer: Start from what the work needs and what we have observed, make it equitable and explain the reasons, and decide it as a policy about work rather than about attendance
Why it works: Exactly. Work-based, reasoned, equitable, and honest.
- Start from the work.
- Explain the reasons.
- Equitable across teams.
- Never a stealth layoff.
How much process should a decision get, and how do you decide that?
The strongest answer: By how hard it is to undo: reversible calls go to whoever is closest, quickly, and get reviewed afterwards; the ones you cannot walk back get the room, the written options and a named owner
Why it works: Exactly — reversibility sets the cost of being wrong, and the cost of being wrong should set the process.
- Match process to reversibility.
- Reversible: decide fast, review later.
- Irreversible: options, room, owner.
- Say which kind it is.
How do you actually shape engineering culture?
The strongest answer: Culture is what gets rewarded and what gets tolerated: I model it, make the norms explicit, and hold my leaders to them in promotions and hard cases
Why it works: Exactly. Rewards, tolerances, and what leaders do when it is inconvenient.
- Rewarded and tolerated.
- Model it yourself.
- Hold leaders to it in hard cases.
- Fit is not similarity.
How do you keep growing as a senior engineering leader?
The strongest answer: A network of peers I can be honest with, a coach or mentor, regular feedback from my own reports, and deliberately delegating things I am good at
Why it works: Exactly. Peers, coaching, upward feedback, and letting go of what you have mastered.
- Honest peers.
- Coach or mentor.
- Feedback from your reports.
- Delegate what you have mastered.