Questions to Ask Your Future Supervisor in an Interview
Questions for a candidate meeting the person who would actually be their manager. They cover how the week really runs, why the role is open, how decisions and promotions get made, what the busy season looks like, and what is not going well on the team right now.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
What does the person in this role actually do in a normal week?
Why ask it
The job description lists responsibilities; you want hours and proportions. If the answer differs noticeably from the posting, the posting was written by someone else and the manager's version is the one you would be living.
Why is this role open: is it new, a backfill, or a replacement?
Why ask it
A new role often means unclear scope and having to prove the job should exist. A replacement means expectations shaped by someone specific, and a role open for months tells you about the pay or the reputation.
What did the last person in this job do well, and what did they find hard?
Why ask it
Managers answer this more honestly than they answer questions about the team, and the hard part is usually the reason the vacancy exists. If they cannot say anything about the previous holder, they may not have managed them closely.
What would you want me to have accomplished by the end of my first three months?
Why ask it
A specific, modest answer means the manager has thought about ramp-up. A long list, or a vague answer about getting up to speed, both predict the same thing: expectations you will discover only when you have failed to meet them.
How often would you and I meet one to one, and what would those meetings be for?
Why ask it
A weekly or fortnightly meeting that belongs to you is the mechanism through which everything else, including your pay, eventually gets discussed. Managers who say they keep an open door and skip scheduled time usually give feedback only when something has gone wrong.
How do you prefer to hear about a problem, and how quickly do you want to know?
Why ask it
You are asking for the operating manual, and most managers appreciate the question. Watch for whether they want problems raised early with no solution yet, or expect them solved first, since guessing wrong on that is a common early stumble.
When you make a decision the team disagrees with, how does that usually go?
Why ask it
Every manager makes unpopular calls, so the interesting part is whether they can describe a real one and what they did with the disagreement. An answer claiming the team always comes around means either no real decisions or no real dissent.
What are you being measured on this year?
Why ask it
Your manager's targets become your priorities, whatever your own objectives say. It also shows whether they know their own numbers, and whether the team's work connects to anything the organisation is tracking.
Which people outside the team would I work with most, and where does friction usually come from?
Why ask it
The honest answer names a department and a recurring dispute over priorities, handovers, or resources. A claim that everyone works well together is worth testing with a later interviewer, because the friction is always somewhere.
What decisions could I make on my own, and what needs to come to you?
Why ask it
This is the single most useful question about autonomy, and it produces a concrete answer where questions about micromanagement do not. Note whether the line is drawn by money, by risk, or by everything.
How does the review process work here, and how are raises and promotions actually decided?
Why ask it
Ask about the mechanism: when it happens, who else is in the room, whether increases come from a fixed pool. A manager who does not know how pay is set at their own employer cannot advocate effectively for yours.
Who was the last person promoted out of this team, and how long had they been here?
Why ask it
One name with a timeline is worth more than any statement about growth opportunities. If nobody has moved up or across in years, the ceiling in this role is lower than the job advert implies.
What is the busiest stretch of your year, and what does it look like for the team?
Why ask it
Every function has a peak: quarter end, an audit, a product launch, a season. Ask what hours it involves and how long it lasts, since averages hide the weeks that actually make people leave.
Are people expected to be reachable outside working hours?
Why ask it
Ask about the actual expectation rather than the policy, including whether there is an on-call rota and who covers holidays. Hesitation here is itself informative, as is an answer about a culture where people simply choose to be online.
How much of the work happens in the office, and is that your decision or a company rule?
Why ask it
Knowing where the requirement comes from tells you how likely it is to change and whether it is negotiable with you specifically. A manager who is vague about it is often anticipating a shift they cannot announce yet.
What have you changed about how this team works in the last year?
Why ask it
Shows whether they respond to problems or wait them out. A specific change, even a small one like moving a meeting or dropping a report, indicates someone who listens to their team; nothing at all suggests inertia.
What do people find hardest about this job?
Why ask it
Asked plainly, this usually produces something real: an unglamorous stretch of the work, a difficult stakeholder, a system everyone dislikes. An answer that it is challenging in a good way means you should ask the same question of a future peer instead.
What kind of person struggles on your team?
Why ask it
A manager who has seen someone fail can describe the mismatch, whether it is needing structure they do not provide or wanting more direction than they give. Compare that description honestly against yourself.
If I asked your team what you are like to work for, what do you think they would say?
Why ask it
The self-aware answer includes a fault, often about pace, detail, or being stretched thin. A flawless self-description at least tells you how much reflection to expect once you are working there.
What is not going well on the team at the moment?
Why ask it
Most managers will tell you something if you ask directly, and a candid answer here is a better sign than a polished one. Silence or a claim that everything is fine is worth weighing against the fact that they are hiring.
What is your timeline for deciding, and is there anything in my background that gives you pause?
Why ask it
The second half gives you one chance to answer an objection you would otherwise never hear. It takes some nerve and it regularly changes outcomes, because the concern is usually a small factual gap you can close on the spot.
Would I be reporting to you day to day, or to someone else?
Why ask it
Job adverts often list the hiring manager rather than the person who assigns your work. If the answer is a shift lead you have not met, ask to meet them, because that relationship will shape your week more than this interview does.
What does training look like in the first few weeks, and who does it?
Why ask it
Ask for a name. Training that belongs to everybody in general tends to happen in gaps between busy periods, and being left to pick it up is the most common reason new hires leave in the first two months.
How does work get assigned on your team, and who sets priorities when everything is urgent?
Why ask it
Reveals whether there is a system or whether the loudest requester wins. If prioritization turns out to be your job without your authority, that is the most useful thing you can learn in the interview.
How much of the work is planned versus reactive?
Why ask it
The split decides whether this is a job with deep work in it or one built around interruptions. A manager who cannot estimate the ratio usually runs a reactive team.
How much of the week goes to meetings and recurring commitments?
Why ask it
Calendar load is the best available predictor of whether you get uninterrupted time. If they cannot estimate it, ask what yesterday looked like on their own calendar.
When another department asks your team for something mid-quarter, how do you handle it?
Why ask it
This is where you find out whether priorities hold or get reset by whoever asks loudest. Ask for a recent case where they said no, and to whom.
How much of your own week is spent on your work versus your team's?
Why ask it
A manager still carrying a heavy delivery load will be hard to reach and will review your work late. It is not disqualifying, but it tells you how much of your development you will be running yourself.
What do you delegate, and what do you keep for yourself?
Why ask it
Specific answers indicate deliberate delegation. A manager who holds onto client contact and final edits may be difficult to grow under regardless of what they say about autonomy.
How is the schedule made, how far ahead do we see it, and how do swaps work?
Why ask it
Notice period for the rota decides whether you can plan anything outside work. Two weeks posted in advance with an agreed swap system is a different life from a rota that appears on Friday for the following week.
How much overtime is normal here, and is it voluntary?
Why ask it
Ask what last month actually looked like rather than what the policy says. Voluntary overtime that everyone is expected to volunteer for is a real pattern, and the supervisor's tone when answering usually tells you which kind this is.
How is coverage handled when someone calls in sick?
Why ask it
The answer tells you what happens to you on your day off, and whether the team runs with any slack at all. If cover depends on the same few people saying yes, you will be asked to be one of them.
How do you feel about someone taking leave in the middle of a busy stretch?
Why ask it
Asked plainly, this produces a more honest answer than any question about work-life balance. Hesitation before the reassurance is the data.
How do you prefer updates: written, spoken, or in a tool?
Why ask it
A small question with large daily consequences. Mismatched preferences here are a common source of friction that neither side ever names out loud.
Do you prefer to give feedback in the moment, or save it for a scheduled review?
Why ask it
Someone who saves everything for review season is telling you that you may hear about a problem months after it started, when it is already part of your record.
When did you last give someone difficult feedback, and how did you do it?
Why ask it
Asking for one recent instance separates managers who actually raise problems from those who quietly wait for review season. If they cannot recall an example, expect your first negative feedback to arrive in writing and late.
How is performance judged here, beyond what the job description says?
Why ask it
Written goals and the real basis for a raise are frequently different. If they can only recite the job description back to you, nobody has defined what good work looks like in this seat.
What happens here when someone makes a mistake?
Why ask it
This is the most revealing question on the list. Answers about fixing the cause and telling people early describe a team that surfaces problems; answers that go straight to write-ups describe one where mistakes get hidden until they are expensive.
When a project goes badly and senior people want an explanation, what do you do?
Why ask it
This asks whether they stand in front of their team or step aside. A manager who describes taking the meeting themselves is a different proposition from one who describes making sure the right people are accountable.
What do you do when someone raises a safety or quality concern?
Why ask it
Ask for the last time it happened and what changed as a result. If nothing has been raised in years, that is not a sign there was nothing to raise, and you should ask how people are expected to bring it.
How do you handle it when two people on your team cannot get along?
Why ask it
Splitting shifts to keep people apart is the common approach, and it means friction gets managed rather than resolved. Ask whether that has happened here, since you may be inheriting a schedule built around an old dispute.
What do you do when someone on your team is underwater?
Why ask it
Look for whether they cut scope, add people, or push the deadline, all of which mean they will absorb load with you. An answer about resilience and prioritizing better means the overload will be treated as your personal failing.
What is the team short of at the moment: people, equipment, or time?
Why ask it
Every team is short of something and a straight answer is a good sign. It also tells you what your first months will feel like, and whether the vacancy exists because the work grew or because someone left.
How long have the people on this team been here, and why have people left?
Why ask it
Tenure is the most honest single number in an interview. High turnover with a shrug is worth weighing heavily, while a supervisor who can explain each departure specifically is probably telling you the truth about the rest too.
What is changing here in the next year that would affect this job?
Why ask it
New equipment, a system migration, a site closure or a contract ending will affect your hours more than anything in the job description. Reluctance to name anything is worth a follow-up with someone on the team.
What say do you have over pay, hours and promotions?
Why ask it
A supervisor with no influence over any of these cannot deliver on encouragement about progression, however sincere. Better to know whose decision it is before you accept promises about your first review.
What do you find hardest about managing?
Why ask it
Nearly everyone finds something hard, so a blank or a humblebrag is the informative outcome. The genuine answers, usually about difficult conversations or letting go of the work, tell you where their attention runs out.
How do you handle it when someone wants to move on from your team?
Why ask it
Managers who help people leave well are the ones whose people stay longer. Hesitation, or a comment about loyalty, is a preview of how a request for a transfer or a promotion outside the team will be received.
If I take this job and it does not work out, what is the most likely reason?
Why ask it
Asks for the risk they can already see, and most managers will answer honestly because the question invites it. Whatever they name, ambiguity, pace, a difficult stakeholder, is the thing to weigh before you accept.
Could I shadow part of a shift, or speak with someone on the team, before I decide?
Why ask it
An hour on the floor tells you what no interview can: the noise, the pace, how people speak to each other. Reluctance without a clear reason such as confidentiality or safety is itself an answer.
Using these in the actual interview
Practical guidance for the conversation itself
Where to put them
Pick five, not twenty
You will usually get ten minutes at the end. Choose the five whose answers would most change your decision, and keep two spares in case someone answers your questions before you ask them.
Ask the hiring manager the manager questions
One-to-ones, decision-making, and what is going badly belong to the person who would supervise you. Save benefits, process, and paperwork for the recruiter, who can answer those faster and better.
Ask peers the same questions separately
If you meet prospective colleagues, ask them what the busy season is like, what the manager is like on a bad week, and why the last person left. Comparing the two accounts is the most reliable read you will get.
Ask through the interview, not only at the end
When they describe a project, ask who decided what and how it was handled. It reads as engagement rather than interrogation, and you get better answers before anyone is watching the clock.
Reading the answers
- Specifics are the signal: names, dates, numbers, a story with an ending. Adjectives about culture are not.
- If they cannot describe what the last person did well, they were not paying attention to that person, and they may not pay attention to you.
- Long hours described as passion, or a team called a family, are worth probing. Ask what happened the last time someone took two consecutive weeks off.
- Watch what they choose not to answer. A question deflected to HR, twice, is a topic with a story behind it.
- Notice whether their view of the team matches what peers told you. Where those diverge is where you would be working.
Questions to skip
- Anything answered on the company website or in the job posting. It reads as not having prepared.
- Compensation, in a first interview, unless they raise it or a recruiter asked you for a number. Handle it with the recruiter instead.
- Vague questions about culture or values. They produce vague answers you cannot act on.
- Do you have any concerns about me, asked as a nervous throwaway. Ask it once, at the end, and then be quiet and listen to the answer.
- Anything you would be uncomfortable having repeated to the rest of the panel afterwards, because it will be.
Before you accept
- 1Write down the three concrete facts you learned while the conversation is fresh. Impressions fade and facts are what you will compare between offers.
- 2If something was answered evasively, ask again in writing when you have an offer. You have more standing then than at any other point.
- 3Ask to speak to one person who currently reports to this manager, if you have not already. It is a normal request for a senior role and revealing if refused.
- 4Get the parts that matter to you in the offer letter: hybrid arrangement, on-call, review date, title. Verbal reassurances do not survive a change of manager.
- 5Weigh the manager heavily. The team, the work, and the pay can all improve within a company; a bad direct manager is the thing most people leave over.