The short answer
A panel is several people scoring you against the same rubric from different angles. Find out who is on it and why, answer to the person who asked but include the room, and expect each panellist to be listening for the thing they were assigned. Preparation is mostly mapping, not extra rehearsal.
What matters most
- Panels usually exist to reduce single-interviewer bias, so scoring is more formal, not less.
- Ask for the names and roles in advance β this is a normal request and it is usually granted.
- Answer to the asker, then bring your eyes across the room; do not address the most senior person throughout.
- Each panellist has an angle. Work out what it is and answer the question behind the question.
Why employers use panels
Panels are not staged to intimidate, whatever they feel like. They exist for three fairly mundane reasons: several stakeholders need to meet you and diary time is scarce; a single interviewer's impressions are unreliable and multiple independent scores are less so; and in the public sector, healthcare, education and academia a panel is frequently a formal requirement of the recruitment policy rather than a choice.
The practical consequence is that panel interviews tend to be structured: a fixed question set, asked in a fixed order, scored against written criteria. That works in your favour. It means every candidate is asked the same things, it means rapport matters slightly less than it does in a one-to-one, and it means clear, well-organised answers are rewarded more than charm.
Assessing whether you can do the job and whether managing you will be work. Their questions are the most specific and their scores usually carry the most weight.
There to check your technical claims. Expect one question that goes a layer deeper than everyone else's and do not bluff at it.
Assessing what you would be like to work beside. Often the person who asks about conflict, workload and how you like to be communicated with.
Running the process, keeping it fair and consistent, and asking the standard questions about motivation, availability and conduct.
Present because the role serves them. They want evidence you understand their problems, not just your own department's.
Sometimes a trainee panellist or a note-taker with no vote. Include them anyway; you cannot reliably tell them apart from a scorer.
What to do before the day
- Ask who will be on the panel, by name and role. Recruiters expect this question and answering it costs them nothing. If they will not say, ask how many people and from which functions.
- Look each of them up. Not to flatter them with a reference to their career history, which reads badly, but so you know whether the third question is coming from an engineer, a clinician or a finance director.
- Map each panellist to a likely concern, and make sure you have at least one story that speaks to each concern. This is where the story bank from our STAR method guide earns its keep.
- Ask about the format. Whether there is a presentation, whether questions are pre-set, how long it runs, and whether there will be a tour or a second session. Panels in the public sector often use identical questions for every candidate and will sometimes tell you so.
- Prepare one question for the panel as a whole and one you can direct at a specific member. A question aimed at the peer, about how the team actually works, lands better than another question for the hiring manager.
Where to look, and other mechanics
The eye contact question is the one candidates ask most. The workable rule: begin your answer to the person who asked it, move your attention across the rest of the panel through the middle of the answer, and return to the asker to close. It is not a rule about fairness so much as about scoring β a panellist who never receives eye contact disengages, and a disengaged panellist marks conservatively.
- Do not play to the most senior person. It is visible to everyone else in the room, including the senior person, and it insults the panellists whose scores may matter more.
- Write down the names as you are introduced. Draw the seating plan on your notepad. Using a name correctly forty minutes later is worth more than any prepared line.
- Do not read the note-taker. Someone writing furiously may be recording a strong answer or a weak one, and someone who has stopped writing may simply have caught up. Panels produce no usable real-time feedback and trying to read one mid-answer degrades your answer.
- Let the chair run the room. If two panellists talk over each other, stop and let them resolve it. Answering both at once is how a good answer becomes an incoherent one.
- Ask for a question to be repeated if you need it. Multi-part questions are common in panels and answering only the first part is a very common loss of marks.
The awkward moments
The panellist who is clearly unconvinced
Someone will occasionally push back hard, and it is more often a deliberate probe than personal hostility. Treat it as information: they are telling you which requirement they doubt. Acknowledge the point without capitulating, give the strongest specific evidence you have, and if the evidence is genuinely thin, say what you would do about it. Arguing to a win in front of a panel is not a win.
"I would say I have plenty of experience with that, more than enough for this role, and I think if you look at my resume it is all there."
"It is a fair challenge β my formal title has never been programme manager. What I have done is run the migration across four teams for eleven months, including the budget and the steering group reporting. If there are parts of the programme discipline I have not covered, the gap is probably formal benefits tracking, and that is a method I would want to learn properly rather than claim."
The silent panellist
Someone who asks nothing and shows nothing is not necessarily hostile β they may be an observer, a note-taker, or simply someone who does not perform in meetings. Include them in your eye contact, direct one answer their way if their function is relevant, and do not let their expression change your delivery. Reading a blank face as failure and speeding up in response is the actual risk here.
Repeating yourself
Panels frequently produce two questions that your best story answers. Use it, but flag it: "this comes back to the same migration, but from the stakeholder side." Panellists hear the acknowledgement as self-awareness rather than repetition. Slipping the same story in twice as if it were new is what gets noticed.
Presentations to a panel
Many panel stages include a short presentation, and the brief is usually vaguer than you would like. Three things fix most of them. Answer the brief literally, including any stated time limit β running over is scored down almost universally, and running to seven minutes of a ten-minute slot is fine. Assume the technology will fail, and bring the deck as a PDF on a memory stick and printed handouts for the panel. And build for questions: panels judge presentations mostly on the discussion afterwards, so leave room for it and do not front-load every point you want to make into the slides.
If the brief invites you to make recommendations about the organisation, be specific but not presumptuous. You are working from public information and one job advert, and a panel that lives with the problem daily will notice which of your points are informed and which are guesswork. Framing a recommendation as a question you would want to answer in the first month is usually safer than delivering it as a verdict.
Afterwards
Send one message rather than five. A single note to the chair or the recruiter, thanking the panel and naming one or two people specifically, is the usual convention β our thank-you note guide covers the panel case in detail, and there is a ready-made structure in the interview thank-you letter template. Separate individual emails to five panellists who sit next to each other reads as a mail merge.
If you are rejected after a panel, feedback is more likely to be available and more likely to be specific than after a one-to-one, because someone has a scoring sheet in front of them. Ask for it plainly and without arguing with it. In structured processes it is often the most useful feedback you will get all year.
Questions people actually ask
How many people are usually on an interview panel?
Three or four is the most common. Two happens in smaller organisations, and five or six is normal in the public sector, academia and executive hiring. More than six is usually a formal committee with a fixed script.
Can I ask who will be on the panel beforehand?
Yes. Ask the recruiter or coordinator for names and roles. It is a routine request, and knowing whether the third chair is an engineer or a finance lead materially changes how you prepare.
Who should I look at when answering a panel question?
Start with the person who asked, move your attention across the panel during the answer, and finish back with the asker. Avoid directing everything at the most senior person, which everyone in the room notices.
Should I bring copies of my resume to a panel interview?
Bring a few. They are rarely needed, because the panel has the pack, but a spare copy for the person who did not receive one is a small, useful courtesy. Bring printed handouts if you are presenting.
Are panel interviews harder than one-to-one interviews?
They feel harder and are often fairer. Structured scoring across several assessors reduces the influence of any single person's impression, which helps candidates who interview well on substance rather than on rapport.
Should I send a thank-you email to every panellist?
One message to the chair or recruiter, mentioning the panel by name, is the standard. Individual notes are fine if you have the addresses and can genuinely make each one different, but near-identical emails to colleagues are worse than one good one.
