Hiring · July 28, 2026 · 10 min read
JLPT N1 or N2 in hiring: what the certificate proves
JLPT in hiring is a strong signal with two blind spots: it tests reading and listening only, and never expires. What N1 or N2 proves, and what to assess.
← Part of The five pillars of hiring: what assessments measure
On this page
- What do JLPT N1 and N2 actually certify?
- Where does a JLPT certificate genuinely help?
- What are the two structural gaps in using JLPT for hiring?
- It never tests production — the skills most jobs run on
- It never expires — but proficiency fades without use
- What does 'work language' actually mean, role by role?
- How do you assess the working language the certificate misses?
- How do you set a fair JLPT bar without over-filtering?
If you lead HR or hire managers screening bilingual and foreign talent for roles in Japan, the JLPT line on a résumé is probably doing more work in your decision than you have examined. It deserves respect — a JLPT N1 or N2 is a strong, hard-won signal, and candidates who hold one have proven something real. But using JLPT in hiring well means understanding precisely what the certificate proves and what it structurally cannot. This matters more now than it used to: hiring foreign talent in Japan is at record levels and language expectations are tightening across the market, a shift that runs alongside the Japan permanent residency changes reshaping how long that talent stays. When the pool is competitive and the stakes are high, an over-read or under-read certificate is an expensive habit.
This piece is not an argument against the JLPT. It is an argument for reading it accurately. The certificate has two structural limits that no amount of respect changes: it tests only reading and listening, and it never expires. Once you see both clearly, the right use becomes obvious — treat JLPT as a signal to filter people in, then assess the actual working language the role runs on. That is the honest position, and it is fairer to candidates than either trashing the certificate or trusting it blindly.
What do JLPT N1 and N2 actually certify?
The JLPT certifies comprehension — reading and listening — at a defined level, from N5 up to N1. N1 signals understanding of Japanese across a wide range of circumstances, including abstract and complex material; N2 covers everyday Japanese plus a broader set of situations with some depth. Both are strong, credible achievements. The key facts sit in the detail below.
Two things about the exam's design matter for hiring, and both are easy to miss. First, the JLPT has no speaking section and no writing section. It measures whether you can understand Japanese — decode a text, follow spoken audio — not whether you can produce it. A candidate can hold N1 and still write an email that lands as blunt or over-familiar, because the exam never asked them to write one. Second, the pass mark is scaled, and the result is pass or fail against that threshold. A pass tells you the bar was cleared on the day; it does not tell you by how much, or how the person performed on the parts of the language your role actually leans on.
The JLPT is a comprehension exam. It measures reading and listening at a defined level and reports pass or fail against a scaled mark. It does not test speaking or writing, and it never expires. Everything about how you use it in hiring should follow from those four facts — respect the signal, and read it for exactly what it is.
None of this diminishes the achievement. Reaching N1 or N2 takes years of disciplined study, and it is a reliable sign of serious commitment to the language as well as genuine comprehension. The mistake is not respecting the certificate too much in the abstract; it is quietly treating it as proof of a broader working fluency it was never designed to measure. The JLPT is precise about what it tests. Hiring goes wrong when we are vaguer about it than the exam itself is.
Where does a JLPT certificate genuinely help?
In plenty of places. A JLPT level is a fast, standardised, low-cost way to filter a large applicant pool to people who clear a comprehension baseline — and standardisation is a real virtue, because it applies the same yardstick to every candidate rather than leaving comprehension to an interviewer's impression. For roles where reading Japanese documentation, following written instructions or understanding spoken briefings is the dominant language demand, the certificate maps closely to the work. It is also portable and independently administered, which makes it more trustworthy than a self-reported 'fluent' that nobody ever verified.
So the sensible instinct is to keep the certificate, not bin it. It does exactly one job well: it tells you, cheaply and consistently, that a candidate can comprehend Japanese at roughly a known level. That is worth having at the top of a funnel. The trouble only starts when comprehension is not the whole of the job — which, for most roles that list Japanese as a requirement, it is not.
What are the two structural gaps in using JLPT for hiring?
There are two, and they are not flaws in the exam — the JLPT does what it says. They are gaps between what the certificate measures and what most jobs actually run on. The first is that it tests no production. The second is that it is a snapshot that never ages. Both are structural, so no version of 'we prefer higher levels' fixes them.
It never tests production — the skills most jobs run on
Most Japanese-language work is production, not comprehension. Writing a clear email in the right register of keigo. Holding a meeting and making a point that lands. Disagreeing politely with a customer without causing offence. Writing a spec that another engineer can build from. The JLPT tests none of this, because it has no speaking and no writing section at all. A candidate can understand every word of a customer's complaint and still be unable to write a reply that a Japanese customer would receive well — and reception is precisely where the register calls in keigo, the fine calibration of formality, quietly decide whether the message helps or harms. Comprehension and production are different muscles. The certificate exercises one and is silent on the other.
It never expires — but proficiency fades without use
A JLPT certificate carries no expiry date. An N2 earned years ago reads exactly like an N2 earned last month. But language is not like that. Proficiency that goes unused attritions — vocabulary thins, fluency stiffens, the reflexes that make writing feel natural slow down. Someone who passed N2, then worked for years in an English-only environment, may sit well below their certificate today; someone who passed N3 but has lived and worked in Japanese since may be far stronger than their paper suggests. The certificate freezes a single exam day. The candidate in front of you is not that day. For any role where current working Japanese matters, the date-free certificate quietly overstates its own relevance.
The language and integration criteria mentioned in the reporting around Japan's planned permanent-residency revisions are, as of writing, reported rather than enacted — no official text sets a specific test or level. Treat any specific language bar attached to that plan as reported, not settled, and do not present it to staff or candidates as a fixed requirement.
What does 'work language' actually mean, role by role?
Work language is the specific bundle of reading, listening, writing and speaking a particular role runs on — and the mix differs sharply by job. That is why a single JLPT number is a poor proxy for readiness across roles. The useful question is not 'what level?' but 'what does this person have to do in Japanese, all day, and can they do it?' Three concrete cases show how differently the answer lands.
A support agent lives on production under time pressure. They read a customer's message, understand the problem, then write a reply that is correct, clear and pitched at the right level of politeness — often dozens of times a day. Comprehension gets them to the starting line; the job is the written reply, and the register call inside it. This is exactly why hiring a customer support representative should start from the language the role produces, not the one it merely understands.
An engineer's mix is different again. They may read Japanese specs and Slack threads all day — heavy comprehension — but produce mostly in code and short written updates, with speaking concentrated in stand-ups and design discussions. The reading bar can be high while the polished-writing bar is moderate. A sales rep inverts it once more: their entire value can rest on spoken persuasion and written follow-ups that build trust, where tone and phrasing move the deal. A blanket 'N2 required' treats these three as the same problem. They are not. The certificate measures the one skill all three happen to share, and stays silent on the ones that actually separate a good hire from a poor one in each case.
How do you assess the working language the certificate misses?
Put the candidate in front of the work. The most predictive way to test production is a job-shaped task: ask a support candidate to write the reply to a real-looking customer complaint, in the register the role demands. Ask an engineer to summarise a short Japanese spec, or explain a technical decision in writing. Run a short meeting simulation for a role that lives on spoken discussion. Each of these observes the actual skill the certificate cannot — and does it under conditions close enough to the job that the result predicts performance rather than approximating it.
This is the logic of work-sample tests applied to language: the closer an assessment sits to the real task, the better it predicts. A comprehension certificate is a proxy; a written customer reply, observed and scored against a consistent rubric, is evidence. The two are complementary. Use the certificate to filter in — it is cheap and standardised — then spend your assessment effort on the production skills that decide whether someone can do the job, not just understand it.
This is also where a structured language gate earns its place. Rather than reading Japanese ability off a résumé line, you can set a hard language requirement at capability level — reading, listening and, crucially, writing — as a prerequisite a candidate clears before the role-specific questions begin. Our note on language proficiency in hiring sets out the wider case: language, where the role depends on it, is a job skill to be measured directly, not a claim to be trusted. Assessing it natively — including modalities a translated multiple-choice item cannot reach — is why the sample assessment includes a Japanese audio question built to separate genuine listening ability from written recognition.
Use the JLPT as a filter-in signal, then assess production directly. Ask the support candidate to write the customer reply; ask the engineer to summarise the spec. A single job-shaped task tells you more about working Japanese than a certificate and an interview combined — because it observes the thing the role actually runs on.
For roles where a business register is the whole game, the BJT — the Business Japanese Proficiency Test — is a fairer instrument than the general JLPT, because it targets Japanese in business settings and reports a graded score rather than a bare pass or fail. It is worth knowing about. But it is still weighted towards receptive skills, so it narrows the production gap without closing it. Even the most business-oriented certificate is not a substitute for watching a candidate write the email the job will actually require.
How do you set a fair JLPT bar without over-filtering?
By matching the certificate requirement to what the role genuinely reads and listens to — and no higher. Demanding N1 where N3 plus strong speaking would serve the work is not rigour; it is over-filtering. It shrinks an already tight pool of Japanese-capable talent, and it biases systematically against capable people who never sat the exam or whose certificate understates their current ability. The bar should track the job, applied identically to everyone who reaches it.
The fairness problem cuts in both directions. Set the bar too high and you screen out strong candidates for a level the work never needed. Read the certificate too generously and you advance people whose production skills nobody checked. The discipline that resolves both is the same one behind skills-based hiring: decide what the role actually requires, measure that directly, and keep proxies in their place. A certificate is a proxy. Used as a filter-in signal and paired with a real production assessment, it is a good one. Used as the whole decision, it quietly does unfair work — sometimes too strict, sometimes too lenient, always on the strength of a single exam day that may be years old.
Don't let a JLPT level become a blunt gate that stands in for the whole judgement. Requiring N1 everywhere over-filters a tight talent pool and penalises capable people whose certificate understates their real Japanese. Set the level to the role's genuine reading and listening demands, then assess production separately — and keep the candidate experience in view, because good people have options.
Getting this right also protects the candidate experience, which matters more when the talent pool is competitive. A candidate asked to demonstrate the actual work — write a real reply, summarise a real spec — generally finds it fairer than being filtered on a certificate alone, because it gives them a chance to show what they can do rather than only what they once passed. That is the whole spirit of using the JLPT well: respect the signal, read it precisely, and let the work itself settle the questions the certificate was never built to answer.
A JLPT certificate proves a candidate understood Japanese on one exam day, years ago perhaps, and says nothing about whether they can write the email your job runs on today. Respect the signal — then test the work.
If you want to see how job-shaped language assessment works in practice — a written reply or a listening item scored against a consistent rubric rather than inferred from a certificate — you can try a sample assessment or book a demo before you change anything about how you screen for Japanese.
Written by
Aayesha Patel · Co-founder, Hanzomon Inc
Co-founder of Hanzomon. Writes about skills-based hiring, fair assessment and building a better candidate experience.