Interview guide · Interview types

Panel interview questions

By TapTalent Editorial TeamUpdated

In short

Panel interview questions are asked by two or more interviewers who meet one candidate together, each covering assigned competencies. This page gives 32 panel interview questions organized by who usually asks them (hiring manager, peer, cross-functional partner, HR, board), what strong answers include, how to split questions across the panel and how to score and debrief.

A panel interview puts three to five people in a room, or on a call, with one candidate. Done well, it saves the candidate four separate interviews and gives every decision maker the same evidence. Done badly, it is four people asking whatever comes to mind, repeating each other and then letting the most senior person decide in the debrief. The difference is preparation: agree the competencies, give each panelist two or three of them, write the questions in advance, and score independently before anyone speaks.

The questions below are organized by the panelist who typically owns them, so you can hand each person their section. A final group covers board interview questions used for executive, public sector and nonprofit appointments. Choose eight to twelve questions for a 60-minute panel, add the standard follow-ups to each, and score against the rubric at the bottom. Panels work best as a structured interview with more than one listener. For the definition of the format, see our glossary entry on the panel interview.

What these questions assess

  • Engaging the whole panelStrong candidates answer the person who asked, then include the others with eye contact or by linking their answer to another panelist's area. That is how they will work with multiple stakeholders on the job.
  • Consistent stories across panelistsDifferent panelists may approach the same project from different angles. Details that stay consistent are a good sign; contradictions are worth a careful follow-up.
  • Depth in each panelist's areaThe finance partner, the peer and the hiring manager each probe a different part of the job. Candidates who are strong in one area and thin in another show up clearly.
  • Composure under multiple questionersBeing questioned by several people is mildly stressful, much like presenting to a leadership team or handling a difficult client meeting. Score how the candidate thinks, not whether they look nervous.
  • Handling disagreement among stakeholdersPanelists sometimes want different things from the role. Candidates who can acknowledge both views and explain how they would balance them show real stakeholder judgment.
  • Good questions back to the panelQuestions directed at specific panelists about their priorities show preparation and genuine interest in how the role fits together.

Opening questions (panel chair)

  1. We have each read your resume. Give us a three-minute summary of the experience you think matters most for this role.

    Why ask it
    Saves the panel from re-reading the resume aloud and tests the candidate's judgment about relevance.
    A strong answer
    Selects two or three experiences that map to the role, gives a result for each and stays near three minutes.
    Red flags
    Walks through every job in date order without linking any of it to the role.
  2. What do you see as the main purpose of this role, and how does it connect to each of our teams?

    Why ask it
    Shows whether the candidate understands why each panelist is in the room.
    A strong answer
    Describes the role's core output and names how it affects the teams represented on the panel.
    Red flags
    Describes only the hiring manager's view and ignores the other functions.
  3. What made you interested in this role at this point in your career?

    Why ask it
    Motivation question asked once by the chair, so panelists do not repeat it.
    A strong answer
    Gives a specific reason tied to the scope, the problem to solve or the team, and a sensible career rationale.
    Red flags
    Only mentions title or pay, or cannot say why this role rather than any other.

Hiring manager questions

  1. Tell us about the result you are proudest of in your current or last role. How did you achieve it?

    Why ask it
    Establishes the candidate's best work and how much of it was theirs.
    A strong answer
    Names a measurable result, the plan they made, the obstacles and their personal contribution.
    Red flags
    Uses "we" throughout with no clear personal role.
  2. If you started next month, what would you focus on in your first 90 days?

    Why ask it
    Tests how the candidate learns a new environment and sets priorities.
    A strong answer
    Balances listening and learning with one or two early, visible wins, and says what information they would need first.
    Red flags
    Plans sweeping changes before understanding the team.
  3. Tell us about a goal you missed. What happened and what did you do about it?

    Why ask it
    Shows accountability and how the candidate reacts to failure.
    A strong answer
    Owns the miss, explains the cause honestly, describes recovery actions and what changed afterward.
    Red flags
    Blames other teams or market conditions entirely.
  4. How do you prefer to be managed, and how do you keep your manager informed?

    Why ask it
    Checks fit with the hiring manager's style and the candidate's communication habits.
    A strong answer
    Describes a preference honestly and concrete habits such as weekly updates, early warnings and how they flag risks.
    Red flags
    Wants no contact or expects daily direction in a role that needs independence.
  5. Describe a time you had to make a decision without all the information you wanted.

    Why ask it
    Tests judgment under uncertainty, needed in most professional roles.
    A strong answer
    Explains what they knew, what was missing, how they limited the risk and how the decision turned out.
    Red flags
    Waited until the deadline passed or decided on instinct with no reasoning.

