Panel interview tips: how to handle several interviewers at once

A panel interview is one conversation with two or more interviewers at the same time, usually 45 to 60 minutes. To handle it well, learn the panelists' names and roles beforehand, answer the person who asked while bringing the others in, treat cross-questions as normal, and follow up with each person afterward. The questions are ordinary. What changes is who you are talking to.

What is a panel interview?

Instead of meeting interviewers one after another, you meet several together. A typical panel has a hiring manager, one or two people from the team, and sometimes someone from a partner team or from HR. They take turns asking questions, and each scores you, often against a shared rubric, before they compare notes.

Companies use panels to save time, to let several people hear the same answers, and to reduce the influence of one interviewer's mood. For you, the upside is that you only tell each story once. The downside is that you have to read several people at the same time.

How roles usually split on a panel

Panels rarely announce roles, but most fall into a recognizable pattern. Spotting it early helps you decide who needs what from your answers.

• The lead asker. Often the hiring manager. Opens, keeps time, and asks the broad questions. Usually the person you should start and finish each answer with.
• The note taker. Types or writes most of the time and asks few questions. Silence from this person is not a bad sign. Their notes often carry weight in the debrief.
• The skeptic. Asks the follow-ups that push: "Why not the simpler option?" "What would you do if that failed?" This is a role, not a judgment of you.
• The specialist. Someone with a narrow interest, such as security, data or design, who asks one or two deep questions in that area.

One person can play two roles, and the roles can rotate. Do not label people out loud. Just notice who asks what kind of question.

How to prepare for a panel interview

1. Get the names and roles. Ask the recruiter who will be on the panel and what each person does. Most will tell you.
2. Guess what each person cares about. A hiring manager usually cares about delivery and judgment. A peer cares about collaboration and code. A partner team cares about how you work across boundaries.
3. Map your stories to those concerns. Three or four stories, each with a detail that speaks to more than one panelist.
4. Prepare one question for each person. Tied to their role. It shows you noticed who was in the room.

Common panel interview questions

Panels ask the same questions as one-on-one interviews. What differs is that each panelist tends to ask from their own angle, so you can often predict who will ask what.

• From the hiring manager: "Walk us through your background." "Why this role?" "Tell us about a project you led."
• From a peer: "Tell us about a time you disagreed with a teammate." "How do you approach code review?"
• From a partner team: "Describe a time you worked with another team to ship something." "How do you handle a dependency that slips?"
• From the skeptic, on any answer: "Why that option?" "What would you change now?" "What if that had failed?"
• From anyone, at the end: "What questions do you have for us?"

Prepare for the angle, not a script. A story about a cross-team launch can serve the hiring manager, the peer and the partner team if you know which detail to bring forward for each.

Eye contact and addressing everyone

The habit that matters most: start your answer looking at the person who asked, let your attention move to the others through the middle, and come back to the asker as you finish. It keeps the asker feeling answered and keeps the rest of the panel included.

• Use names sparingly. Once or twice in the hour is warm. In every answer it sounds rehearsed.
• When a story touches someone's area, look at them for that part: "This is where the data team came in."
• Do not play to the most senior person. The quiet note taker may write the summary.
• If someone has not asked anything, you can bring them in at the end: "Is there anything from your side I could go deeper on?"

How do you handle cross-questions?

Cross-questions happen when a second panelist follows up on someone else's question, or when two people push in different directions. They are normal. They usually mean people are engaged.

Two questions at once

Pick an order out loud, then keep it.

"Two good questions there. I'll take the rollout one first, since the cost answer depends on it, then come back to cost."

A follow-up from someone else

Answer the new person, then connect back to the original question so the first asker is not left hanging.

Panelists who seem to disagree

If one panelist favors speed and another favors safety, do not pick a side to please one of them. Name the trade-off and say how you would decide.

"I think you're both pointing at the real tension. If the change is reversible, I'd ship behind a flag and watch it. If it touches stored data, I'd slow down and test the migration first."

Example: handling the skeptic

An invented exchange in a backend panel. The skeptic pushes twice. The candidate does not get defensive and does not cave.

Panelist: "You said you added a cache. Why not just fix the slow query?" Candidate: "Fair question. I did look at the query first. It was already using the right index, and the slow part was a join across two services we didn't own. The cache gave us room while we asked that team for a better endpoint." Panelist: "And if the cache served stale data?" Candidate: "That was the risk. The data changed a few times a day, so we set a short expiry and added a manual purge for support. If it had needed to be exact, I would not have used a cache there."

Each reply admits the trade-off, gives the reason, and stops. The candidate also says when the choice would have been wrong, which is often what the skeptic is checking for.

Panel interviews over video

• Use gallery view so you can see everyone, and keep the window near your camera.
• Look at the camera when you make your main point, and at the faces when you are listening.
• Read the name labels on the tiles at the start, and write the names down in seating order.
• Expect people to talk over each other because of lag. Pause a beat before answering, and if two people start at once, offer: "Go ahead."
• If a panelist is off camera, still address them by name when their area comes up.

More on the setup side of a remote round is in virtual interview tips. If you will share your screen, screen sharing in interviews covers what to check first.

Common mistakes

• Talking only to the person who asked, or only to the most senior person.
• Treating a skeptical follow-up as hostility and getting defensive.
• Changing your answer to please whoever spoke last.
• Long answers. With several people, each one waits longer for their turn. Keep stories to about two minutes.
• Forgetting names. Write them down in the first minute.
• One generic thank-you email to the whole panel.

A practice loop for panels

1. Recruit two people if you can. Friends or colleagues. Give one the lead role and the other the skeptic role.
2. Run twenty minutes. Three questions, with the skeptic following up on each. Practice the look-at-the-asker, include-the-others, come-back habit.
3. Ask each person one question. Which answer lost them, and where they stopped feeling included.
4. Practice alone if you have to. Put three sticky notes around your screen and move your attention between them as you answer out loud.
5. Write three lines. The answer that ran long, the follow-up that threw you, and one change for next time.

Following up after a panel

Send a short thank-you email to each panelist within a day, if you have their addresses, or ask the recruiter to pass a note along. Make each one different by mentioning something that person asked about. Templates are in the thank-you email after an interview.

Practice panel answers on the Verbal surface

HIDEA AI is a desktop app for macOS and Windows with four separate surfaces: Verbal, Live coding, System design and Project. Panel questions are mostly behavioral and project questions, so practice on Verbal, and use Project for questions about code you have written. You speak or type every answer.

Fifteen session minutes a day is free, with no credit card. A verbal mock interview, where the app asks the questions out loud and scores a 20- or 30-minute round, is on Pro and Pro+, and the Report tab scores the saved session. It will not imitate three people at once, so pair it with a practice panel of friends. See the interview copilot overview and the FAQ for details.

Before using any tool in a real panel, check the employer's rules. Here is what some employers publish.

Where to go next

• Prepare the stories: behavioral interview questions with answers.
• Handle the push-back: how to answer follow-up questions.
• Plan your questions for each panelist: questions to ask the interviewer.