What is a good example of when you went above and beyond

One where you can name the cost. A weekend spent rescuing a customer launch is only half an answer. The half that scores is what moved, who was affected, whether you told them before or after, and what you would sequence differently. Interviewers have heard the heroic half several hundred times.

Does going above and beyond look bad if I dropped something else

No, provided you decided deliberately and told the people affected in advance. Every senior person makes this trade regularly. The version that reads badly is the one where the candidate did not notice a trade had been made at all, because that person will keep making it silently on your team.

Should I describe a time where you went above and beyond outside work

Only if you have no work example at all. The question is really about how you handle competing obligations to colleagues, and volunteering or study examples usually lack the dependency structure that makes the answer interesting. If you do use one, make sure somebody else was relying on the time you spent.

Tell Me About a Time You Went Above and Beyond

Why interviewers ask this

When an interviewer says tell me about a time you went above and beyond, the thing they are quietly checking is whether you understand that the hours came from somewhere. Above and beyond means you spent time that was already committed to something else, and in every workplace that something else belonged to a colleague who was expecting it. Candidates describe the weekend, the late nights, the customer who wrote in to say thank you. Almost none of them name the work that slipped while all of that was happening, and the slip is the only part of the story with any information in it. A hiring manager who has run a team knows the cost existed. They have signed off on that trade themselves. More than once, probably, and then watched the cost land on somebody who was not in the room when it got made. What they want to know is whether you saw it at the time or whether you are seeing it for the first time in this interview.

An answer that sounds fine

We had a customer who was rolling out our product to about two hundred of their staff, and their internal launch was on the Monday. On the Friday afternoon their admin realised none of the accounts had been provisioned with the right permissions, and she was panicking. Nobody expected me to fix it, it was not my account and I had a full week of my own work behind me. I stayed late on the Friday and came in for a few hours on the Saturday to rebuild the permission groups by hand and test them. Their launch went ahead on the Monday exactly as planned, with all two hundred accounts working. The customer's admin emailed my director to say we had saved the rollout, which felt good.

Where it breaks

Every fact in that story is about what was gained and none of it is about what was spent. The candidate says he had a full week of his own work behind him, which is the one honest note in the answer, and then the story simply moves past it and never returns. Somewhere in that week is a person waiting on something he owed them, and that person is not in the account at all. When a candidate describes a time they exceeded expectations without naming what they deprioritised, an interviewer hears somebody who treats their own time as free and, by extension, treats other people's dependencies as flexible. The email to the director is the part that should worry you most. It means the story ends on recognition rather than on a reckoning, and a story that ends on recognition has no reason to go looking for who paid.

The follow-up

Who asked you to, and if nobody did, what did you deprioritise to do it?

Nobody asked me to do it, which was sort of the point at the time. What slipped was, I had a set of onboarding docs due for the new starters on the Monday, and those went in on the Wednesday instead. Two of them, actually, and one of the new people had already started by then. I did tell my manager on the Monday morning. Not before, though.

There it is. Two new joiners started without their documentation because a customer on somebody else's account had an emergency on a Friday, and the manager found out after the fact rather than before. The heroism was real and so was the bill, and the bill landed on people with no say in whether it got paid. Nothing in this disqualifies him, and no sensible interviewer would want it to. What matters is that he can now see both halves of the transaction, because the version of this person who only sees the thank you email is the version who makes the same trade next quarter and never mentions it to anybody.

An answer that holds up

A customer's rollout to two hundred staff was going to fail on the Monday because their permissions had not been provisioned, and I found out on the Friday afternoon. It was not my account. I decided to fix it, which meant my onboarding docs for two new starters slipped from Monday to Wednesday, and one of them started before the documentation existed. I made that call because the customer had a hard external date and my docs had an internal one I could renegotiate, but I got the sequence wrong. I told my manager on the Monday morning, after the fact, when I should have sent her two lines on the Friday afternoon saying what I was picking up and what was going to move. She would have said yes. The difference is that the new starters' manager would have known on the Friday instead of finding out on the Monday.

The interviewer asks who asked him to, and what he dropped.

Nobody asked. I dropped onboarding documentation for two new starters, by two days, and one of them started without it. The trade was defensible and the way I communicated it was not, because the people affected heard about it last.

Practice this question

Say your answer to this question out loud, then get asked what you dropped to do it. Answer it now, free, no account.