Peer and team member questions

  1. Tell us about a time you disagreed with a colleague at your level about how to do something. How was it resolved?

    Why ask it
    Peers want to know how the candidate will behave in everyday disagreements.
    A strong answer
    Explains both views fairly, describes a direct conversation, how they reached a decision and the working relationship afterward.
    Red flags
    Escalated immediately or worked around the colleague.
  2. What do you do when a teammate is behind and it is affecting your work?

    Why ask it
    Tests teamwork and directness.
    A strong answer
    Checks in privately, offers help where possible, agrees a plan and involves the manager only if it continues.
    Red flags
    Complains to others or quietly does the work and resents it.
  3. Walk us through how you would hand over your work if you were out unexpectedly for a week.

    Why ask it
    A practical question that shows organization and documentation habits peers rely on.
    A strong answer
    Describes up-to-date notes, a shared tracker, a named backup and what they would flag as urgent.
    Red flags
    Everything is in their head.
  4. What is something you have taught a colleague that made their job easier?

    Why ask it
    Shows generosity with knowledge and the ability to explain.
    A strong answer
    Names a specific skill or shortcut, how they taught it and the effect on the colleague's work.
    Red flags
    Cannot think of an example.
  5. How do you like to receive feedback from peers, and when did you last act on it?

    Why ask it
    Tests openness to peer feedback, not just manager feedback.
    A strong answer
    Gives a recent example of peer feedback and the change they made.
    Red flags
    Only accepts feedback from their manager.

Cross-functional and stakeholder questions

  1. Tell us about a project that depended on another department. How did you work with them?

    Why ask it
    Cross-functional panelists want evidence the candidate can collaborate beyond their own team.
    A strong answer
    Explains how they understood the other team's goals, agreed responsibilities and timelines, and handled a conflict of priorities.
    Red flags
    Treated the other department as an obstacle.
  2. Two stakeholders on this panel need different things from this role in the same week. How would you decide?

    Why ask it
    A situational question that is very real for shared roles.
    A strong answer
    Clarifies the impact and deadline of each request, suggests options, makes the trade-off visible and gets a decision from the right person.
    Red flags
    Promises both and delivers neither, or always favors the more senior person.
  3. How would you explain a budget or headcount request to a finance partner who is skeptical?

    Why ask it
    Tests business case skills and comfort with numbers.
    A strong answer
    Leads with the business problem and cost of doing nothing, shows the numbers and assumptions, and offers a smaller or phased option.
    Red flags
    Relies on urgency or emotion without data.
  4. Tell us about a time you had to say no to a stakeholder. How did you do it?

    Why ask it
    Shows the candidate can protect priorities while keeping the relationship.
    A strong answer
    Explains the reason, offers an alternative or a later date, and keeps the stakeholder informed.
    Red flags
    Never says no, or says it bluntly with no alternative.
  5. What information would you need from our team to do this job well?

    Why ask it
    Shows the candidate has thought about the panelist's function and how they would work with it.
    A strong answer
    Asks specific, sensible questions about data, timing or processes from that team.
    Red flags
    Has not considered the other teams at all.

HR and values questions

  1. Tell us about a time you saw something at work that did not seem right. What did you do?

    Why ask it
    Tests integrity and willingness to raise concerns.
    A strong answer
    Describes the situation, how they checked their concern, who they raised it with and what happened.
    Red flags
    Ignored it or took dramatic action without checking facts.
  2. How have you made sure people with different backgrounds or working styles could contribute fully on a team?

    Why ask it
    Assesses inclusive behavior through action rather than opinion.
    A strong answer
    Gives specific actions such as rotating who speaks first, adjusting meeting formats or sharing information in writing, and the effect.
    Red flags
    Only states general support for diversity with no example.
  3. What kind of work environment brings out your best work, and what drains you?

    Why ask it
    Helps judge fit with the actual team environment, which should be described honestly to the candidate too.
    A strong answer
    Gives honest, specific preferences and how they adapt when the environment is not ideal.
    Red flags
    Describes an environment completely different from the one on offer.
  4. Is there anything about the role, team or schedule that you would want to know before accepting an offer?

    Why ask it
    Brings potential deal-breakers into the open while the panel is together.
    A strong answer
    Asks direct questions about scope, reporting lines, flexibility or development.
    Red flags
    Says no, then raises major conditions at offer stage.

