How to Answer “Describe a Time You Handled Rejection”

“Describe a time you handled rejection” is a resilience question in disguise. The interviewer is not interested in the rejection itself so much as the next forty-eight hours: what you felt, what you did with the information, and whether you came back better. You can build a strong answer in six steps.

Before you start: what “rejection” means here

This question is different from “tell me about a time you failed”. A failure is usually something you did that went wrong. A rejection is a decision someone else made about you or your work: a proposal turned down, a promotion that went to someone else, a sales pitch that lost, a paper or grant that was declined, an application that did not progress, a client who chose a competitor.

That difference shapes the answer. With a failure, you own the cause. With a rejection, you often do not control the decision, so the panel watches how you respond to something outside your control.

Employers name this quality explicitly. The U.S. Office of Personnel Management’s executive qualifications include “Agility and Resilience”, which covers dealing effectively with pressure and remaining “optimistic and persistent, even under adversity”. The UK Civil Service behaviour framework asks staff to “have a positive and focused attitude to achieving outcomes, despite any setbacks”. Amazon’s “Deliver Results” principle says that “Despite setbacks, they rise to the occasion and never settle.”

Step 1: Pick a rejection that mattered, but not one that still hurts

The example should have had real stakes for you, otherwise there is nothing to recover from. But if you cannot talk about it calmly yet, choose something else. Interviewers notice when a story is still raw, and it can pull the conversation off course.

Useful tests:

• Did the rejection affect your work, goals or plans in a concrete way?
• Did you take a specific action afterwards that you can describe?
• Is there an outcome, even a partial one, to report?
• Can you describe the person or panel who rejected you neutrally?

Strong categories by career stage:

Be careful with job rejections from other employers. They are acceptable, especially for graduates, but keep the focus on what you changed, not on the company that said no.

Step 2: State the rejection in one or two sentences

Set the scene briefly and factually. Include what was at stake and who decided. Skip the backstory. LSE Careers suggests keeping the situation to around 10% of a STAR answer, with most of the time given to your actions.

Example opening (illustrative): “Last year I put forward a proposal to move our quarterly client reports to a self-service dashboard. I’d built a prototype on my own time. The leadership team declined it at the budget review.”

Step 3: Acknowledge the reaction, briefly and honestly

Saying you felt nothing sounds rehearsed. One honest sentence is enough: “I was disappointed, because I’d put a lot into it.” Then move on. The American Psychological Association describes resilience as “the process of adapting well in the face of adversity”, and among its suggested strategies are to “keep things in perspective” and “learn from your past”. You are showing that process in miniature: a natural reaction, then a deliberate response.

Avoid sentences that criticise the decision-makers, even subtly (“they didn’t really understand it”). Interviewers often imagine themselves as the person who said no.

Step 4: Describe what you did to understand the decision

This is the step that separates strong answers from average ones. People who handle rejection well usually go looking for the reason. Show that you did, for example by:

• asking the decision-maker for feedback, and how you phrased the request;
• reading the scoring criteria, tender evaluation or reviewer comments closely;
• comparing your submission with the one that was chosen, where that was possible;
• separating what was within your control (quality, timing, evidence) from what was not (budget, strategy, a stronger competitor).

Continuing the illustration: “I asked the finance director for fifteen minutes to understand the decision. She said the idea was fine but I hadn’t shown what it would save, and the licence cost landed in a tight year.”

Step 5: Show what you changed and what happened next

This is the bouncing-back-from-a-setback part of the story. Now give the actions. This is where most of your speaking time should go. Recovery from rejection usually takes one of three shapes, and any of them can be a good answer:

1. You tried again, better. You reworked the proposal, reapplied, or re-pitched with the gaps fixed.
2. You redirected. You took the idea, skill or relationship somewhere it fitted better.
3. You accepted the decision and committed. You supported the option that was chosen, sometimes the most mature response of all.

Illustration continued: “I tracked how many hours the team spent on manual reports over the next quarter, which came to about two days a month. I rebuilt the case around that number and proposed a three-month pilot using a tool we already had a licence for, so there was no new cost. The pilot was approved in the next cycle.”

Step 6: Close with the result and a lesson you still use

Give two things: what happened as a result of your actions, and what you learned. The lesson should be practical and specific, not a slogan.

Illustration, closing: “The pilot cut report preparation to about half a day a month, and the dashboard was rolled out to two other teams. What I took from it is that I now write the cost and the saving into any proposal before the idea itself. I’ve done that for every business case since.”

Putting it together: the full illustrative answer

“Last year I proposed moving our quarterly client reports to a self-service dashboard and built a prototype. The leadership team declined it at the budget review. I was disappointed, but I asked the finance director for fifteen minutes to understand why. She said the idea was sound, but I hadn’t shown the saving, and new licence costs were difficult that year. So over the next quarter I tracked the time the team spent on manual reports, about two days a month, and rebuilt the case around a three-month pilot using a tool we already licensed. That was approved in the next cycle. Report preparation dropped to about half a day a month and two other teams now use it. The habit I kept is to lead any proposal with its cost and benefit, not the idea.”

It runs a little over a minute aloud, leaves room for follow-ups, and every sentence does a job.

What if the outcome was still a no?

Not every rejection story needs a happy ending. If you reapplied and were turned down again, or the idea never went ahead, the answer can still be strong if:

• you show you understood why and accepted it;
• you describe something you gained anyway, such as a skill, a relationship or a better approach;
• you show you did not let it affect your day-to-day work or your relationship with the decision-maker.

For example, an employee who missed out on a promotion could describe asking for a development plan, completing the items on it, and supporting the colleague who was promoted during the handover. That says a great deal about character, regardless of whether the next promotion came through.

Turning the lesson into application material

If your rejection story ends with a change in how you work, that change often belongs on your CV as well. A line such as “Rebuilt a declined proposal into an approved pilot that reduced reporting time” shows persistence without using the word. Job-search rejections are useful material here too: if an application was not shortlisted, it is worth checking whether your CV was readable by screening systems with the ATS resume score checker, and whether your cover letter answered the advert directly using the cover letter guide.

Frequently asked questions

Can I talk about being rejected for a job?

Yes, especially if you are a student or recent graduate. Keep the focus on the feedback you sought and what you changed, and do not criticise the employer that turned you down.

Is this the same as the failure question?

No. A failure is usually something you did that went wrong, whereas a rejection is a decision someone else made about you or your work. The panel is watching how you respond to an outcome you did not control.

How do I show resilience without sounding defensive?

Acknowledge your disappointment in one sentence, describe the decision-maker neutrally, and spend most of the answer on the actions you took afterwards and their result.

What if I never found out why I was rejected?

Say so, then explain how you assessed it yourself, for example by reviewing the criteria or asking a mentor for a view, and what you changed as a result.

Sources

• Executive Core Qualifications, U.S. Office of Personnel Management
• Success Profiles: Civil Service behaviours, UK Civil Service (GOV.UK)
• Our Leadership Principles, Amazon
• Types of interview questions, LSE Careers, London School of Economics
• Building your resilience, American Psychological Association