Japan Added an N2 Japanese Requirement to Its Main Work Visa — the 7 Steps I Now Run After It Nearly Cost Us Two Engineer Offers

The change landed on 15 April 2026 and I did not take it seriously enough. Japan's Immigration Services Agency revised the Engineer/Specialist in Humanities/International Services visa — the "gijinkoku" status that most foreign software engineers in Japan hold — to require documented Japanese-language proficiency at JLPT N2 or the equivalent CEFR B2 level where the role involves Japanese-language communication.

My reaction at the time was the common one: "our team works in English, this does not apply to us." That was probably correct in substance and nearly wrong in practice, because being an English-working team and being able to evidence an English-working role are two different things. Two offers in our pipeline came uncomfortably close to unravelling, not because the engineers lacked Japanese, but because our own paperwork described roles that sounded like they needed it.

What follows is the 7-step process I now run on every foreign engineering hire in Japan. It is an operational checklist built from that experience, not legal advice — immigration decisions are made case by case, and you should confirm your specific situation with a qualified immigration lawyer or administrative scrivener before relying on any of it.

Step 1 — Classify the role honestly before you write the job description

Everything downstream depends on one question: does this role genuinely involve Japanese-language communication? Not "would Japanese be nice," not "the office is in Tokyo so obviously some Japanese happens" — does the job as performed require it?

Be concrete. Walk through a realistic week for the role and mark each recurring activity as English, Japanese or either: stand-ups, code review, design documents, incident calls, vendor coordination, customer-facing meetings, internal reporting to non-engineering stakeholders. That last one is where teams that consider themselves English-first often discover a Japanese dependency they had not registered.

The outcome of Step 1 is a written classification you are willing to stand behind. If the honest answer is "the engineering work is English but the role reports weekly to a Japanese-only stakeholder group," that is a Japanese-communication role, and pretending otherwise creates a much bigger problem than the visa requirement itself.

Step 2 — Check which of the four exemption routes applies

If Step 1 says the role does involve Japanese, the requirement is still not automatic. Several routes commonly take a case outside it, and most employers I speak to know about one of them at most:

1. The role is conducted primarily in a foreign language. The "International Services" part of the status covers work performed in a foreign language, and a genuinely English-working engineering role falls naturally here.
2. The applicant graduated from a Japanese university or vocational school. Completing higher education in Japan is treated as its own evidence of language capability.
3. The applicant already holds JLPT N2 or above. Obvious, but worth checking early — a surprising number of candidates hold a certificate they never mentioned because nobody asked.
4. The employer's company category. Applications are handled differently depending on the category the sponsoring company falls into, with the more established categories (commonly referred to as Category 1 and 2) subject to lighter documentary requirements.

Ask about routes 2 and 3 in your first screening call. It takes ninety seconds and it occasionally removes the entire question. Note also that the JLPT is not the only accepted certification — but because the accepted list can change, confirm what will be accepted with your adviser rather than telling a candidate that a specific certificate will definitely suffice.

Step 3 — Confirm your company category with your immigration adviser

Your company category shapes how much you have to document, and many employers have never actually confirmed which one they are in. This is a ten-minute question for an adviser and it changes the shape of every filing you make.

Do it once, write the answer down, and put it in the hiring runbook where the recruiter can see it. The recurring pattern I see is that this knowledge lives in one person's head, that person is on holiday when an offer needs to move, and the team defaults to the most conservative and slowest assumption.

Step 4 — Write the job description so it matches what you will file

This is the step that nearly cost us those two offers, and it is the one nobody thinks of as an immigration step at all.

Our job description had been written to attract as many applicants as possible. It said the team was international and English-friendly, and then — in a "nice to have" section added by someone trying to be welcoming — it mentioned business-level Japanese and coordination with domestic partners. Nothing in it was untrue. But read as a description of the role's language requirements, it painted a job that needed Japanese, which is precisely the opposite of what we intended to file.

Fix the pattern at the source. If the role is English-working, say so once, plainly, near the top: "This role is performed in English. Japanese is not required." Then remove every "nice to have" Japanese reference, because a nice-to-have in a job description reads as a job requirement in a document review. If you genuinely want to signal openness to Japanese speakers, do it in the interview process, not in the written specification of the role.

