Rejection rarely means 'not good enough'

A client of mine sat across from me on a coaching call last week and said something that too many people say to themselves on a job search:

"I just don't think I'm good enough."

She has the experience. She's done the prep. She's even gotten positive signals from recruiters, mock interviews, peers, and product leaders.

But after a string of rejections and a contact who promised to help but went silent... she'd started deciding on behalf of companies that she wasn't worth their time.

Another client, a Senior PM with 35 prepared stories, daily interview activity, and a hiring manager who loved him, got rejected twice at the final round in the same month. One company gave feedback that was essentially "you're great, just not for this role." The other? Six interviews. Three follow-up requests for feedback. Nothing.

And then earlier this week, I spoke with a new client. She's been searching for over four months. She's got a specialized background in health tech, a 33% application conversion rate, and active late-stage conversations with companies she'd love to work for. But the pool is small. And when the pool is small, every single rejection feels like a door closing forever.

If any of that sounds familiar, I want to tell you something important.

You're going to get rejected. You're going to want to know why. You probably won't get an answer.

Let's just acknowledge the reality of what it's like out there.

You will face rejection during your job search. Probably more than once. And every time it happens, the first thing you'll want to know is why.

That's completely natural. You invested time. You prepared. You showed up. Of course you want to understand what happened.

But here's the hard truth: most of the time, you won't get an answer.

One of my clients went through six interviews with a company last month. Got rejected. Asked the recruiter for feedback three times. Got nothing. Not a single actionable insight after six rounds of interviews.

That's not unusual. It's the norm. Feedback is either absent, generic to the point of being useless, or in some cases genuinely misleading.

And when you don't get an answer, your brain does a very predictable thing. It fills the void for you. It takes that silence and turns it into a verdict:

Not on the process. On you.

“I must have said something wrong. I wasn't sharp enough. Maybe I'm just not cut out for this level.”

I've watched this pattern play out with dozens of clients. Left to your own devices, the default is to internalize. To assume the worst explanation. To decide that the rejection was a reflection of who you are rather than a reflection of a hundred variables you couldn't see or control.

The reasons people don't get offers are almost always more nuanced, and less personal, than we think.

Let me give you some real examples from this past week alone.

The 3 most common reasons you didn't get the offer (that have nothing to do with your ability)

1. Role fit ≠ capability fit

One of my clients received the most honest rejection email I've seen in a long time. The company said, and I'm paraphrasing, "You're clearly a strong product manager. We were particularly impressed by your commercial and strategic thinking, your empathy for stakeholders, and the way you use data. But in the final round, we needed very strong signals around fast, hands-on execution in a small, high-autonomy team. We didn't get quite enough confidence in those areas."

Read that again. They weren't saying he was bad. They were saying this specific role needed something different from what he naturally leads with. And they even added: "This is very much a 'fit for this role' decision rather than a reflection of your overall capability."

That distinction matters enormously. But when you're the one reading that email, your brain skips right past the nuance and lands on: I failed.

You didn't fail. You weren't the right shape for that particular hole.

That's not the same thing.

2. Delivery, not content

This same client had 35 stories prepared. He'd drilled them with AI tools. He knew the content cold. But in the panel round, which is a very different beast from a hiring manager conversation, his answers ran long and weren't interactive enough.

The style that worked in a one-on-one with a hiring manager didn't translate to a room of four people with limited time and specific signals they needed to hear.

That's not a "you're not good enough" problem. That's a delivery calibration problem.

And it's fixable.

We scheduled a mock session, identified the pattern, and built a plan to adjust. Headline first. Three beats. Proof points. Reflection. Checkpoint question to make it a conversation, not a monologue.

If you've ever walked out of a panel interview thinking "I had great stories but something felt off," this might be your version of the same issue.

3. Things entirely outside your control

I'll give you a personal example.

I interviewed at Wise. Multiple times, actually. Before I moved to the UK and after. One of those processes, I made it all the way to the final stage. They'd even expanded the scope of the role they wanted me for. "You're a better fit for this,"they said.

Cool. Final interview with the CPO.

The guy did not want to be there. I could tell from the moment the call started. He was disengaged, borderline dismissive, and the whole thing felt like a formality he was being forced through.

I walked out of that interview and, if I'm honest, my first instinct was to internalize it. What did I do wrong? Was I not senior enough? Did I say something that put him off?

But the more I reflected, the more I realized: it wasn't about me at all. It was a mismatch between what they thought they needed when they started the process and what they actually wanted by the time I got to the final stage. The expectations had shifted. The CPO had a different vision. And I was caught in the middle of an internal misalignment that had nothing to do with my ability to do the job.

Do I look back on that as me not being good enough for Wise? No. I look back on it as a reminder that the outcome of an interview is never 100% in your hands. And treating it like it is will slowly erode your confidence until you start making decisions on behalf of companies…deciding you're not good enough before they've even had a chance to evaluate you.

The reframe I teach

Here's what I tell every client who's spiraling after a rejection:

Stop asking "Am I good enough for this company?" and start asking "Is this company good enough for me?"

It's not arrogance. It's self-preservation.

Because when you flip the frame, you stop internalizing every no as a referendum on your worth. You start evaluating the process, the people, the culture, and the role with the same critical eye they're using on you.

One of my clients realized mid-interview this week that the company was giving her red flags. Her gut was telling her this doesn't feel right. And instead of powering through because she "needed a job," she trusted that instinct.

That's progress. That's what confidence looks like when it's actually working.

And here's the contrarian bit: a rejection can actually be a gift.

Not in the toxic positivity, "everything happens for a reason" sense. But in the very practical sense that a bad-fit role would have made you miserable, and the company just saved you from finding that out six months in.

Not getting that role at Wise means I'm here helping you, and thousands of other Product Managers, which is way more meaningful to me. It's impact I deeply care about.

Also, a no at a company is also rarely a no forever. Some companies have cool-down periods. Some don't. Sometimes a different role opens up that's a better match. I've seen clients go back to companies that rejected them and land offers months later — because the role changed, the team changed, or they'd leveled up their delivery in the meantime.

The rejection wasn't about you. It was about this role, at this company, at this moment. That's it.

So if you're sitting with a rejection right now and your brain is doing that thing where it turns a single outcome into a sweeping judgment of your entire career...

Pause.

Remember that the PM with 35 stories got told he's a "strong product manager" in the same email that said no.

Remember that the client who thought she wasn't good enough had a hiring team at another company literally call her "a strong candidate" the same week.

Remember that I got rejected by a CPO who didn't even want to be in the room.

You are not your last rejection.

You're the sum of every problem you've solved, every stakeholder you've aligned, every product you've shipped, and every user whose life got a little bit better because of your work.

Don't let one company's "not right now" make you forget that.

Rooting for you, as always

James