Questions to Ask Director
Questions for a candidate interviewing with a director, whether they would be your manager or sit a level above the role. Covers what the team owns, how decisions get made, constraints, turnover, and what the first ninety days would need to produce.
The questions
Open any question for the note
What does your team own, and where does that ownership stop?
Why ask it
Boundaries are where roles turn out to be smaller than the job description suggested. Ask what sits just outside their remit and who owns it, because that is where you would spend your time negotiating.
Why is this role open?
Why ask it
New headcount, a backfill, and a role vacated twice in two years are different risks. If someone left, ask how long they were in the seat and where they went; the answer is rarely volunteered but is usually given honestly when asked.
Who would I report to, and how long have they been in that seat?
Why ask it
Your direct manager matters more to your daily experience than the company does. A manager appointed last month, or a vacancy above you still being filled, changes what you are actually accepting.
What are you accountable for this year that your own boss is watching?
Why ask it
This gets you the real priority list rather than the strategy slide. Anything not on that list will lose whenever the two conflict, including the work you were hired to do.
How do decisions get made in your area when people disagree?
Why ask it
Look for a named decision-maker and a mechanism. An answer about consensus and alignment with nobody breaking ties usually means decisions stall until someone senior loses patience.
What does the first ninety days look like, and what would tell you it went well?
Why ask it
A director with a specific answer has thought about the role; one who says to come in and see is offering you the job of inventing it. Both are workable, but only one is what most people expect.
How often would we speak, and in what form?
Why ask it
Weekly one-to-ones with the director, a fortnightly skip-level, or contact only in a monthly review are very different amounts of access. Ask what has actually happened with their reports in the last month.
What are the constraints on this team: budget, headcount, dependencies?
Why ask it
Ambition is cheap and constraints are the story. Ask which of the three bites hardest, since a team with a mandate and no budget is a job about persuasion rather than delivery.
How much of the work is planned, and how much arrives unexpectedly?
Why ask it
Ask for a rough split rather than a description. Teams where half the quarter is unplanned are usually absorbing failures elsewhere in the organisation, and that becomes your job whether or not it is in the posting.
What has your team tried that did not work?
Why ask it
You want a specific initiative, what it cost, and what changed afterwards. A director who cannot name a failure in the last two years is either new or telling you that nothing gets examined.
Which other team do you depend on most, and how is that relationship?
Why ask it
Cross-team friction is the most common hidden cost in a senior role. Candid answers name the team and the specific friction; smooth answers about great partnerships usually mean you will discover it in month two.
How do you handle it when something needs to be stopped?
Why ask it
Ask for the last thing they cancelled. Organisations that cannot stop work accumulate commitments until nothing finishes, and directors who have never killed a project are rarely able to protect your focus.
How is performance reviewed here, and when is the next cycle?
Why ask it
Timing matters practically: joining just after a cycle can mean eighteen months before your first formal review or raise. Ask what the process weighs and who else has a say.
Who at my level has been promoted recently, and what did that take?
Why ask it
This converts vague growth talk into evidence. A named person with a timeline is a working ladder; a philosophy with no recent example means advancement depends on circumstances nobody controls.
What has turnover been like on this team over the last two years?
Why ask it
Ask how many people left and where they went. Departures to bigger roles elsewhere read very differently from departures to the same role at a competitor, and a director who has not thought about the pattern has not looked.
What would you want me to change, and what should I leave alone?
Why ask it
The second half is the useful one. New hires most often damage their standing by improving something the team is quietly proud of, and this question surfaces it before you arrive.
How do you shield the team when priorities shift above you?
Why ask it
Ask for the last time it happened and what they did. Directors who absorb the change and re-plan protect their people; directors who pass it straight down without adjusting anything produce the churn you would inherit.
What is the part of this job you would not put in the posting?
Why ask it
Asked plainly, this often gets a real answer: a difficult stakeholder, a reporting burden, a system nobody wants to maintain. If they claim there is nothing, you have learned how candid the working relationship will be.
What would make you say in a year that this hire worked?
Why ask it
The answer is the actual job description. Compare it to what you were told in the earlier interviews, because a mismatch between the two is worth resolving before you accept rather than after.
Is there anything about my background you are unsure about?
Why ask it
The one question that can still change the outcome. It gives you a chance to answer the objection while you are in the room, and their willingness to say it out loud tells you how feedback works on this team.
Interviewing with a director
Practical guidance for the conversation itself
Match the question to the seat
If the director would be your manager
Prioritise the one-to-one cadence, the first ninety days, what they would want changed, and how they handle shifting priorities. You are interviewing a working relationship, not a company.
If the director is a level above the role
Prioritise what they are accountable for, how decisions get resolved, and which other teams they depend on. Skip the day-to-day questions, which they will answer from a distance and get wrong.
Save two questions for the end
The unposted part of the job and the question about their reservations both land best when the conversation has already gone well. Asked early, they read as defensive.
Verify what you are told
- Ask a prospective peer the same question about unplanned work, and compare the two answers.
- Ask the recruiter when the last person in this role left, then ask the director where they went.
- Ask two different interviewers what success in the first year looks like. Divergent answers mean the role is not agreed internally.
- Look up whether the team has been reorganised recently, and ask what problem that was solving.
- If a promotion path is described, ask for the name and timeline of the last person who took it.
What to avoid
Asking what you could have looked up
Questions about the company's products, funding, or public strategy waste the one slot where you get to interview them. Ask about the things that are not written down.
Asking for a leadership philosophy
It reliably produces a prepared paragraph. Asking how they handled a specific situation, the last cancelled project, the last shifted priority, gets the same information in a form you can check.
Leading with compensation and title
Both are worth resolving, but with the recruiter rather than in the middle of a conversation with the person deciding whether they want you.
Asking only friendly questions
Turnover, constraints, and what did not work are the questions a serious candidate asks, and directors generally read them as a good sign. A candidate with no hard questions looks like one who has not decided whether they want the job.