Hiring · August 4, 2026 · 10 min read
Job-based employment in Japan: hiring for the job
Job-based employment in Japan (ジョブ型雇用) changes what you hire for. What it is, who has adopted it, and why job-type hiring needs job-shaped evaluation.
← Part of The five pillars of hiring: what assessments measure
On this page
- What is job-based employment, and how does it differ from membership-type?
- How far has Japan actually gone toward job-based employment?
- Who has adopted it — and what does official policy say?
- The artefact most companies discover they never had
- Why job-type hiring needs job-shaped evaluation
- What per-job evaluation looks like in practice
- Where job-based employment fits — and its honest limits
This guide is for the HR leaders, hiring managers and talent teams in Japan weighing the biggest structural change to how the country employs people in a generation: the move toward ジョブ型雇用 (job-based employment), where you hire for a defined job rather than into the organisation for life. The stakes are not abstract. Adopting the model without changing how you evaluate candidates leaves you with the hardest part of the old system — judging a person's vague potential — bolted onto a framework that now demands you judge them against a specific job. This post covers what job-based employment actually is, how far Japanese employers have really gone, what official policy says, and the part most rollouts underestimate: hiring for the job means evaluating for the job, and that is a different exercise from the one most Japanese recruiting was built to do.
What is job-based employment, and how does it differ from membership-type?
Job-based employment defines the job first and hires a person for it; membership-type hires a person into the company first and assigns the work later. That single reversal is the whole story. Under メンバーシップ型雇用 (membership-type employment) — the model that built post-war corporate Japan — a company recruits graduates in a batch, offers implicit long-term security, and rotates them through departments over decades, paying largely by seniority. The employee's loyalty is to the firm; the firm's obligation is to keep finding them a place. Under ジョブ型雇用, the unit is the job: its scope, its responsibilities and its required skills are written down, the pay attaches to that job, and the person is hired to do it.
The distinction matters far beyond org-chart theory, because the two models ask completely different questions at the point of hire. Membership-type hiring asks, "Will this person grow well inside our company over the next thirty years?" — a bet on general aptitude, trainability and cultural fit, made hardest of all at the new-graduate stage when there is little track record to read. Job-based hiring asks a narrower, more answerable question: "Can this person do this job?" The second question is the one you can actually test. It is also the one that quietly exposes an artefact many Japanese companies discover they never really had.
The shift in one line: membership-type hiring evaluates a person's potential to grow inside the organisation; job-based hiring evaluates a person against a specific job. Everything downstream — the job description, the interview, the assessment — has to move with that change, or the new model inherits the old model's weakest habit.
How far has Japan actually gone toward job-based employment?
Further among large firms than among small ones, rising steadily, but still a minority everywhere — this is a shift in motion, not a completed transition. The most-cited figures come from JAC Research, a recruitment firm; read them as an industry survey rather than government statistics. In its surveys, 29.5% of companies with 1,000 or more employees had introduced ジョブ型雇用 by August 2024, climbing to 36.0% in the 2025 survey. Across companies of all sizes, adoption moved more modestly, from 19.8% to 21.8%. The pattern is clear enough: the largest employers are moving first and fastest, and the trend line points up each year, but even among the giants roughly two in three had not fully adopted as of the latest reading.
Two cautions keep those numbers honest. First, "introduced" covers a wide range — from a full job-description-and-job-pay overhaul to a pilot in one division — so headline adoption overstates how deeply the model runs in practice. Second, these are recruitment-industry figures; treat them as directional rather than definitive, and never as an official count. What they reliably tell you is direction and momentum, not a precise national share.
Who has adopted it — and what does official policy say?
The most-watched adopters are among Japan's largest and best-known employers, which is part of why the shift carries such weight. Hitachi began writing job descriptions for all its domestic non-managerial employees from July 2022, and has been extending the model toward roughly 160,000 group employees — one of the most comprehensive rollouts in corporate Japan. Fujitsu applied job-based personnel to about 15,000 senior staff from 2020, then extended the logic into new-graduate hiring from 2023 — a notable move, given how tied new-graduate recruitment has been to the membership model. KDDI introduced its version from August 2020 and later extended it to some 2,400 managers. Shiseido and Panasonic Connect have also been reported among the adopters. These are not fringe experiments; they are flagship firms rebuilding the spine of how they employ people.
Government policy is pointing the same way, and here the sourcing is firmer. The 三位一体の労働市場改革 (three-pronged labour-market reform) guideline, published in May 2023, names the adoption of 職務給 (job-based pay) and ジョブ型 personnel systems as one of its three pillars, alongside reskilling and smoother labour mobility. The Cabinet Office followed with a ジョブ型人事指針 (job-based personnel guideline) in 2024, a reference for how to make the transition. This is a stated policy direction you can cite as such. What it is not is a mandate: no company is compelled to adopt, and each employer still decides for itself.
Keep the two evidence types separate when you make the internal case. Adoption percentages come from recruitment-industry surveys (JAC Research) and are best read as trend signals. The endorsement of 職務給 and ジョブ型 personnel systems comes from official reform guidelines (2023) and a Cabinet Office 指針 (2024) — that part is government policy direction, not a survey.
The artefact most companies discover they never had
Here is the practical snag that surprises teams partway through a rollout. Job-based employment runs on the job description — the scoped, honest statement of what a role does and what it requires. Membership-type employment never needed one. When you hire people into the company and sort out their work afterwards, a real job description is optional; a title, a department and a seniority band will do. So the moment a Japanese firm commits to ジョブ型雇用, it often finds that the document the whole model depends on does not yet exist in usable form for most of its roles. The rollout stalls not on pay bands or policy, but on the unglamorous work of writing down what each job actually is.
This is worth dwelling on because it is where the strategy meets a keyboard. A job-based system is only as good as the job descriptions underneath it, and a vague description quietly reimports the old problem: if the job is not clearly defined, you fall back to assessing the person's general promise, which is exactly the membership-type habit you were trying to leave behind. A tight description — real responsibilities, genuine must-haves separated from nice-to-haves, the level named — is the foundation, and it is a discipline in its own right. Our guide on how to write a job description walks through it; in a job-based context that document stops being an HR formality and becomes the specification your hiring runs on.