Board interview questions for executive and public sector roles

  1. What do you see as the biggest risks facing this organization over the next three years, and how would you address them?

    Why ask it
    Boards want strategic thinking grounded in research on the organization.
    A strong answer
    Names specific, well-researched risks (funding, regulation, workforce, technology), prioritizes them and outlines a realistic approach.
    Red flags
    Gives generic risks that could apply to any organization.
  2. How would you keep this board informed without overwhelming it with detail?

    Why ask it
    Tests understanding of governance and the board-executive relationship.
    A strong answer
    Describes a regular reporting rhythm, a short set of key measures, early notice on major risks and a clear line between governance and management.
    Red flags
    Plans to report only good news, or to bring operational decisions to the board.
  3. Tell us about a time you had to deliver difficult news to a board, council or senior leadership group.

    Why ask it
    Shows candor and composure with a governing body.
    A strong answer
    Raised it early, came with facts and options, took responsibility for their part and followed up on the agreed actions.
    Red flags
    Delayed the news or framed it to avoid blame.
  4. How would you handle a board member who contacts staff directly with instructions?

    Why ask it
    A common governance problem in nonprofits, schools and public bodies.
    A strong answer
    Addresses it privately and respectfully with the board member, refers to agreed governance policies and involves the chair if it continues.
    Red flags
    Ignores it or complains about the board member to staff.
  5. Describe how you have built trust with a community, members or the public in a previous role.

    Why ask it
    Public and nonprofit leaders are accountable to people outside the organization.
    A strong answer
    Gives specific actions: listening sessions, transparent reporting, responding to complaints, and a measurable change in trust or engagement.
    Red flags
    Treats public engagement as a communications task only.

Sample answers

Two stakeholders on this panel need different things from this role in the same week. How would you decide?
First I would make sure I understood each request properly: what the deadline really is, what happens if it slips, and who else depends on it. Often one of them is less fixed than it first sounds. If both are genuinely urgent, I would write a short note to both stakeholders and my manager laying out the two requests, what I can deliver by when, and the options, for example finishing one fully and a first version of the other. Then I would ask my manager to make the call if the two of them cannot agree. In my last role as an HR business partner, this happened during open enrollment and a reorganization at the same time. Putting the trade-off in writing made it much easier for the two directors to agree on the order, and neither of them felt surprised.
If you started next month, what would you focus on in your first 90 days?
The first month would mostly be listening. I would meet everyone on the team one-on-one, sit in on the main processes and ask each of you on this panel what a good first year looks like from your side. I would also look at the numbers we track, so I know where we actually stand. In the second month I would pick one or two problems that people agree on and that I can fix quickly, probably something like the reporting delays you mentioned earlier, so the team sees progress. By day 90 I would want to bring a short plan for the rest of the year back to my manager, based on what I have learned, with clear priorities and what I would stop doing.
Tell us about a time you had to deliver difficult news to a board, council or senior leadership group.
As operations director for a regional nonprofit, I found three months into the fiscal year that a state contract we counted on for about 15 percent of revenue would be cut in half. I called the board chair the same day and asked for a special finance committee meeting that week rather than waiting for the quarterly meeting. I brought the facts, our cash position, and three options: drawing on reserves, pausing one program, or a mix of both with a fundraising push. I recommended the mix and was clear about the risk. The board chose that option and asked for monthly updates instead of quarterly. We ended the year with a small deficit, well inside what the reserves policy allowed, and the board later said they appreciated hearing it early.

Interview scorecard

CompetencyWeightStrong (4–5)Weak (1–2)
Role-specific expertise30%Answers in each panelist's area show depth, accurate detail and results that match the level of the role.Strong in one area but vague or inaccurate in others that matter for the role.
Stakeholder management and collaboration25%Gives clear examples of balancing competing needs, working across teams and saying no constructively.Favors one group, avoids conflict or describes other teams as obstacles.
Judgment and problem solving20%Reasons clearly through situational questions, identifies risks and proposes sensible options.Jumps to conclusions or cannot explain reasoning when probed.
Communication with the panel15%Answers concisely, includes all panelists and adjusts detail to each person's area.Talks only to one panelist, rambles or loses the question.
Integrity and values10%Raises concerns appropriately, owns mistakes and shows inclusive behavior with examples.Blames others, avoids accountability or offers only general statements about values.

Score each competency from 1 to 5 straight after the interview, before discussing the candidate with anyone else, then multiply by the weight.

Panel interview format: who sits on it and how to split the questions

Three to five panelists is the practical range. Two is just an interview with a note-taker; six or more turns into a presentation and candidates struggle to build rapport with anyone. A typical professional panel includes the hiring manager, a peer from the team, a partner from another function the role works with, and someone from HR or talent acquisition who chairs.

