An engineering manager onsite interview typically has four to six rounds covering people management, execution and delivery, system design or architecture, cross-functional partnership and, at some companies, a coding round. Strong EM answers center on what your team achieved, the numbers that show it, and the hard people decisions you made yourself.
The exact mix varies by company, level and how hands-on the role is, so treat the structure below as common practice and ask your recruiter for your agenda. For prep timing and logistics across any onsite, see our hub on how to prepare for an onsite interview.
What rounds are in an engineering manager onsite interview?
| Round | What it tests | Common format |
|---|---|---|
| People management | Hiring, coaching, performance problems, retention, team health | Behavioral questions with deep follow-ups |
| Execution and delivery | Planning, prioritization, handling slips, incidents, process | Behavioral plus "how would you" scenarios |
| System design or architecture | Technical judgement, trade-offs, ability to guide engineers' designs | A design prompt or a review of a past system |
| Cross-functional partnership | Working with product, design and other teams; managing disagreement | Often run by a product manager or peer manager |
| Coding or technical depth | Whether you can still read and reason about code | Included at some companies, usually lighter than for engineers |
| Hiring manager or senior leader | Motivation, scope, fit with the org | Conversation with your future manager or a skip-level |
If the role leans hands-on, expect the coding and design rounds to count more. If it manages managers, expect more weight on org design and leadership.
What do strong engineering manager answers include?
EM interviewers hear many answers that describe good intentions. The answers that score well usually contain five concrete things:
- A team outcome. What the team delivered or changed, not only what you did in meetings.
- Metrics. Delivery predictability, incident counts, attrition, hiring speed, cycle time or customer impact, with before and after numbers.
- A hard decision you owned. Moving someone off a project, managing out an underperformer, cancelling work or saying no to a senior stakeholder.
- Your specific actions. The conversations, documents and changes you made, in order.
- Reflection. What you would do differently, which shows judgement and self-awareness.
20 example engineering manager onsite questions
These are example questions we wrote, grouped by round, each with what a strong answer includes. For a larger bank, see our engineering manager interview questions.
People management
- Tell me about a time you managed an underperformer. Clear expectations, documented support, a timeline, and the outcome, whether they improved or left.
- How do you run one-on-ones? A specific structure, how the agenda is owned, and an example of a problem one-on-ones surfaced early.
- Tell me about someone you promoted or helped get promoted. The gap you saw, the stretch work you gave them, and how you made the case.
- Tell me about a time you gave difficult feedback. The specific behavior, the impact, and what changed. Our sample answers for giving difficult feedback show the shape.
- How do you hire? Your process, how you reduce bias, a hire you are proud of and a miss you learned from.
- Tell me about a time someone on your team was about to quit. How you noticed, what you could and couldn't change, and the result.
Execution and delivery
- Tell me about a project that slipped. What did you do? When you saw it, how you told stakeholders, the options you offered and the delivery fix.
- How do you decide what your team works on next quarter? Inputs, a prioritization method, how you balance tech debt, and how you say no.
- Walk me through a serious incident on your team. Your role during it, the blameless review, and the change that stopped a repeat.
- What delivery metrics do you track, and why? A few metrics, how they drove a real decision, and how you avoid gaming them.
- Tell me about a process you introduced or removed. The problem, the change, adoption and measured effect.
System design and architecture
- Design a system your team might own, such as a notification service or an internal job scheduler. Requirements, trade-offs and how you would split the work across engineers.
- Tell me about a major technical decision your team made. Options considered, who decided, and how you balanced speed with long-term cost.
- How do you handle a disagreement between two senior engineers about architecture? A decision process, written proposals, and how you keep both engaged after the call.
- How do you manage technical debt? How you make it visible, a share of capacity, and one example where paying it down changed delivery.
Cross-functional partnership
- Tell me about a disagreement with a product manager. Shared goals, data, the compromise, and the relationship afterward.
- How do you set expectations with stakeholders when scope grows? Trade-off conversations, written agreements and early warning.
- Tell me about a time you had to deliver bad news to leadership. Timing, ownership and the options you brought with it.
Coding or technical depth
- Solve a medium-difficulty coding problem while talking through it. Clean reasoning, testing and stated complexity; speed matters less than for engineer roles at many companies.
- Review this pull request. What would you comment on? Correctness first, then readability, tests and how you would phrase feedback to the author.
For the questions you should ask at the end of each round, use our list of questions to ask in an engineering manager interview.
Example answer we wrote: managing an underperformer
Situation: A mid-level engineer on my eight-person platform team had missed three sprint commitments in a row, and two teammates were picking up his reviews.
Task: I needed to find out whether this was a skill, motivation or personal problem, and either fix it or make a fair call within a quarter.
Action: In our one-on-one I shared the three missed items and their impact on the team, then asked what was getting in the way. He said he was struggling with the new service framework and didn't want to ask for help. We agreed on a written six-week plan: smaller tickets, pairing twice a week with a senior engineer, and a weekly check-in on two measurable goals. I told him plainly that if things didn't improve, we would discuss a formal performance plan.
Result: By week five he was closing his commitments and had taken back his share of reviews. Two quarters later he led a small migration. I now run a short skills check with every engineer when we adopt a new framework, instead of waiting for missed sprints.
Interviewers often follow up with "What if it hadn't worked?" Have an honest answer about how you would have moved to a formal process and supported the rest of the team.
How should you prepare for each round?
- People and execution: Build eight to ten stories covering hiring, performance, promotion, conflict, a slipped project, an incident, a process change and a stakeholder disagreement. Our guide to manager interview questions helps you check coverage.
- Design: Practice two or three prompts out loud and review the systems your current team owns. Our system design interview explainer covers the structure.
- Cross-functional: Prepare one story where you and a product partner disagreed and still shipped well together.
- Coding: If the loop includes it, spend a week on medium problems so the mechanics feel familiar again.
- Your numbers: Write down team size, scope, key metrics and outcomes for your last two roles so you can quote them without hesitating.
Related reading: the senior software engineer onsite for how technical depth is judged, and how onsite interviews are scored for what happens after your last round.
Practice it
EM stories go wrong in two ways: too long, or too vague on numbers. Both are easier to fix when you hear yourself. Rehearse out loud with an AI interviewer that builds the session from your résumé and the job description, get each answer scored out of 10 with what to fix, and repeat your weakest people-management story until it fits in about two minutes. It is free for 15 minutes a day, with no account. For structuring stories, the behavioral interview help page is a good companion. Follow each employer's rules on AI tools, and use AI to prepare beforehand.
Rehearse your EM stories out loud
Answer people, execution and design questions built from your résumé and the job description, and get a score out of 10 with what to fix on each.
Try a free AI mock interviewFAQ
Do engineering manager interviews include coding?
Some do and some don't. Hands-on EM roles more often include a coding or code review round, usually lighter than for engineers. Ask your recruiter whether coding is part of your loop.
How many rounds are in an engineering manager onsite?
Commonly four to six, covering people management, execution, system design or architecture, cross-functional partnership and a conversation with your future manager or a senior leader.
What is the most important round for an engineering manager?
It depends on the role, but people management and execution usually carry heavy weight because they show how you lead a team day to day. Design matters more for hands-on roles.
How many stories should an engineering manager prepare?
Eight to ten stories usually cover the common themes: hiring, underperformance, promotion, conflict, a slipped project, an incident, a process change and a stakeholder disagreement.
How technical should an engineering manager be in the design round?
Enough to lead a real design discussion: set requirements, compare options, name trade-offs and explain how you would divide the work. You are not expected to know every implementation detail.
Should I bring metrics from my current team?
Yes, as long as they are not confidential. Rounded or relative numbers, such as halving incident count, show impact without exposing your employer's internal data.