This question is designed to get beyond the surface level. Anyone can claim to be a high performer. This question asks you to prove it with a specific story. The detail is what makes it work — vague claims about "going above and beyond" are unconvincing. Quantified, specific outcomes are not.
What 'exceeding expectations' actually means
There are several ways to genuinely exceed expectations, and not all of them involve doing more work:
Delivering more than was asked. The brief was X; you delivered X plus something that made X significantly more valuable.
Delivering significantly faster or under budget. The expectation was a two-month timeline; you delivered in six weeks. The budget was £50k; you came in at £38k.
Solving a problem that wasn't initially part of the brief. While doing the work, you identified a related issue and fixed it — without being asked.
Producing a measurably better outcome than benchmarked. The team average was X; your result was Y.
Choose a story that demonstrates one of these clearly. The more specific the outcome, the more convincing the story.
What interviewers are listening for
They want evidence of initiative, ownership, and impact. The question is looking for someone who doesn't just fulfil a brief — they think about the brief, they push where they can, and the result shows it. Avoid stories where you just worked harder than expected. Work ethic is one thing; impact is what matters here.
How to structure your answer
Use STAR: Situation (brief context), Task (what was expected of you), Action (specifically what you did beyond the expectation), Result (the quantified or clearly articulated outcome).
The key is in the T and the R. Be explicit about what was expected so the gap between expectation and delivery is clear. And make the result as specific as you can — a number, a comparison, a piece of feedback from a stakeholder.
Sample answers
Commercial / client-facing role
"Last year I was given a target of growing my client portfolio by 15% in the financial year. The expectation was straightforward: retain existing accounts, expand a few, hit the number. I ended up at 34%. The main reason wasn't luck — it was that I'd spent the first quarter mapping all my accounts by revenue potential versus our current share of wallet. I noticed that two of my mid-tier clients were spending significantly with a competitor on a service we actually offered, and they just hadn't been told. I went back with a proposal specifically tailored to those gaps, and both clients moved a meaningful portion of their budget across. My manager highlighted it in the team meeting as an example of proactive account management rather than just reactive relationship maintenance."
Project delivery / non-sales role
"I was project managing an office relocation — 80 people, two-month timeline, £120k budget. The expectation was that we hit the date and came in on budget. We finished three weeks early and came in £22k under budget. The main thing I did differently was front-load the coordination work. Most projects like this lose time in the middle because of dependencies — IT isn't ready when facilities is, that kind of thing. I built a dependencies tracker in week one and ran a fifteen-minute sync every morning with the workstream leads. It felt like overkill at the start, but it meant we caught blockers three to five days before they became delays rather than on the day. My director specifically used the project as a case study for the rest of the property team."