Why job-type hiring needs job-shaped evaluation
Because the question has changed, the way you answer it has to change too. Membership-type hiring could lean on general instruments — an aptitude test, a personality inventory, a series of interviews about character and potential — because it was betting on a person's capacity to grow into whatever the company needed. Job-based hiring makes a specific claim: that this person can do this job. A generic aptitude score cannot support that claim. To hire for a defined job, you have to evaluate the candidate against that job's actual requirements — the very requirements you were forced to write down in the job description.
This is where job-based employment and skills-based evaluation turn out to be two names for the same idea approached from different ends. The strategic reform tells you to define the job and hire for it; the hiring method tells you to measure demonstrated ability against that definition rather than infer it from pedigree. We make the full case for the method in the skills-based hiring guide, and it maps almost perfectly onto ジョブ型雇用: name the job's real skills, measure them directly on a task that mirrors the work, and score every candidate on one rubric. A job-based system that still selects on 学歴 (educational background) and interview impressions has adopted the structure of the reform while keeping the substance of the model it replaced.
A quick test of whether your job-based rollout is real: look at what decides the hire. If the deciding evidence is a candidate's performance on the job's actual required skills, you have made the shift. If it is still university tier, general aptitude and a rapport-based interview, you have renamed the roles without changing how you choose people for them.
What per-job evaluation looks like in practice
The obstacle used to be cost. Building an assessment tuned to one specific job — its skills, its level, its real tasks — was expensive enough that most teams settled for an off-the-shelf battery run across every role, which is precisely the generic instrument job-based hiring outgrows. That trade-off is what an AI-native skills assessment platform is built to remove. Because H-Evaluate produces AI-generated assessments per job, the job description you write becomes the direct input to the evaluation: the role's named requirements turn into what every candidate is measured against, on a task calibrated to that job rather than a one-size-fits-all quiz. The capability the reform demands — evaluate the person against the job — is exactly what per-job generation provides.
Two features of that approach matter for a job-based context. First, it keeps the whole loop anchored to one definition of the role: the job description feeds the assessment, so what you advertised, what you tested and what you decided on all describe the same job, instead of drifting apart as they usually do when three different people write them. Second, it lets you assess the job's real dimensions rather than a single narrow score. Most jobs are not one skill — a role calls for domain knowledge, judgement and other capabilities in a mix particular to it, which is why we frame a complete evaluation across the five pillars of a hire. For the role-particular expertise a job description names, the domain skills assessment approach is the closest fit to what ジョブ型雇用 asks you to verify.
As a technique this is not unique to Japan, but it lands with particular force here because the reform makes the requirement explicit. Elsewhere, hiring for the job is good practice you can choose. Under a ジョブ型雇用 model backed by official policy, it becomes the internal logic of the whole system: you have written down what the job needs, so you may as well measure it. To see how an evaluation is composed directly from a role's requirements, you can book a demo against one of your own job descriptions, or request a sample assessment shaped to a specific role. The tool matters less than the principle underneath it, which the reform has now made hard to avoid.
Where job-based employment fits — and its honest limits
Job-based employment is not a universal upgrade, and treating it as one is how rollouts go wrong. It fits most naturally where roles are well-defined and skill-specific — specialist, professional and technical positions where you can state clearly what the job requires and check whether a candidate meets it. It sits alongside Japan's wider hiring pressures, too: in a tight labour market, defining jobs by skill rather than pedigree widens the pool you can draw from, a thread we follow through the market as a whole in the guide to hiring in Japan. For roles built around long internal rotation, deep institutional knowledge and gradual generalist development, the membership model still has real logic, and many firms will run the two side by side for years rather than switching wholesale.
Be honest, too, about what the model does not solve on its own. Writing a job description does not guarantee it is a good one; a vague or copy-pasted spec produces vague hiring whatever framework surrounds it. Adopting job-based pay raises hard questions about existing staff, transitions and internal equity that no assessment addresses. And a role-shaped evaluation improves how you choose between candidates — it does not conjure candidates where a shortage leaves too few to choose from. Job-based hiring done well makes each decision sharper and more defensible; it is not a substitute for a competitive offer or a working pipeline. Adopt it for what it genuinely does: it forces you to define the job, then lets you hire the person who can actually do it.
Membership-type hiring asked whether a person would grow well inside the company. Job-based hiring asks whether they can do the job in front of them. The reform's real work is not renaming the roles — it is writing down what each job needs, and then having the discipline to measure it.
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.