Three ways to read a rejection

After a few rounds of interviews, I’ve realized that “didn’t pass,” on its own, doesn’t actually tell me what to do next.

When I look back on an interview, I try to break the problem into three types.

01 | Capability gap: I really can’t do this yet

One interview was for a role leaning toward AI Platform, and they kept digging deeper into platforms, infrastructure, and Engineer workflow.

My experience there honestly isn’t as deep as it is in application-layer AI, complex workflows, and regulated systems.

This kind of gap isn’t something you fix by phrasing things differently.

If it’s in a direction I want to keep growing in, I need to actually close it: understand the systems, build projects, work with more technical people—not keep memorizing interview answers.

02 | Interview gap: I can do it, but I didn’t show it in the moment

I’ve run into this one plenty of times too.

For example, the question was about prioritization and I answered about evaluation; I spent too long on background and got to the conclusion too late; the question had three parts and I only answered two; or I had a perfectly good experience to draw on but picked a story in the moment that didn’t quite fit.

What’s missing here isn’t necessarily knowledge—it’s listening to the question, structuring the answer, and articulating it.

So the review should focus on this: at which step did I lose something I already had?

03 | Fit gap: what they need just isn’t my strength

Roles all called AI PM can look very different. Some are heavy on enterprise delivery, some on discovery, some need deep platform experience, and some depend heavily on a particular industry background.

No one can be the best match in every direction at once.

But fit gap can’t be used to explain every failure either.

If the roles I want long-term keep exposing the same weakness, that looks more like a capability gap than “just not the right match.”

So now, when I review an interview, I ask three questions:

1. Is this something I genuinely can’t do?

2. Can I do it, but I didn’t let them see it?

3. Or is the capability this role really needs just not one of my strengths to begin with?

In reality, the three often get mixed together.

But once I try to separate them, the next step gets a lot clearer:

- Build the skills that need building;

- Practice the interview performance that needs practice;

- And for roles that just aren’t a fit, there’s no need to redefine myself over one rejection.