A Guide to Writing Japanese Resumes

Photo of Rebecca Callahan

Rebecca Callahan

TokyoDev Contributor

Job-hunting in Japan as a developer may require you to create an English resume, a Japanese resume, or both. While the companies posting on TokyoDev expect an English-language resume, companies with a mainly Japanese workforce may have different requirements.

There are two types of Japanese resumes:

  1. Rirekisho (履歴書): A personal profile that contains a standard set of information, such as name, birthdate, address, and a timeline of professional and educational history.
  2. Shokumu keirekisho (職務経歴書): A detailed history of employment and responsibilities that is roughly equivalent to a Western-style resume.

Of these two, the latter document is both more critical and more complicated to create. Following is a detailed manual on when a shokumu keirekisho is necessary and how to write one, including:

What is a shokumu keirekisho, and what is it used for?

In post-war Japan, companies developed the custom of evaluating, not only a person’s skillset, but their background and character, through a standardized form. The rirekisho was established as a fixed-format, personal profile sheet that included information such as the applicant’s school, address, age, and family background.

Since at that time companies also engaged in mass new-graduate hiring and lifetime employment, the rirekisho alone was considered sufficient: new hires usually didn’t have any work history to describe. However, as mid-career hiring and foreign-affiliated companies became more common in Japan, a more detailed document was required, one that could also describe the candidate’s work experience and achievements—the shokumu keirekisho.

Today the rirekisho is primarily used by HR to manage candidates’ data, rather than playing an important part in the hiring process. Applicants fill out a standardized template that includes basic information such as name, address, qualifications, and a brief timeline of education and employment history.

In the past, handwriting the rirekisho was seen as a sign of sincerity, and the quality of a candidate’s handwriting was believed to represent their character. While there is less expectation for rirekisho to be handwritten today, don’t be surprised if someone suggests that you do so.

The shokumu keirekisho, by contrast, is not as strictly defined, and is expected to contain the following information:

  • Past work roles
  • Prior projects
  • Work achievements
  • Details on the candidate’s skills

It’s easy to understand why the shokumu keirekisho is essential, especially for mid-career applications—if you submit only a rirekisho, you won’t be sharing any details about your actual work experience. Even if you have little or no formal work experience, writing about personal or freelance projects on your shokumu keirekisho is strongly recommended.

How to write a shokumu keirekisho

If you’re going to create a shokumu keirekisho, then it should be written in Japanese. For most companies and positions hiring English speakers, you will not be expected to provide a shokumu keirekisho at all. When applying to bilingual or Japanese-dominant roles, however, you may be asked for one.

In those cases, preparing the document in Japanese allows you to demonstrate your language abilities. Even if the company doesn’t ask for one, if you know that the position requires some Japanese, it may not hurt to give them both an English CV and your shokumu keirekisho. According to TokyoDev’s client representative Sayana Takagi, applicants who submit both have a noticeably higher screening pass rate. If there’s only a single resume field, then you can combine the different forms together into a single document.

Your shokumu keirekisho should follow a template, and be written in black and white and in a traditional font. It shouldn’t include graphics or personal branding.

Organization

A typical shokumu keirekisho contains these sections:

  1. Career Summary
  2. Work History
  3. Skills
  4. Self-Promotion

Career Summary

In this section, you’ll briefly summarize your overall career, preferably in three to four sentences. The goal is to give readers a clear overview before they dive into the details.

In Japanese:

■職務要約
〇〇大学を卒業し、株式会社〇〇へ入社。システム開発部にて、〇〇や〇〇を用いた開発業務に従事してまいりました。これまでに〇〇や〇〇といった多様なプロジェクトに参加し、要件定義から設計、実装、テストに至るまで、上流から下流までの全開発フェーズを一貫して担当いたしました。

In English:

Professional Summary
After graduating from [〇〇 University], I joined [〇〇 Co., Ltd.]. I have been engaged in development work in the System Development Department, using technologies such as [〇〇] and [〇〇]. I have participated in a variety of projects, including [〇〇] and [〇〇], and have been consistently responsible for the entire development lifecycle—from requirements definition and design to implementation and testing.

Work History

This is the main section of the document, and includes not just what companies you have worked for, but also details on individual projects, the technologies used, and your achievements. All of this information should be written in reverse chronological order and divided by company. This information is frequently organized in a table, and there are many free templates available online.

