STAR method examples for interview questions

Situation: In my final year at university, I was one of four students building a marketing plan for a local not-for-profit, with three weeks until the presentation.

Task: Two members had clashing ideas, and the work had stalled. I was responsible for the research section and wanted the team to agree on a direction.

Action: I suggested we test both ideas against the organisation's brief instead of debating them. I built a one-page comparison of each idea against the client's three stated goals and asked everyone to score them. We chose a combined approach, and I set up a shared task list with owners and dates so progress was visible.

Result: We presented on time, and the not-for-profit adopted two of our recommendations for its next campaign. I learned that shifting a disagreement onto shared criteria is often faster than trying to win the argument.

Situation: As a practice coordinator at a busy medical clinic, I noticed tension between reception and the nursing team over how same-day appointments were being booked.

Task: Nurses felt overloaded late in the day, and reception felt blamed. I needed to fix the booking process without either team feeling singled out.

Action: I met each team separately to hear their side, then pulled two weeks of booking data to see when the pressure actually occurred. I brought both groups together with the data rather than the complaints, and we agreed to hold back a small number of afternoon slots for urgent cases. I checked in with both teams weekly for the first month.

Result: Late-day overruns dropped noticeably over the following month, and the weekly check-ins were no longer needed. Both team leaders asked me to use the same approach for a later rostering issue.

Situation: In my first year as a junior analyst, I sent a weekly sales report to regional managers that used the wrong date range.

Task: One manager had already made a staffing decision based on it. I needed to correct the report quickly and stop it happening again.

Action: I told my manager as soon as I found the error, then sent a corrected report to every recipient with a short note explaining what had changed. I called the regional manager directly to walk through the correct figures. Afterwards, I added an automatic date check to the report and a two-minute review step before each send.

Result: The staffing decision was adjusted the same day, and the report has not had a date error since. It taught me to raise problems early; owning the mistake quickly made it much easier to fix.

Situation: Our software team's code reviews were taking several days, which slowed every release.

Task: I was not a team lead, but I wanted to shorten review time without adding pressure on anyone.

Action: I tracked review times for a fortnight to understand where the delays happened, and found most were caused by very large changes. I proposed smaller pull requests and a daily fifteen-minute review slot, trialled it myself for two weeks, and shared the results at our retrospective. I then wrote a short guide for new starters.

Result: The team adopted the approach, and reviews routinely finished within a day. My manager later asked me to mentor two graduate engineers, partly because of how I had led the change.

Situation: Two days before a large corporate event, the venue I was coordinating for cancelled because of a burst water pipe.

Task: I had to find a new venue and move 180 guests without losing the event or blowing the budget.

Action: I split the problem into venue, communication, and suppliers. I called five venues from our preferred list that morning and secured one within budget by moving the start time by an hour. I drafted the guest update for the client to approve, rebooked the caterer and audio-visual supplier, and kept a single shared checklist so the client could see progress hourly.

Result: The event went ahead on the original date, and the client booked us for their next two events. I now keep a backup venue shortlist for every large booking.

Situation: While working as a retail supervisor, a customer came in upset because a special-order item had arrived damaged for the second time.

Task: I needed to resolve the problem and keep the customer, who had been shopping with us for years.

Action: I listened without interrupting, apologised, and acknowledged that it was our problem to fix. I checked stock at nearby stores, found an undamaged item, and arranged a transfer for the next day. I inspected it myself on arrival and called the customer to confirm before they made the trip. I also reported the packaging issue to our supplier with photos.

Result: The customer collected the item the next day and thanked the team in a review. The supplier changed its packaging for that product line.

• Title: a short name you will remember, such as "Venue cancellation".
• Situation: one or two sentences of context.
• Task: what you were responsible for.
• Action: three to five specific steps you took, in order.
• Result: what changed, how you know, and what you learned.
• Skills it shows: for example problem-solving, stakeholder management, or attention to detail.
• When it happened: the month and year, so you can place it in your career history.