Questions to Ask in a Panel Interview, Role by Role

In a panel interview, aim each question at a specific panelist's role: priorities and expectations for the hiring manager, technical tradeoffs for the senior engineer, day-to-day work for a peer, cross-team handoffs for a product manager or designer, and next steps for the recruiter. Add one cross-functional question the whole panel can answer together. Plan to ask three to five questions in total, start each answer by looking at the person who asked before widening to everyone else, and send each panelist a separate thank-you note afterward.

The questions are not that different from a one-on-one. What changes is the audience: several people judging you at once, each from a different angle, each with a say in the outcome. For a broader bank of questions organized by topic, see our guide to questions to ask the interviewer.

Who is usually on the panel

A panel interview is simply two or more interviewers meeting you at the same time. Who sits on it varies by company, team and level, but for software and other technical roles these seats come up often:

Panels exist partly to keep one person's bias from deciding the outcome. The US Office of Personnel Management's guidance on structured interviews for federal hiring says a panel reduces the risk of bias in ratings, that most structured interview panels have two to four members, and that the interviewers must reach consensus on the rating they give each answer. Private employers combine panel feedback in different ways, but the practical lesson holds everywhere: every person in the room may influence the decision, including the one who barely speaks.

If your onsite is instead a sequence of one-on-one sessions, that is a full loop; our full loop interview guide covers that format.

Before the interview: map the panel

1. Ask who will be there. It is a normal request to the recruiter or coordinator: "Could you share the names and roles of the people I'll be meeting?" Some employers will tell you; some will not.
2. Look each person up. Check the company site and professional profiles for title, team and anything they have presented publicly. You want to know what they own, not personal details.
3. Write one line per person, such as "tech lead, owns the payments service, probably cares about reliability."
4. Prepare about two questions per panelist, plus two or three for the whole group. The extras cover questions that get answered during the conversation.
5. Plan for surprises. Panels change at the last minute. If someone unexpected joins, it is fine to ask, "Would you mind telling me a bit about your role on the team?"
6. Rehearse out loud. Your opening answer sets the tone for everyone at once. Practice your introduction (our "tell me about yourself" guide for software engineers has a structure) and a few core stories until each comes out in about two minutes.

Questions to ask, by panelist role

Pick the ones that fit the people actually in the room. Each question below works because the person you ask is the one best placed to answer it honestly.

The hiring manager

• "What would you want this person to have accomplished by the end of the first six months?"
• "What is the biggest thing the team needs to deliver this year, and what is most likely to get in the way?"
• "How do you like to give feedback, and how often do you meet one-on-one with the team?"
• "What tends to separate people who do well on this team from people who struggle?"

The senior engineer or tech lead

• "What is a technical decision the team made in the past year that you would make differently now?"
• "Where does the team carry the most tech debt, and how does paying it down get prioritized?"
• "How do design reviews work here? Who has to agree before something large ships?"
• "What would you want a new engineer to understand about the system in their first month?"

A peer engineer

• "What did your last two weeks actually look like?"
• "How quickly do code reviews usually turn around, and what kind of change gets pushback?"
• "How does on-call work, and how often does it interrupt evenings or weekends?"
• "What do you wish you had known before you joined?"

A product manager or designer

• "When a deadline is at risk, how do product and engineering decide what gets cut?"
• "At what point do engineers get involved in a new feature: discovery, spec, or after the design is done?"
• "Could you walk me through a recent disagreement between product and engineering and how it got resolved?"

The recruiter or HR partner

• "What are the next steps after today, and when should I expect to hear back?"
• "How does onboarding work for new engineers in the first few weeks?"
• "Which learning or growth programs do engineers here actually use?"

A director or skip-level manager

• "How does this team's work connect to the company's priorities for the next year?"
• "A year from now, what would make you say this hire was a great decision?"

Cross-functional questions for the whole panel

The most useful questions in a panel are often the ones that get two or three people answering the same thing. You hear how the team really works, and any differences between answers tell you more than a polished single response would.

• "How does each of you work with this role day to day?" This is a strong early question when you are unsure who does what.
• "When engineering and product disagree on scope, how does it usually get settled? I'd be curious to hear from a couple of you."
• "What has changed most about the team in the past year?"
• "If I joined, where would each of you want my help first?"

Direct the question rather than tossing it to the room. A question thrown open to everyone tends to produce a pause, and then the most senior person answers for the group. Naming two people works better: "Maybe [name] from the engineering side and [name] from product could each take this?"