Begin each new company section with a short summary of your overall responsibilities. Then, break down your work for that company by project. If you have worked at a company for a long time, you would be expected to list multiple projects for that term of employment. For each project, include the following:

  • Project Overview: the purpose and scale of the project
    Role: your job title in that position or for that project (e.g., Tech Lead, Backend Engineer)
  • Responsibilities: use bullet points and describe what you actually did, not what the team did
  • Tech Stack: specify the technologies used, and if they were different for each project, list each stack separately. You should use the actual name of the tool rather than katakana (e.g. “Redis” vs “レディス”)
  • Achievements/Results: explain how you contributed, using quantifiable outcomes as much as possible (e.g. “Reduced expenses by 30 percent”)

In Japanese:

2020年7月~現在  株式会社○○○○○○    
事業内容:マッチングアプリサービスの開発・提供 正社員  
2021年11月~2022年6月 /メッセージング機能の開発    
【プロジェクトの目的】
自社マッチングアプリ内の「メッセージ機能」を全面的にリニューアルし、よりリアルタイムで快適なコミュニケーションを実現するプロジェクトです。従来は動作が重く、通知が遅延するなどユーザー体験に課題がありましたが、新システムではメッセージの送受信速度の向上と安定稼働の実現を目指しました。

【担当工程】
要件定義、サーバーサイドの設計
・開発、負荷試験の実施とパフォーマンス改善

【具体的な業務】
・リアルタイム通信(WebSocket)を導入し、メッセージの送受信を即時反映できるよう設計・実装。
・メッセージの重複送信や順序の乱れを防ぐ仕組みを開発し、安定したチャット体験を実現。
・サーバー負荷を分散させる設計を行い、同時接続数が2倍以上になっても快適に動作。
・通知機能を改善し、ユーザーが複数のメッセージをまとめて受け取れるよう最適化。
・スパムメッセージ対策(レート制限・異常検知)を導入し、ユーザー保護を強化。

【成果と工夫した点】
・メッセージ送信失敗率を約半分に改善・負荷の高い夜間ピーク時にも安定稼働を実現
・新旧システムを同時に動かしながら徐々に移行する「段階リリース」を採用し、ダウンタイムなしで切り替えを行った
【OS】 Windows

【言語】 TypeScript / Node.js

【DB】 PostgreSQL

【その他】
Redis / AWS (EKS, S3, CloudFront) / Firebase Cloud Messaging
全5名

サブリーダー

In English:

July 2020 – Present [Company Name]      
Business: Custom application development Full-time Employee    
October 2021 to June 2022 Development of Messaging Functions for ([Client Name])    
Project Objective
This project involved a complete overhaul of the messaging function within the company’s app, enabling smooth real-time communication. Previously, the system had issues with the user experience, such as slow performance and delayed notifications, but the new system aimed to improve message sending and receiving speeds and ensure stable operation.

Phases Handled
Requirements, Server-side Design and Development, Testing, and Performance Improvement

Key Responsibilities
- Introduced real-time communication (WebSocket) and designed and implemented the program to ensure that sent and received messages are reflected immediately
- Developed a system to prevent duplicate messages and messages arriving out of order, ensuring a stable chat experience
- Distributed the server load, so that the service operates smoothly even when the number of simultaneous connections more than doubles Improved and optimized notifications, allowing users to receive multiple messages at once
- Implemented anti-spam measures (rate limiting and anomaly detection) to strengthen user protection

Achievements and Initiatives
- Reduced the message failure rate by approximately half
- Achieved stable operation even during peak nighttime hours
- Adopted a “phased release” approach, allowing for a gradual transition while running both the old and new systems simultaneously, enabling a seamless transition without downtime
OS
Windows

Languages
TypeScript / Node.js

Other
Redis / AWS (EKS, S3, CloudFront) / Firebase Cloud Messaging
Team Size
5 members

Role
Sub-Leader
 

Skills and certifications

Your skills are commonly listed in a table and divided into sections, such as Frontend, Backend, and Infrastructure, with your years of experience and proficiency level described for each one.

You should also include relevant certifications and awards in this section, especially if you have not prepared a rirekisho with this information.

In Japanese:

カテゴリ 技術スタック 使用期間 レベル
バックエンド Java 5年 JVMの特性を理解し、パフォーマンスを考慮した設計・実装、指導が可能
バックエンド Go 2年 マイクロサービス環境でのAPIサーバー開発、並行処理の実装が可能
バックエンド TypeScript (Node.js) 3年 Express, NestJS等を用いたAPI開発、型安全なコード実装が可能
フロントエンド TypeScript 3年 大規模なフロントエンド開発で型定義を設計し、安全な開発が可能
フロントエンド React / Next.js 3年 コンポーネント設計、状態管理ライブラリを用いたSPA/SSR開発が可能
フロントエンド Vue.js / Nuxt.js 1年 基本的なコンポーネント作成、状態管理を用いたSPA開発が可能
フレームワーク Spring Boot (Java) 4年 DI, AOPを理解し、Web APIの設計・開発、テストコードの実装が可能
フレームワーク Gin (Go) 2年 パフォーマンスを意識したRESTful APIの開発が可能
データベース PostgreSQL / MySQL 5年 インデックス設計やクエリ最適化など、パフォーマンスチューニングが可能
データベース Amazon Aurora 3年 クラウドネイティブな設計、スケーリングを考慮した運用が可能
データベース Redis 2年 キャッシュ戦略の設計、セッション管理などでの利用が可能
CI/CD GitHub Actions 3年 テスト、ビルド、デプロイのパイプラインを自律的に構築・運用可能
CI/CD Jenkins 2年 既存パイプラインのメンテナンス、新規ジョブの作成が可能
クラウド AWS (主要サービス:
EC2, S3, RDS, Lambda, ECS)
5年 VPC等のネットワーク設計、可用性を考慮したインフラ構築が可能
クラウド GCP 1年 Cloud Run, Cloud Functions等を用いたサーバーレス開発が可能
コンテナ Docker 4年 Dockerfile作成、マルチステージビルドによるイメージ最適化が可能
コンテナ Kubernetes 2年 マニフェスト作成、基本的なPod/Service/Deploymentの運用が可能
その他 Terraform 2年 Infrastructure as Codeによるクラウド環境の構築・管理が可能
その他 Nginx 4年 リバースプロキシ、ロードバランシング等の設定、パフォーマンス管理が可能
その他 Shell Script 5年 定型業務の自動化、サーバーの基本的なオペレーションが可能

資格・認定
- 日本語能力試験N1(2025年9月)
- 漢字検定2級(2024年6月)
- 安全確保支援士(2024年4月)
- CCNA(2022年)
- 在留資格 技術・人文知識・国際業務(2028年4月まで)

In English:

Category Tech Stack Experience Proficiency
Backend Java 5 years Able to design, implement, and optimize performance-critical applications with a deep understanding of the JVM. Capable of mentoring team members.
Backend Go 2 years Capable of developing API servers in a microservices architecture and implementing concurrent processing.
Backend TypeScript (Node.js) 3 years Can develop type-safe APIs using frameworks like Express and NestJS.
Frontend TypeScript 3 years Able to design type definitions and ensure type safety in large-scale frontend development.
Frontend React / Next.js 3 years Proficient in developing SPAs and SSR applications, including component design and state management.
Frontend Vue.js / Nuxt.js 1 year Can develop SPAs with basic component creation and state management.
Frameworks Spring Boot (Java) 4 years Can design, develop, and test Web APIs with a solid understanding of DI and AOP principles.
Frameworks Gin (Go) 2 years Capable of developing performance-conscious RESTful APIs.
Databases PostgreSQL / MySQL 5 years Able to perform database tuning, including index design and query optimization.
Databases Amazon Aurora 3 years Proficient in cloud-native design and managing scalable database operations.
Databases Redis 2 years Can design caching strategies and implement solutions for session management.
CI/CD GitHub Actions 3 years Can autonomously build and manage CI/CD pipelines for testing, building, and deployment.
CI/CD Jenkins 2 years Able to maintain existing pipelines and create new jobs.
Cloud AWS (Core services: EC2, S3, RDS, Lambda, ECS) 5 years Can design and build highly available infrastructure, including network design (VPC, etc.).
Cloud GCP 1 year Capable of serverless development using services like Cloud Run and Cloud Functions.
Containers Docker 4 years Proficient in writing Dockerfiles and optimizing images using multi-stage builds.
Containers Kubernetes 2 years Can write manifests and manage basic Kubernetes objects (Pods, Services, Deployments).
Other Terraform 2 years Able to build and manage cloud infrastructure using Infrastructure as Code (IaC).
Other Nginx 4 years Can configure reverse proxies, load balancing, and manage server performance.
Other Shell Script 5 years Able to automate routine tasks and perform basic server operations.

