Job Descriptions
Templates

A job description template for all 70 tech roles you are likely to hire in Japan. Written for the local market, compliant with Japanese Labor Law.

How do you know what to require of a role you have not hired before?

For a small company, the first or second hire in a role carries far more weight than any hire after it. There is no bench to absorb a mistake and no internal benchmark to hire against, so the difference between a strong hire and a poor one shows up in the roadmap within a quarter.

Knowing what to ask for. Which competencies actually predict contribution in this role, which requirements are genuinely non-negotiable, and how to write it up so the posting is compelling to read and compliant to publish in Japan.

Pick a job family below and click the role. Every template is built on a role profile: the industry-standard scope, core competencies, and level expectations for that specific tech role. You get a modifiable template plus an analysis separating the requirements that matter from the trade-offs you can afford. Free, no signup.

For active help running the search itself, SaiyouTeam provides recruitment support and candidate research in Japan, and you can book a free strategy call.

Browse job description templates by role

The 70 roles below are grouped into 13 families, and inside each family they run from the most commonly hired down to the more specialised. Click any role for its template and role profile.

Software Engineering 6

  • Front-End Developer
  • Back-End Engineer Soon
  • Full-Stack Developer Soon
  • Software Architect Soon
  • Mobile Engineer Soon
  • Web Developer Soon

Data, Machine Learning and AI 7

  • Data Analyst Soon
  • Data Engineer Soon
  • Data Scientist Soon
  • Machine Learning Engineer Soon
  • AI Engineer Soon
  • MLOps Engineer Soon
  • BI Developer Soon

Cloud, DevOps and SRE 6

  • DevOps Engineer Soon
  • Cloud Engineer Soon
  • Site Reliability Engineer (SRE) Soon
  • Infrastructure Engineer Soon
  • Platform Engineer Soon
  • DevSecOps Engineer Soon

Testing and QA 4

  • QA Engineer Soon
  • SDET Soon
  • Performance Engineer Soon
  • QA Manager Soon

IT and Networking 6

  • Systems Administrator Soon
  • Network Engineer Soon
  • Network Administrator Soon
  • IT Support Specialist Soon
  • Database Administrator Soon
  • IT Manager Soon

Cyber Security 7

  • Security Engineer Soon
  • SOC Analyst Soon
  • Penetration Tester Soon
  • GRC Analyst Soon
  • Cloud Security Engineer Soon
  • Application Security Engineer Soon
  • Incident Response Engineer (DFIR) Soon

Hardware and Firmware 6

  • Embedded Software Engineer Soon
  • Systems Engineer Soon
  • Hardware Engineer Soon
  • Electrical Engineer Soon
  • FPGA Engineer Soon
  • ASIC Engineer Soon

Engineering Leadership 5

  • Tech Lead Soon
  • Staff Engineer Soon
  • Engineering Manager Soon
  • Director of Engineering Soon
  • CTO Soon

Product 3

  • Product Manager Soon
  • Product Owner Soon
  • Technical Product Manager Soon

Project and Program Management 7

  • Scrum Master Soon
  • Agile Coach Soon
  • Project Manager Soon
  • Program Manager Soon
  • Technical Program Manager Soon
  • Delivery Manager Soon
  • Business Analyst Soon

Solutions and Sales Engineering 5

  • Sales Engineer Soon
  • Solutions Architect Soon
  • Forward-Deployed Engineer (FDE) Soon
  • Customer Success Engineer (CSE) Soon
  • Post-Sales Engineer Soon

Game Development 4

  • Game Developer Soon
  • Engine Programmer Soon
  • Graphics Engineer Soon
  • Technical Artist Soon

Design 4

  • UX/UI Designer Soon
  • Product Designer Soon
  • UX Researcher Soon
  • Design Systems Designer Soon

Before you post the role

Get the role scoped against the real market

Most failed searches in Japan are decided at the job description stage: a band set below market, a Japanese-level requirement nobody questioned, or a must-have list that rules out the whole pool. In a free strategy call we go through the role you are opening, the band it needs, and how long it should realistically take to fill.

Frequently asked

Common questions about job descriptions in Japan

