Engineering leadership interviews test less engineering than most candidates expect. One interview platform that analyzed the questions asked in engineering manager interviews found that almost none of the most common ones tested technical skill: the panel asks about your team, your hiring, your conflicts and what you want next. What changes as you move up is the size of the problem. A manager is asked about people and delivery. A director is asked about managers and the system across teams. A VP is asked about the organization, the strategy and the CEO.
I have held the VP of Engineering seat, at Cox Automotive through a cloud and DevOps transformation across more than 1,000 engineers, and the CTO and CEO seats an engineering leader reports to. I have hired thousands of people. This page sorts the questions by level, says what each one is really asking, and how to answer it. The method behind every answer (find the question under the question, ask one back, answer with one story, close with "did I answer your question?") is in how to prepare for an executive interview.
Key takeaways
- The higher the level, the less the interview tests code and the more it tests the organization: people, then managers, then the company.
- Prepare a story for every line on your resume, and three or four you know cold that carry most questions.
- At every level the panel listens for "I": what you decided, not what the team shipped.
- Know what you want in the next role. It is one of the questions engineering leaders are asked most.
- Expect an AI question about how your teams build software, not only about the product. Current postings ask leaders to define it.
- At VP level, expect the CEO and often the head of product to test how you scale the organization and talk about the business.
How the questions change by level
| Level | What the panel is testing | The story to bring |
|---|---|---|
| Engineering manager | people, delivery, hiring, conflict with product | a team you improved, and a hard conversation you had |
| Director of engineering | managing managers, delivery across teams, measures | a manager you developed or replaced, and a cross-team problem you fixed |
| VP of engineering | organization design, strategy, scaling, the CEO and the board | an organization you scaled or reshaped, and the business result |
Engineering manager questions
How do you handle a low performer on your team?
What they are really asking: will you act, and will you act fairly?
How to answer: one real case: what you saw and how you knew, the conversation, the support and the deadline you set, and the outcome, whether they improved or left. Panels distrust a manager who has never had this conversation.
Tell me about a conflict with product, and how it was resolved.
What they are really asking: can you disagree with a peer and still ship?
How to answer: what each side wanted and why both were reasonable, how you made the trade-off visible (scope, date, quality), who decided, and what you did after. Avoid the version where product was simply wrong.
How do you hire, and what do you look for?
What they are really asking: do you have a bar, and can you explain it?
How to answer: your process in a sentence, the two or three things you screen for and why, and one hire that proved the process right or one that taught you to change it. This is one of the questions engineering managers are asked most often.
If you could do one project over, what would you change?
What they are really asking: can you examine your own judgment?
How to answer: a real project, the decision you would change, what it cost, and what you do differently now. Do not pick a project that failed because of someone else.
Director of engineering questions
How do you manage managers?
What they are really asking: can you lead through other people, or do you go around them?
Ask back first: "How many managers would report to me, and how new are they?"
How to answer: how you set expectations for managers, how you know whether a team is healthy without doing the manager's job, and one manager you developed or moved out, with what changed in the team after.
How do you measure engineering performance?
What they are really asking: do you measure what matters to the business, or what is easy to count?
How to answer: two or three measures you used (delivery, quality, reliability), how you kept them from being gamed, and one decision a measure changed. Tie at least one to a business result.
How do you make sure the engineering decisions your teams make are sound?
What they are really asking: how do you keep technical judgment high once you no longer write the code?
How to answer: the review points you used, who has the final call on what, and one decision you overturned or chose not to overturn, and why.
Tell me about a complex technical initiative you led.
What they are really asking: how do you think, and what did your decisions do for the business?
How to answer: the common miss is describing the system, the technologies and the timeline, until the interviewer stops listening. The panel already believes you can do the work. Tell it as decisions, trade-offs and outcomes: what you chose, what you gave up, and what it did for the business.
How do you run delivery across several teams?
What they are really asking: can you see the system, not just your teams?
How to answer: one cross-team problem (dependencies, a missed launch, a platform everybody needed), what you changed in how teams plan and hand off, and the result in dates or quality.
VP of engineering questions
How would you scale this organization?
What they are really asking: do you have a model for the next size, and will you diagnose before you redesign?
Ask back first: "Where does it hurt today: delivery speed, quality, hiring, or alignment with product?"
How to answer: an organization you grew or reshaped: the size before and after, the structure you chose and why, the layer of managers you added, and what happened to delivery. Then how you would find out what this one needs first.
How are your teams using AI to build software, and how do you know it helps?
What they are really asking: will you lead the change in how engineering works, with judgment? Current postings ask engineering leaders to define the organization's approach to AI-assisted software engineering and to scale the team with it.
Ask back first: "How are your teams using AI today, and what has it changed?"
How to answer: what you introduced, where it helped and where it did not, how you kept quality and security, and the measure you used: cycle time, throughput, defects or cost. A leader who can name where AI did not help is more credible on where it did.
How do you balance speed, quality and technical debt?
What they are really asking: can you make the trade-off in business terms?
How to answer: how you decide how much capacity goes to debt, and one time you argued for paying it down or for leaving it, with the result. A CEO wants to hear the trade-off in dates, money and risk.
How do you work with the CEO and the head of product?
What they are really asking: will you be a partner at the executive table, or the person who explains why it will be late?
How to answer: how you planned with product and reported to the CEO, one disagreement and how it ended, and one time you brought bad news early.
What is important for you in your next role?
What they are really asking: do you want this job, here, and will you stay?
How to answer: be specific and honest: the problem you want to own, the size, the kind of leadership team. Then connect it to what you have heard about their problem. It is one of the most common questions engineering leaders are asked, and a vague answer makes the panel wonder whether you are running from something.
Have an upcoming big interview?
What engineering leader postings are telling you
Read the posting for the question under each line. Current postings for software engineering directors and VPs share these:
| The posting says | The question under it | The story to bring |
|---|---|---|
| Lead the organization through directors and engineering managers | Can you lead through other leaders? | a manager you developed or replaced, and the team after |
| Establish engineering measures: predictability, quality, security, productivity | Will you measure what the business cares about? | a measure you introduced and the decision it changed |
| Ensure scalability, reliability and security of the platform | Will it hold as we grow? | a reliability or scale problem you fixed |
| Define the approach to AI-enabled software engineering | Will you lead the change in how we build? | where AI helped your teams, where it did not, and the number |
| Partner with product and the business on the roadmap | Will you plan with product, or argue with it? | a trade-off you made with product and the result |
| Scale talent and the operating model | Can you build the next version of this organization? | an organization you grew or reshaped |
What changes when you interview for VP of engineering
The VP search is longer and more personal than the ones below it. One VP of engineering described 20 company processes and 99 individual interviews in a single year of searching, and many VP roles are filled through networks before they are posted. Three things follow:
- Start signalling early. Let the people who might hire you know what you are looking for well before you need it.
- Prepare a story for every point on your resume. At this level any line can become a question.
- Expect to meet the CEO more than once, and to be asked how you would talk about engineering to the board.
Questions to ask the panel
- What does the team ship well today, and what does it ship late?
- How are engineering and product planning done together now?
- What would you want different about engineering a year from now?
- How many managers would report to me, and how long have they been managers?
- What is the biggest technical risk the company is carrying?
- Twelve months from now, what will have happened for you to say hiring me was the right call?
Questions people ask
What are the most common engineering manager interview questions?
How you handle a low performer, a conflict with product, how you hire and what you look for, a project you would do over, your management style, and what you want in your next role. Few of the common ones test technical skill.
How do I prepare for an engineering manager interview?
Prepare three or four stories with results: a team you improved, a hard people conversation, a delivery problem you fixed and a hire you made. Practice the follow-ups out loud, and prepare what you want in the next role.
What does a VP of engineering interview look like?
Several conversations with the CEO, the head of product, peers and engineering leaders, focused on organization design, scaling, the trade-offs between speed, quality and debt, and how you work at the executive table.
How is a director of engineering interview different from a manager interview?
A director is tested on managing managers and on delivery across teams: how you develop managers, measure performance and keep technical decisions sound without writing the code.
What questions should I ask in an engineering leadership interview?
How engineering and product plan together, what ships late, what they want different in a year, how experienced the managers are, and what would make hiring you the right call.
Have an upcoming big interview?
See how I can help you prepare for it.
“I’ve often described working with Ken as being shot out of a cannon. The clarity, confidence, and momentum he helps create can fundamentally change the direction of your career.” Karsten Summerall, 5-star Google review