TL;DR: Behavioural questions ("tell me about a time when...") ask for evidence of how you have actually handled situations, because past behaviour is the best available predictor of future behaviour. Answer each one with a real example in STAR order (Situation, Task, Action, Result), speak in the first person about what you did, and quantify the outcome. Prepare a bank of five to seven stories that cover failure, conflict, pressure and initiative.
The idea behind behavioural interviewing is simple: how you handled things in the past is the best available guide to how you will handle them in the future. Where a technical question tests what you know, a behavioural question digs into your actual track record.
This format runs deep in Australian hiring. Structured panel interviews are the norm across government, health, education, and most graduate programs, and they lean heavily on behavioural questions to assess the soft skills a resume cannot show: how you handle team friction, keep your head under deadline pressure, and work with people who are not like you.
What Panels Are Really Listening For
Interviewers are not hunting for a single "correct" answer. They are listening for authenticity and evidence. A competency question checks whether you can use a piece of software; a behavioural question reveals what you actually did the day that software fell over hours before a board presentation.
These questions are also built to test cultural fit. So the best preparation is to comb back through your own history and pull out moments that show resilience, initiative, and adaptability. When you are in the room, resist the urge to speak in broad generalities. Specifics win.
Structuring Answers With the STAR Method
Behavioural questions are really requests for a short, well-told story, and a wandering story loses the panel. The STAR method, Situation, Task, Action, Result, keeps yours tight. It is not a gimmick: the Australian Public Service Commission's applicant guide, Cracking the Code, presents the STAR model as a way to set out evidence against selection criteria and asks for specific examples of what you did, how well you did it and what you achieved. Interview panels score the same things.
1. Situation
Give the panel just enough context to understand the challenge, without a five-minute backstory.
In practice: "At my previous agency, our biggest client was threatening to walk after a run of missed deadlines and patchy communication from the account team."
2. Task
Pin down your role. What were you actually responsible for? Keep it short and separate your job from the team's.
In practice: "As the newly appointed lead on the account, my job was to repair the relationship, audit what had been missed, and put a reliable communication rhythm in place."
3. Action
This is the heart of it, and where most people slip. Walk through the specific steps you took. Say "I", not "we". The panel is assessing you, not your old department, and in APS-style interviews a team-focused answer that hides your personal contribution is one of the most common reasons a strong candidate gets marked down.
In practice: "I booked a face-to-face meeting with the client for an honest listening session. Back at the office I set up a shared project dashboard so they could see our progress in real time, and I introduced a 15-minute daily stand-up with our team to catch problems early."
4. Result
Never leave the story hanging. The result is where you prove the value, ideally with a number: a percentage, dollars, hours saved, or specific feedback.
In practice: "Within 60 days we cleared the backlog. The client's satisfaction score climbed by 45%, and at the end of the financial year they renewed and lifted their retainer by 20%."
Common Prompts, and How to Handle Them
1. "Tell me about a project or idea of yours that failed. What did you take from it?"
Why they ask: every workplace needs people who can cop a setback and learn from it rather than point fingers. This one tests emotional maturity.
A strong response:
"In a community outreach role, I championed a local direct-mail campaign to lift engagement. The conversion rate was poor and we ended up underwater on it. I'd leaned too hard on demographic assumptions instead of running a small test first. I shifted the remaining budget into targeted digital ads, which recovered the numbers, and I rebuilt our campaign checklist so pilot testing is now mandatory before any full launch."
2. "Tell me about a time you disagreed with a manager's decision but had to carry it out anyway."
Why they ask: it is a test of professionalism. Can you disagree respectfully and still commit fully once the call is made?
A strong response:
"During a major rollout, my director cut the QA window sharply to hit a quarterly target. I pushed back and documented my concerns about the bug risk. Leadership decided to proceed, so I got behind it, rallied the team through a focused sprint, and we launched. We did hit a couple of the issues I'd flagged, but because I'd documented them we patched fast. It reinforced for me that you can voice a concern clearly and still commit to the team's decision."
3. "Tell me about a time you turned an angry customer around."
Why they ask: client-facing work needs patience and empathy. This checks your de-escalation skills and whether you can put the relationship ahead of your ego.
A strong response:
"A major client hit a service outage and was, fairly, furious, and talking about cancelling. Instead of jumping in with excuses, I let them vent for a few minutes, acknowledged the frustration, and took personal ownership of getting it fixed. I coordinated directly with our engineering lead and gave the client hourly updates until it was resolved. They not only renewed, they asked to have me as their account manager."
4. "Tell me about a conflict with a colleague."
Why they ask: friction happens in every team. Panels want to see you stay objective and fix the problem rather than sound like you are dobbing someone in.
A strong response:
"I was co-leading a software launch with a peer who kept missing internal deadlines, which put our release date at risk. Rather than escalating straight to our manager, I had a quiet one-on-one with them. It turned out they were buried under a hidden workload from another project. We reworked the timeline together and I picked up two of their admin tasks to give them breathing room. We shipped on schedule, and the working relationship came out stronger."
How to Prepare
Theory is easy; delivery is the hard part.
- Build a small story bank. You do not need 50 stories. Pick 5 to 7 defining moments that cover a range of skills, such as leading a team, recovering from a setback and improving a process, and you can reshape one good story to answer several questions. If you are applying for APS roles, draft these directly against the selection criteria.
- Say them out loud. Writing them down helps, but speaking them is what makes you sound natural instead of scripted. Practise with a friend, record yourself, or run a voice mock interview that asks behavioural questions, adapts its follow-ups to your resume and target role, and scores each answer on STAR structure and specificity.
- Reuse the structure elsewhere. STAR works just as well for resume bullet points, cover letters, and your next performance review.
The Bottom Line
Doing well in a behavioural interview comes down to preparation. Build a bank of varied real experiences, each showing a different side of how you work, and rehearse them in STAR order. Do that and "tell me about a time" turns from a stumbling block into your strongest few minutes in the room.
Frequently Asked Questions
Q: What are behavioural interview questions?
A: Questions that ask for a specific example from your past, usually starting "tell me about a time when" or "describe a situation where". They assess how you actually behaved under real conditions, such as conflict, pressure or failure, rather than how you say you would behave.
Q: What are the most common behavioural interview questions?
A: A time you failed and what you learned, a disagreement with a manager or colleague, a difficult customer or stakeholder, a tight deadline or competing priorities, a time you showed initiative, and a time you had to influence someone without authority. Most prompts are variations on those themes.
Q: How do I answer a behavioural question if I have no work experience?
A: Draw on university projects, part-time or casual work, volunteering, sport or community roles. Panels want evidence of the behaviour, not a corporate setting. A group assignment where you resolved a conflict is a legitimate example of teamwork under pressure.
Q: What does STAR stand for in an interview?
A: Situation, Task, Action, Result. You set the scene briefly, state what you were responsible for, describe the specific steps you personally took, and finish with the outcome, ideally with a number such as a percentage, dollar figure or time saved.
Q: How long should a behavioural interview answer be?
A: About one to two minutes spoken. Keep the Situation to two or three sentences, spend most of the time on the Action and Result, and let the panel ask a follow-up if they want more. A written STAR response to an APS selection criterion is usually a few short paragraphs per criterion, within whatever word limit the agency sets.
Q: Is the STAR method used for APS selection criteria?
A: Yes. The Australian Public Service Commission's Cracking the Code guide describes the STAR model as one way to present information against selection criteria, and asks applicants for specific examples of what they did and what they achieved.
Q: Should I say "I" or "we" in a STAR answer?
A: Say "I" for the Action. The panel is assessing your contribution, not your team's. You can mention the team in the Situation, but the steps you describe should be the ones you took yourself.
Q: How many STAR stories should I prepare?
A: Five to seven real examples covering different skills, such as leading others, handling conflict, recovering from a mistake and improving a process. One good story can usually be reshaped to answer several different questions.
