In a panel interview, several people hear your answers at once, often because the role works across a team. Your task is to make each answer easy for the whole group to follow: pause, answer the question asked, give one relevant example, and check that you have addressed the concern. You do not need to win over each person separately or maintain eye contact with everyone on every sentence.
The format varies by employer. Some panels rotate prepared questions; others interrupt with follow-ups. The U.S. Office of Personnel Management explains how structured interviews can ask candidates consistent, job-related questions. Do not infer that every panel is formally structured, but expect more than one viewpoint on the same skill.
Learn the room before you enter
Ask the coordinator for the panelists' names, roles, expected length, and whether you will present or complete an exercise. Read the role description and identify the functions that work with this job. For a customer operations role, a manager may care about prioritization, a peer about handoffs, and a technical partner about precise issue reports. Use that knowledge to select examples with shared relevance, not to stereotype individuals.
Bring a one-page note with three examples: a decision under pressure, a collaboration, and a mistake you corrected. Be able to explain your own contribution and what teammates did. Our behavioral interview guide helps you build these stories.
Use a response that travels around the table
Begin by looking at the person who asked the question. State your answer in one sentence, then give a compact example. As you explain, include the rest of the panel naturally; return to the questioner when you finish. The goal is to speak to a group, not to count eye-contact seconds.
For “How do you handle competing requests?” a useful answer is: “I first clarify which deadline has real consequences. Last quarter two teams needed the same report by Friday; I checked the decisions each report supported, agreed on a short version for Thursday, and delivered the full analysis Monday. Both teams knew the trade-off.” A vague “I'm good at multitasking” gives the panel nothing to evaluate.
When questions come quickly or conflict
If someone adds a new question before you finish, pause and say, “Let me finish the first point briefly, then I will take that.” If two people ask at once, choose an order aloud. Taking a breath is professional; you do not have to answer at conversational speed. If you did not hear a question, ask for it to be repeated.
Panelists may challenge the same choice from different angles. Do not treat this automatically as hostility. Explain the information you had, acknowledge the trade-off, and state what would change your decision. If a hypothetical lacks essential details, say what assumption you are making. Avoid defending an obviously weak choice just to appear consistent.
Make your examples legible to different roles
A technical story can lose a nontechnical panelist. Give the business or user problem first, explain the key action without jargon, and then add the technical depth if asked. Conversely, do not strip every example of substance for a specialist. A short opening allows the panel to choose where to probe. Be honest about results that were shared by a team or still uncertain.
If one panelist looks unconvinced, do not assume you know why. Ask, “Would it help if I explained how we measured the result?” This invites a specific follow-up. Spending the rest of the interview trying to read facial expressions is less useful than answering accurately.
Questions and follow-up
Prepare two or three questions that benefit from different viewpoints: “Where do handoffs between your teams work well, and where are they difficult?” or “What would each of you need from this role in the first three months?” Our question guide offers other options. Avoid asking every person the same question solely to fill time.
Take brief notes about names and topics so a follow-up can be accurate. UC Berkeley recommends a timely thank-you after interviews. If you have each person's contact details, you may send short individualized notes; if not, a single message to the coordinator thanking the panel is sufficient. Our follow-up guide has templates. The panel is evaluating your work, but you are also seeing how colleagues communicate and disagree. Use that evidence when deciding whether to join.