Tell Me About a Time You Went Above and Beyond: Answer Framework and Examples

"Tell me about a time you went above and beyond" is a behavioural interview question. Interviewers ask it because past behaviour is the best evidence they have of future behaviour, and because the phrase "above and beyond" is a neat way of separating people who do what is asked from people who care about the outcome. It is rarely asking whether you work long hours. It is asking whether you notice what a situation needs and act on it without being told.

Behind the wording, there are usually four things being assessed. First is ownership: did you treat the problem as yours, even though nobody forced you to? Second is judgement: did you pick something worth the extra effort, or did you burn energy on something that did not matter? Third is impact: did the extra effort change something measurable for a customer, a team, a society or a project? Finally, there is sustainability: can you do this without damaging your work, your colleagues or yourself?

Keep this four-part lens in mind as you read the rest of this guide. Every choice, from the story you pick to the way you close it, should help the interviewer tick those boxes.

The most common reason answers to this question fall flat is that the story is wrong, not that the delivery is poor. A good story has a clear baseline (what was expected of you), a clear extra (what you chose to add) and a clear result (what changed because of it). If you cannot state the baseline in a single sentence, the interviewer cannot see how far beyond it you went.

Test each candidate story against five questions. Was the extra effort voluntary? Was it aimed at something that mattered to someone else? Did it require skill or thought, not just hours? Is there a result you can describe? Can you tell it in two minutes without losing the thread? A story that passes at least four of these is usually worth rehearsing.

Prepare two or three candidates and decide on the day which fits the role. A story from a part-time job, a society, volunteering, a group project or a hobby is entirely acceptable, and often better than a thin work-experience story. If you are early in your career, our first job interview questions guide covers how to draw on non-work experience credibly.

The standard structure for behavioural answers is the STAR technique: Situation, Task, Action, Result. It works well here, but "above and beyond" answers benefit from emphasising one thing STAR can hide, namely the gap between what was required and what you did. A simple way to do that is to think in three parts: Baseline, Extra, Impact.

Baseline (about 20% of your answer)

Set the scene and state, explicitly, what your role required. "My job on the help desk was to resolve tickets within the target time" is a baseline. This sentence is what makes the rest of the story meaningful, so do not skip it. Keep context brief: one sentence on where you were, one on what was expected.

Extra (about 50% of your answer)

This is the heart of the answer. Explain what you noticed, why it mattered, what you decided to do and how you did it. Use the first person: "I" decided, "I" built, "I" asked. If colleagues helped, say so, but make clear which part was yours. Include one detail that shows thinking, such as a trade-off you weighed or someone you consulted before acting.

Impact (about 30% of your answer)

Close with the result, preferably quantified, and with what you learned or what changed afterwards. "Tickets from that category fell by roughly a third over the next quarter" is stronger than "it worked well". If you do not have numbers, use a specific observable outcome, such as a manager adopting your approach for the whole team.

Practise aloud with a timer. Most spoken answers run longer than they feel, and two minutes is a sensible ceiling for a first answer. If the interviewer wants more detail, they will ask a follow-up, and a concise answer invites exactly the follow-up you want.

If you have limited work experience, the question can feel unfair. It is not. Interviewers for graduate schemes expect stories from university, part-time jobs, volunteering and projects, and they judge the quality of the thinking rather than the prestige of the setting. The trick is to mine your experience systematically rather than hoping a story will occur to you in the interview.

Start by listing every role or responsibility you have held in the past three years, including informal ones. For each, ask: "When did I do something nobody asked me to, and what happened?" You are looking for moments where you noticed something, such as a confusing process, an unhappy customer, a struggling teammate or a missing resource, and acted.

Once you have a handful of candidate stories, map each to several competencies. A single strong story can often answer questions on initiative, teamwork, problem solving or customer focus with small changes in emphasis. Our competency-based interview guide shows how to build a story bank so that you walk in prepared for most behavioural questions rather than just this one.

The examples below are illustrative models, not scripts to memorise. Replace the details with your own, keep the shape, and keep each to around two minutes when spoken.

Example 1: Retail assistant (customer focus)

Baseline: "I worked weekends in an electronics shop, where my role was to serve customers at the till and on the shop floor. Closing a sale and answering product questions was the expectation." Extra: "One Saturday a customer was upset because the laptop charger they needed was out of stock, and they were travelling the next day. Nobody had asked me to chase it, but I phoned two nearby branches, found one with stock, and arranged to have it held at the counter. I then wrote the customer a short note with the address and opening hours. I also told my manager about the gap so we could review how often that charger sold out." Impact: "The customer collected it that afternoon and later left a positive review mentioning my name. My manager increased the reorder level for that item, and we had no repeat stock-outs during my remaining months there."

Example 2: University group project (ownership)

Baseline: "In my third-year marketing module, I was one of five students on a group assignment. My assigned part was the market analysis section." Extra: "About halfway through, I noticed that two teammates were duplicating work and a deadline was slipping because nobody had an overview. Without being asked, I built a simple shared tracker listing every task, owner and deadline, and proposed a fifteen-minute check-in twice a week. I also offered to review the final slides for consistency, which was outside my section." Impact: "We submitted a day early, the duplication stopped, and our mark was in the top band for the module. Two teammates later told me the tracker was why they felt in control. I have used the same approach on every group task since."

Example 3: Internship (impact beyond the brief)

Baseline: "During a summer internship in a finance team, I was asked to reconcile monthly supplier invoices against purchase orders." Extra: "The task took me most of two days each month. I noticed that most mismatches came from the same three suppliers' formats, so after finishing the assigned work I wrote a set of spreadsheet formulas to flag those mismatches automatically. I checked the approach with my supervisor before using it, tested it against the previous quarter's data, and documented the steps so someone else could run it." Impact: "The reconciliation fell from about two days to roughly half a day. My supervisor asked me to present the method to the team, and the documented process was kept after I left."

The same question lands slightly differently depending on who is asking. You do not need a separate story for each employer, but you should adjust the emphasis, and the result you highlight, to match what the organisation says it values. Always check the employer's own careers pages for its stated values and competencies, since these are the best evidence of what interviewers will listen for.

Amazon publishes its Leadership Principles on its careers site, and several of them, such as Customer Obsession, Ownership and Deliver Results, map naturally onto an "above and beyond" story. Candidates preparing for Amazon often structure stories around those principles; see our Amazon online assessment guide for the wider process. Professional-services firms such as the Big Four typically use competency-based interviews following online assessments, with values and behaviours listed on their graduate pages. Our PwC assessment centre guide shows one example of how those stages fit together.

If you are applying to several employers at once, build one master version of each story and a short "tilt" note beside it: which value it best illustrates, and which detail to lead with. That keeps your preparation efficient while still sounding tailored.

Most failed answers fall into a handful of patterns. Knowing them in advance is the easiest way to avoid them. The biggest is mistaking effort for impact: describing how hard you worked without saying what it achieved. Others include being vague, taking all the credit, choosing a story that raises concerns, and ignoring the question's own wording by describing something that was actually part of your job.

Related questions you may meet in the same interview include "tell me about a time you showed leadership", "tell me about a time you solved a difficult problem" and "tell me about a time you worked in a team". A strong story bank covers all of them. See our guides on showing leadership and working in a team to see how a single experience can be reshaped for each.

Finally, remember that the delivery matters as much as the content. Speak at a measured pace, make eye contact or look at the camera, and pause before you start so that you can choose your story deliberately. If nerves are a problem, our interview nerves guide offers practical techniques you can use on the day.