“Describe a time you went above and beyond” invites heroic stories: the all-nighter, the weekend rescue, the customer saved at the last minute. Some of those answers land well. Many land badly, because they rest on assumptions about what interviewers want that do not hold up.
Here are seven common myths about this question, what the evidence suggests instead, and an example answer that avoids the traps. The examples throughout are illustrative.
Myth 1: Going above and beyond means working longer hours
Fact: Hours are the weakest evidence you can offer, and they can count against you.
An interviewer hearing “I worked until 2 am every night for a month” may wonder about your planning, your workload management or your health. The health concern is not trivial. A joint World Health Organization and International Labour Organization analysis estimated that long working hours “led to 745 000 deaths from stroke and ischemic heart disease in 2016”. It compared people working “at least 55 hours a week” with those working “35-40 hours a week” and found “an estimated 35% higher risk of a stroke and a 17% higher risk of dying from ischemic heart disease”. WHO’s Director-General put it bluntly: “No job is worth the risk of stroke or heart disease.”
A good employer is not looking to hire someone who burns out. If extra time was part of your story, mention it briefly and put the emphasis on what you did with it.
Myth 2: It has to be a dramatic rescue
Fact: The question is about discretionary effort, and small, well-chosen examples work.
O*NET, the U.S. occupational database, defines the work style Initiative as taking on extra responsibilities and tasks outside your required role. That definition says nothing about scale. Calling a customer back the next day to check a fix worked, translating a safety notice for colleagues who struggled with the English version, or rebuilding a confusing form are all valid. What matters is that it was beyond what the role required, and that it helped.
Myth 3: Any extra effort counts
Fact: Extra effort only counts if it served a real need.
Polishing a report nobody reads is extra effort. It is not going the extra mile in any sense an employer cares about. Amazon’s “Customer Obsession” principle starts with “Leaders start with the customer and work backwards”, and its “Ownership” principle says leaders “act on behalf of the entire company, beyond just their own team”. The useful test: who benefited, and would they agree the effort was worth it?
Myth 4: Bending the rules for a customer shows commitment
Fact: It usually shows poor judgement.
Stories like “I gave the customer a refund I was not authorised to give” or “I skipped the check to get the shipment out” are common, and they worry interviewers. The person hearing your answer is imagining you in their organisation, with their policies, their regulators and their risk. Exceeding expectations within the rules is impressive. Exceeding your authority is a red flag.
If your best story involved an exception, show that you got approval for it, or that you raised the policy gap afterwards so it could be fixed properly.
Myth 5: Being modest means saying “we”
Fact: The interviewer needs to hear what you did.
LSE Careers’ STAR guidance asks “how did YOU go about tackling the situation and what was YOUR role in this”. Credit colleagues where they deserve it, but describe your own actions in the first person. “We stayed late to finish it” gives the interviewer nothing to score.
Myth 6: The result is “the customer was really happy”
Fact: Happiness is a start. A strong answer adds evidence and a lasting effect.
The National Careers Service describes the Result step as “what happened as a result of your action and what you learned from the experience”. Good results are observable: a renewed contract, a written compliment, a complaint withdrawn, an error that did not recur. The strongest answers go one step further and show that the extra effort changed something for the future, so the next customer or colleague did not need a rescue at all.
Myth 7: Doing my normal job very well counts as going above and beyond
Fact: Excellent delivery of your core job is valuable, but it answers a different question.
O*NET separates Dependability, “a tendency to be reliable, responsible, and consistent in meeting work-related obligations”, from Initiative, which is about tasks “outside of one’s required work role”. Hitting every deadline is dependability. Spotting that the deadline process itself was causing errors, and fixing it, is going beyond. If your example is just “I did my job really well”, interviewers may hear that you have not yet done anything extra.
An example that avoids the myths
Illustrative example. Front desk agent at a hotel.
“A guest checking in mentioned that her elderly father, who was joining her the next day, used a wheelchair, and she was worried because their booking was for a room on a floor where the lift had been out of service that week. Room allocation was handled by reservations, not by me.
I checked with the duty manager whether I could move the booking. She agreed, so I found an accessible room on the ground floor for the same rate, and I walked the route from the entrance to the room myself to check there were no steps. I also left a note for the next shift so they knew to expect him and could meet them at the door.
The guest emailed the hotel afterwards to thank the team, and the manager shared the email at our briefing. The more useful outcome was that I suggested we add a question about accessibility needs to the pre-arrival email. The manager took it to the reservations team, and it was added the next month, so those requests now come in before arrival instead of at the desk.”
Why it works against each myth:
- Myth 1: no heroic hours; the effort was thought and follow-through.
- Myth 2: a modest situation, handled well.
- Myth 3: a clear beneficiary with a real need.
- Myth 4: the agent got approval before changing a booking outside their remit.
- Myth 5: first-person actions throughout.
- Myth 6: evidence (the email) plus a lasting change (the pre-arrival question).
- Myth 7: room allocation and process changes sat outside the agent’s role.
A quick self-test before the interview
Run your chosen story through these questions. If you cannot answer one, rework the story or choose another.
- What exactly was expected of me, and what did I do beyond that?
- Who benefited, and how do I know?
- Did I stay within my authority, or get approval?
- Can I describe my own actions in three to five steps?
- Did anything change for the future because of what I did?
- Does the story suit the job I am applying for?
The same story can strengthen your CV. A line such as “Introduced an accessibility question to pre-arrival emails, so guest needs are known before check-in” shows discretionary effort on paper. The hotel front desk resume builder and the customer service resume builder include examples of service achievements in this style, and the full list of role-specific builders covers other jobs.
FAQ
Is “go the extra mile” the same as “above and beyond”?
Yes. Interviewers use “extra mile”, “exceeding expectations” and “above and beyond” interchangeably. One well-prepared story covers all three.
Can I use an example from volunteering or study?
Yes. Make sure the expected baseline is clear, so the interviewer can see what was extra.
What if I am asked whether I would do it again?
Say yes if it was sustainable, and be honest if it was not. “I would do the same for a guest, but I would also make sure the process catches it earlier, which is why I suggested the change” is a strong reply.
Should I mention that I was not paid for the extra time?
There is usually no need. It can sound like a grievance. Focus on the need you met and the result.
Sources
- Long working hours increasing deaths from heart disease and stroke: WHO, ILO, World Health Organization
- Browse by Work Styles, O*NET OnLine
- Our Leadership Principles, Amazon
- Types of interview questions, LSE Careers
- The STAR method, National Careers Service