You open the interview invitation. It says: “Please prepare examples demonstrating leadership, teamwork, resilience and problem-solving.” Small issue: you’re 21 and have never managed the turnaround of an international corporation.
This is where a lot of students convince themselves they have “no examples.” Usually, they do - they’re just looking in the wrong places.
What STAR actually means
STAR is simply a way of telling a story clearly:
- Situation - what was happening?
- Task - what did you personally need to achieve?
- Action - what did you actually do?
- Result - what happened?
A competency question like “tell me about a time you worked effectively in a team” isn’t asking for your philosophy of teamwork. It’s asking for evidence.
Your examples don’t need to come from corporate jobs
Student examples can come from group coursework, university societies, sports teams, part-time work, volunteering, personal projects, hackathons, dissertations, competitions, tutoring, committee roles, organising events, or a difficult academic period. The experience matters less than whether it actually demonstrates the skill - someone can learn more about your leadership from organising a chaotic society event than from three weeks of shadowing people at a large bank.
Example: teamwork from a university project
Question: “Tell me about a time you worked with others to solve a problem.”
Weak answer: “In second year I did a group project. We had different ideas but worked together well and got a good mark.” Technically an answer. Not exactly gripping.
A STAR version:
Situation: In second year, I worked in a four-person group on a statistics project analysing a large public-health dataset.
Task: We had two weeks to produce the analysis and presentation, but halfway through the project we realised two members had interpreted the brief differently and we were duplicating work.
Action: I suggested we spend 20 minutes breaking the project into specific outputs, assigned ownership for each section and created a shared checklist so everyone could see what was still outstanding. I also combined our Python analysis into one notebook so we were working from the same results.
Result: We finished a day before the deadline and received 74%. More importantly, after restructuring the work we stopped duplicating analysis and the final presentation felt much more coherent.
Nothing spectacular happened - nobody saved the company £8 million. It’s still a good example because the behaviour is clear.
The Action section matters most
A common STAR mistake is spending 80% of the answer explaining the background: “There were four of us, and the assignment was worth 30%, and we’d been given it three weeks earlier, and one person was from Manchester…” Eventually the interviewer starts wondering whether they’ll live long enough to reach the Action.
Keep the Situation and Task short. Spend most of your answer on what you did, why you did it, and what decisions you made - that’s what’s actually being assessed.
Avoid saying “we” for everything
You can absolutely describe a team achievement, but the interviewer needs to know your contribution. Compare “We decided to organise the project differently” with “I suggested splitting the project into four workstreams and volunteered to combine the analysis before the final presentation.” The second version gives the interviewer something to assess.
A good rule: use “we” for team context, and “I” for your own actions.
Careevio’s Interview Prep tool is built around exactly this problem - turning things you’ve actually done into a reusable bank of STAR-shaped answers.
How to find examples when your mind goes blank
Don’t start with the competency - start with your experiences. Write down seven or eight things you’ve done over the last few years, then ask what each one might demonstrate:
| Experience | Possible competencies |
|---|---|
| Group coding project | Teamwork, conflict, problem-solving |
| Retail job | Communication, pressure, customer service |
| Dissertation | Organisation, independence, analytical thinking |
| Society event | Leadership, planning, persuasion |
| Marathon training | Resilience, discipline, goal-setting |
Suddenly you don’t need 25 different stories - you need a small bank of strong stories that can support several questions.
Build an evidence bank
For each useful experience, record the situation in a line or two, the problem or task, exactly what you did, what changed as a result, and which competencies it could demonstrate. For example:
Experience: Organising a society careers event
Situation: A speaker cancelled three days before the event.
Task: Avoid cancelling an event with 80 sign-ups.
Actions: Contacted previous society speakers, approached local alumni, changed the format from a single talk to a panel, and updated attendees.
Result: The event went ahead with three speakers and 65 attendees.
Competencies: Resilience, communication, initiative, organisation.
That one story could answer several different questions depending on which part you emphasise.
You don’t need a perfect result
Another misconception is that STAR stories must end triumphantly. Questions like “tell me about a mistake” or “tell me about a disagreement” are specifically asking for imperfect situations. A good Result might be: “We still missed our original target, but the changes reduced the delay, and I learned that I should have raised the issue earlier.” That can be far more believable than a story where everything worked out perfectly.
Add reflection when it helps
STAR technically ends at Result, but for graduate interviews, one sentence of reflection can make an answer noticeably stronger - for example: “Looking back, I should have clarified responsibilities at the start rather than waiting until halfway through the project, and I’ve done that much earlier in group work since.” That shows self-awareness. Call it STAR+R if you like, or don’t - there are enough acronyms in graduate recruitment already.
Example: leadership without being “the leader”
You don’t need to have been president of anything. Leadership can mean taking ownership when something needed doing:
“During a first-year engineering project, our group was falling behind because nobody had taken responsibility for coordinating the final submission. I created a timeline for the remaining tasks, checked what each person was comfortable owning and scheduled two short progress meetings before the deadline. I wasn’t the appointed group leader, but taking responsibility for the coordination helped us finish on time and receive a first-class mark.”
Job title: irrelevant. Behaviour: relevant.
Example: resilience without a dramatic life event
Resilience questions make some students panic because they think they need a cinematic hardship story. You don’t - a poor module result, a rejected society proposal, a repeatedly failing coding project, a difficult customer, or an unsuccessful application all work perfectly well. The interviewer is usually interested in what you did after things went wrong, not whether Hollywood could turn it into a film.
The best examples are specific
Weak: “I’m very organised because I always meet deadlines.”
Stronger: “During exam season I had three coursework deadlines within six days, so I mapped the remaining tasks by estimated hours, prioritised the earliest dependencies and blocked specific work sessions across the week. I submitted all three on time and avoided the usual final-night panic.”
Specific actions make ordinary experiences credible.
Prepare stories, not scripts
Don’t memorise a four-minute monologue for every competency. Instead, remember the situation, the challenge, three or four actions, the result, and the lesson - then practise explaining it naturally. If the interviewer interrupts or asks a follow-up, you can adapt, which is much easier than trying to find your way back to line 47 of a memorised speech.
Your goal before an interview
Aim to have six to eight strong experiences you understand properly. Between them, you should be able to cover common themes such as teamwork, leadership, communication, problem-solving, resilience, organisation, initiative, conflict, failure and achievement. That’s far more useful than desperately inventing a fresh example the night before every interview.
If you haven’t settled on your opening introduction yet, it’s worth pairing this with how to answer “tell me about yourself” in a graduate interview - and if your evidence bank feels thin, our guide on writing a CV with no work experience covers the same “find the evidence you already have” idea for your CV.
