Engineering Manager interview questions
46 questions asked in Engineering Manager interviews, on people, delivery, hiring and technical direction. They are built from thousands of real job ads. Under each one: what the interviewer is listening for, and the follow-up they may ask. For the recruiter call, see the HR screen questions.
Behavioral questions
Questions about how you work in this role. More in behavioral questions for any tech role.
-
1
Tell me about the hardest feedback you've had to give someone on your team.
All levels
Listening for Clear, specific feedback given with care and followed up.
Follow-up Ask how the person reacted and what changed afterwards.
-
2
Tell me about a time you protected your team from too many requests or too much pressure.
All levels
Listening for Pushing back with data and offering trade-offs, not just saying no.
Follow-up Ask how the people asking reacted.
-
3
Tell me about the first time you led other engineers. What was harder than you expected?
Junior
Listening for Honest reflection on moving from doing to leading.
Follow-up Ask what they stopped doing to make room for it.
-
4
Tell me about a time you had to let someone go, or move them off the team.
Mid, Senior
Listening for A fair process, clear warnings and respect for the person.
Follow-up Ask how they explained it to the rest of the team.
-
5
Tell me about a hire that didn't work out. What did you change in how you hire?
Mid, Senior
Listening for Owning the hiring mistake and fixing the process, not only the person.
Follow-up Ask what signal they missed in the interviews.
-
6
Tell me about a time someone on your team was close to burning out. How did you notice?
Mid, Senior
Listening for Spotting early signs and changing workload, not just offering kind words.
Follow-up Ask what they changed so it would not happen again.
-
7
Tell me about a technical decision you made as a manager that most of the team disagreed with.
Senior
Listening for Listening first, deciding with clear reasons and owning the result.
Follow-up Ask how it turned out and what they would do now.
-
8
Tell me about a team you built or rebuilt. What did you change first?
Senior
Listening for A clear picture of the team they wanted and the steps to get there.
Follow-up Ask how long it took before they saw a difference.
Technical discussion questions
Talking through your experience and decisions, not a coding test. Grouped by topic.
People management
-
1
What do you talk about in a one-on-one, and how do you make it useful for the engineer?
Junior, Mid
Listening for Their agenda first, growth and blockers, not only status updates.
Follow-up Ask how often they hold them and what they do when one feels empty.
-
2
As a new lead, how do you decide how much code to write yourself and how much to hand to the team?
Junior
Listening for Staying off the critical path and using their coding to unblock and teach.
Follow-up Ask what kind of task they would still keep for themselves.
Mentoring
-
3
How would you help a mid-level engineer get to senior?
Mid, Senior
Listening for Clear expectations for the next level and real chances to show them.
Follow-up Ask how they would know the engineer is ready.
Hiring
-
4
Walk me through how you'd run a technical interview to see if someone is a good fit for the team.
Junior, Mid
Listening for Clear signals to look for, a fair structure and writing feedback straight after.
Follow-up Ask how they keep their own bias out of it.
-
5
You're hiring the first engineer for your new team. What would you look for beyond technical skills?
Junior
Listening for Clear needs of the team, ownership and communication, and how to test them in an interview.
Follow-up Ask what would make them say no to a strong coder.
-
6
You need to hire five engineers in the next six months. How would you plan it?
Mid, Senior
Listening for Which roles first, the interview loop, recruiter partnership and onboarding capacity.
Follow-up Ask how they would keep delivery going meanwhile.
-
7
How do you keep the hiring bar consistent when lots of different people are interviewing?
Senior
Listening for Clear rubrics, interviewer training and calibration.
Follow-up Ask what they do when two interviewers strongly disagree.
Roadmap
-
8
Product wants new features, but the team says tech debt is slowing them down. How do you split the time?
All levels
Listening for Making the cost of debt visible to product in their terms and agreeing a share.
Follow-up Ask how they would show the debt work paid off.
Stakeholder management
-
9
Stakeholders ask when a feature will be ready, and the team isn't sure. What do you tell them?
Junior, Mid
Listening for An honest range with the main risks and a date for a better estimate.
Follow-up Ask how they would update people if it slips.
Team building
-
10
A new engineer joins next week. How would you help them ship something in their first month?
Junior, Mid
Listening for A ready dev setup, a buddy, a small real task and regular check-ins.
Follow-up Ask what they would expect them to ship in week one.
-
11
How do you know if your team is healthy, beyond whether it ships on time?
Mid, Senior
Listening for Signals like openness in retros, on-call load, attrition and who speaks up.
Follow-up Ask what they would do if one signal looked bad.
-
12
Two teams are merging under you after a reorg. How would you make it work?
Senior
Listening for Listening to both teams, a shared goal and clear ownership.
Follow-up Ask what they would expect to go wrong first.
Performance management
-
13
One of your engineers has missed their last few deadlines. How would you handle it?
All levels
Listening for Finding the cause before judging, clear expectations and follow-up.
Follow-up Ask what they would do if nothing changes in a month.
-
14
How do you write a performance review that's fair and that the engineer can act on?
Junior, Mid
Listening for Evidence collected over time, clear examples and next steps, and no surprises.
Follow-up Ask how they handle an engineer who disagrees.
-
15
You've coached someone for months and they're still not meeting the bar. How do you decide what happens next?
Senior
Listening for A fair, documented process, considering a different role, and acting in time.
Follow-up Ask how they work with HR on it.
System design
-
16
Walk me through how you review a design doc from someone on your team. What do you look for?
Junior, Mid
Listening for Problem first, alternatives, failure cases and operational cost, while letting the author own it.
Follow-up Ask how they push back without taking over.
-
17
An engineer proposes adding a cache to fix a slow page. What would you ask before saying yes?
Junior, Mid
Listening for Where the time really goes, stale data, invalidation and what happens when the cache fails.
Follow-up Ask what they would measure first.
-
18
Your team wants to split a monolith into services. How would you decide whether it's worth it?
Mid, Senior
Listening for The real problem it solves against the cost of running many services.
Follow-up Ask what they would split out first, if anything.
-
19
Traffic is expected to grow ten times next year. How would you get your systems and your team ready?
Senior
Listening for Finding what breaks first, load testing and planning both tech work and people.
Follow-up Ask what they would do in the first month.
Observability
-
20
Your on-call engineers keep getting woken up by alerts that don't matter. What would you do?
Junior, Mid
Listening for Alerting on user impact, cleaning up noisy alerts and treating on-call load as a team health issue.
Follow-up Ask how they would decide which alerts to delete.
-
21
How would you make sure your team knows something is wrong before customers tell you?
Mid, Senior
Listening for Monitoring user-facing signals, good dashboards and alerts tied to impact.
Follow-up Ask which metric they would add first.
API design
-
22
Another team's service broke because your team changed an API. How would you stop that happening again?
All levels
Listening for Versioning, contract tests and talking to consumers before changes.
Follow-up Ask how they would handle the team that was hit.
Reliability
-
23
Your service keeps having small outages, but leadership wants features. How do you make the case for reliability work?
Senior
Listening for Showing the cost of outages in business terms and agreeing a reliability target.
Follow-up Ask what they would do if leadership still says no.
-
24
Leadership wants the product to stay up even if a whole cloud region fails. How would you respond?
Senior
Listening for Clarifying the real target and cost, then options from backups to multi-region.
Follow-up Ask how they would test that it works.
Machine learning
-
25
Your team needs to put a machine learning model into production for the first time. What would you plan for?
Junior
Listening for Serving, monitoring model quality and not only uptime, retraining and rollback.
Follow-up Ask who on the team would own the model after launch.
-
26
How is managing a team that ships machine learning models different from managing a team that ships regular features?
Mid, Senior
Listening for Uncertain timelines, experiments that fail and planning around them.
Follow-up Ask how they would report progress to stakeholders.
Agile
-
27
Your team keeps carrying half the sprint over to the next one. What would you look at?
Junior
Listening for Looking at planning, unplanned work and task size before blaming people.
Follow-up Ask what they would change in the next planning meeting.
-
28
How do you decide which agile practices your teams keep and which ones they drop?
Senior
Listening for Judging rituals by the problem they solve, letting teams adapt within some shared rules.
Follow-up Ask about a practice they removed.
AWS
-
29
Our AWS bill doubled this year. How would you bring it under control without slowing the team down?
Mid, Senior
Listening for Finding where the money goes, quick wins and making cost visible to teams.
Follow-up Ask what they would not cut.
CI/CD
-
30
Releases take a full day and the team is afraid to deploy on Fridays. How would you improve that?
All levels
Listening for Smaller, automated, reversible deploys and finding what makes releases scary.
Follow-up Ask which change they would make first.
Kubernetes
-
31
The company is moving all services to Kubernetes. How would you plan your team's part of the move?
Junior, Mid
Listening for Ordering services by risk, training the team and fitting it around feature work.
Follow-up Ask which service they would move first.
Incident response
-
32
Production is down and your team is on call. What do you do in the first hour?
Junior, Mid
Listening for Clear roles, focus on recovery before root cause, and regular updates to others.
Follow-up Ask what they would do if the on-call engineer is stuck.
-
33
How do you run a post-mortem so people learn from it instead of feeling blamed?
Mid, Senior
Listening for Focusing on systems, not people, with actions that get done.
Follow-up Ask how they make sure the actions are not forgotten.
-
34
The same kind of incident happened three times this quarter, in different teams. What would you do?
Senior
Listening for Looking for the shared cause across teams and fixing it at platform level.
Follow-up Ask who should own the fix.
Platform engineering
-
35
Your team owns an internal platform, but other teams keep building their own tools instead. What would you do?
Junior, Mid
Listening for Treating other teams as customers and finding out why they avoid it.
Follow-up Ask what would make them stop supporting the platform.
-
36
How would you decide whether we need a separate platform team?
Senior
Listening for Clear reasons like repeated work across teams, and a clear line of ownership.
Follow-up Ask how they would stop it becoming a bottleneck.
LLMs
-
37
Product wants a feature built on a large language model by next quarter. What risks would you raise with your team?
All levels
Listening for Quality, cost, latency, provider outages and how to test it.
Follow-up Ask how they would know the feature is good enough to ship.
-
38
Some engineers use AI coding tools a lot and some won't touch them. How would you handle that as a manager?
All levels
Listening for Clear rules on quality and review, not forcing one way of working.
Follow-up Ask how they would tell if the tools help or hurt.