The STAR method for UK application forms, with examples
STAR stands for Situation, Task, Action, Result. It's a way to tell one specific example clearly. On a written form, keep the situation and task short and spend most of your words on what you did and what changed.
What STAR means
| Letter | What to write | Share of a 250-word answer |
|---|---|---|
| Situation | Where and when, in one or two sentences | about 15% (with Task) |
| Task | What needed doing, and your part in it | |
| Action | The steps you took, and why | about 60% |
| Result | What changed, and what you learned | about 25% |
The split is a rule of thumb, not a requirement. The point is that recruiters score your actions, so those get the most space.
What recruiters look for
- One specific occasion. "Tell us about a time" means one event, not what you usually do.
- "I", not "we". Group projects are fine, but say what you personally did.
- Reasons, not just steps. Why you chose that approach shows your judgement.
- A real result. Numbers if they're true; otherwise say plainly what changed.
- Reflection. One line on what you learned or would do differently.
A structure to follow
- Write one or two sentences of context: where you were and what the challenge was.
- Write one sentence on your responsibility.
- Write three or four sentences of action, each starting with something you did.
- Write one or two sentences of result, then one on what you learned.
Some universities teach STARR or STARS, which add a final "Reflection" step. Use whichever you like; it's the same idea.
Example answer
Sam is a fictional second-year mechanical engineering student. The details are invented to show the shape of a good answer. Use your own.
Question: Tell us about a time you solved a problem.
Situation: Our Formula Student team's 3D printer kept failing halfway through long prints, wasting material and delaying parts.
Task: Other members had changed the print settings several times over two weeks. I offered to find the cause.
Action: Instead of changing settings again, I logged every failure: the time, the filament, the settings and the room temperature. The pattern pointed to one spool that had been left unsealed and had absorbed moisture. I dried it following the manufacturer's guidance, ran a test print with the original settings, and put a short note on the printer asking people to seal spools after use.
Result: The failures stopped and we got back on schedule. I learned to collect evidence before changing anything, and I now do that first.
About 125 words. On a real form you can drop the labels and write it as one paragraph.
Common mistakes
- Too much situation. Half the answer spent setting the scene.
- A general habit instead of an event. "I always communicate well in teams."
- No result, or an invented one. A made-up percentage falls apart when an interviewer asks how you measured it.
- The same example for every question. Use a different story for teamwork, leadership and problem solving where you can.
- AI-polished but empty. Generic tools can produce smooth STAR answers with no real detail. Recruiters notice the stock phrases. Start from your own notes on what happened.
FAQs
Should I write the STAR labels in my answer?
Usually not. Write a normal paragraph in STAR order. Labels can help in a very short answer if the form allows it.
What if my example isn't impressive?
The size of the example matters less than how clearly you explain what you did. A part-time job, a society or a group project all work.
Is STAR used in interviews too?
Yes. Competency interviews often follow the same pattern, and interviewers may ask about examples from your written answers.