Prepare the panel like this:

  1. Agree four to six competencies from the job analysis and assign each to one panelist. Nobody asks about everything.
  2. Write the questions in advance, one or two per competency, with anchored scores. Share the plan so panelists do not overlap.
  3. Name a chair. The chair opens, introduces everyone, keeps time, makes sure every competency is covered and closes. In a 60-minute panel, allow about 5 minutes for introductions, 45 for questions and 10 for the candidate's questions.
  4. Tell the candidate who will be on the panel and their roles. It reduces anxiety and gets better answers.
  5. Score independently right after each answer, then submit scores before the debrief.

For video panels, the chair should call on panelists by name, and panelists should keep cameras on and mute when not speaking. If the candidate has already had a first interview, avoid repeating questions from it and use our second interview questions to go deeper on the gaps.

Running the debrief and avoiding common panel mistakes

The debrief is where panel interviews most often go wrong. Senior panelists speak first, others adjust, and the final decision reflects one person's view rather than the panel's evidence. A simple order fixes most of it: scores are submitted before the meeting, the chair shows them side by side, each panelist explains their scores for their own competencies, and large differences are discussed by looking at the evidence notes.

Other frequent mistakes:

  • Panelists asking their favorite questions instead of the agreed ones. It leaves gaps in coverage and makes candidates hard to compare.
  • Rapid-fire questioning. Back-to-back questions from different people with no pause feel like an interrogation. Let the candidate finish, allow the assigned follow-up, then move on.
  • No diversity on the panel. A panel of people with very similar backgrounds tends to reward candidates like themselves. Many organizations aim for panels with a mix of functions, levels and backgrounds.
  • Inconsistent panels for the same role. If candidate A meets four people and candidate B meets two, comparing their scores is unreliable.
  • Off-limits questions. Every panelist, not just HR, needs to know which questions are off-limits. In the US, avoid questions about age, religion, national origin, disability, pregnancy or family plans, and check state rules on pay history and criminal history questions. Public sector employers often have additional rules on panel composition and record-keeping, so check your policy.

Panels in high-volume and multi-site hiring

Full panels are expensive: four people for an hour is four hours of interviewer time per candidate. For high-volume roles such as contact center agents or warehouse associates, that rarely makes sense. Use a short structured interview with one trained interviewer, or a group interview when you want to see team behavior, and save panels for supervisors, managers and roles that serve several departments.

Where panels are needed at volume, such as team leader promotions across 20 sites or a graduate intake, a few habits keep them consistent:

  • Use the same competencies, questions and anchors at every site, with a short interviewer training session and a recorded example answer to calibrate against.
  • Rotate one trained talent acquisition partner across all panels so someone sees every candidate and can spot sites that score high or low.
  • Use AI-assisted note-taking or summaries only with candidate notice and consent where required, and check summaries against what was actually said.
  • Track the time from final panel to decision. Panels slow things down because several calendars must align, so set a rule such as decisions within two business days.

Finally, compare panel scores with performance at six or twelve months. If one panelist's ratings never match how hires perform, revisit their training or role on the panel.

Frequently asked questions

What are common panel interview questions and answers?

Common panel questions include a summary of relevant experience, your proudest result, your first 90 days, a disagreement with a colleague, working with another department, and balancing two stakeholders' competing requests. Strong answers are specific, include a measurable result and speak to the whole panel, not just the person who asked.

What is the typical panel interview format?

A typical panel has three to five interviewers and lasts 45 to 90 minutes. A chair opens and introduces everyone, panelists take turns asking prepared questions on their assigned competencies, the candidate asks their own questions at the end, and each panelist scores independently before a debrief.

What are board interview questions?

Board interview questions are asked by a board of directors, trustees, a council or a school board, usually for executive, superintendent or public sector roles. They focus on strategy, governance, working with the board, community trust and handling difficult news, and are often asked in a fixed order with scored responses.

How many people should be on an interview panel?

Three to five is the common range. Fewer than three adds little over a one-to-one interview, and more than five makes it hard for the candidate to build rapport and for the panel to cover questions in the time available. Keep the panel size the same for every candidate for the role.

How should panel interviewers divide questions?

Assign each panelist one or two competencies that match their expertise, such as the hiring manager on results and priorities, a peer on teamwork and a partner from another team on cross-functional work. Write the questions in advance and share the plan so nobody repeats another panelist's questions.

How do you score a panel interview?

Each panelist scores every answer they hear against the same anchored rating scale, records evidence notes, and submits scores before the debrief. The chair then compares scores side by side and the panel discusses large differences using the evidence, rather than voting on overall impressions.