What has to be disclosed in a job posting in Japan?

Under the Employment Security Act, the conditions shown when you advertise have to be accurate and cover the core items: duties, workplace, working hours and overtime, wages, insurance, and contract type and term. Since 1 April 2024 the list also includes the scope of possible future changes to duties and workplace, both in the posting and in the labor conditions notice issued by the start date at the latest. The practical rule is that the posting and the eventual contract have to match.

What is the difference between a job posting and a job description in Japan?

The job posting is the advertisement a candidate reads, carrying the statutory disclosure items and written to attract applications. A job description in the Western sense is an internal document defining scope, level, and evaluation criteria, and it is far less common in Japan outside job-based employment systems. These templates serve both: the posting sections are written to be published, and the responsibilities and requirements are precise enough to interview against.

Should the job description be in English or Japanese?

Write it in the language the job is performed in. English filters correctly for a genuinely English-speaking team. Japanese reaches a much larger pool, because most mid-career candidates in Japan search in Japanese. Bilingual teams do best with a Japanese posting plus a short English section, not a machine translation of one into the other. What matters more than the language is that the Japanese level you state is the level you actually enforce at interview.

Do I need to state a salary range?

There is no pay-transparency statute in Japan forcing a published band, but whatever wage information you show has to be accurate. Competitively it is close to mandatory for tech roles: candidates filter by salary, and a posting with no figure gets skipped. State the annual figure, say whether it assumes a fixed overtime allowance, and say how many months of bonus are included.

How many must-have requirements should a tech job description have?

Three to five for most roles. Every additional must-have multiplies against the others, and the mid-career pool for a given stack in Japan is small before you start filtering. Write the list, then move anything the person could learn in their first quarter into nice-to-have. If a requirement is genuinely non-negotiable, be ready to say how you will test it at interview.

Should I require JLPT N2 or N1?

Ask what the job needs rather than which certificate sounds safe. N1 is a reading-heavy exam and a poor proxy for running a stand-up or handling a customer call, and plenty of engineers who work comfortably in Japanese have never sat it. Describe the situation instead: daily stand-up in Japanese, specifications in Japanese, customer-facing meetings in Japanese. Defaulting to N1 on a role that is genuinely English-capable is one of the most common ways companies shrink their own pool for no return.

Should the posting say whether we sponsor a visa?

Yes, explicitly. Silence is read as no by candidates who need sponsorship and as yes by candidates who hope for it, so an unstated position costs you applicants at the top of the funnel and wastes time further down. One line covers it: whether you sponsor, and whether you support a change of status for someone already in Japan. The Engineer / Specialist in Humanities / International Services visa guide covers what Immigration looks for.

How long should a job description be?

One page of substance. What moves response rate is concrete detail: what the person ships in the first six months, the real stack, team size and reporting line, working model, and the band. Cut every line that would be equally true at any other company hiring the same role, then look at what survives.

Can the job description affect a work visa application?

Indirectly, yes. For the Engineer / Specialist in Humanities / International Services status, Immigration looks for a clear match between the duties, the candidate's degree or documented experience, and a salary at least equal to what a Japanese national would receive for the same work. Vague or general-labor duties make that match harder to demonstrate.

How often should a job description be updated?

Review it every time you reopen the role, and rewrite the salary band at least once a year. Tech compensation in Japan has moved fast enough that a band carried over from a search two years ago now sits below market for most engineering roles, and an underpriced posting goes quiet rather than producing weak applicants. If a posting has been live six weeks with no qualified applicants, the problem is almost always the band, the must-have list, or the Japanese-language line.

About the author

Emmanuel Gendre, Founder of SaiyouTeam

Emmanuel Gendre

Founder, SaiyouTeam · TechieCV K.K.

Former Google recruiter 12 years recruiting in Japan

Emmanuel advises small and mid-sized companies (SMBs) on HR and recruiting in Japan. He brings 12 years recruiting in Japan placing IT professionals, plus earlier experience hiring engineers across EMEA as a Google recruiter. He wrote these job description templates as part of that advisory work, starting from the postings he rewrites with clients before a search goes live.