Somewhere near the end of most interviews, someone on the panel asks what you'd like to know. It's easy to treat that as the wind-down, but it's the one part of the meeting where you choose what's discussed, and it's a chance to work out whether this role and team are right for you.
That second part took me a while to take seriously: you're assessing them as well. Walking in with that in mind changed the tone of what I asked, for the better.
What makes a question worth asking
A simple three-part test covers most of it:
- Is the question relevant to this role and team?
- Is the answer not already obvious, or sitting on the department's website?
- Will the answer actually help you understand the role, the team or the work?
If a question passes all three, it's worth its slot. If a ninety-second look at the website would answer it, it's probably not the best use of your limited time.
Research makes questions specific. "While I was reading your annual report, I noticed the move towards regional service delivery. How does that affect this team's work?" is more useful than "what's the department's direction?", and you can only ask it because you did the reading. There's no formula needed. Mention what you read when it makes the question clearer, add why you're asking when that helps aim the answer, and otherwise keep questions short. A brief question with a follow-up is usually easier to answer than a long, layered one.
How many to prepare
Somewhere around four to eight, written down in priority order, works well for many people, though there's no correct number. Panels vary in how much time they leave for candidate questions, and some leave very little, so put the questions you most need answered first.
If the conversation has already covered your list, it's fine to say so: "you've actually answered most of what I'd prepared, particularly around the reporting line. The one thing I'd still like to ask is..." That's a normal thing to say, and it beats padding the time.
A page of notes is fine in many interviews. If you're unsure what's allowed in a particular process, the candidate information pack or the contact officer can tell you.
Questions about the role
These are the core of the list, because the answers affect what your working life would actually be like.
- What would you hope the person in this role has achieved after the first 12 months?
- What are the main priorities for the team at the moment, and what's proving hardest about them?
- What does the role involve day to day, beyond what's in the position description?
- Why is the position vacant?
- How is the team structured, and where does this role fit?
- How much autonomy does the role carry?
- What opportunities are there for development, training or study support?
The 12-month question is the one I'd usually ask first if time is short, because the answer gives you a concrete picture of what the role involves and how realistic the expectations are. If the answer is brief or general, it's worth remembering that panels are answering under time pressure and the person best placed to answer may not be in the room, so it isn't worth reading much into a short reply on its own.
Questions about the team and the manager
The person who'd supervise you affects a lot about the day-to-day experience of a role, so it's reasonable to spend a question here, respectfully.
- How does the manager usually support and communicate with the team?
- What do people who do well in this team tend to have in common?
- What's kept you working here?
What you're checking is fit. If you do your best work with room to run and the answer describes daily check-ins, better to learn that now. Both styles are legitimate ways to manage; one of them may not be right for you.
Keep away from questions the panel may not be able to discuss: confidential staffing decisions, why a specific person left, other applicants, or internal matters. If a question would put a panel member in an awkward position, it doesn't belong in the interview.
Conditions, flexibility and salary
Questions about flexible work, location, travel, hours and conditions are legitimate. They're often material to whether the role works for your life at all.
The practical question is who to ask and when, and that varies. Some of it is on the advertisement or in the candidate information pack. The contact officer can usually answer conditions questions before you even apply, which is often the easiest route. Recruitment or HR handle the detail at offer stage. And the panel can answer if it comes up naturally, though the interview itself, where time is short and focused on assessing your claims, is rarely the best moment for a detailed conditions discussion. If something is a dealbreaker, like a fixed location requirement, sort it out early through the contact officer rather than at offer stage.
Salary is attached to the classification and the range is published, so there's rarely a reason to ask what the role pays. The one live question, whether you might start at a higher pay point within the range, usually belongs after an offer, with recruitment staff, unless the panel raises it. A later chapter covers that conversation.
If panel members have different roles
When you know who's on the panel, it makes sense to direct questions to the people best placed to answer them: the technical question to the technical specialist, the team question to the person who works in it. Include the whole panel naturally so the discussion doesn't become focused only on the chair, but there's no need to manufacture a separate question for each person. One good question aimed at the right person is worth more than four forced ones.
What to do with the answers
The answers are information to weigh alongside everything else you learn through the process: the position description, the contact officer conversation, the offer itself. Collect it all and judge the overall picture rather than any single response, since interviews are short and answers get compressed.
Some answers are worth acting on within the process too. If the panel describes what a successful first year looks like and it matches your experience, it's natural to say so briefly. And whatever you learn about the team's priorities can help you decide which examples to lead with in any later round.
For what to ask about next steps and timeframes, see the chapter on finishing the interview.