“Tell me about a time when…” questions are called behavioral questions. Interviewers use them because past behavior is a reasonable predictor of future behavior. Instead of asking “Are you good under pressure?”, which everyone answers with “Yes”, they ask you to describe a real situation.
The STAR method is a simple structure for answering these questions clearly. It works just as well with school and volunteer examples as with work experience.
What STAR stands for
| Letter | Meaning | What to say | Share of your answer |
|---|---|---|---|
| S | Situation | The context: where, when, who | About 15% |
| T | Task | Your responsibility or the challenge | About 15% |
| A | Action | The specific steps you took | About 50% |
| R | Result | What happened, ideally with a measurable or observable outcome, and what you learned | About 20% |
The most common mistake is spending too long on the situation and too little on the action. Interviewers want to know what you did.
Common behavioral questions for entry-level roles
- Tell me about a time you worked on a team.
- Describe a time you had to meet a tight deadline.
- Tell me about a mistake you made and how you handled it.
- Give an example of a time you solved a problem.
- Describe a situation where you dealt with a difficult person.
- Tell me about a time you learned something new quickly.
- Tell me about a time you showed leadership.
Prepare four or five strong stories and you will be able to adapt them to most of these.
Example 1: Teamwork (from a school project)
“Tell me about a time you worked on a team.”
Situation: In my final-year marketing course, I was in a four-person team creating a campaign proposal for a local coffee shop.
Task: Two weeks before the deadline, we realized two teammates had researched the same competitor while nobody had done the customer survey.
Action: I suggested a 20-minute check-in, listed every remaining task in a shared document and asked each person to choose one based on their strengths. I took the survey, built it in Google Forms and shared it in three student groups. I also set two short check-ins per week.
Result: We collected 85 responses in five days and submitted on time. The owner liked our loyalty-card idea enough to try it. I learned that a short planning conversation early saves a lot of stress later.
Example 2: Pressure and deadlines (from a part-time job)
“Describe a time you worked under pressure.”
Situation: I worked weekend shifts at a busy bakery. One Saturday, a coworker called in sick and a large pre-order was due at 10 a.m.
Task: I had to keep the counter running and help prepare the order.
Action: I told the manager I could handle the counter alone if we put a sign up asking customers to be patient, and I packed the order in between customers using the order sheet as a checklist. I double-checked it against the receipt before the customer arrived.
Result: The order was ready by 9:50, and the customer came back the next month with another order. My manager asked me to train the next new hire on our pre-order process.
Example 3: A mistake (from volunteering)
“Tell me about a mistake you made.”
Situation: As a volunteer at a food bank, I was responsible for the weekly sign-in spreadsheet.
Task: One week, I noticed I had sorted one column without the rest, which mixed up family names and visit dates.
Action: I told the coordinator immediately, restored the file from the previous version and re-entered that day’s sign-ins from the paper sheet. Then I added a header row freeze and taught myself how to sort the whole table safely.
Result: The records were correct before the monthly report. Since then I always work on a copy before making big changes, which is a habit I now use for all data work.
Owning a mistake honestly, and showing what you changed, impresses interviewers far more than claiming you never make them. Our guide to handling mistakes at your first job builds on the same idea.
Example 4: Learning quickly (from a personal project)
“Tell me about a time you learned something new quickly.”
Situation: I wanted to apply for junior data roles but had never used pivot tables.
Task: I gave myself one week to learn them well enough to analyze a real dataset.
Action: I followed the official Microsoft Support tutorial, then practiced on a public dataset of library checkouts and built a summary by month and category. I wrote a short note explaining how I validated the totals.
Result: I can now build and check a pivot table confidently, and I used the project as a portfolio example in applications.
If you want a practice dataset, our pivot table walkthrough includes one.
Tips for strong STAR answers
- Use “I”, not only “we”. Teamwork matters, but the interviewer needs to know your contribution.
- Be specific. Names of tools, numbers, timeframes and outcomes make stories believable. Keep numbers truthful.
- Keep it to about two minutes. Practice out loud and trim.
- End with a lesson when the result was modest. What you learned is a result too.
- Prepare a story bank. Write your stories in a document and note which questions each one can answer.
Write four stories this week
Write four STAR stories this week using the template above: teamwork, pressure, a mistake and learning quickly. Practice each aloud twice. Then use them as the backbone of your 48-hour interview preparation plan.