'Tell Me About a Time You Had to Say No' Interview Answer: Three Examples

A good saying-no story has five parts: the request, why no was the right answer, how you said it, what you offered instead, and what happened. Interviewers ask because people who cannot say no overcommit teams and people who say it badly damage relationships, and they want to see judgment in both directions. The question is close to tell me about a time you disagreed with your manager, draws on the same logic as how do you prioritize multiple tasks, and shares territory with managing stakeholder expectations. 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 say no for good reasons (capacity, risk, scope, ethics) rather than preference; whether you say it early, clearly and with an alternative; and whether the relationship survived. They are also probing the two extremes: the person who never says no, which shows up as a thin story, and the person who says no reflexively, which shows up as a story with no alternative offered. The strongest answers include a no to someone senior and a result that proved the no right.

A structure that works

1. The request and who made it, in a sentence.
2. Why no: the capacity, risk or scope reason, with a number if possible.
3. How you said it: early, directly, with the reason.
4. What you offered instead, and the outcome.

Three sample answers

To a manager

My manager asked me to add a third client onboarding to a week that already had two. I had the numbers: each took about twenty hours and we had forty. I said no the same morning, showed the hours, and offered two options: push one by a week with the client told now, or bring in a colleague for the data migration part. She chose the colleague. All three onboardings landed on time, and she started asking for the capacity picture before committing.

To a client

A client asked us to skip user testing to hit a launch date. I said we could hit the date, but not without testing, because the last untested flow had cost them a month of support tickets. I offered a cut-down test with five users in two days instead of ten in a week. They agreed. The test caught a checkout error that would have been visible on launch day.

To a senior stakeholder

A director asked for a feature that would have required storing data we had no legal basis to keep. I said no and explained the retention rule, then asked what decision the feature was meant to support. It turned out an aggregate report answered it with no personal data at all. We built that in a week. He was irritated for a day and then used the report in his own board deck.

Mistakes that sink the answer

• A story where you said no and nothing else; no alternative offered.
• Saying no for preference rather than for a capacity, risk or scope reason.
• A no delivered late, after the commitment was already made.
• A story where the relationship was damaged and nothing was learned.
• A trivial request.

A ten-minute practice routine

1. Recall a no that mattered, ideally to someone senior; that is the story.
2. Write the five parts: request, reason, how you said it, alternative, outcome.
3. Say it aloud in sixty to ninety seconds.
4. Answer it in the browser demo or a mock interview and compare with the structured answer.
5. Prepare a second story in case the first overlaps with the disagreement question.

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 you had to say no'?

The request, why no was right (capacity, risk, scope or ethics), how you said it early and directly, what you offered instead, and the outcome.

Is it safe to describe saying no to a manager?

Yes, if the reason was sound, you offered an alternative and the outcome supported you. It is often the strongest version.

What if I always say yes?

Find the time you pushed back on scope or timing, even softly. A thin story here suggests overcommitment.

How long should the answer be?

Sixty to ninety seconds.