Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo ads on medical, legal or end-of-life pagesCopy or print any set and take it with you
03 · Professional & Academic

Questions to Ask a Potential Supervisor Candidate

Interview questions for hiring someone into a supervisor or team lead role, written for the manager running the interview. They ask for specific past episodes: feedback given, someone who improved, someone who did not, a change the team resisted, and a deadline that had to be renegotiated upward.

20 questions · each with a note on why · conversation guide

The questions

Open any question for the note

  1. How many people have you supervised, and were any of them your peers before?

    Why ask it

    Supervising former colleagues is a different job from arriving as an outsider, and many first-time supervisors fail at exactly that transition. If they have done it, ask what changed in those relationships.

  2. Walk me through your first two weeks taking over a team you did not know.

    Why ask it

    Strong answers involve listening first: one-to-ones with everyone, learning the current commitments, changing little. Anyone whose first move is a reorganisation or a new process is telling you how they handle uncertainty.

  3. Tell me about the hardest piece of feedback you have had to give. What did you actually say?

    Why ask it

    Ask for the words. Candidates who avoid these conversations describe the situation in detail and the conversation in generalities, which is what their team will experience as problems being discussed everywhere except with the person.

  4. Tell me about someone who worked for you and got noticeably better. What did you do?

    Why ask it

    You are looking for their part in it, described concretely: sitting in on their work, changing what they were assigned, weekly practice on one thing. Answers that credit the person's own motivation are pleasant but tell you nothing about the supervisor.

  5. Tell me about someone who did not improve. How did it end?

    Why ask it

    This is the harder half and it is where you learn about their honesty. Listen for whether they can say what they got wrong, how long they left it, and whether the person was told clearly before the outcome arrived.

  6. How do you decide what the team works on when there is more work than time?

    Why ask it

    Look for a stated basis, whatever it is: customer impact, risk, a queue, the manager's ranking. Supervisors without one end up allocating by whoever asked most recently or most loudly, and the team can feel it.

  7. What do you look at each week to know whether the team is on track?

    Why ask it

    A few real numbers or a short list of checks is a good sign. If the answer is that they can tell by talking to people, ask what they missed the last time that turned out to be wrong.

  8. Describe a time you had to tell your own manager that a deadline would not be met.

    Why ask it

    This is the single most useful predictor for the role. Supervisors who cannot deliver that message pass the pressure down instead, and you find out from a resignation rather than from a status update.

  9. How do you handle a conflict between two people who both do good work?

    Why ask it

    Separating them is the common answer and the weak one. Better answers involve talking to each, naming the specific behaviour rather than the personalities, and being clear about what will change on Monday.

  10. What do you do about someone who hits their targets but treats colleagues badly?

    Why ask it

    How they answer tells you their real standard. Tolerating it for the sake of output is a choice with a cost, and you want to know whether they can name the cost and act on it before others leave.

  11. Tell me about a change you introduced that the team resisted. What did you do?

    Why ask it

    Ask what the resistance was actually about, since it is often a practical objection dressed as reluctance. Candidates who describe the team as simply resistant to change usually did not find out.

  12. How do you respond when another department asks for something that would overload your team?

    Why ask it

    Supervisors sit exactly on this seam. You are checking whether they say no with a reason, bring it to you, or quietly absorb it and let their team carry the extra.

  13. How do you decide when to do the work yourself and when to leave it with someone?

    Why ask it

    New supervisors default to doing it themselves because it is faster and visible. Look for a rule about the difference between a genuine emergency and a habit, and for awareness of what taking over signals to the person.

  14. What do you delegate that you find hardest to hand over?

    Why ask it

    The honest answer is usually the part of the old job they were best at. Someone who claims to find delegation easy either supervises very little or has not noticed what they are holding on to.

  15. What do you do when something personal is affecting someone's work?

    Why ask it

    You want a balance: humane adjustment, a clear limit, and knowledge of what the organisation can offer. Both extremes are problems, since indefinite accommodation shifts the load onto the rest of the team and rigidity loses good people.

  16. How do you cover absence and holidays without exhausting the reliable people?

    Why ask it

    Ask how they track who has picked up the slack. Without deliberate attention the same two or three people absorb every gap, which is invisible on a rota and obvious in the exit interviews.

  17. Have you hired anyone? Walk me through how you decided.

    Why ask it

    Listen for evidence gathered rather than impressions: a work sample, the same questions for each candidate, reference calls. Hiring on gut feel is common and it is the habit that most quickly changes the shape of a team.

  18. Have you had to let someone go, and what would you do differently?

    Why ask it

    Handled well, the person knew it was coming and the team was told plainly. Answers with no regret at all, or with visible relish, are both worth probing.

  19. What would the people who reported to you say you are best at, and where would they say you need help?

    Why ask it

    The second half needs to be a real limitation, and one you can verify in a reference call. Attention to detail offered as a weakness is a rehearsed answer and worth pressing past.

  20. What support would you want from me if we hire you?

    Why ask it

    A candidate who has supervised before will name something specific: cover for decisions on pay, an introduction to another department, a weekly slot for the first two months. It also tells you whether they will ask for help before things go wrong.

Structuring the interview

Practical guidance for the conversation itself

How to run it

Ask for episodes, not philosophies

Every question here should end in a story with a date, a person and an outcome. When a candidate answers in general terms, ask when that last happened and what was said. The shift from theory to instance is where interviews start telling you something.

Use one real scenario from your own team

Describe an actual situation, anonymised: a strong performer refusing a process, two shifts blaming each other, a deadline slipping quietly. Ask what they would do in the first week. It tests judgement in your context rather than in theirs.

Have a future report on the panel

Someone who will be supervised by this person should meet them and give a view. They notice things a manager will not, particularly how the candidate speaks about people who worked for them.

Ask referees about the people, not the projects

Call a former direct report if you can, and ask what the candidate was like on a bad week, how feedback arrived, and whether anyone left. Referee lists rarely include direct reports unless you ask for one.

What to weigh most heavily

Willingness to deliver bad news upward

Of everything in this list, this predicts the most. A supervisor who cannot say a date will slip protects you from information you need and passes the pressure to the team instead.

Whether they describe their team as individuals

Candidates who have paid attention will name people, strengths and specific difficulties. Answers that refer to the team as a single unit throughout usually mean the supervision was procedural.

How they talk about their predecessor or current manager

Some criticism is fair and useful. Uniform contempt for everyone above them is a preview of how they will describe you to their team in a year.

Common mistakes

Promoting the best individual performer by default

Skill at the work is weak evidence for skill at supervising it, and the promotion often removes your strongest contributor while creating a struggling supervisor. Interview internal candidates against the same questions as external ones.

Testing technical depth and calling it done

It is the comfortable part of the conversation for both sides. Budget at least half the interview for feedback, conflict and workload, because that is where supervisors actually fail.

Leaving the scope of authority vague

Say plainly what they can decide about schedules, spending, hiring and performance. Candidates who accept an unclear remit are the ones who discover in month three that they carry the responsibility without the authority.

Not asking what they would need

A supervisor moving up needs training, cover and a peer to talk to. If nobody discusses that in the interview, it usually does not get arranged afterwards either.