Questions to Ask a Director in an Interview
Questions to ask a director in an interview, for the part where it is your turn to ask. The director may be the person you would report to or your boss's boss, so these 71 questions cover both. They open with the staples (what success looks like, the biggest challenges, the first 90 days, why the role exists) and go on to scope and sign-off, the director as a boss, the team, where the department and the job are heading, and how to close. When the director sits a level above the hiring manager, begin with the run in The director group written for that interview, then The future.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
The role
What would success in this role look like after the first year?
Why ask it
A director who has thought about the hire can name two or three results: a number moved, a project delivered, a problem they no longer hear about. Write down their exact words, since they are the closest thing to a first review you can get before you start. If the answer stays general, ask what the last person in the job did that they were pleased with.
What are the biggest challenges someone in this role will face?
Why ask it
Notice which kind of difficulty comes up first: the workload, a system, a customer or a person. If the reply is hesitant, one follow-up about who the role has to win over is fair. Then say briefly how you have dealt with something similar, while the problem is still on their mind.
What would you expect from me in the first 90 days?
Why ask it
Some directors want a new hire listening for a quarter, and others want a visible result by week six. Either can work, but you need to know which one you would be agreeing to. If the director sits above your manager, put the same question to the manager and compare the two answers.
What problem is this hire meant to solve for you?
Why ask it
The posting lists duties. This asks why the director wanted the headcount in the first place: a backlog, a client at risk, a launch date. Whatever they name is likely to be what you are judged on first, and if the answer is only that someone left, ask what that person left unfinished.
Is this a new role, or would I be replacing someone?
Why ask it
If the role is new, nobody has yet agreed what it covers, and settling that would be part of the job. If you would be replacing someone, ask how long they stayed and where they went: a promotion and a quiet exit after eight months are different things to inherit. Leave it out if the recruiter has already told you.
What does a typical week look like in this role?
Why ask it
Ask about last week in particular: which meetings were fixed, how much time went on planned work and how much on whatever came in. A director a level above the role may know it only in outline. That is useful too, because it shows how closely they follow the work.
How will my performance be measured, and who does the measuring?
Why ask it
You are after the measures by name and the person who writes the review. Where the director sets the targets and someone else scores you against them, ask how often the two of them compare notes. Ask when the review cycle runs as well, which tells you when pay is next looked at.
Who has been doing this work in the meantime?
Why ask it
You find out whether you would inherit a working function or have to assemble one. If the work has been split across several people, ask what each of them expects to keep, because that is where the handover gets awkward.
What is the first piece of work you would hand me?
Why ask it
A named project or problem means the director has pictured you in the seat. It is often the thing that has waited longest for an owner, so ask how long it has been waiting and why.
What would you want to be different in a year that is not in the job description?
Why ask it
The unwritten part of the job tends to come out here: a team to rebuild, a stakeholder to win back, a process nobody will own. Take it seriously, because it can weigh more in your first review than anything in the posting.
Where does this hire sit among your priorities for the year?
Why ask it
Nobody gives ten priorities equal attention. If this role serves one of the top two or three, expect a hearing when you need budget or a decision. If it sits further down, plan on making your own case each time.
How has this role changed since you last hired for it?
Why ask it
Postings get reused after the job has moved on, so the director's account is the current version. The differences from the posting are often what the last person learned the hard way. Skip it if the role is new.
What would I need to learn fastest to be useful here?
Why ask it
Their answer names the real barrier to entry: a system, a customer base, a set of regulations, the internal politics. It also shows what the director assumes you do not know, and you can correct that on the spot if they are wrong.
Whose work depends on this role being done well?
Why ask it
These are the people who will praise you or complain about you to the director. If most of them sit outside the department, you would be serving people your own manager cannot overrule.
Scope
Can you give me an example of a decision I could make without checking with you?
Why ask it
Scope stated as a title means little, and an example shows the real level of the job. Then ask for one that would have to come back to them. If both examples are small, so is the role, whatever it is called.
How much could I spend before it needed your approval?
Why ask it
Even a modest figure tells you how far the trust extends. If every purchase, contract and hire goes up the line, the role carries responsibility without the means, and it is fair to ask how long those approvals usually take.
Who else has to agree before something I propose can go ahead?
Why ask it
This is a request for the veto points by name: finance, legal, a peer director, a long-standing client. Write them down. An approver nobody mentioned at interview is a hard thing to discover in your second month.
How does work reach this team, and can you decline it?
Why ask it
If requests arrive from anyone and nothing can be refused, the team's priorities are set by whoever asks loudest. A director who can describe the last request they turned down has a working filter, and you would be behind it.
Would I see the budget and forecast behind my targets, or only the targets?
Why ask it
What you are shown tells you how far you are trusted to reason for yourself. Hitting a number without seeing how it was built means being managed by instruction, which suits some people and frustrates others.
Does anyone else think part of this job is theirs?
Why ask it
Sometimes a peer covered the work during the vacancy and liked it, or another team has always claimed a piece of it. Either way, some of your scope would have to be won back. Ask how the director would settle it if you and that person disagreed.
If the first year went well, what would you add to this role?
Why ask it
A quick answer, such as a second product line, a direct report or a region, means they have pictured your second year. If they say the role is what it is, you have been told it is not expected to grow, which matters if you were counting on that.
The director
How would you describe your leadership style?
Why ask it
Most people answer with a label such as hands-off, collaborative or direct, and the label alone tells you little. Follow it by asking about the last time that style was tested, for instance when a deadline slipped or two of their people disagreed. What they did then is the style you would be working under.
How does someone on your team get the best out of you?
Why ask it
Where the style question gets a label, this one gets habits: how much notice they want, whether they read long messages, how they like to hear that something has gone wrong. Note the last of those especially.
How do you give feedback to your team, and how often?
Why ask it
Listen for a routine: regular one-to-ones, comments on the work as it happens, or a formal review once or twice a year. If you would report to one of their managers, ask when feedback would come from the director directly. If the answer is that their door is always open, it is probably left to you to ask.
How much of your week goes to this team?
Why ask it
Someone running six teams is unlikely to be on hand during your first difficult month. Take the answer as the amount of cover you can count on, and ask who you would go to when they are not available.
How did you come to lead this department?
Why ask it
Whether they were promoted from inside, moved across from another function or hired from outside shapes what they know in detail and what they take on trust. Someone who once did your job is likely to have firm views on how it should be done.
Who do you report to, and how closely do they follow this team's work?
Why ask it
A boss who reads the team's weekly numbers is likely to reach past the director to you sooner or later. One who rarely looks leaves the director free to run things, and leaves the team relying on the director to speak up for it.
What do you get involved in yourself, and what do you leave to your managers?
Why ask it
Some directors read every draft and others appear at quarter end. If the work they like to stay close to is the work you would be doing, you would have two bosses in practice, and it is better to know that before you start.
How often do you talk with the people who report to your managers?
Why ask it
For when the director sits a level above the role. Regular skip-level conversations mean there is a route to them if things go wrong with your manager. If the only contact is an annual all-hands, their picture of the team comes through one person.
What part do you play in the hiring decision at this stage?
Why ask it
When your boss's boss joins late in the process, the meeting may be a final approval, a real second opinion or a courtesy. Knowing which tells you how much weight this hour carries, and whether your questions about scope belong here or back with the hiring manager.
How did you and the hiring manager settle on what this role should be?
Why ask it
You learn whose idea the hire was: the director who argued for the headcount or the manager who designed the job. Where their two descriptions differ, ask which one your first review would follow.
What would you want to hear from me directly, and what should go through my manager?
Why ask it
Only for a director you would not report to. Some want a line to everyone in the department, and others treat going around the manager as a breach. Having the rule stated before you start keeps you from offending either of them in your first month.
How long has the manager of this team been in that job?
Why ask it
A manager who is new to the team is still earning the director's confidence, and that would shape your first year as well. Keep the tone neutral, as a question about the team's history, because you are asking about someone in front of their boss.
When you and the team's manager disagree about priorities, what happens?
Why ask it
Whatever the two of them settle on, you would be the one carrying it out. An example where the manager's view held suggests the person you report to has real authority. With no such example, expect instructions to arrive from both levels.
When did someone on your team last change your mind?
Why ask it
You are asking whether disagreement goes anywhere. A recent example with a named decision suggests pushing back is safe. A long pause, or a story from years ago, suggests decisions mostly travel one way.
What is the hardest call you have had to make in this job?
Why ask it
The story they choose shows what they count as hard: letting someone go, stopping a project, telling their own boss no. Listen for whether they mention what it cost other people or only what it cost them.
What do you want to have built here before you move on?
Why ask it
A gentler way of asking how long they plan to stay. Unfinished plans for the department suggest they will be around to back you. A vague answer is worth weighing, since the person hiring you is a large part of the job you would be accepting.
What has kept you here?
Why ask it
Best asked late, once the formal part is over, because it invites a personal answer. If it reaches only for pay or habit, weigh that against everything encouraging said earlier in the conversation.
The team
How is the team structured, and who would I report to day to day?
Why ask it
Get names and reporting lines, including whether a manager sits between you and the director. If one does and you have not met them, ask to before any offer, since they would shape your days more than the director would. A line that is dotted, shared or still to be decided deserves a second question.
How would you describe the culture on your team?
Why ask it
The adjectives will be pleasant ones, so ask for the behavior behind them: what happens when someone misses a deadline, who speaks up in meetings, how a recent mistake was handled. Put the same question to a team member if you get the chance. Where the two accounts differ, give more weight to the one from the person who works inside it.
What do the people who do well on your team have in common?
Why ask it
This is the director's picture of a good hire, given without the awkwardness of describing you. Notice whether the traits are about the work, such as raising problems early or finishing things, or about temperament. If one of them is a real strength of yours, give a short example before the conversation moves on.
What has this team struggled with over the past year?
Why ask it
Ask it plainly and wait. If nothing has been hard, either they have not been in the job long or they are not going to be candid with a candidate, and it helps to know which before you rely on the rest of what they say.
Who on this team would you least want to lose, and why?
Why ask it
The reason shows which behavior this director values in practice, and it may not be what the competency framework lists. Notice whether it is results, judgment, or being the one who never causes trouble.
Has anyone in this role or on this team not worked out, and what happened?
Why ask it
The way the story is told matters as much as the facts. A director who describes a former colleague fairly, including what the company got wrong, would probably describe you fairly too. One who puts all of it on the person has shown you how a bad year here would be remembered.
How long have the people on this team been here?
Why ask it
Tenure is turnover seen from the other side, and easier to answer without getting defensive. If nearly everyone arrived in the last year, the team was either just built or just emptied, so ask which.
Where does this team's work get stuck waiting on another department?
Why ask it
Asking where work gets stuck, not how collaboration is going, gets you a specific handoff. Ask how long the last delay ran and who sorted it out, because that is the person you would be calling.
What does the team do well that the rest of the company does not see?
Why ask it
Answering this takes someone who has been watching the work and not only the dashboard. You also learn what the team is proud of, which is worth knowing before you suggest changing anything.
What skills is the team short of right now?
Why ask it
This is the gap you would be hired into, and it may not be the one in the posting. If you have the missing skill, give an example straight away. If you do not, it is better to hear it now than in month three.
Who joined the team most recently, and how did their first few months go?
Why ask it
The latest hire is the nearest thing to a forecast of your own start. Listen for what was set up for them and what they had to work out alone.
How does the team find out about decisions made above it?
Why ask it
The route matters: a weekly meeting, a note from the director, or the grapevine. A team that learns of a reorganization from another department first has little reason to trust the next announcement.
What hours does the team keep, and how often are people in the office?
Why ask it
Policy and practice can differ, so ask what the team did last month: which days people came in, how late messages were answered, what a busy stretch looked like. Asked in a matter-of-fact way it comes across as planning. If you have a fixed constraint, you can raise it here or hold it for the offer, but do not leave it until after you accept.
What happens on this team when there is more work than people?
Why ask it
The honest answers are that deadlines move, quality slips or people work weekends. Each one tells you what the director protects when forced to choose. Ask about the last time it happened.
What do you count on the manager of this team for most?
Why ask it
Another one for a director who is your manager's boss. The answer shows how your future manager stands with theirs: trusted with decisions, or relied on mainly to pass things along. Skip it if the director would manage you directly.
The future
What is changing in the organization over the next year that would affect this role?
Why ask it
Restructures, funding rounds and leadership changes are often known inside well before they are announced, and the director may not be free to say. A careful or partial answer still tells you something is moving, so do not press for detail they cannot give.
What are the department's goals for the coming year, and who set them?
Why ask it
The goals tell you what the work will be. Who set them tells you whether the director shaped the targets or was handed a number, and a number handed down without discussion is one they may not fully believe in.
How does this department's work show up in the company's results?
Why ask it
Someone who can trace the line from the team's output to revenue, cost or risk has probably had to defend the budget before. If the link is vague, the team's value is being taken on trust, which holds until someone new starts asking.
What happened to this department the last time the company had to cut costs?
Why ask it
History is a better guide than reassurance. Whether the team lost people, lost projects or was left alone shows how it is valued, and the way the director tells it shows whether they argued for their people.
What do you expect to be different about this department in three years?
Why ask it
It might be larger, smaller, merged with another group or partly automated. Whatever they describe, ask where someone hired now would fit in it, and notice whether this role is near the center of the plan or at its edge.
Which competitor or outside change concerns you most?
Why ask it
A specific answer, such as a rival's pricing, a new regulation or a new tool, shows how far they look up from the day-to-day. It also gives you something to read up on before the next round.
When did you last put someone forward for promotion, and what happened?
Why ask it
A promotion policy says what should happen. This asks what this director has done with it: a recent example tells you what the case rested on and who else had to agree. No example at all tells you where the ceiling sits on this team.
What have people who held this role gone on to do?
Why ask it
Promoted, moved sideways or left the company: the pattern is the real career path, whatever the framework says. If nobody has stayed long enough to go anywhere, that is an answer too.
What training or development has someone on your team had this year?
Why ask it
Ask for what was approved and paid for, not what the policy allows. A course, a conference or a stretch project with cover arranged shows that the budget exists and that this director signs it off.
Closing
Do you have any reservations about my experience that I could address now?
Why ask it
A doubt left unspoken gets discussed after you have gone, with nobody there to answer it. If they name a gap, respond briefly with one piece of evidence and do not argue the point. If they say there is nothing, accept that and move on.
What would make you conclude this hire was a mistake?
Why ask it
It is uncomfortable to ask, so save it for a conversation that has been frank so far. What you get is their own list of ways the hire could fail, and you can judge honestly whether any of them describe you.
Is anyone inside the company being considered for this role?
Why ask it
An internal candidate changes the odds, and it changes the job if you get it: you may end up working beside, or managing, the person who was passed over. Ask it plainly, without edge, and accept a short answer.
Who would I work with most closely, and could I speak to them before deciding?
Why ask it
The request matters as much as the description. Being offered the conversation readily suggests the director is confident about what that colleague will say. If the answer is no, ask why: there may be a simple reason, such as a confidential search.
What are the next steps, and when should I expect to hear?
Why ask it
Ask it even if the recruiter has told you, because the director's version shows how settled the process is. Try to leave with a date or a week, and with the name of whoever will be in touch. That gives you a fair point at which to follow up.
What is left to decide before you can make an offer?
Why ask it
One answer covers who else has a say, whether more rounds are coming and whether the budget for the hire is signed off. If that approval is still pending, treat any timeline you are given as a hope.
When do you need someone to start, and what is driving that date?
Why ask it
The driver tells you more than the date: a project launch, a departure, a budget that lapses at year end. It also tells you how much room there is for a notice period before you come to negotiate.
What should I read or look at before we next speak?
Why ask it
It signals that you intend to prepare, and what they point you to shows what they think matters: the annual report, the product itself, a competitor. Follow through, and mention what you found in the next conversation.
Is there anything I have not asked that I should know before deciding?
Why ask it
This hands them the floor for whatever they have been waiting to mention, good or bad. Leave a real silence after asking. What is said into it can be the most useful answer of the interview.
Using your questions well
Practical guidance for the conversation itself
Which questions belong at which stage
First conversation
Stay near the top of The role group: what success looks like after a year, what the first 90 days should hold, and what problem the hire is meant to solve. These are easy to answer and they frame everything that comes after. Whatever the round, end by asking about next steps.
Second or third conversation
This is where Scope belongs: what you could decide and spend, who else has to approve, and what you would be shown. A director who has already given you two conversations has more reason to be specific about constraints. One or two questions from The director group fit here as well, starting with leadership style and how they give feedback.
Final conversation or offer stage
Save tenure, departures, the last promotion, your own reservations question and what would make the hire a mistake for the end, along with the rest of the Closing group. By then they have decided they want you, or nearly, and a candid answer costs them less.
When the director is your boss's boss
Spend the time on what only they can answer: The future group, their part in the hiring decision, what they count on your manager for, what they would want to hear from you directly, and what they stay close to themselves. Leave tools and schedules for the hiring manager, then compare the two accounts of the role.
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 often marks where the friction is.
- If two interviewers describe the role's priorities differently, say so and ask about it. You would be the one working between them.
- Listen for what is quantified. Budget, headcount and timelines tend to get vague when they are unresolved.
- Note anything they will not answer. There may be a good reason, and you can ask again at offer stage.
- 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 uses up a question you could have spent on scope or the team. If you want to test the posting, quote it and ask what it means in practice.
Only asking about growth
Questions solely about your own progression can suggest you are treating the role as a step. Mix them with questions about the team's actual problems, which is closer to what the director is worried about.
Accepting an abstract answer
When you get culture language in reply to a question about decisions or money, follow up once with a request for an example. One polite follow-up is fair. Three start to feel like an interrogation.
Bringing a list of fifteen
There is rarely time for more than four or five. Choose one or two from each group that fits the stage, favor the ones whose answers would change your decision, and hold the rest for a later round or for the hiring manager.