The short answer: Engineering managers lead a team of engineers and stay close enough to the technical work to guide it. Their interviews mix people management and leadership rounds with system design, and sometimes coding or code review. Amazon is the only one of the three that publishes its manager loop: a phone screen, a writing assessment and five 55-minute interviews for its Software Development Managers. Google and Meta publish only their company-wide hiring processes, so their manager rounds come from candidate reports. Whether you will code is the question candidate reports disagree on most, so ask your recruiter. Last reviewed October 2026.
Engineering Manager interview: quick answers
| Question | Short answer |
|---|---|
| What does an engineering manager do? | Hires, grows and manages a team of engineers, owns its roadmap and delivery, and leads design and operational work. Postings at all three companies expect managers to stay technical. |
| What do the interviews test? | People management (hiring, growth, underperformance), system design, leadership on a past project and behavioral questions. Some loops add coding or code review. |
| Can I use AI tools? | Google says no. Meta allows no outside AI tools, only the tools inside the interview environment. Amazon publishes no rule, so ask your recruiter. |
| How much do engineering managers make? | Posted US base ranges run from $184K for Meta's front-line Software Engineering Manager to $364K for Google's Senior Software Engineering Manager. All three add bonus or equity. |
| Do engineering managers have to code in interviews? | It varies. Candidate reports describe a coding round at Meta and code review or coding at Google. Amazon's SDM page lists no coding round, and candidate reports disagree. |
| Is there an entry-level path? | No. None of the three posts an entry program for managers. Postings ask for years of engineering plus 2 or more years managing people. |
What engineering managers do
Google's postings describe a Software Engineering Manager who provides technical leadership on major projects and manages a team, optimizes their own code and makes sure their engineers can optimize theirs. Google also hires a hands-on Tech Lead Manager under the same band. Its published manager research, Project Oxygen, names behaviors such as coaching, supporting career development and having key technical skills.
Meta's Software Engineering Managers lead a team, set goals and expectations, give feedback, recruit and close candidates, and work closely with product, design and data partners. Postings expect them to write design documents and code to keep credibility, on teams such as recommendation systems and MTIA accelerator software.
Amazon calls the role Software Development Manager. SDMs own their team's roadmap, software quality and delivery, usually for a two-pizza team, and Amazon names operational excellence as a core competency: monitoring, major incidents, operational reviews and readiness documents. Ideas are shared in written narratives, which is why SDM candidates submit a writing assessment.
How 3 companies run the engineering manager interview
The short version of each process. Each company guide has the full detail, with links to the company's own pages, and says which parts come from candidate reports.
| Company | Screens | Main interviews | AI tools | What stands out |
|---|---|---|---|---|
| Recruiter calls; coding screen, sometimes skipped (candidate reports) | 2 design, code review or coding, people, leadership (candidate reports) | Not permitted | Code review round for managers (candidate reports) | |
| Meta | Behavioral and design screens (candidate reports) | Design, coding, retrospective, people, behavioral (candidate reports) | Only tools inside the interview environment | Project retrospective round (candidate reports) |
| Amazon | 60-minute screen: Leadership Principles and design | Five 55-minute interviews: design, management, LPs | No published rule | Writing assessment before the loop |
The interview types in depth
People management
This is the round that most separates manager loops from engineer loops. Expect questions on hiring, growing engineers, managing low and high performers, giving hard feedback and handling conflict. Amazon lists people management as an SDM competency, and candidate reports describe a dedicated people management round at Google and Meta, with one Meta candidate calling it the toughest round.
Interviewers push for detail with follow-ups, so a story that stays general falls apart fast. Bring specific cases with names changed, the actions you personally took, and the outcome, including the cases that did not end well.
System design
Manager design rounds look like senior engineer design rounds, with more attention to trade-offs and how you would run the work. Amazon says its SDM loop includes at least one systems design question and that the screen can be a deep dive on a system you supported. Candidate reports describe two design rounds at Google and one or two at Meta, where some candidates pick product architecture or ML design.
A structure that works: clarify requirements and scale, lay out the whole high-level design, then go deep on one or two parts. Plan for growth, name what fails first, and cover monitoring and rollout. Candidates who get stuck on one detail early tend to run out of time for the rest.
Project retrospective and technical leadership
You walk through one large project you led while the interviewer probes it for half an hour or more. Candidate reports describe a project retrospective round at Meta and a technical leadership round at Google where one interviewer spent about 30 minutes on a single project.
Pick a project with real technical difficulty and real stakes. Know the goal and metric, the key trade-offs, what slipped and why, how you managed stakeholders and what you would change. Keep your own decisions separate from the team's work.
Coding and code review
Coding is the least predictable part of a manager loop. Candidate reports describe a coding round at Meta, recently AI-assisted in some loops, and a code review round at Google offered in place of coding, where you find logic bugs and comment on naming and structure. Amazon's SDM page lists no coding round, and candidate reports disagree on whether one appears.
Keep medium-level problem solving in practice either way, and practice reading code you did not write. In code review, find correctness bugs first, then structure and tests, and say which comments would block a merge.
Writing and company values
Amazon asks SDM candidates for a written narrative about something innovative and complex they drove, due 2 days before the loop, and every Amazon interviewer asks Leadership Principles questions. Google suggests STAR answers with impact stated as "accomplished X, as measured by Y, by doing Z".
Write your main stories down before the loop even if no company asks for writing. It forces you to find the numbers and your own part in the result, which is what follow-up questions dig for.
Pay in US job postings
US salary ranges from each company's own postings for this role, seen October 29, 2026. They are base salary unless the company guide says the posting lists total salary. Each company guide has the postings and links.
| Company | Titles in the postings | Posted US pay range |
|---|---|---|
| Software Engineering Manager (often with a team suffix), Software Engineering Manager II, Engineering Manager, Tech Lead Manager and Senior Software Engineering Manager | $207K to $364K | |
| Meta | Software Engineering Manager, posted plain or with a team suffix (for example Recommendation Systems), and Engineering Manager on some teams | $184K to $301K |
| Amazon | Software Development Manager (SDM), often with a team suffix such as S3 or SageMaker Training; Software Development Manager III; and Sr. Software Development Manager | $184.9K to $342.3K |
AI tools in engineering manager interviews
Rules on AI differ by company, so ask your recruiter before every round.
Google. Google says AI tools are not permitted during interviews, and its tips page says the same of Google Search and AI.
Meta. Meta says no outside AI tools or assistance are authorized, and only the tools available within the interview environment may be used. Its FAQ says many interviews include a built-in AI assistant that candidates are expected to use, and that design interviews use the same assistant. It does not say which engineering manager rounds use it.
Amazon. Amazon does not publish a rule on AI use in interviews. A March 2025 news report described internal Amazon guidance asking candidates not to use generative AI tools during interviews unless explicitly permitted, which is a report and not a published Amazon rule.
A 6-week prep plan
| When | Focus |
|---|---|
| Week 1 | Read your target company's postings and guide. Note its title for the role, the rounds it publishes or candidates report, its AI rule, and whether your loop may include coding. Ask your recruiter what you can. |
| Week 2 | People management stories: hiring, growing an engineer, an underperformer, a high performer, hard feedback and a conflict. Write each one down with your actions and the outcome. |
| Week 3 | System design: two problems a week, laying out the full design before going deep, with growth, failure handling, monitoring and rollout. |
| Week 4 | Project leadership: prepare one large project for a 30-minute deep dive and a second as backup, with metrics, trade-offs, slips and stakeholders. |
| Week 5 | Coding and code review: medium problems with no AI help, plus reviewing code you did not write. For Amazon, finish the writing assessment draft. |
| Week 6 | Values and mock loops: map your stories to the company's values, then run two full practice loops with follow-up questions. |
Courses for each round
Practice questions
Questions from our bank, then practice prompts from the company guides.
Questions from our bank
From the DataInterview question bank, picked for engineering manager interviews. Open one to answer it.
Assess Resource Allocation
Boost Development Productivity
Communicating Project Roadmap
Managing Team Performance
Low Performance Termination
Hiring Top Engineers
Best Employee Example
Building Team Trust
Building Trust During Change
People management practice
One prompt per company, from the company guides. These are our prompts, not reported interview questions.
One of your senior engineers on a Google Cloud team ships features on time but blocks others in code review and two people have asked to move teams. What do you do?
Sample Answer
Start by collecting specifics: which reviews, what was said, and the impact on velocity and on the people who want to leave. Give the engineer direct feedback with examples and agree on observable changes, such as review turnaround and tone. Separate their strong delivery from the behavior so the message is clear. Follow up on a set date and check with the affected engineers. A strong answer says what you would do if nothing changes and how you would protect the team in the meantime.
One of your engineers on a recommendation systems team has missed three commitments in a row, and the team is starting to work around them. What do you do?
Tell me about an underperformer you managed. What happened?
System design practice
One prompt per company, from the company guides. These are our prompts, not reported interview questions.
Design a service that counts views and likes on short videos and shows near real-time counts to creators.
Sample Answer
Clarify scale (events per second, number of videos, freshness target) and whether counts must be exact. A common shape is clients sending events to a log, stream processing that aggregates per video per minute, and a store that serves the latest totals. Handle hot videos with sharded counters and merge them on read. Discuss deduplication, late events and what creators see during a backfill. As a manager, add how you would split the work across teams and stage the launch.
Design real-time comments on live videos, where popular streams get thousands of comments per second.
Design the backend for a ride-hailing app that matches riders with nearby drivers.
Code review practice
One prompt per company, from the company guides. These are our prompts, not reported interview questions.
A report's change wraps a call to a Cloud API in a loop that retries forever on any exception. What comments do you leave?
Sample Answer
Point out that the broad exception catch hides real bugs and that infinite retries can hang the caller and overload the API. Ask for a bounded number of retries, a backoff that doubles the wait each time with some jitter, and retries only on errors that are safe to retry. Ask whether the call is idempotent. Suggest a test that simulates a failing API and a log line or metric for each retry.
Operational excellence practice
One prompt per company, from the company guides. These are our prompts, not reported interview questions.
Tell me about a major operational incident your team had. What did you change afterward?
Sample Answer
Give the customer impact in numbers, how the team detected and mitigated it, and the root cause. Then explain the follow-up: the review you ran, the action items, and the monitoring or process change that stopped it from happening again. Keep background short and say what you personally did.
Behavioral practice
Prompts we wrote for engineering manager behavioral rounds, with what a strong answer covers.
Tell me about an engineer who was underperforming.
Sample Answer
Describe the gap with specifics, the feedback you gave, the plan you agreed on and how you supported it. Give the outcome honestly, including if they left, and what you would do sooner next time.
Tell me about someone you helped grow into a bigger role.
Tell me about a project that slipped.
Tell me about a disagreement with a product partner or another team.
Are you ready for engineering manager interviews?
1 / 5Can you describe how you handled an underperformer, from first signal to outcome?
Company guides
Read the guide for each company you are interviewing with:
- Google: The Google engineering manager interview: Google's official hiring steps, the manager rounds candidate reports describe, the AI rule and pay in Google's postings.
- Meta: The Meta engineering manager interview: Meta's official hiring steps, the manager rounds candidate reports describe, the AI rule and pay in Meta's postings.
- Amazon: The Amazon Software Development Manager interview from Amazon's own SDM prep page: the screen, the writing assessment, the five-round loop, the coding question and posted pay.
Frequently Asked Questions
What is an engineering manager interview like?
Expect people management and leadership rounds, system design, a deep dive on a past project and behavioral questions. Some loops add coding or code review. Amazon publishes its SDM loop; at Google and Meta the manager rounds come from candidate reports.
Do engineering managers code in interviews?
Sometimes. Candidate reports describe a coding round at Meta and a code review or coding round at Google. Amazon's SDM page does not list coding, and candidate reports disagree. Ask your recruiter.
Can I use AI tools in engineering manager interviews?
Google does not permit AI tools. Meta allows no outside AI tools, only the tools inside the interview environment, including a built-in AI assistant in many interviews. Amazon publishes no rule, so ask your recruiter.
How much do engineering managers make at Google, Meta and Amazon?
In US postings seen in October 2026, Google lists $207K to $300K base for Software Engineering Manager roles and $262K to $364K for Senior, Meta lists $184K to $301K, and Amazon lists $184.9K to $287.7K for SDMs and $220.1K to $342.3K for Senior SDMs. All three add bonus or equity.
What titles do these companies use?
Google uses Software Engineering Manager, Engineering Manager and Tech Lead Manager. Meta uses Software Engineering Manager for both front-line and multi-team roles. Amazon uses Software Development Manager (SDM).
How long does the process take?
Google says about 6 to 8 weeks once interviews start. Meta says about 2 to 3 months. Amazon says to expect a decision within 5 business days of the loop.
How much management experience do I need?
Google and Meta front-line postings ask for 2 years of people management, and Amazon SDM postings ask for 3+ years of engineering team management. On top of that, Google asks for 8 years of software development, Meta for 8+ years of software engineering (or shorter paths such as a PhD plus 4), and Amazon for 7+ years working within engineering teams.
