How to choose your best STAR interview examples
Your biggest project may be a poor STAR example. In a large program, your own decisions can disappear behind the size of the team or the prestige of the client.
A smaller story often works better. The interviewer can see what you did, why you chose that approach and what changed. You only need a few stories like that, not a memorised account of every project you have completed.
Quick answer: Choose STAR interview examples that closely match the role, involve a specific situation, show your individual contribution and end with a result you can support. Prefer examples with enough complexity to demonstrate judgement, but do not select a dramatic story if your role in it was minor or the claimed impact cannot be verified.
Quick selection guide
A strong STAR example should:
- relate directly to a capability or responsibility in the role description
- describe one specific situation rather than your usual approach
- make your responsibility and decisions clear
- contain enough challenge, ambiguity or constraint to demonstrate judgement
- finish with a credible result, lesson or next step
- remain accurate when the interviewer asks follow-up questions
An impressive title cannot rescue a story that does not answer the question. Relevance and credibility matter more than scale.
For guidance on structuring the answer after you select the example, read The STAR Interview Method: A Practical Guide With Credible Examples.
How do you choose your best STAR interview examples?
The Australian Public Service Commission recommends examples that relate to the duties and level of the job. The NSW Public Service Commission gives similar advice: focus on the capabilities and behavioural indicators in the role description.
Before searching your memory, mark up the role description. Look for:
- role purpose
- key responsibilities
- required capabilities or selection criteria
- seniority and expected level of autonomy
- repeated words in the advertisement
- challenges mentioned by the hiring manager or recruiter
Then turn the notes into a short evidence map.
| Role requirement | What an interviewer may want to hear | Possible evidence |
|---|---|---|
| Stakeholder management | How you built agreement or managed competing needs | A disagreement, escalation or cross-functional decision |
| Problem-solving | How you analysed an unclear issue and chose a response | A delivery risk, process failure or customer problem |
| Leadership | How you created direction, enabled others or made a difficult decision | A recovery plan, team change or decision under pressure |
| Planning and delivery | How you balanced scope, time, dependencies and quality | A launch, transition, implementation or competing deadlines |
| Communication | How you adjusted information for different audiences | An executive briefing, workshop or difficult conversation |
| Adaptability | How you responded when assumptions or conditions changed | A revised plan, new constraint or unexpected dependency |
Preparing one answer for every possible question is wasted effort. A good story can cover several related capabilities, although that does not mean it fits every question.
Build a candidate story list
Start with six to ten situations. A few words are enough at this stage. You are collecting possibilities, not writing answers.
Look for times when you:
- resolved a difficult problem
- influenced a decision
- managed disagreement
- identified or reduced a risk
- recovered delayed or unclear work
- improved a process
- handled competing priorities
- supported a customer or stakeholder through change
- made a mistake and corrected it
- enabled a team to succeed
Examples can come from employment, study, volunteering, community work or sport. The Australian Public Service Commission points to work, study and community roles. Monash University suggests checking whether a personal example is acceptable when no work example fits. Experienced professionals will usually have a closer match at work, but the source matters less than the quality of the evidence.
Use a simple candidate list:
Situation:
Capability demonstrated:
My responsibility:
Key action:
Result or current status:
Evidence available:
Concerns or missing information:
Do not skip the final line. It catches stories that sound strong until you realise they depend on a number, outcome or level of authority you cannot confirm.
Ascending Careers keeps these details while they are fresh. When an interview appears, you can look for a relevant situation instead of rebuilding the last few years from memory.
Score each example against five criteria
The scorecard below helps when several stories seem equally useful. Give each one a score from 0 to 2 in five areas.
| Criterion | 0 points | 1 point | 2 points |
|---|---|---|---|
| Role match | Weak connection to the role | Relevant to a general capability | Directly demonstrates an important requirement |
| Personal action | Your contribution is unclear | You supported the action | Your decisions and actions are specific |
| Appropriate complexity | Routine activity with little judgement | Some challenge or constraint | Clear ambiguity, risk, trade-off or stakeholder complexity |
| Evidence quality | Result is assumed or unsupported | Result is partly observable | Result is specific and supportable |
| Adaptability | Useful for one narrow question | Could answer two related questions | Can support several related questions without changing the facts |
Treat the total as a prompt, not a verdict. You still need to remember the story accurately, discuss it safely and match it to the question.
Illustrative comparison
The examples below are fictional and demonstrate the selection method only.
| Candidate example | Role match | Personal action | Complexity | Evidence | Adaptability | Selection decision |
|---|---|---|---|---|---|---|
| Coordinated resolution of conflicting testing assumptions across two teams | 2 | 2 | 2 | 2 | 2 | Strong example for influence, problem-solving and stakeholder alignment |
| Attended weekly status meetings for a major transformation | 1 | 0 | 0 | 0 | 0 | Do not select unless there was a specific contribution or decision |
| Created a decision log that clarified ownership during a delayed project | 2 | 2 | 1 | 2 | 2 | Strong example for communication, organisation and recovery |
| Contributed to a successful company-wide launch | 2 | 0 | 2 | 1 | 1 | Clarify your individual contribution before selecting it |
| Recommended a process change that was accepted, but post-launch results are unavailable | 2 | 2 | 1 | 1 | 2 | Usable if the result is described honestly as adoption, not proven long-term impact |
The fifth story is still usable even though the long-term result is unknown. The recommendation was accepted. That is the verified result. Leave out later savings or performance improvements if you never saw the evidence.
Choose relevance over prestige
Suppose you are interviewing for a role that requires influencing stakeholders without formal authority.
You have two possible examples:
- A large transformation program where you were one member of a broad delivery team.
- A smaller project where two teams disagreed, and you personally clarified the issue, brought the right people together and facilitated a workable decision.
The transformation sounds more prestigious. The smaller project is probably the better answer because the interviewer can see your actions and how they match the capability.
Ask four questions:
- Can I explain exactly what I did?
- Did I make a decision, solve a problem or influence an outcome?
- Can I explain why I chose that approach?
- Can I support the result without exaggeration?
If those answers come easily, the story should hold up when the interviewer asks for more detail.
Make your personal contribution clear
Team results are fair to use. Just make your part clear.
Too vague:
We worked together, improved the process and delivered the project successfully.
Clearer:
Two teams were using different approval assumptions. I mapped the conflicting steps, confirmed the constraints and facilitated agreement on one approval path. I documented the decision and owners. The project resumed with one agreed process, although I did not have access to post-launch cycle-time data.
The second version shows your part without claiming the team’s work or inventing an impact that nobody measured.
Choose a mix of story types
If every story ends in a successful launch, you will struggle with questions about disagreement, changing direction or work that went wrong.
Include examples involving:
- a strong delivery or achievement
- a difficult stakeholder or disagreement
- a risk or problem you identified
- a change in direction or unexpected constraint
- a mistake, setback or approach that needed adjustment
- collaboration or influence without formal authority
For a setback question, choose something real but safe to discuss. The interviewer wants to hear that you took responsibility, corrected the problem and learned from it. A flawless story misses the point.
Use recent examples when they are equally strong
Monash University advises candidates to use experiences from the previous 18 to 24 months. Use that as a guide rather than a cut-off date.
A recent example is easier to recall and usually reflects your current level. Keep an older one when it:
- closely matches the role
- demonstrates a capability not shown in your recent work
- involved significant complexity
- remains accurate and safe to discuss
- reflects the level at which you are now applying
Before discarding an older story, check whether a recent one gives you evidence that is just as good.
Avoid these common selection mistakes
| Mistake | Better approach |
|---|---|
| Choosing a routine task | Find the specific challenge, decision or improvement within the work |
| Using a team success with no clear contribution | Separate your action from the shared outcome |
| Adding an invented result | State the observable result and what remains unknown |
| Preparing several similar stories | Include delivery, disagreement, risk, change and learning examples |
| Choosing prestige over relevance | Select the story that best demonstrates the assessed capability |
| Revealing restricted information | Generalise names and details while preserving the professional evidence |
A practical 20-minute selection exercise
- Read the role description and list the five requirements most likely to be assessed.
- Write one-line reminders of six to ten relevant experiences.
- Score each example for role match, personal action, complexity, evidence quality and adaptability.
- Choose three stories that cover several important capabilities between them.
Once you have your three, record what happened, your responsibility, your actions, the shared outcome and the evidence. Add anything you cannot verify. Ascending Careers keeps those source details together, so you can prepare without memorising a script or stretching the result.
Frequently asked questions
Should I choose my biggest achievement?
Only if it matches the role and makes your contribution clear. A smaller example may give the interviewer better evidence.
Can I use the same STAR example for more than one question?
Yes, if it genuinely demonstrates several capabilities. Change the emphasis, not the facts. During one interview, use another suitable story rather than repeating the same one several times.
What if I do not have a workplace example?
Try study, volunteering, community activities or sport. The Australian Public Service Commission points to work, study and community roles. Monash University suggests asking whether a personal example is acceptable when no work example fits. Whichever source you use, match it to the capability and explain the context.
Does every example need a positive result?
No. A question about a setback or mistake needs an honest example. Explain what happened, how you responded and what you changed afterwards. Trying to disguise every failure as a hidden success sounds rehearsed.
What if the final outcome is unknown?
Stop at the last result you can verify. Perhaps your analysis was accepted, a risk was escalated or a revised process was approved. Leave out any downstream impact you did not observe.
How many STAR examples should I prepare?
There is no universal number. Start with three adaptable examples tied to the main role requirements. Then look for gaps, such as conflict, setbacks or leadership. A later article in this series will examine how many stories are practical for different interviews.
Choose evidence you can defend
The best STAR example is the one you can defend when the interviewer starts probing. They should be able to see your judgement, your actions and the result without having to untangle you from the rest of the team.
Start with the role, compare a few stories and keep the ones that still sound accurate when someone asks, “What did you do, and how do you know it made a difference?”
Start building your career story bank
Editorial note
The workplace examples and scorecard results in this article are illustrative. They are designed to demonstrate a selection process and should not be copied as claims about your own experience.
References
- Australian Public Service Commission, Cracking the Code: Applying for an APS Job, accessed 2 August 2026. https://www.apsc.gov.au/working-aps/joining-aps/cracking-code/3-applying-aps-job-cracking-code
- Australian Public Service Commission, The Interview and Other Assessment: Cracking the Code, accessed 2 August 2026. https://www.apsc.gov.au/working-aps/joining-aps/cracking-code/7-interview-and-other-assessment-cracking-code
- NSW Public Service Commission, Capability Application Tool, accessed 2 August 2026. https://www.nsw.gov.au/nsw-government/public-sector-capability-framework/resources-index/capability-application-tool
- The University of Queensland, STAR Template, 2025, accessed 2 August 2026. https://employability.uq.edu.au/files/199782/SES%20-%20Careers%20-%20STAR%20Template%20-%202025.pdf
- Monash University, Preparing for an Interview, accessed 2 August 2026. https://www.monash.edu/jobs/how-to-apply/interview-preparation
- The University of Western Australia, Interview: Careers and Jobs, updated 27 November 2024. https://www.uwa.edu.au/about/working-at-uwa/careers/applying/interview