The STAR Method (and STARR, the Dutch Twist) for Behavioural Interview Questions

Most graduate interviews include at least one question that starts with “Tell me about a time when…” These are behavioural questions. They ask about real moments from your past, not what you would do in theory. The interviewer wants concrete proof that you have already done the things the job will require. 

The STAR method is the most common way to answer them. It stands for Situation, Task, Action, Result. It works because it forces a clear story instead of a vague claim. Saying “I am good with deadlines” proves nothing. Walking the interviewer through one specific deadline you actually hit, and how, proves it.

If you are interviewing in the Netherlands, there is a wrinkle that almost no English-language guide mentions. Dutch employers, the official Dutch jobs platform werk.nl, and most Dutch universities teach a five-step version called STARR. The extra R stands for Reflectie, or reflection. Skipping it in a Dutch interview can make a strong answer feel incomplete.

This guide covers both. STAR for the structure, STARR for the Dutch context, plus when to switch to one of the shorter variants (CAR, SOAR, PAR), and six worked examples you can borrow the shape of for your own stories.

Worth Knowing

STAR is the standard structure for behavioural interview answers: Situation, Task, Action, Result.

In the Netherlands, most employers expect the five-step version: STARR. The fifth step, Reflectie, is what you learned and what you would do differently.

Behavioural interviewing has 50+ years of research behind it. The core idea: past behaviour is the best predictor of future behaviour at work (Janz, 1982).

Prepare 5 to 7 stories that each cover a different skill. Most graduate interviews recycle the same question types: teamwork, conflict, leadership, failure, initiative, deadline pressure.

When STAR feels forced, switch to a variant: CAR for short answers, PAR for problem-led roles, SOAR for goal-led roles.

In 1973, the American psychologist David McClelland published an article in American Psychologist arguing that grades and IQ tests do not predict who will succeed at work. What predicts performance, he argued, is competencies: actual skills, demonstrated through actual behaviour. The article reshaped how recruiters think about hiring.

A decade later, Tom Janz tested the idea directly. In a 1982 study in the Journal of Applied Psychology, he compared what he called the patterned behaviour description interview, where candidates describe specific past situations, against unstructured interviews, where the conversation just flows. The behaviour-based interviews predicted job performance much more accurately.

That is the basis for every “Tell me about a time when…” question you will ever get asked. The reasoning is simple: someone who has handled a tough deadline before is more likely to handle the next one well. Someone who has resolved a team conflict before is more likely to do it again. Past behaviour predicts future behaviour.

This matters for your prep. Interviewers using behavioural questions are not trying to trick you. They are running a structured test. They have a list of competencies the job requires (often called a competency framework), and each question maps to one of them. Your job is to give them clear, specific evidence for each.

STAR has four steps. STARR has five. The difference is the second R, and in the Netherlands it is rarely optional.

STAR (international standard)

• Situation. The context. Where, when, who was involved.
• Task. Your specific responsibility or what needed to happen.
• Action. What you actually did. Use “I”, not “we”.
• Result. What happened. Numbers if you have them. The shorter, the better.

STARR (Dutch standard)

• Situation. Same as STAR.
• Task. Same as STAR.
• Action. Same as STAR.
• Result. Same as STAR.
• Reflectie (Reflection). What you learned, and what you would do differently next time.

STARR is taught by werk.nl (the Dutch government jobs platform run by UWV), Tempo-Team, Indeed Netherlands, the careerzone of Universiteit Leiden, and the HR resources at the Universiteit Twente, among many others. If your interviewer is Dutch and trained in the Netherlands, they are almost certainly running a STARR script, even if they don’t name it.

The interview question: “Tell me about a time when you had to work with a teammate you did not get along with.”

Situation (15 to 20 seconds)

“In my final-year group project at the Hogeschool van Amsterdam, I was paired with three classmates to build a market entry plan for a Dutch retailer expanding into Germany. One teammate had a very different working style from the rest of us. He preferred to work alone until the deadline and would not engage with our weekly check-ins.”