Listen for consistency. If the tech lead says releases are smooth and the peer engineer describes weekend hotfixes, do not point it out as a gotcha. A neutral follow-up such as "What does a typical release week look like?" lets the panel fill in the picture.

How to distribute your attention

A few habits keep a panel feeling like one conversation instead of several separate ones:

• Start with the asker, then widen. Northeastern University's career center suggests facing the person who asked as you begin, then bringing your gaze across the panel as you continue so everyone feels included. Finishing back on the asker is a natural way to signal you have answered their question.
• Use names accurately or not at all. "Good question, [name]" builds rapport. Getting a name wrong does the opposite, so skip names you are unsure of.
• Do not play to one person. It is natural to drift toward the most senior panelist or the friendliest face. Spread your attention evenly, including to the person quietly taking notes.
• Bring quiet panelists in. If someone has not spoken, a question aimed at their area is the easiest way to include them without putting them on the spot.
• Keep answers tighter than usual. A long answer loses a group faster than it loses one listener. Give a clear answer, then stop and let the panel steer.
• Handle overlapping questions calmly. If two people ask at once, pick one and acknowledge the other: "Let me take [name]'s question first, and I'll come right back to yours."
• Reference earlier answers instead of repeating them. If a panelist asks something close to an earlier question, say so briefly and add a new angle: "Building on what I told [name] about the migration, the part I'd add is..."

Being watched by several people at once is what makes panels feel hard. If that spikes your nerves, the methods in our interview anxiety techniques guide apply directly. Practicing out loud helps too: a free AI mock interview in CoPilot Interview reads questions aloud and scores your spoken answer with notes on what to improve.

Follow-up questions that show you were listening

The strongest questions in a panel connect what different people said during the interview. They show you were tracking the whole conversation, not waiting for your turn.

To make this possible, jot down one short phrase per panelist as they speak: a project, a problem, a question they asked you. Those notes feed your follow-ups now and your thank-you notes later.

Remote panel etiquette

Video panels remove most of the cues you would use in a room. You cannot turn toward someone, and everyone sees their own arrangement of tiles. A few adjustments make up for it:

• Use gallery view. Learn how to switch between gallery and speaker view before the call so you can see every panelist at once.
• Put the camera at eye level and talk to the lens. Look at the camera when you speak and at faces when you listen. Remember you are on screen the whole time, including while others talk.
• Let names do the work your eyes would. Tile order differs on each person's screen, so looking left or right signals nothing. Saying "[name], to your question about testing..." tells everyone who you are answering.
• Hide your own video if it distracts you. Zoom and Microsoft Teams both let you hide your own tile from your view while others still see you.
• Leave a beat before answering. Lag makes people talk over each other. Wait a moment after a question ends, and if you collide with someone, stop and say, "Sorry, please go ahead."
• Have a fallback. Test the link and audio beforehand, keep the coordinator's contact handy, and if you drop, rejoin and give a one-sentence recap of where you were.

When you get to your questions on video, say whom each one is for before you ask it. "I have one for [name] and then one for the group" sets up the handoff and avoids the awkward silence of five people waiting to see who unmutes first.

After the panel: one thank-you note per person

• Get contact details. If you do not have everyone's email, ask the coordinator, or ask them to pass your thanks along with each panelist named.
• Send separate notes, ideally within 24 hours, each three or four sentences long.
• Make each note specific. Reference something that person said or asked. Panelists may compare messages, so do not send the same text with the name swapped.
• Restate interest once. One sentence connecting their point to why you want the role is enough.

For wording you can adapt to each panelist, see our thank-you email templates.

FAQ

How many questions should I ask in a panel interview?

Prepare about two per panelist and plan to ask three to five in total, depending on how much time is left. One well-aimed question for each key role plus one question for the whole group usually covers it.

Do I need to ask every panel member a question?

Not necessarily, but try to engage each person at some point, either with a direct question or by inviting them to add to a colleague's answer. If time runs short, prioritize the hiring manager and the people you would work with most closely.

Who should I look at when answering a panel question?

Start your answer facing the person who asked, move your eye contact across the rest of the panel as you explain, and return to the asker as you finish. On video, look at the camera and use names to make clear whom you are addressing.

What if one panelist is quiet or hard to read?

Do not write them off, because they may still have a say in the decision. Include them in your eye contact and, if there is a natural opening, ask them a question about their area of work.

Should I send a thank-you note to each panel member?

Yes, if you can get their contact details. Send a short, separate note to each person within about a day and reference something specific they said, so the notes do not read as copies of one another.