Engineering manager interview questions in English

Engineering manager interviews in English are mostly behavioural: performance problems, hiring, conflict, delivery and strategy, plus usually a system design round. English matters more here than in any IC role, because the job is communication. Prepare six to eight management stories with clear outcomes, practise giving difficult feedback out loud, and learn softening phrases that sound direct but kind.

What a engineering manager interview looks like

1. Recruiter screen
Team size, scope, management style, why management.
English focus: Say your scope precisely: 'I manage eight engineers across two teams, including one tech lead.'
2. People management
Underperformance, feedback, growing engineers, conflict, retention.
English focus: Show the conversation itself: what you actually said, in direct speech.
3. Delivery and execution
Missed deadlines, prioritisation, technical debt, working with product.
English focus: Trade-off language: what you said yes to, and what you said no to.
4. System design or technical
Design a system or review architecture decisions at a higher level.
English focus: Show judgement and how you'd involve the team, not just the design.
5. Leadership or bar-raiser
Strategy, culture, hiring bar, handling ambiguity.
English focus: Concise answers with a principle and an example.

10 engineering manager interview questions, with spoken answers

Each answer is written to be said out loud: short sentences, the main point first, and one concrete detail. Change the details to your own experience before you practise.

1. Tell me about a time you managed an underperforming engineer.

People management

What they listen for: Early, clear, kind feedback, support, and a decision either way.

“One engineer was missing sprint commitments for about two months. In our one-to-one I said directly: 'Your last four tickets were late, and it's affecting the team. I want to understand what's going on.' It turned out he was stuck on an unfamiliar codebase. We paired him with a senior for a month and agreed clear goals. He got back on track, and we documented it in his review.”

2. How do you give difficult feedback?

People management

What they listen for: Specific, timely, behaviour-focused feedback and a two-way conversation.

“Soon, in private, and specific. I describe the situation, the behaviour and the impact: 'In yesterday's design review, you interrupted Ana three times, and she stopped contributing.' Then I ask for their view, because there's often context I don't have. And we agree what happens next.”

3. Your team is going to miss an important deadline. What do you do?

Delivery and execution

What they listen for: Early escalation with options, not heroics.

“I'd tell stakeholders as soon as I know, not at the deadline. And I'd come with options: reduce scope and keep the date, keep scope and move the date, or add people if the work really allows it. Then we decide together. Asking the team to work weekends isn't a plan.”

4. How do you balance technical debt with feature work?

Delivery and execution

What they listen for: A business case for debt and a sustainable mechanism.

“I make debt visible in business terms: 'This module causes a third of our incidents' or 'it slows every payments change by days.' Then we agree a standing share of capacity, around 20% for my team, plus bigger items prioritised with product like any other work.”

5. How do you hire?

Leadership or bar-raiser

What they listen for: A structured, fair process and a high bar.

“I start by agreeing with the team what the role really needs. Then a structured process: the same questions and a scoring rubric for every candidate, so we compare fairly. I'd rather leave a role open than hire someone below the bar, because a wrong hire costs the team much more than an empty seat.”

6. Tell me about a conflict between two engineers on your team.

People management

What they listen for: Hearing both sides and focusing on the work, not the personalities.

“Two senior engineers disagreed about rewriting a service, and code reviews were becoming tense. I spoke to each separately first, then together, and moved the discussion to written trade-offs: cost, risk and timeline. We agreed on an incremental migration. The key was making it a decision about the system, not about who was right.”

7. How do you help engineers grow?

People management

What they listen for: Individual goals, stretch work and evidence of promotions or growth.

“In one-to-ones, I ask where they want to be in a year, and we find work that gets them there, like leading a design for someone aiming at senior. I give feedback continuously, not only in reviews. In the last year, two people on my team were promoted.”

8. How do you work with product managers?

Delivery and execution

What they listen for: Partnership with healthy tension.

“As a partnership: product owns what and why, engineering owns how and how long, and we agree priorities together. We meet weekly. When we disagree, we usually go back to the goal and the data. I'd rather we argue privately and present one plan to the team.”

9. Why do you want to be a manager?

Recruiter screen

What they listen for: Motivation from people and outcomes, not status.

“I found that what I enjoyed most as a tech lead was unblocking other people and seeing them grow. The impact I can have through a team is bigger than through my own code. I still enjoy technical discussions, but my main job now is making the team effective.”

10. Tell me about a decision you made that turned out to be wrong.

Leadership or bar-raiser

What they listen for: Ownership, learning and a changed behaviour.

“I promoted a strong engineer to tech lead without giving her support for the people side. She struggled with running meetings and was unhappy. I took responsibility, set up coaching and paired her with an experienced lead. She did well in the end, and now I always agree a support plan before anyone moves into a lead role.”

Phrases to have ready

Opening difficult feedback: “I want to talk about something I noticed, and I'd like to hear your view too.”
Being direct but kind: “I'll be direct, because I think it's more helpful: this isn't at the level we need yet.”
Escalating early: “I want to flag a risk early, while we still have options.”
Offering trade-offs: “We can keep the date or the scope, but realistically not both.”
Disagreeing with leadership: “I see the reasoning. My concern is the impact on on-call. Can we talk through that?”
Owning a mistake: “That was my call, and in hindsight it was the wrong one. Here's what I changed.”

Engineering Manager vocabulary in plain English

One-to-one: A regular private meeting between a manager and one team member.
Performance improvement plan (PIP): A formal plan with clear goals and a time limit for someone who is underperforming.
Headcount: The number of people approved for a team.
Bus factor: How many people could leave before nobody understands a system.
Roadmap: The plan of what the team will build over the next few months.
Stakeholder management: Keeping the people affected by your work informed and aligned.

English mistakes that cost points

Avoid: Describing a hard conversation in general terms: 'I talked to him about it.'
Instead: Quote yourself: 'I said: your last four tickets were late, and I want to understand why.'
Avoid: Feedback that sounds too blunt in English: 'Your work is bad.'
Instead: Specific and behavioural: 'The last two PRs had no tests, which put the release at risk.'
Avoid: Feedback that is so soft the message is lost.
Instead: Be clear about the gap and the expectation, then be kind about the support.
Avoid: Every story is about the team, and your role is invisible.
Instead: Say what you decided and did: 'I made the call to cut scope.'

FAQ

What are common engineering manager interview questions?

Managing underperformance, giving feedback, resolving conflict, hiring, missed deadlines, technical debt, working with product, growing engineers, and why you want to manage. Most loops also include system design or an architecture discussion.

How many stories should I prepare for an engineering manager interview?

Six to eight strong stories usually cover the loop: underperformance, conflict, hiring, a missed deadline, a difficult stakeholder, growing someone, a wrong decision and a strategic change. Practise each one out loud in about two minutes.

Is my English good enough to interview for a manager role?

If your team can understand you, yes. Interviewers listen for clarity, structure and tone. Learning a small set of phrases for feedback, escalation and disagreement makes a bigger difference than vocabulary.

Ready to practise?

Turn interview English into a repeatable skill

Work through the Interview English Course, then book live coaching with engineers who give feedback on both your technical answers and how you deliver them in English.