“Tell me about a time you said no” is a question about trade-offs. The refusal itself is the easy part. Pick a story where the request came from someone you couldn’t simply overrule. Then tell it in five moves. Name the request and why it mattered to them. Give one reason for the no, stated as a cost they would feel. Say whether you meant “never” or “not now.” Describe the alternative you offered and actually built. Finish with who made the final call and what you did after it. Interviewers listen for two things here. Can you refuse without damaging the relationship? And once the call is made, do you commit to it? A story where you won the argument and walked away answers only the first. A story that ends with the other person getting most of what they needed answers both. The rest of this post builds one Android engineer’s answer around that shape.
“Tell me about a time you said no” is also scored on what you did next
Amazon states the expectation plainly in its leadership principles page. The page carries no date. “Have Backbone; Disagree and Commit” says leaders must “respectfully challenge decisions when they disagree.” It ends with “Once a decision is determined, they commit wholly.” Other companies use different words for the same pair. The interviewer wants to see the challenge and the commitment in one story.
That is why “I said no and I was right” scores poorly. It shows the backbone. It shows nothing about what happens when you lose. It can also suggest you treat requests as threats to your plan. The stronger story shows a no that changed the shape of the work.
Mike Cohn’s company, Mountain Goat Software, sells agile training. Its post on six guidelines for saying no to a stakeholder was last updated in December 2024. It was written for product owners. Still, three of its points fit an interview story well. Give “one compelling reason rather than a list of reasons.” Be clear whether you mean no or “no, for now.” Offer an alternative only if you mean it. Each of those becomes a sentence in your answer.
Leila’s request came from a director two levels above her
Here is the running example. Leila is an Android engineer on a grocery delivery app. On a Tuesday, Sam messages her directly. He is the director of growth. A holiday campaign starts the following Monday. Sam wants a full-screen offer to appear every time the app opens. He asks her to add it to the release that cuts on Thursday.
Sam is two levels above Leila. He isn’t in her reporting line, so she can’t simply defer to her manager’s priorities. The campaign also matters. Marketing has paid for ads that point to the offer.
Leila’s first version of this story was short. She said the release was frozen, the screen was untested and the timeline was unrealistic. Sam escalated. Her manager backed her. That version gives three reasons, no alternative and a win by escalation. An interviewer would score it as rigid.
Give one reason, and make it a cost the requester would feel
Leila had several true reasons. The release branch was two days from cutting. A screen on every launch needed a network call before the home screen loaded. Nobody had tested how it behaved offline. A list like that invites Sam to argue with the weakest item.
So she picked the reason that touched Sam’s goal. Say the offer screen failed or loaded slowly. Every customer would see that on launch day. A broken first screen during a paid campaign would cost him more than a missing offer. That reason belonged to Sam. He could weigh it without trusting her view of code quality.
In your answer, say the reason in one sentence. If you mention the others at all, say you left them out on purpose.
Say whether it was “no” or “not now,” then offer something you would build
Leila’s no was “not this release.” The full-screen offer could go into the next release, two weeks later, after testing. She said that in the same message, with the date.
Then she offered an alternative she could deliver that week. The app already showed a promo banner on the home screen. Its text and link came from Firebase Remote Config. That service changes app behavior without users downloading an update. So the campaign banner could go live on Monday without touching the frozen release. It would reach every user, though less loudly than a full-screen offer.
The interviewer will check this part with a follow-up such as “what did you offer instead?” An alternative you invented to end the conversation sounds hollow. One you shipped, with a date, sounds like someone who wanted the requester to succeed.
Was your no about your own capacity rather than the requester’s risk? Then the story is about dropping work. Our post on the competing priorities question covers that version.
Name who made the call, especially when they outrank you
Sam outranked Leila. Still, he didn’t own the release. Her product manager, Ana, did. So Leila didn’t decide alone. She didn’t let Sam decide alone either. She set up a fifteen-minute call with both of them. She gave the one reason, the “not now” date and the banner option.
Ana chose the banner for Monday and the full-screen offer for the next release. Sam agreed, without enthusiasm. Say this plainly in your answer. A no that ended with everyone delighted sounds edited.
Going around Sam to her own manager would have been the easy move. It also would have read as a power play. Is the person you refused your own lead? Our post on disagreeing with your manager covers that case.
The commit part is what you did after the call
Leila set the banner copy and link in Remote Config with Sam’s team on Friday. She checked on Monday morning that it showed on both app versions in use. Then she built the full-screen offer for the next release, with an offline fallback that skipped the screen.
The banner ran for the full campaign. Sam’s team reported a few thousand redemptions from it. The full-screen offer shipped two weeks later for the campaign’s second week. The launch release went out with no new crash on startup.
Those facts also answer “did the no cost anything?” The loud version of the offer missed the first week. Leila says so in her answer.
Put together, the answer runs about ninety seconds
None of this happened. Leila, Sam, Ana and the grocery app are a composite built to show the order. Your own story will have different people and numbers. Keep the five moves in the same order.
I’m an Android engineer on a grocery delivery app. Our director of growth, Sam, messaged me on a Tuesday. A holiday campaign started the next Monday. He wanted a full-screen offer on every app launch, in the release cutting that Thursday.
I didn’t think we should. The screen needed a network call before the home screen loaded. If it failed during a paid campaign, every customer would hit a broken first screen. That would hurt the campaign more than a missing offer, so that was the reason I gave him.
My answer wasn’t a flat no, just not this release. I could ship the full-screen version two weeks later, tested. For Monday, I suggested our existing home-screen banner. Its content comes from Remote Config, so it could go live without a new release.
Our PM, Ana, owns release scope. So I set up a short call with both of them. Ana picked the banner now and the full screen next release. Sam agreed, though he wasn’t thrilled.
I set up the banner with his team on Friday and checked it on Monday morning. It ran all campaign and drove a few thousand redemptions. The full-screen offer shipped two weeks later with an offline fallback. The cost was that the loud version missed week one.
The order matches the sections above. Paragraph two holds the single reason. Paragraph three holds “not now,” the date and the alternative. Paragraph four names who decided. Paragraph five is the commitment and the cost.
When the request is one you won’t do at any date, the alternative changes
The five moves assume the request is fine in principle. Sometimes it isn’t. Say Sam had asked Leila to log precise location on every launch for ad targeting. He wanted it with no consent prompt. “Not now” doesn’t fit, because the date isn’t the problem. A quieter version of the same tracking doesn’t fit either.
Tell this version only if it really happened. Its follow-ups ask who the privacy lead was and what they decided. In that story, the no is permanent, so say so in one sentence. The alternative becomes a route to whoever owns that decision. That might be the privacy or legal lead. Leila’s answer would name the policy she pointed to and who she brought in. It would also name what Sam could still get. One option is asking for location in context, with consent. The commit part changes too. Leila would follow the privacy lead’s ruling, even if it allowed more tracking than she wanted.
1 thought on “Tell Me About a Time You Said No to Someone Who Outranked You”