Questions to Ask in an Engineering Manager Interview
For a candidate in an engineering manager interview, with questions to put to the three kinds of people in the loop: the director or VP who would be your boss, the managers who would be your peers, and the engineers who would report to you. The list moves the way the decision does. It starts with why the seat is empty and how much code comes with it, then the team itself, the roles you could hire for, the product partner and the deadlines, reviews and promotions, and what you would be judged on by month six.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The seat
Why is the engineering manager seat open, and where did the last person go?
Why ask it
Promoted, moved to another team, went back to writing code, or left the company: each leaves a different team behind. If they are still in the building, ask whether you could talk to them before you decide. A newly created seat means a tech lead or a stretched director has been running things, and someone is about to hand over authority they have held for a while.
How hands-on is this role: would I be expected to write code, review it, or stay out of the codebase?
Why ask it
The title covers three different jobs: a tech lead who also manages, a manager who reviews designs but ships nothing, and a manager who has not opened an editor in years. What the last manager did, and whether the director liked it, is the best guide to which one this is. Coding plus eight one-on-ones a week rarely fits in one calendar, so weigh the answer against the number of reports.
How many engineers would report to me, and is that one team or several?
Why ask it
Five reports on one product and eleven across two are different weeks. Ask whether the number is expected to grow this year and at what size the team would be split. If a designer, a tester or a data analyst would also report to you, check who gives them feedback on their craft.
Who has been running the team since the last manager left, and what happens to that person when I start?
Why ask it
An acting lead who goes back to being an engineer on your team is your first delicate one-on-one. Months of a director covering usually means feedback and career conversations were put off, and they will be waiting for you.
Which decisions would be mine alone, and which would need your sign-off?
Why ask it
Name cases so the answer cannot stay abstract: making an offer, moving a deadline, changing the on-call schedule, starting a performance plan, buying a tool. Count how many come back as 'run it by me first'. That count is the difference between running a team and relaying a director's decisions to it.
Who makes the technical calls on this team, and where would a manager's say begin and end?
Why ask it
A team with a strong tech lead or staff engineer wants a manager who clears the path, and a team without one wants architecture opinions from you on day one. Put this to the engineers too. If their answer and the director's do not match, you would be walking into a disagreement about what a manager is for.
Was there an internal candidate for this job, and how was the decision explained to them?
Why ask it
One for the hiring manager, never the team. An engineer who applied and lost will be in your standup on the first morning, and what they were told decides whether they help you or start reading job postings. If nobody has had that conversation with them, request that it happen before your start date.
How many managers has this team had in the past few years, and has it been moved or reorganized?
Why ask it
Three managers in three years teaches engineers to wait out the fourth, so expect polite distance until you have stayed a while. A team that has changed departments has had its priorities reset each time. After one long-serving manager the difficulty is the opposite: whatever you change gets measured against how it was always done.
How often would you and I meet, and what do you want to hear about between those meetings?
Why ask it
For the director or VP you would report to. A weekly hour and a wish for no surprises is a workable arrangement. Daily status requests suggest the team is being watched closely, in which case ask what happened to put it there.
When did one of your managers last change your mind, and how did they do it?
Why ask it
A recent example with detail means disagreement is survivable under this boss, and it shows the form that works: a written proposal, numbers, a quiet word before the meeting. If nothing comes to mind, decisions probably travel one way. A peer manager can tell you what pushing back has cost.
What do the other engineering managers here spend most of their week on?
Why ask it
Save this for a peer manager, who has no reason to sell you the job. Hiring, planning meetings, incident follow-up and one-on-ones each claim a share, and the mix shows what the company thinks a manager is. Find out which part they would hand back if they could, and check whether the job description mentions it.
The team
Who is on the team today: levels, tenure, and how long they have worked together?
Why ask it
A group of seniors who have shipped together for years needs little direction and may be wary of a newcomer. A group of recent hires needs structure quickly. Listen for a gap in the middle, where two veterans carry everyone else's code reviews and questions.
Is anyone on the team on a performance plan, or is there someone you are worried about losing?
Why ask it
The interviewer may not be able to name anyone, and you should not push for names. What you can fairly ask is whether open cases exist and who has been handling them, because they become yours the morning you start. A plain 'yes, one, and here is where it stands' says something good about the person you would report to.
Who has left the team in the past year, and what reason did each of them give?
Why ask it
Departures clustered around one event, such as a reorganization, a cancelled project or the previous manager, point to a cause you can raise directly. A steady trickle to better-paid jobs is a pay problem you may have no budget to fix. The engineers on the panel worked beside the people who left and often know a reason that never reached the exit interview.
What would the engineers say is the most frustrating part of working on this team?
Why ask it
Ask the director first, then ask an engineer in the loop the same thing in the first person. Slow builds, unclear priorities and too many meetings are ordinary and fixable. If the director's guess and the engineer's answer have nothing in common, nobody above the team has been listening, and you would be the first.
What does the team want from its next manager?
Why ask it
Best asked of the engineers interviewing you, since they lived with the last one. 'Someone who shields us from changing priorities' and 'someone who gets us promoted' are different requests and describe different histories. Whatever they say is the yardstick they will hold you to.
How is this team seen by the rest of engineering and by the business?
Why ask it
Reputation sets how much room you get. A trusted team can turn down a request, while one known for late dates has every estimate questioned until the record changes. It matters whether the reputation rests on a single bad launch or on a pattern: the first fades with one good quarter and the second is yours to repair.
What does the team own, and which part of it does everyone avoid touching?
Why ask it
The list of services, apps or pipelines is the size of the job. The avoided part is where your first incident is likely to come from, and what is known about it usually sits with one engineer. Getting a second person able to cover it makes a sensible early goal.
Where are the engineers based, and how do they work across locations and time zones?
Why ask it
A split team means your one-on-ones, standups and incident cover all have to fit the overlap, so get the actual hours. Office-day rules belong in the same answer. If they are still changing, you would be the one announcing the next version to the team.
Headcount
How many open roles does the team have, and are they approved and funded today?
Why ask it
Approved in a plan and open with a recruiter assigned are different states, and a role can sit in the first for a long time. If you are being hired to grow the team, ask what happens to the roadmap if those positions are frozen.
If an engineer resigned next month, would I get to replace them?
Why ask it
Backfill rules vary by company and by quarter, so ask how it works there right now. Where every departure goes back to a central pool for review, a team shrinks by attrition without anyone deciding it should.
Has engineering had layoffs or a hiring freeze in the last couple of years, and was this team affected?
Why ask it
A team that lost people that way remembers how it was announced and who chose the names. If the manager before you delivered the news, some of the distrust stays with the job and not the person. Notice whether the director explains how the choices were made or only says that they were hard.
How much of the hiring would I run myself: sourcing, the interview loop, the final decision, the offer?
Why ask it
In some companies the manager owns the whole pipeline and gives it a large share of the week during a growth push. In others a committee decides and the manager only makes the case. The detail that settles it is who can overrule a hire you want, and when that last happened.
What levels am I allowed to hire at, and who sets the pay band for an offer?
Why ask it
A team short on senior people cannot fix that with junior openings. Ask whether two approved roles could be traded for one more senior one, and how long an exception to the band takes. Pay practice differs widely between employers, so get this company's actual process and not a general assurance.
How long does it take to fill an engineering role here, from opening it to the person's first day?
Why ask it
Take the number and count forward from your own start date: that is when help could realistically arrive. If the peer managers give a longer figure than the recruiter, believe the peers.
Does the team rely on contractors or an outside agency, and would I manage them?
Why ask it
Contractors often hold the knowledge of a system with no obligation to stay, so the end dates of their terms belong in your notes. Whether converting or replacing them would be your call differs from one employer to the next. A team of six with three contractors in it plans very differently from six employees.
Delivery
Who would my product counterpart be, and how do the two roles split the decisions?
Why ask it
You would work with this person every day, so try to meet them before accepting. One common split gives product the what and the why and engineering the how and the how long, with the order of work argued out between you. Where there is no product manager, the requirements may turn out to be yours to write.
Where does this team's work rank among the company's priorities this year?
Why ask it
A team on the main bet gets headcount and executive attention in equal measure. A team keeping an older product alive gets little of either, which can be a calm place to manage and a hard place to win promotions for your people. If you hear that everything is a priority, ask which team received the most recent new hire.
Who sets the team's roadmap, and how much of the current one is already promised to someone?
Why ask it
A quarter that is fully committed before you arrive leaves you managing dates you did not agree to. The items with a customer or an executive attached will not move, whatever you learn about the team's capacity in your first weeks, so get those named.
How does the team plan and ship today: sprints, release schedule, code review, and how much of that could I change?
Why ask it
You are listening for where work waits: in review, in testing, in a release that only goes out every two weeks. A process the engineers describe with a sigh was probably imposed on them. One handed down by a central group is not yours to change, which is worth knowing before you promise the team anything.
When a delivery date is set, does the team's estimate come before the commitment or after it?
Why ask it
Have them walk through the most recent launch, from first conversation to announced date. Dates handed down by sales or the executive team are a fact of life in many companies. What matters to you is whether a manager there can go back and renegotiate, and whether anyone ever has.
What happened the last time this team missed a date?
Why ask it
The story shows who took the heat: the manager, the tech lead, the whole team, or nobody. Notice whether the fix was a smaller scope, a later date or weekends. That response is the default you would have to work within or argue against.
How does the on-call rotation work, and would I be on it or be the escalation point?
Why ask it
Get the size of the rotation, how often each person is on, and how many pages came outside working hours in the last cycle. Manager duties differ: some carry the pager, some are the second call, some hear about it in the morning. If on-call is paid or earns time off, ask how that works there, since your team will ask you.
When did the team last work late or over a weekend to hit a deadline, and who asked them to?
Why ask it
A single launch crunch with time given back afterward is one thing. If an engineer says 'last week' and the director says 'rarely', the pressure is not visible from above, and making it visible would be part of your job.
How much of the team's time goes to maintenance, incidents and technical debt, and who protects that time?
Why ask it
A reserved share that survives planning means someone senior agreed to it. If the answer is 'whatever the manager can negotiate', find out how the last manager fared and what they traded for it. The share is often generous on paper, so check when the team last spent a full week of it.
How does the company judge whether this team is delivering well?
Why ask it
Shipped features, velocity charts, uptime, customer numbers or a director's impression: whichever it is will shape what you are asked for in every review. Be wary of a measure the team cannot influence. If output is counted per engineer, ask what those numbers are used for.
How do other teams' requests reach this one, and who is allowed to say no to them?
Why ask it
Support escalations, favors for sales and asks from teams that depend on yours tend to arrive sideways, outside the roadmap. A manager with the authority to decline or queue them can keep a plan. One without it spends the quarter apologizing to the product manager.
People
How does the performance review cycle work, and when is the next one?
Why ask it
If a cycle lands in your first couple of months, you could be writing reviews for people you barely know. Whatever the last manager left in writing is your raw material, and a considerate director offers to carry that round. Where ratings are compared across teams, find out who sits in that meeting, since you would be arguing your team's case to them.
How are promotions decided, and how much depends on the manager's written case?
Why ask it
Processes range from a manager's recommendation with a signature above it to a committee reading packets. Ask to see the engineering ladder if one is written down, and who shows a new manager how to write a case. If you are told that good work speaks for itself, the manager's persuasion is doing the job a process should.
When was someone on this team last promoted, and is anyone overdue?
Why ask it
A long gap means either the levels are full or the cases were not being made. An engineer who was promised a promotion by your predecessor will raise it in your first one-on-one, so learn the history now.
What authority would I have over raises, bonuses and equity for my reports?
Why ask it
Some managers set numbers inside a budget, some recommend and learn the outcome later, and some only deliver the letter. This is specific to each employer, so ask for theirs. If your say is small, ask what else you could offer a strong engineer who is underpaid.
What is the process when an engineer is not meeting the bar, and how much support would I get from you and HR?
Why ask it
You are asking two things: whether a path exists, and whether your boss will back you along it. The steps and the paperwork depend on the company and on local employment rules, so ask how it works there and do not assume. A director who says the last manager avoided this is telling you what is waiting.
How are engineering managers themselves evaluated here?
Why ask it
Delivery alone rewards a manager who wears a team out to hit two quarters. Listen for anything about retention, survey results, the growth of reports or feedback gathered from the engineers. The quickest check is what the most recent highly rated manager had done to earn it.
What does growth look like for a manager here: a larger team, managers reporting to me, or a move back to the technical track?
Why ask it
A path is real once somebody has walked it, so get a name: the last manager to become a senior manager or director, and how long it took. If you might want to return to individual contributor work one day, check whether anyone has done it there without dropping a level.
What training do new managers get here, and is there a regular forum where the engineering managers compare notes?
Why ask it
A first-time manager needs this most, but an experienced one still has to learn how this company handles reviews, pay and difficult exits. A regular managers' meeting is also where you find out how another team solved the problem you are stuck on. If there is neither, your director is your only source.
First six months
What has to be true six months in for you to call this hire a success?
Why ask it
Push for something that could be checked: two roles filled, a date met, departures stopped, a stalled migration moving again. Write the answer down and bring it back in your first week as a draft of your goals. If the director and a peer manager name different things, ask the director which comes first.
What should the first thirty days be: listening, or is there a decision waiting for me on day one?
Why ask it
Most new managers want a month of one-on-ones before changing anything. Some seats do not allow it: a reorganization pending, a launch three weeks out, a resignation already on the desk. Better to hear that now than to plan a listening tour that gets cancelled.
What is the hardest problem I would be handed in the first quarter?
Why ask it
Nearly every open seat has one: a late project, a difficult stakeholder, two engineers who will not work together. Hearing it named lets you ask what has been tried and how free you would be to act. If you are told everything is in good shape, ask what the last manager would say.
Which of the team's habits would you want protected, even if I arrived with a better idea?
Why ask it
New managers get into trouble by replacing something the team valued: a weekly demo, a day without meetings, a particular way of running retrospectives. The answer also shows what the director is proud of. The engineers' list may differ, and the habits on theirs but not the director's are the ones a newcomer breaks by accident.
What mistake have new managers made here in their first months?
Why ask it
The answer is a map of the local hazards: moving too fast, going around a product partner, contradicting a director in front of the team. Peer managers answer this more freely than the hiring manager does. With a peer, follow up with what they wish someone had told them in their own first month.
Having talked through all this, where do you see the gap between my experience and what the team needs?
Why ask it
Keep it for the last few minutes with the person you would report to. A named gap, such as scale, domain or never having managed managers, can be answered on the spot or in your follow-up note. It also tells you what you would need to prove early if you took the job.
What are the remaining steps, and who makes the final decision?
Why ask it
Loops for a management job often include a round that engineering loops do not, such as a meeting with the product partner or a session with the team. If no time with the engineers is planned, ask for it. Accepting a team you have never spoken to is a risk for both sides.
Interviewing the company for an engineering manager job
Practical guidance for the conversation itself
Who in the loop can answer what
The director or VP you would report to
This is the only interviewer who can speak to why the seat is open, what authority comes with it, the approved headcount and what the first six months are judged on. Spend this slot on The seat, Headcount and First six months. Questions about the day-to-day mood of the team are better put to the people who live it.
The peer managers
Another engineering manager does the same job under the same boss and gains nothing by selling it to you. Ask them about the review cycle, how long hiring takes, what the director is like when a date slips and what new managers get wrong. For the People and Delivery groups, a peer's account is usually the most accurate one you will get.
The engineers you would manage
They are working out whether they want you as their manager, so every question here does double duty. Ask what they want from the next manager, what frustrates them and when they last worked a weekend. Leave pay, headcount and performance cases out of this conversation: they cannot answer, and being asked puts them in an awkward spot.
The product partner
Many loops for this job include the product manager or designer you would work beside. If yours does not, ask the recruiter whether a short call can be added. Hearing how the roadmap gets argued out, from the other side of that argument, shows you a part of the daily job the director can only describe secondhand.
Getting more from each slot
Bring two or three per interviewer
A loop usually leaves you a few minutes at the end of each conversation. Choose the questions only that interviewer can answer and rank them, with the one that could change your decision first. The page is long so that the third interviewer does not hear what the first one heard, unless you mean them to.
Repeat one question on purpose
Pick a question where the truth matters to you, such as how dates are set or who makes the technical calls, and ask it of the director, a peer and an engineer. If the three accounts line up, you can trust the description of the job. If they do not, take the difference back to the hiring manager before you accept, because settling it would become your first assignment.
Asking about your predecessor
You need to know what the previous manager did and how the team took it, and interviewers are rightly careful about discussing a colleague. Two framings help: what the team lost when that manager left, and what the director hopes the next one will change. Either can be answered without criticizing anyone.
Let the questions show how you would manage
The panel is still assessing you while you ask. Questions about open performance cases, overdue promotions and who protects maintenance time show that you know where a manager's week goes. A candidate who asks only about the tech stack sounds like someone applying for a senior engineer job.
Putting the answers together
Separate what you would inherit from what you could change
After the loop, sort your notes into two lists. One holds what comes with the seat and sits outside a manager's reach there, such as who sets dates or whether a departure gets replaced. The other holds problems inside the team, which are what a manager is hired to work on. A long second list is the job, while a long first list deserves another conversation before you say yes.
Go back with follow-ups once there is an offer
Once an offer is out, the hiring manager has the most reason to answer hard questions. Ask for a second conversation on anything left vague: the approved roles, the review cycle you would walk into, the split with the tech lead. If you never met the engineers, ask for that meeting now.
Confirm the scope you were told
Team size, the roles approved for hiring and whether the job includes hands-on coding can drift between the interview and the first week. It is reasonable to send the hiring manager a short note summarizing what you understood and inviting corrections. What an employer will put in writing differs, so ask how they usually handle it.
Weigh the boss as much as the team
A struggling team under a director who tells you the truth and backs your decisions is a fixable assignment. A healthy team under one who sidestepped every direct question is a harder bet. Look back at how the open-cases and missed-date questions were answered, since those are the ones that cost something to answer honestly.
Where candidates for this job go wrong
Asking an engineer's questions
Build times, languages and architecture matter, but they are not what decides whether a manager succeeds. If your whole list could be asked by someone joining as an individual contributor, swap half of it for questions about people, hiring and the product relationship.
Announcing a plan for a team you have not met
It is tempting to answer a described problem with the fix you used at your last company. Engineers on the panel hear that as a manager who has already decided. Ask what has been tried, and keep the proposals until you have had a first round of one-on-ones.
Skipping the uncomfortable ones
Whether someone was passed over, whether a performance case is open, why people left: these feel intrusive in an interview, so candidates leave them out and find the answers in week one. Asked plainly and without pressing for names, they come across as experience, not nosiness.
Taking the title as the job
Engineering manager can mean a tech lead with reports, a full-time people manager, or a coordinator with no say over hiring or pay. The decisions, the headcount and the hands-on split are what define it. Leave the loop able to state each of those three in a sentence.