'Tell Me About a Time Your Idea Was Rejected' Interview Answer: Grace and a Second Try

A rejected-idea story shows resilience and judgment when it has four parts: the idea, why it was turned down and whether the reason was good, what you did next, and what happened to the idea later. It is the personal version of feedback you disagree with, its successful twin is a time you persuaded someone, and how you took the no is really a question about how you handle criticism. This page explains what the interviewer is really asking, gives a structure that works, three sample answers of forty to eighty words to adapt, the mistakes that sink the answer, and a ten-minute practice routine.

What the interviewer is asking

Whether you can hear no without sulking or quitting, whether you can tell a good reason from a bad one, whether you keep contributing ideas after one is turned down, and whether you can talk about the people who said no without contempt. Interviewers in collaborative and senior roles ask it because most ideas get rejected and the people who keep proposing are the ones who move things. The weak answers are the martyr ('they never listened') and the saint ('I accepted it gracefully' with no detail). The strong one shows you learned something and kept going, and ideally that a version of the idea came back.

A structure that works

1. The idea, in one sentence, and why you believed in it.
2. The rejection: who, why, and your honest view of whether the reason was good.
3. What you did next: asked questions, adjusted, dropped it, kept the relationship.
4. What happened later: it came back changed, or it stayed dead and you were fine.

Three sample answers

Individual contributor

I proposed moving our weekly status report from a document to a dashboard, and my manager turned it down because the executives who read it wanted something they could print and annotate. I thought the reason was fair, though I was disappointed. I asked whether I could build the dashboard for the team's own use, which she agreed to, and six months later a new director saw it and asked for exactly that for the executive meeting. If he had not, I would still think it was the right call to build it for us.

Technical

I pushed for rewriting a service that was slowing everyone down, and the team lead said no: the risk was too high for the quarter and the business value was hard to see. I disagreed at the time and I argued it once, with numbers, and lost. What I did next was break the rewrite into small pieces that could be done inside normal work, and over a year we replaced most of it without anyone approving a rewrite. The lesson I took was that 'no' to a big idea is often 'yes' to a smaller one.

Management

I proposed a four-day week pilot for my team and the leadership team rejected it, partly for reasons I thought were weak and partly for a client-coverage reason I had not considered. I took the coverage point seriously, dropped the proposal, and told my team honestly why it had not gone through. The idea has not come back and probably will not in that company. I do not regret proposing it; I regret not asking the client-facing teams first, which is now how I prepare proposals.

Mistakes that sink the answer

• Contempt for the people who said no.
• A story where the rejection was obviously wrong and you were vindicated; it reads as a grudge.
• No learning; the interviewer wants to see what changed in how you propose things.
• Giving up on ideas afterwards, said out loud or implied.
• Choosing a trivial idea so the rejection does not matter.

A ten-minute practice routine

1. Pick one rejected idea you still think was reasonable and write why it was turned down, fairly.
2. Write what you did next and what happened later, including if nothing did.
3. Add the one thing it changed about how you propose ideas.
4. Say it aloud in under ninety seconds, without edge.
5. Run it in a mock interview and read the transcript for grudge.

Where CoPilot Interview fits

CoPilot Interview is an AI interview assistant whose browser demo at /try lets you answer this question aloud and compare your answer with a structured one, free and with no signup, and whose free AI mock interview asks it in the context of your résumé and the job description and scores your spoken answer out of ten. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Practice is the use nobody objects to; if you consider live help in a real interview, follow your employer's rules.

Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.

Frequently asked questions

How do you answer 'tell me about a time your idea was rejected'?

The idea in a sentence, why it was rejected and whether the reason was fair, what you did next, and what happened later, plus one thing it changed about how you propose ideas.

Should I pick an idea that was later adopted?

It helps, but it is not required. An idea that stayed dead, handled well, is just as strong.

What if the rejection was unfair?

Say so briefly and fairly, then spend the answer on what you did about it. Grudges fail the question.

How long should the answer be?

Sixty to ninety seconds.