Questions to Ask a Director in an Interview
Questions for the part of the interview where you get to ask. Aimed at a director or senior hiring manager, they test scope, budget, decision rights, how the team is doing, and what would count as failure.
The questions
Open any question for the note
What made you open this role?
Why ask it
New headcount, a resignation, and a reorganization each carry different expectations. If it is a backfill, the natural follow-up is why the last person left, and how readily that is answered matters.
Who has been doing this work in the meantime?
Why ask it
This shows whether you are inheriting a working function or assembling one. Work split across three people for a year usually arrives with three incompatible sets of expectations.
What does the first ninety days need to produce?
Why ask it
A director who has thought about the role can name something concrete. If they cannot, the definition of success will be set after you start, quite possibly by someone else.
What would you want to be different in a year that is not in the job description?
Why ask it
This surfaces the unwritten mandate: a team to rebuild, a stakeholder to win back, a process nobody will own. It is usually what you will actually be judged on.
How will my performance be assessed at the end of the first year?
Why ask it
Push past values language to the mechanism: who writes the review, what evidence they use, and whether the numbers involved are things you can influence.
Which decisions would sit with me, and which come back to you?
Why ask it
Scope stated as a title means little; scope stated as decisions means a lot. Ask for two examples of each and the real level of the job becomes clear.
What budget and headcount come with this?
Why ask it
A role described as strategic with neither is an advisory job. The figure, or the reluctance to give one, tells you how much of the mandate exists on paper only.
Who else has to agree before something I propose can go ahead?
Why ask it
This maps the veto points. Roles fail more often on unnamed approvers than on the work, and most directors will name them when asked this directly.
How much of your week goes to this team?
Why ask it
A director spread across six teams will not be available during your first difficult month. The answer sets realistic expectations for how much cover you can count on.
How would you describe your management style, and how does someone get the best out of you?
Why ask it
Asking how to work with them rather than how they work draws a franker answer, often including how they prefer to receive bad news.
What has this team struggled with over the past year?
Why ask it
A direct question about difficulty. An answer claiming nothing has been hard means either a very short tenure or an unwillingness to be candid, and both are worth knowing.
Who has done well on this team, and what did they do differently?
Why ask it
You learn which behavior actually gets rewarded here, which is frequently not what the competency framework describes.
Has anyone in this role or on this team not worked out, and what happened?
Why ask it
One of the most informative questions available and one of the least asked. How they narrate someone else's departure is roughly how they would narrate yours.
What has turnover on this team looked like?
Why ask it
Sustained churn under one director says something about the director. Listen for whether the explanation names structural causes or blames the individuals who left.
How does work reach this team, and can you decline it?
Why ask it
Teams with no control over intake are permanently behind. The answer shows whether prioritization is real or whether everything that arrives is treated as urgent.
Which other team do you depend on most, and how is that relationship right now?
Why ask it
Naming a specific interface rather than asking about collaboration in the abstract gets you an honest read on the friction you would be inheriting.
How do promotions actually happen at this level?
Why ask it
Ask for the most recent real example rather than the policy. A director who cannot recall one on their own team is telling you where the ceiling sits.
What is changing in the organization over the next year that would affect this role?
Why ask it
Restructures, funding cycles, and leadership changes are known internally long before they are announced. A pause before the answer is itself worth registering.
What would make you conclude this hire was a mistake?
Why ask it
Uncomfortable to ask and unusually revealing. You get their real failure modes and can judge honestly whether any of them describe you.
What has kept you here?
Why ask it
A closing question that invites a personal answer. If it reaches only for compensation or inertia, weigh that against everything encouraging said earlier in the conversation.
Using your questions well
Practical guidance for the conversation itself
Which questions belong at which stage
First conversation
Stick to why the role exists, what the first ninety days require, and who has been covering the work. These are easy to answer and give you the frame for everything after.
Second or third conversation
This is where scope, budget, decision rights, and approvals belong. By now the director has an interest in you and is more willing to be specific about constraints.
Final conversation or offer stage
Save turnover, departures, promotion examples, and what would make the hire a mistake for the end. Your leverage is highest and a candid answer costs them less.
How to read what you hear
- A specific example beats a description of a principle. Ask for the last time it happened.
- Watch for the shift from we to they when they talk about other teams; it locates the friction.
- If two interviewers describe the role's priorities differently, that disagreement is the job.
- Listen for what is quantified. Budget, headcount, and timelines get vague when they are unresolved.
- Note anything they will not answer. A declined question is data, and you can ask again later.
- Take one minute after the call to write down the answer that surprised you most.
Where candidates lose ground
Asking things the job posting already answered
It reads as unpreparedness and burns a question you could have spent on scope or budget. If you want to test the posting, quote it and ask what it means in practice.
Only asking about growth
Questions solely about your progression suggest you are treating the role as a step. Mix them with questions about the team's actual problems, which is what the director is worried about.
Accepting an abstract answer
When you get culture language in reply to a question about decisions or budget, follow up once with a request for an example. One polite follow-up is expected; three become an interrogation.
Bringing a list of fifteen
You will get through four or five. Choose the ones whose answers would change your decision and hold the rest for a later round or a reference call.