Director of Engineering Interview: Rounds and Questions

A director of engineering interview is the first loop in which nobody checks whether you can manage a team. That is assumed. What the company is deciding is whether to hand you sixty or a hundred people, several managers, a budget, and a seat in the room where engineering argues with product and finance.
Senior managers going for their first director role tend to prepare by sharpening the stories that got them the last job: the low performer turned round, the project rescued. Those stories are one level too low. A director who answers every question from inside a single team sounds like a strong manager, and that is the level they are offered. Below: how the role differs, the rounds you are likely to meet, thirty example questions in three groups, the presentation, the reference stage, and the mistakes.
Director against senior manager
The jump is from managing engineers to managing managers, and it changes what counts as your work.
- Your output is other people's judgment. A senior manager can still fix a team by stepping in. A director with five teams cannot, and stepping in undermines the manager whose team it is. You are graded on the managers you hired, grew and removed.
- You own the shape of the organisation. Which teams exist, what each owns, where the boundaries fall, how many people each gets. A senior manager is given that shape; a director proposes it and defends it.
- You carry a budget and a plan. Headcount, vendor spend, a roadmap that has to survive a planning cycle and a reforecast.
- Your peers are not engineers. Product, design, finance, sales, legal. Much of the job is trading with them.
- You represent engineering upward. To a vice president or a chief technology officer, and sometimes to a board, in their language.
Titles vary. At a company of eighty people "director" may mean managing two teams directly; at a large one it may mean an organisation of several hundred. Ask the recruiter for the number of reports, the number of managers among them, and who the role reports to. If the scope is one or two teams, prepare from the engineering manager interview guide as well.
The loop, including executive and peer rounds
Companies do not publish director loops, and the loop is often built for the search. The descriptions that exist come from people who run them.
Will Larson, writing in 2020 about interviewing senior engineering leaders, describes processes of six to twelve interviews made from a recognisable set of parts: a walk through your career role by role, deep dives on topics such as hiring and organisation structure, a presentation to a group, a group question-and-answer session, a working session on a real problem with your would-be manager or peers, fit conversations with stakeholders including future direct reports, and references. His argument is that good loops make a candidate demonstrate a skill, for example by critiquing a badly written set of team goals, and do not settle for a description of it.
An account from November 2026 by the recruiting firm KORE1 (kore1.com) describes a tighter version: four rounds over about two weeks, a conversation with the vice president who owns the hire, a panel that includes an engineering manager who would report to you, a round working through exhibits (a sample organisation chart, a delivery forecast for four teams, a headcount request) with finance present, and a final round with the person the director will depend on most.
Between those two you can expect, in some mix:
- The hiring executive. Usually first and last. Scope, philosophy, and whether they can picture giving you the problem they have.
- Peers. A product director, another engineering director, sometimes design or data. They are asking whether you will be easy to trade with and honest about dates.
- Future reports. One or two managers, occasionally a staff engineer. They are asking whether they would want to work for you. Treat this as a full interview.
- A technical conversation. Rarely a whiteboard design at this level. More often architecture judgment: a system you were accountable for, what you would fund, how you decide between rebuild and repair.
- A presentation or working session. Covered below.
- The executive above the hiring manager. A short conversation about business sense and presence.
The questions fall into three groups whoever asks them.
Organisation design and managing managers
- How is your current organisation structured, and why that way and not another?
- Tell me about a reorganisation you led. What triggered it, and what did it cost?
- You inherit five teams, two of which overlap. Walk me through your first sixty days.
- Tell me about a manager on your staff who was not working out. How did you know, and what did you do?
- How do you tell a good manager from a team that is merely quiet?
- Describe how you grew a senior engineer or tech lead into a manager. What did you get wrong?
- How do you run your staff meeting, and what is it for?
- What do you ask in a skip-level conversation, and what have you learned from one that changed a decision?
- How do you decide the ratio of managers to engineers, and of senior to junior engineers?
- Tell me about the most senior person you have hired. How did you close them, and how did the first six months go?
What they listen for. A model of the organisation that you can explain in two minutes, and decisions that follow from it. On question 1, "it was like that when I arrived" is honest and not enough; say what you would change and why you have or have not. On the manager questions, the panel wants evidence that you act on managers as firmly as you once acted on engineers: a clear expectation, a time limit, a decision. Directors who protect a weak manager for a year are common, and every interviewer has worked under one.
The reorganisation question deserves a prepared answer with its costs in it: who left, which project slipped, how long before the new shape paid back.
Strategy and the business
- What does your organisation cost per year, and what does the company get for it?
- Tell me about a time you said no to something the chief executive or a major customer wanted.
- How do you divide capacity between new features, reliability and paying down old decisions? Who agreed to that split?
- Describe a build-or-buy decision you owned. What was the number that settled it?
- You are asked to cut ten per cent of your budget. How do you decide where?
- Product wants a date you believe is impossible. What do you do in the meeting, and afterwards?
- Which technical bet from the last three years would you take back?
- How do you explain technical debt to a finance director?
- What would you want to know about our business before deciding what to change here?
- Where should engineering leadership in a company like ours spend less attention than it does?
What they listen for. Whether you talk about engineering as a part of a business. A director should know roughly what their organisation costs, what it earns or protects, and what a month of delay is worth. You do not need exact figures from a past employer; you need to show that you worked with them. Question 15 is asked more often than candidates expect, and the weak answer spreads the cut evenly so that nobody is upset. The stronger one names what would stop.
For candidates whose next step after this role is a vice president or chief technology officer post, the interview with Adelina Chalmers on becoming a CTO is a good account of how executives outside engineering hear technical arguments.
Delivery at scale and incidents
- Tell me about a programme across several teams that was late. When did you know, and who did you tell?
- How do you know the state of delivery across your organisation without attending every stand-up?
- Describe your planning cycle. What happens when the plan meets the second month?
- Tell me about the worst incident on your watch. What was your own role in the first hour?
- After that incident, what changed that is still in place today?
- A team has missed three commitments in a row. Their manager says it is under control. What do you do?
- How do you handle a dependency on another director's team that is not being met?
- What do you measure, and which measure have you stopped trusting?
- How do you set quality and on-call expectations across teams with different habits?
- Tell me about a launch you delayed. Who disagreed?
What they listen for. Mechanisms that work when you are not in the room. The senior manager's answer to question 22 is "I stay close to the work". The director's answer names the two or three signals they read weekly, what a bad week looks like in them, and what they do next. On incidents, the panel is checking that you led the response and did not take over the keyboard: who you put in charge, what you told the business and when, and what you funded afterwards.
Question 26 tests the hardest habit of the job, which is inspecting without removing the manager's authority. Describe what you would ask to see, the time you would give, and the point at which you would step in.
These questions are examples written for practice, not leaked questions from any company.
The presentation round
Many director loops include a presentation, and Larson notes that the usual prompt is a plan for your first ninety days. Others ask you to present a past transformation, or to respond to a written scenario sent a few days ahead.
A ninety-day plan is a test of restraint. The panel knows you cannot know their problems yet, so a plan full of changes shows you would act before understanding. A sound shape is this:
- Days 1 to 30: learn. Who you would talk to and what you would ask each. What you would read: the organisation chart, the roadmap, the last three incident reviews, attrition, the budget. The decisions you would refuse to make yet.
- Days 31 to 60: diagnose. How you would write up what you found and test it with your manager and your staff. One or two small, safe fixes that earn trust.
- Days 61 to 90: commit. The two or three priorities you would propose, what each costs, and what you would stop.
State your assumptions about their situation on the first slide and invite correction. The best version of this round turns into a working conversation by the tenth minute, which is the signal the panel is looking for. Keep to the time you were given; an executive who overruns a slot in an interview will be assumed to do it in a board meeting.
If the exercise is live, such as the exhibits round described above, think aloud and ask for the missing number before you decide. Asking what a team's attrition was before judging its forecast is the job, not a delay.
References and back-channel
At this level references are part of the assessment, not a formality after it. Expect to be asked for former managers who will take a call. The recruiting firm quoted earlier also recommends that the hiring side speak to a former direct report, and treats that call as more informative than a reference from an old vice president.
Expect back-channel checks too. Larson calls them biased but necessary for executive hires. In practice somebody on the panel knows somebody who worked with you, and they will ask.
What you can do:
- Choose references who saw the work the role needs. A manager you reported to as a director-level leader, a peer in product, a manager who reported to you.
- Brief them. Tell each what the role is and which parts of your work together are relevant. This is normal and they will thank you.
- Tell the hiring manager what they will hear. If there is a difficult chapter, such as a reorganisation that went badly or a team that was cut, raise it yourself in the loop with what you learned. A surprise in a reference call does more harm than the event.
- Ask for confidentiality where you need it. If your current employer does not know you are looking, say so plainly and ask that nobody there is contacted before an offer.
Mistakes
- Answering as a manager of one team. If a story has five engineers in it and no managers, it is the wrong story.
- No numbers. Organisation size, budget, attrition, delivery against plan. A director who cannot quote their own organisation's figures sounds like a visitor in it.
- Hero stories. "I stepped in and fixed it" raises the question of what your managers were doing.
- Speaking ill of peers. Product was unreasonable, finance did not understand. The peer interviewers hear how you will describe them next year.
- A philosophy with no scar. Every candidate believes in autonomy and accountability. Tell the panel when your belief failed and what you changed.
- Treating future reports as an audience. Managers on the panel have a real say. Ask them what they need from a director and listen to the answer.
- Skipping the questions you should ask. Why the role is open, what happened to the last person in it, how success will be judged after a year, and what the executive would want different in six months.
If this would be your first time managing managers, read how to move from individual contributor to manager again with your own staff in mind; the transition your managers went through is now your job to coach.
Rehearsal for this loop needs a listener who has sat on the other side of it. Colleagues are too close to your stories to hear what is missing, and the presentation in particular improves most when someone who has hired directors interrupts it. A session with one of the leadership coaches is one way to get that; look for a profile that shows experience running an engineering organisation.
Where coaching fits
The two things worth rehearsing with another person are the presentation and the executive conversation, because both depend on how you sound under interruption. On techinterview.coach, 20 of the 40 coaches list leadership coaching as of November 2026, and the coaches' own titles include engineering managers, a VP of Engineering and an executive coach; the leadership coaching page lists them, and a profile will tell you whether a coach has hired at director level. For a first spoken run of your stories, the practice interview offers a behavioural round with an AI interviewer and a written recap. It is free; sign in to start.
Related guides
- 50 engineering manager interview questions: the level below, useful for the people-management basics a director is assumed to have.
- The engineering manager interview: the loop for one or two teams, if the "director" title is small at your target company.
- Principal engineer interview: the individual-contributor loop at similar seniority.
- How to become a CTO: how technical leaders are heard by the rest of the executive team.
- Moving from individual contributor to manager: the transition you will be coaching your own managers through.
- Tech salary negotiation: for the offer stage, where level and scope are still on the table.