Notice: specific (final-year, Hogeschool van Amsterdam, market entry plan), short, and sets up the problem. Do not spend two minutes here.

Task (10 to 15 seconds)

“My responsibility was the financial section, which depended on his market sizing work. I needed his numbers a week before the deadline so I could finish my model and have time for review.”

Notice: it specifies your part, not the team’s. The interviewer is hiring you, not the team.

Action (60 to 90 seconds, the longest part)

“I tried two things. First, I sent him a calendar invite for a 30-minute one-on-one and brought a single concrete question: which retail categories he was sizing. He responded much better to a focused conversation than to the group chat. Second, I asked him whether he would prefer to share work in writing rather than in meetings, and we agreed he would post a draft in our shared Google Doc by a fixed Friday deadline. He did, and I used the data on the Monday.”

Notice: “I”, not “we”. Two specific actions, not five vague ones. No bad-mouthing of the teammate.

Result (15 to 20 seconds)

“We submitted on time and got an 8.2. More importantly, the rest of the team noticed and used the same approach with him for the final presentation prep, which was the smoothest part of the project.”

Notice: a number where possible, and a wider impact beyond just “it worked”.

Reflection (15 to 20 seconds)

“What I learned is that some teammates need a different format, not more pressure. If I had defaulted to the group’s preferred format, the project would have stayed stuck. Next time, I would have that one-on-one conversation in week one rather than week three.”

Notice: an honest learning, not a humble-brag. “Next time I would do X earlier” works much better than “I realised I was right all along.”

These are graduate-realistic. The situations are from group projects, internships, side jobs, and student board roles, not from a 10-year career. Each is structured as a STARR answer, slightly compressed, so you can see the shape rather than read a full transcript.

1. Teamwork

Common phrasings: “Tell me about a successful team project.” “What is your role in a team?” “Describe a rewarding team experience.”

Situation. During my Erasmus exchange in Lisbon, I joined a five-person group on an entrepreneurship course where nobody knew each other and three of us spoke different first languages.

Task. We had to build a business plan in eight weeks. I took on the role of integrating everyone’s sections into one coherent pitch.

Action. I set up a shared template in week one with consistent headings and tone, ran a 20-minute weekly sync to catch alignment issues early, and kept a single open question list so nothing got lost in WhatsApp threads.

Result. Our plan placed second out of twelve teams, and the lecturer flagged the consistency of voice as a strength.

Reflection. I underestimated how much of teamwork is just removing friction. Almost none of what I did was about ‘leadership’ in the dramatic sense, just keeping the system tidy. I would be more deliberate about that role from day one in future teams.

2. Conflict

Common phrasings: “Tell me about a time you disagreed with someone at work.” “Describe a conflict you handled.” “What do you do when a colleague is not pulling their weight?”

Situation. In my part-time job at a café in Utrecht, a more senior colleague kept changing the closing checklist without telling the rest of the team, and tasks were getting missed the next morning.

Task. I needed to address it without escalating to the manager and without making her feel attacked, since we worked the same shifts every week.

Action. I asked her for a 10-minute coffee before our next shift, framed it as me wanting to learn her reasoning, and asked whether we could agree on a single shared checklist that anyone could update with a date and initials. She agreed and was actually relieved someone had brought it up.

Result. The morning task gap dropped to zero within two weeks. Our manager noticed and asked her to roll out the same approach to the other shift teams.

Reflection. I learned that conflict often is not about the thing it appears to be about. She wanted the system to work; she just had not been asked. I now default to assuming good intent and asking the question early.

3. Leadership (without a leadership title)

Common phrasings: “Tell me about a time you led a team.” “Describe a time you took initiative.” “How have you influenced people who do not report to you?”

Situation. I was on the board of my study association, responsible for the introduction week for first-year students. Two weeks in, attendance at the evening events dropped by half.

Task. I was not the formal chair, but I felt the events were the part of intro week that actually built friendships, so I wanted to fix it.