Certifications & Qualifications

  • Japanese Language Proficiency Test N1 (September 2025)
  • Kanji Examination Level 2 (June 2024)
  • Safety and Security Support Staff (April 2024)
  • CCNA (2022)
  • Visa: Engineer, Specialist in Humanities, International Services (until April 2028)

Self-Promotion

This section is just as described—you should promote yourself. Really, the purpose is to ensure the company wants to meet you, so you should do your best to write from the company’s perspective. This means first understanding the job description, then highlighting your most relevant experiences.

Usually this part contains three short sections of around five lines each. Following is an example for a management-focused position.

In Japanese:

【チームビルディングとメンタリング】
エンジニアリングマネージャーとして、最大15名の開発チームを率いました。
メンバーの強みとキャリア目標に基づいた個別の成長プランを作成し、その結果、1年以内に3名がシニアポジションへ昇進しました。定期的なコードレビューや1on1を通じて、安全に学べる文化を醸成し、定着率の向上につなげました。

In English:

Team Building and Mentorship As an Engineering Manager, I led a development team of up to 15 members. I created individualized growth plans based on each member’s strengths and career goals, resulting in three promotions to senior positions within one year. Through regular code reviews and one-on-ones, I fostered a safe learning culture that improved retention.

Can I use machine translation?

You can use machine translation to help create your shokumu keirekisho, but proceed with caution.

First, as most people who have used machine translation already know, it doesn’t always produce natural-sounding language. If you do use machine translation, you should have a Japanese speaker give the document a quick review for awkward phrases or bad translations.

Second, keep in mind that the company will make assumptions about your Japanese level based on the document: if it’s in perfect Japanese, your interviewers may assume your spoken Japanese is equally fluent. For candidates who have better spoken than written Japanese, this could be a beneficial assumption. For those who don’t have much Japanese ability at all, it may still be worthwhile to send in a Japanese shokumu keirekisho, but you should state your actual Japanese level clearly in several places. Otherwise, when the company discovers that you’re not fluent, they may feel that you’ve wasted their time.

How do recruiters use the shokumu keirekisho?

A recruiter’s top priority is determining the candidate’s fit with the specific job opening. That’s why it’s important to clearly include as many requirements and nice-to-have skills mentioned in the job post as possible.

When it comes to your work history, employers focus more on business and engineering results than on the tasks performed. Performance improvements, reduced workload, increased sales, and user growth are the sort of metrics of success recruiters want to see. In addition, self-initiated or proactive efforts in the workplace are highly respected, so be sure to list as many of those as you can.

Recruiters also look closely at your role and level of responsibility, such as leadership experience, your involvement in tech selection, and the scope of projects you’ve handled. The more senior the position you’re applying for, the more important these aspects become.

Final advice

The goal of the shokumu keirekisho is to highlight your unique strengths, so its exact format and details will naturally vary. However, applicants frequently make certain mistakes that reduce the document’s overall impact.

Common errors include:

  • Listing tasks without outcomes. Never forget to include the outcomes! In particular, always strive for measurable results as much as possible. Numbers, percentages, and other concrete metrics are best.
  • Repeating similar content across sections. Do your best to make each section distinct from the others.
  • Making it too short or too long. It doesn’t need to fit on one page, but more than five pages is too much. In general, however, more relevant detail is better than too little, so err on the side of length.

While the shokumu keirekisho is a flexible document, following the guidelines and examples above should produce excellent results.

If you’d like to consult with others who have written a Japanese-style resume, or discuss other aspects of applying to Japanese companies, you can join our Discord.

If you’d like to read more about getting a software developer job in Japan, passing the resume screening stage, or working with a Japanese recruiter, check out our extensive library of articles.

More about the author

Photo of Rebecca Callahan

Rebecca Callahan

Contributor

Rebecca Callahan is a narrative designer and editor living in Japan. In 2015 she founded Callahan Creatives, a writing agency specializing in storytelling for brands and IPs. She enjoys making cool things with cool people, and drinking way too much coffee.

🚀 Opportunities for English speaking developers in Japan

New job postings as they're listed, delivered to your inbox. Your email stays private, I don't share or sell it to anyone.

Other articles you might like