Skip to content
Question Vault?
Free to readNo accountNo email wallNo invented statisticsNo ads on medical, legal or end-of-life pagesCopy or print any set and take it with you
03 · Professional & Academic

Group Interview Questions to Ask

Twenty questions to ask when you are the candidate facing a panel, or sitting alongside other candidates. They cover what the first 90 days involves, why the role is open, how work reaches the team, where handoffs break down, how mistakes get raised, the busiest month of the year, and what happens next in the process.

20 questions · each with a note on why · conversation guide

The questions

Open any question for the note

  1. Could you each say how you work with this role day to day?

    Why ask it

    In a panel, knowing who owns what stops you aiming a technical answer at the HR partner. It also gives you names to use later, which is the cheapest way to look composed in a room of five people.

  2. What does the first 90 days look like for whoever takes this job?

    Why ask it

    Asking about whoever takes it, rather than about yourself, is less presumptuous and gets a franker answer. Listen for whether those 90 days are described as learning or as delivery, because delivery means a backlog is already waiting.

  3. What problem are you hoping this hire takes off your hands?

    Why ask it

    The reason for the opening is more informative than the job description. If nobody on the panel can name a specific problem, the role may be a headcount allocation rather than a need, which usually turns into unclear priorities later.

  4. Is there anything on the job description that matters less than it looks?

    Why ask it

    Invites the panel to be honest about the wish list. Anyone who has read a hundred applications knows which requirement is decorative, and the answer tells you what to emphasize for the rest of the interview.

  5. Could you tell me what happened with the last person in this role?

    Why ask it

    Neutral phrasing, and the answer separates growth from churn. Promoted internally, left for a competitor, or quietly gone after six months describe three very different places. Ask once and let the panel decide who fields it.

  6. How does work reach this team, and who decides what gets done first?

    Why ask it

    This is a question about intake and prioritization, which sits behind most day-to-day frustration in any job. A vague answer often means whoever asks loudest gets served first.

  7. What tools does the team spend most of its day in?

    Why ask it

    Practical, and easy for anyone on the panel to answer, which makes it a good one to hand to a quieter interviewer. A stack that is years old is not automatically bad, but it tells you what the work will feel like.

  8. Where do handoffs between this team and other teams tend to go wrong?

    Why ask it

    Cross-team friction is the part of a job that never appears in a posting. Naming a specific handoff shows self-awareness; insisting there is none usually means nobody on the panel does the work themselves.

  9. If I made a mistake here, how would I find out about it?

    Why ask it

    Ask about mistakes rather than feedback in general. The route is the useful detail: straight from your manager, in a review three months later, or as a hint from a colleague. That route is the actual feedback culture.

  10. What was the last thing this team disagreed about, and how did it get settled?

    Why ask it

    Asking for the last disagreement rather than how disagreement is handled forces something concrete. Watch how the panel members look at each other while it is answered, which in a group setting tells you more than the words.

  11. How much of a normal week in this role is meetings?

    Why ask it

    A number is hard to dodge, and it predicts whether you will get to do the work you are being hired for. If nobody can say, ask what was on their own calendar yesterday.

  12. What does the team do when a deadline is clearly going to slip?

    Why ask it

    Deadlines slip everywhere; the response is what varies. Answers about renegotiating scope describe a functional team. Answers about pushing through describe the hours you will be keeping.

  13. Who trains new people, and is that part of their job or added on top?

    Why ask it

    Onboarding quality depends almost entirely on whether teaching you is somebody's actual responsibility or an unpaid extra alongside their own targets. This phrasing gets at that without sounding demanding.

  14. What is the busiest stretch of the year here, and what does it look like?

    Why ask it

    Every organization has a peak: a quarter close, a season, one annual event. What that month does to people's evenings is far more informative than any answer about work-life balance.

  15. What has changed on this team in the last year?

    Why ask it

    Recent change shows how stable the ground is: a reorganization, a new manager, half the team replaced. Panels tend to answer this honestly, on the assumption you could find out anyway.

  16. Is there anything about working here that people find harder than they expected?

    Why ask it

    Framed as harder than expected, which is much easier to answer than a question about drawbacks. If one person answers quickly and the rest go quiet, that pause is part of the answer.

  17. What would you want a new person to do differently from how it is done now?

    Why ask it

    Asks them to admit something needs improving, and hands you a plausible early contribution. It also tests whether they want a fresh perspective or simply another pair of hands.

  18. Where have people gone after this role, inside and outside the company?

    Why ask it

    Where people actually went matters more than the published ladder. If everyone who held this job had to leave the company to progress, the internal path is theoretical.

  19. Is there anything in my background you have reservations about?

    Why ask it

    Uncomfortable and worth asking, because an unspoken doubt does not resolve itself once you leave the room. Direct it to the hiring manager and give them space to be straight with you.

  20. What are the next steps, and when should I expect to hear from you?

    Why ask it

    Ends with information rather than another impression. Ask for the date they expect to decide and write it down: a missed timeline later is itself useful information about how the place is run.

Asking questions when you are not the only candidate

Practical guidance for the conversation itself

Work out which kind of interview this is

A panel: several interviewers, one of you

Here your questions are yours alone, and you have time for three or four. Address each question to a specific person by name and role, and try to give at least one to each interviewer. People who never got to speak tend to remember the candidate who included them.

A group: several candidates in the room together

You will realistically get one question, sometimes two. Choose one that helps everybody in the room, ask it clearly, and stop. Questions that are transparently about you individually land badly in a group format, where they are also assessing how you behave around others.

Find out the format in advance

Ask the recruiter who will be in the room and how long is set aside for candidate questions. This is a routine request, and the answer decides whether you prepare four questions or one good one.

Timing and delivery

Cut anything already answered

Half your list will be covered before you are invited to ask. Asking anyway signals you were rehearsing rather than listening. Prepare six so that three survive, and be ready to say that your other questions were already answered.

Build on what someone else asked

In a group interview, following another candidate's question with a specific extension of it works better than introducing a new topic. It shows you were listening, and the panel gets a fuller answer out of the exchange.

One question at a time

Stacking two questions into one turn means the panel answers the easier half. Ask, let it be answered fully, then decide whether the follow-up is still worth your remaining time.

Write the answer down

Taking a note of the 90-day answer and the timeline is not rude; it reads as serious. It also gives you something concrete to reference in a follow-up message.

What goes wrong

  • Do not lead with pay, vacation or remote policy in a group setting. Those are recruiter questions, and asking them in front of other candidates makes the panel wince even when the questions are fair.
  • Avoid asking the panel to describe the culture. You will get the values from the careers page. Asking what changed in the last year, or what people find harder than expected, gets the same information with evidence attached.
  • Do not try to catch a panel out. A question designed to expose a weak answer makes an enemy of whoever fumbles it, and that person is usually in the debrief.
  • Do not compete with the other candidates in the room. Interrupting, asking a fourth question, or correcting someone else's point is remembered longer than anything you said about your experience.
  • If time runs out, say you have two more questions and ask whether you can send them by email. That is a normal request and often gets you a written answer with more detail than the room would have allowed.