Action. I ran a five-question survey to the cohort that evening, found that the issue was scheduling clashes with mandatory tutorials, and proposed moving the events 90 minutes later. I brought the data and the proposal to the next board meeting rather than just complaining about the problem.

Result. Attendance recovered to 80 percent of week-one levels in the following week, and the schedule change was kept for the next year.

Reflection. I learned that taking the lead does not mean overriding people. It means being the one who turns a vague complaint into a clear proposal with evidence. That is a much more reusable skill than being officially in charge.

4. Failure (or a mistake)

Common phrasings: “Tell me about a time you failed.” “Describe a mistake you made.” “What is something you would do differently?”

This is the question Dutch interviewers care most about and where Dutch directness is most rewarded. Do not pick a fake failure. Pick a real one with a real lesson.

Situation. In my bachelor thesis, I committed to a complex econometric model in week two without testing whether I could actually run the analysis on the dataset I had.

Task. Five weeks in, I realised the dataset was too small for the model to give meaningful results.

Action. I had a hard conversation with my supervisor about resetting scope. I switched to a simpler regression model that fit the data, rewrote my methodology section over a long weekend, and re-planned the remaining timeline with two weeks of buffer rather than one.

Result. The thesis still got a 7.5, which was below my target but acceptable, and I submitted on time.

Reflection. The real failure was not the model choice. It was that I committed before testing. I now build a one-day feasibility check into any project plan before I lock the approach. I have used that habit on every project since.

5. Initiative

Common phrasings: “Tell me about a time you went beyond what was asked.” “Describe a project you started yourself.” “When have you spotted a problem before others did?”

Situation. In my marketing internship at a Rotterdam scale-up, I noticed the team was manually pulling weekly metrics from three different tools every Monday, which took the marketing manager around two hours.

Task. Nobody had asked me to fix it. It was outside my brief, which was content writing.

Action. On my own time, I spent a Saturday building a Google Sheet that pulled the data from each tool’s export. I showed it to the manager on Monday, asked whether it would help, and offered to maintain it for the rest of my internship.

Result. It saved her around 90 minutes a week. She asked me to demo it in the team meeting, and I left the company with something they kept using after my internship ended.

Reflection. I learned that the highest-leverage initiative is usually a small, dull thing nobody else has time to fix. Splashy ideas are almost never the right place to start as an intern.

6. Deadline or stress

Common phrasings: “Tell me about a time you worked under pressure.” “Describe a tight deadline you had to meet.” “How do you handle competing priorities?”

Situation. In the final week of a four-month consultancy project for a client class, our main contact pulled out of the final presentation 48 hours before the deadline.

Task. I was the team’s presentation lead and needed both to keep the slide work on track and to find a replacement audience contact at the client so the presentation still had stakes.

Action. I split the problem in two. I delegated final slide polish to two teammates with clear styling rules so I did not have to micromanage. I spent my own time on the client side: emailed the contact’s manager directly, was honest about the situation, and got a colleague of theirs to attend.

Result. We presented on time, the new contact gave a strong endorsement, and the project got the highest grade in the cohort.

Reflection. I learned that under deadline pressure, the trap is doing everything yourself. Splitting cleanly and trusting people to do their parts is faster, even though it feels slower in the moment.

If a question does not have a clean “my task was X”, STAR can feel artificial. The Situation and Task steps blur together, and you waste time setting up rather than answering. That is when a variant earns its place.

The four frameworks at a glance

STAR / STARR is the default. It stands for Situation, Task, Action, Result, plus Reflectie in the Netherlands. Use it for most behavioural questions. A typical trigger is "Tell me about a time you led a team."

CAR is for short answers. It stands for Challenge, Action, Result. Reach for it on phone screens or whenever time is tight. A typical trigger is "In 60 seconds, why are you the right fit?"

PAR is for problem-solving roles. It stands for Problem, Action, Result. Use it in engineering, ops, or analyst interviews. A typical trigger is "Describe a problem you solved."

