Handling follow-up questions in a government interview
Short answer
Follow-up questions are the panel's way of testing an example: what exactly you did, why you did it, what happened next and what you learned. They are normal and not a sign that your answer went badly. Prepare by asking yourself the obvious next questions about each example, and answer them briefly and honestly, including when the honest answer is “I'm not sure” or “I'd do it differently now”.
Why panels ask follow-up questions
Government recruitment is based on merit. In the APS, the Public Service Act 1999 sets out the merit principle in its Employment Principles, and panels are expected to compare candidates fairly against what the role requires. A first answer, however well prepared, often leaves gaps: whose idea it was, how hard the situation really was, whether the result lasted. Follow-up questions fill those gaps.
They are also how a panel tells a rehearsed answer from a real one. Someone who lived through an example can usually say more about it. Someone reciting a template tends to repeat themselves.
Not every panel works the same way. Some ask set questions and few follow-ups, so that every candidate gets the same treatment. Others probe more. Prepare as if follow-ups will come, and you will be ready either way.
Common types of follow-up
| Type | Sounds like | What it checks |
|---|---|---|
| Your role | “What did you do, specifically?” | That the example shows your capability, not the team’s |
| Reasoning | “Why did you choose that?” “What else did you consider?” | Judgement, which matters more as the level rises |
| Difficulty | “What made it hard?” “What did you do when that didn’t work?” | Whether the example is strong enough for the role’s level |
| Result | “How did you know it worked?” “What happened after?” | That the outcome was real and lasting |
| Reflection | “What would you do differently?” “What did you learn?” | Self-awareness and willingness to learn |
| Values and integrity | “Who else did you tell?” “Was there any pressure to do it another way?” | Accountability and ethical judgement |
| Clarifying | “Can you explain what that system does?” | That the panel understood the context |
How to answer a follow-up well
Answer the question asked. A follow-up is usually narrower than the original question. Answer it in a few sentences, then stop. You do not need to retell the whole example.
Be concrete. If the panel asks what you did, list your actions. If it asks why, give your reasoning, including what you were weighing up.
Stay consistent. Do not stretch your role or the result to sound stronger. The APSC notes that referee checks help panels validate claims made in your application or at interview, so an exaggerated detail can come back later.
It is fine to admit limits. “I wasn’t involved in that part, but I know the team lead handled it by…” is a better answer than a guess. So is “I’m not sure of the exact figure, but the backlog went from weeks to days.”
Take a moment if you need it. A short pause before answering is normal. You can also ask the panel to repeat or clarify a question.
Preparing for follow-ups
For each example in your bank, write down short answers to these:
- What exactly did I do, and what did others do?
- Why did I choose that approach? What else could I have done?
- What was the hardest part?
- How did I know it worked? What happened afterwards?
- What would I do differently now?
- Did anything about it involve a rule, a value or a judgement call?
If you cannot answer two or more of these for an example, it may not be strong enough. Pick another, or think back for the missing detail before the interview.
The NSW Capability Application Tool’s practice questions can help here: try answering one, then ask yourself the six questions above about your own answer. In the app, after you get feedback on an answer, you can answer the same question again with the fix and compare the two versions, which is a useful way to rehearse the deeper detail panels tend to ask for.
One answer, three follow-ups
Here is how a short exchange might go, using a fictional example.
The candidate says they cleared a backlog of reimbursement claims at a university faculty office by sorting them by type and handling the simplest ones first.
Panel: “Why the simplest ones first?”
Good answer: “Most of the simple claims only needed a receipt check, so clearing them quickly meant most staff got their money sooner. It also left a smaller pile of complex claims, which I could look at properly.”
Panel: “Did anyone disagree with that?”
Good answer: “One academic whose claim was complex asked why theirs was taking longer. I explained the order and gave them a date, and I kept to it.”
Panel: “What would you change?”
Good answer: “I’d tell the faculty about the order at the start, so people knew what to expect.”
Each answer is short, specific and honest. None of them retells the whole story.
Common mistakes
- Restarting the whole story instead of answering the narrow question.
- Getting defensive. A probing question is not an accusation.
- Falling back on “we” when asked about your role.
- Saying “nothing” when asked what you would change. Almost every example has something you would do differently.
- Making up detail to fill a gap. Say what you know.
Checklist
- For each example, I know my exact part and my reasons.
- I have one realistic thing I would do differently for each.
- I can describe the result without exaggerating.
- I am comfortable saying “I’m not sure” and offering what I do know.
- I have practised answering a follow-up out loud, not just the first question.
Answer makeover · fictional example
Q. You said the team fixed the backlog. What was your part in that, specifically?
First answer
Well, it was really a team effort. We all pitched in and worked together, and everyone did their bit to get it done.
What is missing
- Your own actions
- A clear boundary between your work and the team's
- Why your part mattered to the result
Improved answer
Fair question. Three of us were working on it, and my part was sorting the backlog. I went through around two hundred open requests and grouped them by type, which showed that about a third were duplicates that could be closed after a quick check. I closed those myself and passed the rest to my two colleagues by type so each of us worked on one kind. The sorting was my idea, and it's the part I'd say made the biggest difference.
Answer makeover · fictional example
Q. Looking back, what would you do differently?
First answer
Honestly, I don't think I would change anything. It went really well.
What is missing
- Reflection on the example
- A specific, realistic change
- What you have done since
Improved answer
I'd raise the problem earlier. I noticed the booking errors for about a week before I told my supervisor, because I wanted to be sure first. In that week more clients were affected than needed to be. Now, if I see something that could affect clients, I flag it early as a possible issue, even before I've worked out the cause.
Questions to try with your own experience
- Pick one of your examples. What did you do that no one else on the team did?
- Why did you choose that approach instead of another option?
- What would have happened if you hadn't stepped in?
- How did you know the result was a success?
- What would you do differently if the same situation came up tomorrow?
Sketch your answer, then say it out loud in the app and read the feedback.
After installing, choose “Government administration” · Free to start
An Android version is not available yet