"Are you resilient under pressure?" - "Yes, very." The question has been answered and nothing has been said. Someone running four interviews in a day hears that sentence four times, and by evening all four sets of notes say the same thing.
The STAR method turns it around. Instead of naming a quality, you tell an episode that proves it: Situation, Task, Action, Result, in that order. Where the interview sits in the German hiring process is covered in the complete application guide.
Why claims fall flat in an interview
Adjectives are free. "Team player", "structured", "resilient" are things anyone can say, and because everyone does, none of them carries information. The interviewer has one job: to predict how you will behave in the role, and the only material for that is how you behaved before.
Claims also do not stick, stories do. When three people discuss you afterwards, nobody quotes "she said she was resilient". They say: "That was the one with the month-end close."
And every claim provokes the same follow-up: "Can you give me an example?" Then you improvise in front of an audience. A STAR answer settles that before anyone asks.
STAR in four steps
S for Situation. The context, in two sentences: where, when, what was going on. The situation is the stage, not the play.
"In March the colleague who handled our Monatsabschluss, the monthly closing of the books, was out. Two days before the deadline, no handover."
The common mistake: the situation grows into half a CV and attention is gone before you have done anything.
T for Task. Your role in it, the step almost everyone skips. It separates "I was there" from "I was responsible".
"I had to take it over knowing only one of the three sites."
A for Action. What you did, step by step. The longest part, at least half the answer, and the only one where "I" belongs. The moment "we" appears, you vanish from your own story.
"I sorted out what was genuinely due first, then moved my own quarterly report with my manager."
R for Result. How it ended, as checkable as possible. Not "it went well in the end", but something a person could count.
"The closing went out on time, with two open items I had flagged in advance."
One complete example, before and after
Same question, same person, answered twice: "Erzählen Sie von einer Situation, in der Sie unter Zeitdruck standen." (Tell me about a time you were under time pressure.)
The claim version:
"I am used to time pressure, there was basically always time pressure where I worked. I am pretty stress resistant, I keep the overview and I prioritise. And when it gets tight, I stay a bit longer."
Not one of those sentences is checkable. The only concrete thing is the line about staying longer, and it says: I solve overload with overtime.
The same thing as a STAR story:
"In March the colleague who handled the monthly closing for three sites was out, two days before the deadline and with no handover. I stepped in knowing only one of the sites, with my own quarterly report running in parallel.
The first thing I did was sort out what was genuinely due. The closing was, the quarterly report had two weeks of slack, so I moved it with my manager, giving her a new date rather than a maybe. Then I asked each of the two unfamiliar sites for half an hour to walk me through their particularities, instead of guessing my way through unfamiliar folders. I worked through the numbers in delivery order, not alphabetically.
The closing went out on the deadline, with two open items I had flagged in advance. The list of questions I put together back then is now our handover guide."
Spoken, that is a little over ninety seconds, and both answers describe the same person. The second proves what the first asserts: prioritising, visible in what got moved; communication, because the manager knew beforehand; pragmatism, in the delivery order. And it invites "How did you justify moving the report?" rather than "What did that look like in practice?".
The weak R: results somebody could count
Most people manage S, T and A. The R is where it breaks down, usually as "in the end it went well", the sentence that lets a good story evaporate on the finish line.
That is rarely because there was no result. Plenty of jobs just do not produce percentages, and four substitutes carry as far:
- Time. "Onboarding used to take six weeks, afterwards two."
- Frequency. "Three queries a week turned into one a month."
- What others did with it. "The guide is used for every stand-in now."
- What did not happen. "Not one deadline missed, all year."
If no measure comes to mind, describe the state before and after. That is more honest than an invented figure. And estimate the order of magnitude: "roughly a third less" you can explain when somebody digs, an invented decimal place you cannot.
Record a result on the day it happens, not the evening before the interview: one sentence in your strengths collection is enough.
Five stories cover twenty questions
The classic preparation mistake is preparing for questions. There are too many. Prepare material instead, and five stories will get you through most interviews:
- A success you started yourself, not one that landed in your lap.
- A conflict with a person, not with a system.
- A mistake you spotted and reported yourself.
- A decision under pressure where you had to leave something out.
- Something new you taught yourself without instruction.
This works because interview questions are variations. "When were you out of your depth?" and "Tell me about a difficult decision" both reach for story four. You do not swap the story, you shift the weight: onto the A for the decision, onto the T for the overload.
Write four lines per story, one per letter, and do not memorise them word for word: memorised answers give themselves away through a rhythm that does not match the conversation. Rehearse them out loud, which is what interview practice is for.
When STAR does not fit
The method is a tool for behavioural questions, not for the whole conversation. Three places where it gets in the way:
The opening. "Wie war die Anreise?" (How was the journey?) is a warm-up, not a test. A structured story here makes you sound rehearsed before anything starts.
Motivation questions. "Why us?" and "Why the change?" want a position, not an episode. What counts is something concrete about this employer and a next step that follows from your last. A mini episode may appear as evidence, never as the main course.
Technical questions. "How would you approach that?" wants a method, explained hypothetically. Half a sentence of proof at the end is plenty: "That is how I did it at my last employer."
A warning on dosage: if every answer takes ninety seconds, you are giving a lecture. A conversation also needs one-sentence answers.
The short form: cover letter and CV
The same material works in writing, just compressed. In the Anschreiben, the German cover letter, a STAR paragraph is two sentences with no headings:
"When the colleague responsible dropped out two days before the monthly closing, I took over for three sites, sorted the tasks by deadline and delivered on time. The list of questions I compiled then is our handover guide today."
One sentence of action, one of result. That is the difference from "I am resilient and I work in a structured way", which proves nothing anywhere it appears.
In the Lebenslauf, the German CV, it compresses further: the R becomes the bullet point, S, T and A sit in the clause before it. What result-driven bullets look like is in the CV guide; more small things that decide between two similar applications are in the application tips.
The effort is a one-off: five stories written in one evening, then used in every interview, every cover letter and, when money comes up, to justify the number you name.
Frequently asked questions
Which questions is the STAR method for?
Behavioural questions: anything starting with "Erzählen Sie von einer Situation, in der ..." ("Tell me about a time when ...") or reducible to it, so conflict, mistakes, success, responsibility, time pressure, change. You do not need it for technical questions or for the question about your motivation.
How long should a STAR answer be?
Ninety seconds to two minutes is the ceiling, spoken out loud and timed. Situation and task in about two sentences each, your actions as the longest part, the result short and checkable. Longer turns into a lecture. Shorter stays a claim.
Do I need a separate story for every question?
No, and trying leads you astray, because there are far too many possible questions. A handful of well prepared stories covers most interviews, since the questions are variations on the same themes. You do not swap the story, you shift the weight between the four steps.
What if the outcome was bad?
Tell it anyway and add an L for Learning to the R. The project failed over one specific thing, since then you handle a second thing differently, and next time that is exactly what prevented the damage. For questions about mistakes, the reflection is the real answer, not a happy ending.