SOAR is for goal-led roles. It stands for Situation, Objective, Action, Result. Use it in sales, strategy, or project management interviews. A typical trigger is "Tell me about a goal you set and hit."

Notice: the actions and results steps are the same across all four. The variation is in how you set up the question. If your strongest setup is a problem (PAR), a goal (SOAR), or a tight challenge (CAR), use that. The interviewer cares about the substance, not the acronym.

Step 1 (10 minutes): pull the competencies from the job description

Read the job description carefully. List every phrase that describes a behaviour or skill. “Collaborates across teams”, “structured thinker”, “comfortable with ambiguity”, and so on. You are looking for four to six core competencies.

Step 2 (10 minutes): match a story to each

For each competency, write down one situation from your past that demonstrates it. It does not need to be from a job. Group projects, internships, side jobs, student board roles, volunteering, hackathons, sports teams: all of these count for graduate interviews.

Step 3 (25 minutes): write the STARR for your three strongest stories

Pick the three most versatile stories, the ones that could answer multiple competencies. Write each one out as a STARR, around 200 words total per story. Aim for two minutes when read aloud.

Step 4 (10 minutes): rehearse out loud, once

Read each story aloud. Time yourself. If you hit three minutes, cut. If you hit one minute, the Action step is probably too thin and you need more specifics. Read it aloud once more.

Step 5 (5 minutes): build a quick mental index

Make a one-line mental note for each story: “Erasmus group project = teamwork and integration.” “Café checklist = conflict and process.” “Bachelor thesis pivot = failure and recovery.” In the interview, when you hear the question, you scan the index, pick the story, and run it.

1. “We” instead of “I”

Saying “we decided to refactor the process” tells the interviewer nothing about you. They are hiring you, not the team. Replace “we” with “I” every time you can do so honestly. “I suggested we refactor the process”, “I led the refactor”, or “I did the data work while my teammate did the write-up” are all stronger.

This matters extra in the Netherlands. Dutch culture scores high on individualism in Hofstede’s framework, and Dutch interviewers expect you to claim your own contribution clearly. Hiding behind “we” reads as either modest to the point of vague, or as stealing credit.

2. The Situation eats the answer

Most graduates spend 60 to 90 seconds on Situation, then rush Action in 30 seconds. Reverse that. Situation should be a fast scene-setter (15 to 20 seconds). Action is where the interviewer is taking notes.

3. No numbers in the Result

“It went really well” is not a result. “We finished a week ahead of the deadline”, “attendance went up by 30 percent”, “the grade was 8.5”, or even “the team adopted the approach for the rest of the year” are. Even small numbers help. If you genuinely have none, name a concrete consequence.

4. Skipping the Reflection in a Dutch interview

If your answer ends with the Result and stops, a Dutch interviewer often pauses and waits. They are giving you space to add the reflection. Treat that pause as a prompt. Add what you learned and what you would do differently. If you do not, the answer feels incomplete to them, even if it would be fine internationally.

5. The fake failure

“My biggest weakness is that I work too hard.” Dutch interviewers find this almost insulting. Pick a real failure with a real lesson, told without melodrama. The point is not that you have never failed. The point is that you can think clearly about why something went wrong and what you took from it.

6. Polished to the point of robotic

Practising STARR is essential. Memorising STARR word-for-word is counterproductive. The interviewer can tell. Practise the structure and the key facts of each story, then let the wording vary. A small “um” in the right place reads as honest. A flawless recital reads as scripted.

STARR is a framework, not a script. The only way it actually clicks is by running through your own stories out loud, getting feedback, and tightening them.

That is exactly the kind of thing Aurora, GradGuide’s free AI career coach, is built for. You can run mock interviews with her, work through the question types you are most likely to get for the kind of role you are targeting, and pressure-test your STARR answers (including whether your Reflectie actually lands). She will push back on “we” answers, vague Results, and stories that are doing too much.