Step 5 — Build the evidence pack before the offer, not after

The single highest-leverage change we made was moving evidence collection ahead of the offer. Previously we made an offer, the candidate accepted, and only then did someone start assembling documents — which is exactly when you discover that the job description contradicts the contract.

Our pack now contains, prepared in advance: the finalised job description in its filed form; a one-page statement of the team's working language with supporting examples (documentation, meeting invitations, code review language); the employment contract template with duties aligned to the job description; the company category confirmation from Step 3; and, where relevant, the candidate's education records or language certificate.

Assembling this costs a couple of hours once and is reusable across every subsequent hire for the same role family. It also has a useful side effect: the act of writing down "our team works in English" and looking for evidence occasionally reveals that it is not quite true, which is much better learned in July than in a document review.

Step 6 — Decide between gijinkoku and the Highly Skilled Professional route

For strong senior engineers, the Highly Skilled Professional (HSP) status is frequently the better answer, and it is worth assessing early rather than treating it as a fallback after a problem.

HSP is a distinct status with a points-based assessment covering factors such as salary, education, professional experience and age. It is not simply a different way of filing the same application, and it does not exist to bypass language requirements — it is a separate route with its own bar. But for a senior engineer with a strong package, clearing that bar is often realistic, and the status carries a materially faster track to permanent residence, which is a genuine closing advantage in a competitive offer.

Run the points assessment during the interview process, not after the offer. Our detailed walkthrough of the documents and the point calculation is in sponsoring the Highly Skilled Professional visa, and the practical tax and payroll traps that come with foreign hires are covered in the six visa and tax traps we hit.

Step 7 — Brief the candidate honestly and file within five business days

Tell the candidate the truth about their route as soon as you know it, including any uncertainty. Engineers considering a move to Japan are making a decision about their life, and vague reassurance is worse than an honest "here is the route we are filing, here is the realistic timeline, here is the one thing that could complicate it." Candidates who are told the truth wait. Candidates who are told everything is fine and then hit a delay assume they were misled.

Then move fast. Have the paperwork prepared so you file within five business days of signature. Speed here is not just administrative hygiene — it is a closing tool, because the competing offer is usually from an employer who has not prepared and will take weeks longer to get the candidate legally working.

Keep the candidate updated on a fixed cadence even when nothing has changed. A weekly "no news, still in process, expected window unchanged" message costs nothing and prevents the silence that makes people reconsider.

The 7 steps as a working checklist

1. Classify the role honestly — map a realistic week, mark each activity English or Japanese, write the classification down.
2. Check the four exemption routes — foreign-language role, Japanese education, existing certificate, employer category.
3. Confirm your company category — once, in writing, in the hiring runbook.
4. Align the job description — one plain statement of working language, zero stray Japanese "nice to haves".
5. Build the evidence pack before the offer — JD, working-language statement, contract, category, candidate records.
6. Assess gijinkoku vs HSP during the loop — let the route inform compensation, not the reverse.
7. Brief honestly, file within five business days — then update on a fixed cadence.

Where this sits in the wider Japan hiring picture

Getting the visa route right matters more in 2026 than it did two years ago, because the competition for senior engineering talent in Japan has intensified from a direction most employers did not plan for. State-backed AI programmes are concentrating exactly the senior profiles the private market wants — I went through the specifics in our analysis of Japan's ¥387.3bn physical AI programme and its hiring signals.

The practical consequence is that speed and certainty have become differentiators. When two employers want the same engineer, the one who can say "your route is confirmed, we file within five business days" wins offers that salary alone would not. Our full sourcing-to-offer method is in the 8-step remote hiring playbook. And if your search is genuinely regional rather than Japan-specific, our teams cover Singapore and the UAE, where the immigration mechanics are different and often faster.

One closing caveat, repeated because it matters: immigration decisions are made case by case, the details above reflect the rules as they were reported following the 15 April 2026 revision, and requirements change. Use this as an operational checklist to get your own house in order — and confirm the specifics with a qualified immigration lawyer or administrative scrivener before you rely on them for a particular hire.

AI summarize

FAQ — The 2026 N2 Rule and English-Speaking Engineer Hires