---
title: After a rejection, read which layer you got stuck on
description: "Two kinds of rejection: you hit a veto item, which means changing roles, or your weakest layer fell short, which can be fixed. How to tell from the interview."
image: https://nobusato.jp/hubfs/reading-a-rejection-en.png
---

[Nobu Sato](https://nobusato.jp/en?hsLang=en)

[Home](https://nobusato.jp/en?hsLang=en) [Profile](https://nobusato.jp/en/profile?hsLang=en) [Articles](https://nobusato.jp/en/blog?hsLang=en) [Contact](https://nobusato.jp/en/contact?hsLang=en)

[日本語](https://nobusato.jp/ja/blog/reading-a-rejection)[English](https://nobusato.jp/en/blog/reading-a-rejection)[中文](https://nobusato.jp/zh/blog/reading-a-rejection)

[Career](https://nobusato.jp/en/blog/tag/career)

# After a rejection, read which layer you got stuck on

[Nobu Sato](https://nobusato.jp/en/profile?hsLang=en)

![After a rejection,read which layeryou got stuck on](https://nobusato.jp/hs-fs/hubfs/reading-a-rejection-en.png?width=1200&height=630&name=reading-a-rejection-en.png)

The interview ends, and a few days later the polite rejection arrives. Most people react one of two ways: blame themselves or blame the company. Neither helps, because neither tells you where you got stuck.

## Two kinds of rejection, two completely different fixes

When I judge fit between a person and a role, I don't take a weighted average. First I check the veto items. Then I look at the weakest layer. Rejections split the same way.

Kind one: you hit a veto item. Your drivers don't match the role, your values clash with the company's, or one of your under-pressure patterns resonates with a risk the team already has. Interviewers usually decide this in the first twenty minutes; the rest is procedure.

Kind two: no veto, but your weakest layer fell short. Usually the equipment layer: a capability one notch below what the role needs, or a key experience you were present for rather than responsible for.

Hit a veto itemDrivers mismatch · values clash · pattern resonanceCan't fix → change the roleWeakest layer fell shortOne notch low · present, not responsibleCan fix → three to six months

**Fig.1**Two kinds of rejection. Decide which first, then whether and where to fix.

Kind one can't be fixed, and shouldn't be. Bending your drivers to suit a role gets you in and then out again. The fix is a different role, which is what [the four-layer self-portrait](https://nobusato.jp/en/blog/four-layer-self-portrait-before-changing-jobs?hsLang=en) is for. Kind two can be fixed, and the direction is specific.

## How to tell

Read the interview itself.

The interview ends early, questions suddenly get shallow, the interviewer starts chatting instead of probing: that's kind one. They've decided you don't fit and are closing politely.

The interviewer keeps pressing on one topic, asks for a second example, a third, and then the topic disappears: that's kind two. They were looking for evidence and didn't find it. That topic is your weakest layer.

The other way is to ask. Japanese companies won't tell you the reason. Recruiters will. If you went through a recruiter, after a rejection always ask where the client got stuck. The recruiter knows, and most will tell you, because they want to put you forward again.

## Fixing kind two

If it's a capability notch: I score 0 to 3, where 1 is needs pushing, 2 delivers independently, 3 leads others. If the role needs 2 and you're at 1, find one chance to deliver something end to end on your own. Three to six months.

If it's experience you were present for rather than responsible for: next time, tell the part you did, however small. "I owned X on that project" is worth ten times "I was on that project." [Telling failure as evidence](https://nobusato.jp/en/blog/telling-failure-as-evidence?hsLang=en) is the same principle.

## Where I'm not sure

Some rejections have nothing to do with you: the role was frozen, someone internal got it, the budget was cut. You can't read those from the interview. Only the recruiter can tell you.

Your last rejection: which kind was it?

---

Shorter notes that don't make it into a full article go on LinkedIn. [Follow me there](https://www.linkedin.com/in/realnobusato/).

## More in this column

- ### [After AI, which layer of you loses value first?](https://nobusato.jp/en/blog/which-layer-loses-value-first?hsLang=en)
  
  Split a person into four layers and the writable part of your skills loses value first. Stanford found a 13% drop for ...
- ### [Telling failure as evidence](https://nobusato.jp/en/blog/telling-failure-as-evidence?hsLang=en)
  
  Interviewers ask about failure to see your patterns under pressure. They want what you did at the time, not the lesson ...
- ### [Choose your boss, not the company](https://nobusato.jp/en/blog/choose-your-boss-not-the-company?hsLang=en)
  
  Nearly 30% of resignation-proxy users in Japan feared their boss. People leave bosses, not companies. Spend the last ...

[← All articles](https://nobusato.jp/en/blog?hsLang=en)

## Writing about launching in Japan, in three languages.

[Profile](https://nobusato.jp/en/profile?hsLang=en) [Get in touch](https://nobusato.jp/en/contact?hsLang=en)

Nobu Sato

Writing about launching in Japan, in three languages.

[info@nobusato.jp](mailto:info@nobusato.jp) [LinkedIn](https://www.linkedin.com/in/realnobusato/) [X](https://x.com/nobusato5888)

© 2026 Nobu Sato. All rights reserved.

```json
{
  "@context" : "https://schema.org",
  "@type" : "BreadcrumbList",
  "itemListElement" : [ {
    "@type" : "ListItem",
    "item" : "https://nobusato.jp/en",
    "name" : "Home",
    "position" : 1
  }, {
    "@type" : "ListItem",
    "item" : "https://nobusato.jp/en/blog",
    "name" : "Articles",
    "position" : 2
  }, {
    "@type" : "ListItem",
    "item" : "https://nobusato.jp/en/blog/reading-a-rejection",
    "name" : "After a rejection, read which layer you got stuck on",
    "position" : 3
  } ]
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nobusato.jp/en/blog/reading-a-rejection",
  "@type" : "WebPage",
  "author" : {
    "@id" : "https://nobusato.jp/#person"
  },
  "inLanguage" : "en",
  "isPartOf" : {
    "@id" : "https://nobusato.jp/en/blog",
    "@type" : "Blog",
    "name" : "Articles"
  },
  "name" : "After a rejection, read which layer you got stuck on",
  "url" : "https://nobusato.jp/en/blog/reading-a-rejection"
}
```

```json
{
  "@context" : "https://schema.org",
  "@id" : "https://nobusato.jp/#person",
  "@type" : "Person",
  "name" : "Nobu Sato",
  "sameAs" : [ "https://www.linkedin.com/in/realnobusato/", "https://x.com/nobusato5888" ],
  "url" : "https://nobusato.jp/en/profile"
}
```

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "Nobu Sato",
    "url" : "https://nobusato.jp/en/blog/author/nobu-sato"
  },
  "dateModified" : "2026-10-23T23:20:54.259Z",
  "datePublished" : "2026-10-23T23:20:54.000Z",
  "headline" : "After a rejection, read which layer you got stuck on",
  "image" : [ "https://nobusato.jp/hubfs/reading-a-rejection-en.png" ],
  "mainEntityOfPage" : {
    "@id" : "https://nobusato.jp/en/blog/reading-a-rejection",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://nobusato.jp/hubfs/nobusatojp-1.jpg"
    },
    "name" : "nobusato.jp"
  }
}
```