Quick verdict: Interview an engineering manager candidate on four areas, in this order of weight: people leadership, delivery, technical judgement and hiring. Ask for real episodes with names, numbers and dates, and score each area on its own. The role is expensive to get wrong: BLS puts the median computer and information systems manager at $175,140 a year (May 2025), with 16% projected growth to 2035.
What is on this page: 20 questions for engineering manager candidates grouped by area, the evidence each answer should contain, a weighted scorecard, a loop design for five interview slots, and the pay and demand data to set the offer.
Updated October 9, 2026. Pay and outlook figures checked against the BLS pages linked below.
What should you ask an engineering manager candidate?
Ask about the four things the job is made of: growing and correcting people, getting software shipped reliably, making sound technical calls without writing all the code, and building the team through hiring. A candidate who is strong on one and silent on the others is usually a strong senior engineer, not yet a manager.
The questions below are written for hiring managers, recruiters and panel interviewers. They are not the questions a candidate asks the company; this page is about assessing the person in the chair. Run each one with the probe next to it, and keep the same wording for every candidate on the slate.
What does an engineering manager actually do all week?
Build your questions from the duties, not the job title. BLS lists the typical duties of computer and information systems managers as assessing the costs and benefits of new projects and justifying funding, determining personnel needs, planning and directing the work of developers and other IT staff, managing security processes, and negotiating with and monitoring vendors, according to its duties summary. Every one of those should show up somewhere in your loop.
Two duties are often skipped in interviews: budget justification and vendor management. If the role owns a cloud bill or a contractor relationship, add one question on each. A manager who has never defended a headcount request will struggle in their first planning cycle.
How much do engineering managers earn, and why does that matter for the interview?
The pay sets the bar. The BLS reports a May 2025 median of $175,140 for computer and information systems managers, the BLS occupation closest to software engineering managers, with the lowest 10% under $107,550 and the top 10% above $297,510, according to the BLS outlook. Architectural and engineering managers, the closer fit for hardware and civil engineering teams, had a median of $171,270, per the BLS engineering managers page.
The gap between a manager and the developers they lead is the useful number for recruiters. Using the BLS medians, a computer and information systems manager earns about $39,160 more than the median software developer ($135,980, per the BLS developers page), a premium of roughly 29%. That is Work Insiders arithmetic on BLS figures. It is also why your loop has to test management, not just engineering: you are paying for the management.
Where are engineering managers paid most?
| Industry (BLS, May 2025) | Median pay, computer and information systems managers |
|---|---|
| Information | $200,510 |
| Finance and insurance | $182,510 |
| Computer systems design and related services | $179,510 |
| Manufacturing | $178,110 |
| Management of companies and enterprises | $176,950 |
If you are hiring outside the information sector, expect candidates from software companies to anchor on the higher end. Our AI engineer salary benchmarks cover pay for the people these managers will lead.
How fast is demand for engineering managers growing?
BLS projects 16% growth for computer and information systems managers from 2025 to 2035, described as much faster than average, with about 53,500 openings a year, most from replacing people who move on or retire. The occupation held 685,800 jobs in 2025 and typically needs five years or more of related experience, all from the BLS summary. For the current hiring climate in tech, see our tech job market report.
What should you ask to test people leadership?
Weight this area most. Google’s Project Oxygen listed the behaviors of its best managers, starting with being a good coach and empowering the team without micromanaging, and later adding decision making and collaboration; the updated list of ten was more predictive of turnover, satisfaction and performance than the original eight, as Nextgov reported. The questions below map onto those behaviors.
| Question | Probe | Evidence a strong answer contains | Red flag |
|---|---|---|---|
| Tell me about an engineer you moved from struggling to solid. | What did you change first? How long did it take? | A named gap, a plan with dates, the result in their own words | Only “I gave them space” |
| Describe the last time you managed someone out. | When did you first raise it with them? | Early, documented feedback before any formal step; HR involved properly | The person was surprised by the outcome |
| How do you run one to ones? | What did the last three cover? | Agenda owned by the report, career topics, not just status | One to ones are status updates |
| Tell me about a senior engineer who disagreed with your direction. | What did you change because of them? | Changed something real, or explained the call and kept trust | Overruled with “I am the manager” |
| How have you supported someone’s promotion? | What evidence did you gather? | Built the case over months with examples | Promotion “just happened” |
What should you ask to test delivery?
Delivery questions should get to numbers. DORA, a long running software delivery research programme, measures delivery with five metrics: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate, and warns against turning any one metric into a target, according to its metrics guide. A strong candidate will know some version of these for their own team.
| Question | Probe | Evidence a strong answer contains | Red flag |
|---|---|---|---|
| How did you know your team was delivering well last quarter? | Which numbers did you watch weekly? | Two or more delivery measures with a trend, plus a quality signal | Only story points or velocity |
| Tell me about a project that slipped badly. | When did you know, and when did you tell people? | Early warning, scope cut or reset, honest communication | Learned of the slip at the deadline |
| Walk me through your last serious production incident. | What changed afterwards? | Blameless review, a specific fix, follow through tracked | Named an engineer as the cause |
| How do you balance roadmap work against technical debt? | Give me the split last quarter. | A deliberate allocation agreed with product | “We will fix it later” |
| How do you stop a metric being gamed? | Example? | Pairs speed with stability measures | Set deployment targets for each engineer |
What should you ask to test technical judgement?
An engineering manager does not need to be the best coder on the team, but they must be able to tell a sound design from a risky one and know when to step back. Google’s list includes having key technical skills to help advise the team, which is the right framing: advising, not doing.
| Question | Probe | Evidence a strong answer contains | Red flag |
|---|---|---|---|
| Tell me about a technical decision you reversed. | What did it cost? How did you tell the team? | Clear trigger for the reversal, cost stated, no blame | Never been wrong |
| Describe an architecture choice your team made that you would not have made. | Why did you let it stand? | Trusted the team, set guard rails, checked later | Rewrote it themselves at night |
| How do you decide build versus buy? | Last real example? | Total cost, team capacity and lock in all weighed | Always builds |
| How much code do you still write, and why? | What do you never pick up? | Stays off the critical path, reviews and unblocks | Owns critical features alone |
| How is AI changing how your team writes and reviews code? | What rule have you set? | A concrete policy on review and quality | Has not thought about it |
What should you ask to test hiring and team building?
Managers multiply themselves through hiring, so test it directly. Ask for the funnel, not the philosophy.
| Question | Probe | Evidence a strong answer contains | Red flag |
|---|---|---|---|
| Walk me through the last engineer you hired, from intake to offer. | What did your scorecard say? | Written criteria before sourcing, structured loop, scored debrief | Hired on gut feel |
| Tell me about a hire that did not work out. | What did you change in your process? | Specific process change, not blame | “Bad luck” |
| How do you work with your recruiter? | How often do you meet? | Weekly calibration, fast feedback on profiles | Recruiter “just sends CVs” |
| How have you made your interviews fairer? | What did you measure? | Same questions, rubrics, panel diversity | No changes ever made |
| How did you grow the team’s skills without hiring? | Example? | Training, rotation or pairing with an outcome | Only hiring as the answer |
If the candidate describes a structured, scored loop, that is a good sign: Google’s re:Work guide says it expects people managers to empower a team, shape a long term vision and develop their reports, and it scores leadership answers against rubrics, per its structured interviewing guide.
How should you score an engineering manager interview?
Score each area from 1 to 4, weight it, and add up. Weighting forces the panel to agree in advance what matters most for this team, which stops the strongest coder winning a management role by default.
| Area | Weight | 4 Outstanding | 2 Borderline |
|---|---|---|---|
| People leadership | 35% | Several named people grown or moved on, with dates and outcomes | Talks about “the team” with no individuals |
| Delivery | 25% | Knows their delivery numbers and the trend, owns a slip honestly | Describes process, not results |
| Technical judgement | 20% | Advises without taking over, has reversed a decision cleanly | Either hands off entirely or still the main coder |
| Hiring and team building | 20% | Structured loop with a scorecard, learned from a miss | Hires on instinct |
Worked example (Work Insiders arithmetic): a candidate scoring 4 on people, 3 on delivery, 3 on technical judgement and 2 on hiring gets 4 x 0.35 + 3 x 0.25 + 3 x 0.20 + 2 x 0.20 = 3.15 out of 4. Set your bar before the loop starts, for example 3.0 with no area below 2.
How should you structure the interview loop?
| Interviewer | Area owned | Format | Length |
|---|---|---|---|
| Engineering director or VP | People leadership | Behavioral, with two probes per question | 60 minutes |
| Product manager peer | Delivery | Behavioral plus a planning scenario | 45 minutes |
| Staff or principal engineer | Technical judgement | Design review of a past system | 60 minutes |
| Recruiter or talent partner | Hiring | Behavioral on their last three hires | 45 minutes |
| Two future direct reports | Day to day management style | Conversation scored on the same rubric | 30 minutes |
Each interviewer owns one area, so the loop collects four different kinds of evidence instead of the same one four times. Every score goes in before the debrief starts. Timings are Work Insiders suggestions.
Copy and paste: reference check questions for an engineering manager
1. What was the size and seniority of the team they managed while you worked together?
2. Name one engineer who grew under them. What did they do to help?
3. Tell me about a time they delivered bad news upward. How did it land?
4. How did they handle a production incident?
5. On a scale of 1 to 10, how keen would you be to work for them again, and what would make it a 10?
How we built this page
Pay, employment, openings and growth figures come from the BLS Occupational Outlook Handbook pages for computer and information systems managers, architectural and engineering managers, and software developers, using May 2025 wage data and 2025 to 2035 projections, checked October 9, 2026. Manager behaviors come from Google’s Project Oxygen as reported by Nextgov; delivery metrics come from DORA’s own guide. The questions, probes, weights, loop design and reference questions are Work Insiders editorial guidance. The pay premium and scoring example are our arithmetic on the cited figures.
Quick answers
What is the most important question for an engineering manager?
“Tell me about an engineer you moved from struggling to solid.” It shows coaching, patience and honesty in one answer, and people leadership should carry the most weight.
Should engineering managers do a coding interview?
A design review of a system they actually ran usually tells you more than a live coding test, because the job is advising on technical choices, not writing most of the code.
What do engineering managers earn?
The BLS median for computer and information systems managers was $175,140 in May 2025, rising to a $200,510 median in the information industry.
Is demand for engineering managers growing?
Yes. BLS projects 16% growth from 2025 to 2035 for computer and information systems managers, much faster than average, with about 53,500 openings a year.
Which delivery metrics should a candidate know?
DORA’s five: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate.
How many interviews should the loop have?
Four or five, each owning one area, so you collect different evidence rather than repeating the same conversation.
What is the biggest red flag?
A candidate who cannot name a single person they developed, or who describes every incident as someone else’s mistake.
Where are general interview questions?
Our interview question bank covers questions for any role, with a scoring rubric.
The bottom line
Hire engineering managers on management evidence. Weight people leadership highest, ask for delivery numbers, test technical judgement through a real system they ran, and make them walk through their own hiring. Score each area separately, agree the bar before the loop, and check references against the same four areas.
With a median salary near $175,000 and demand projected to grow 16% over the decade, a structured loop is the cheapest insurance you can buy. Agree the four areas and their weights with the hiring director in an intake meeting before the first screen, and brief interviewers on AI interview assistants for remote rounds.
Sources: BLS IS managers, BLS engineering managers, BLS software developers, Nextgov on Oxygen, DORA metrics guide, Google re:Work
Free newsletter
Get the Work Insiders weekly
One email a week: the recruiting and HR tech news that mattered, the tools we just added to the directory, and one practical guide. No spam, and you can unsubscribe in one click.