Advice corner · 就活ガイド

Becoming a developer in Japan

A practical guide in English to Japanese job hunting for engineers: how to prepare, how 就活 works, what to expect at 説明会, the SPI, entry sheets, the interview flow, and how to write a 履歴書 and 職務経歴書.

Written by Avie Fukai: came to Japan as a student, studied at a Japanese 専門学校, joined a Tokyo tech company as a new graduate, and has since worked as an engineer, Bridge SE and project manager.

  1. 01 Which path are you on?
  2. 02 Prepare: best practices
  3. 03 The new-graduate 就活 timeline
  4. 04 説明会: company info sessions
  5. 05 Entry sheets & the SPI
  6. 06 The interview flow
  7. 07 Writing a 履歴書 & 職務経歴書
  8. 08 Mid-career & moving from abroad
  9. 09 After the offer
  10. 10 Checklist, glossary & resources

01 Which path are you on?

Japan hires in two very different ways. Find yours first, because the timing, documents and tests all depend on it.

新卒 New graduate

University, graduate school or 専門学校

Companies hire whole cohorts at once (新卒一括採用) on a fixed yearly calendar, with everyone starting on April 1. They judge potential more than skills, so the SPI, entry sheets and interviews matter a lot. International students in Japan use this path too.

中途 Mid-career

You already have work experience

Hiring happens all year for specific positions. Companies judge what you have done: your 職務経歴書, technical interviews and coding tests. Recruitment agents and scouting sites are common.

第二新卒 Early career

About 1–3 years after graduating

Many companies welcome people who left their first job early. You are judged a bit like a new graduate (potential) and a bit like mid-career (what you learned).

未経験 Career change

New to software

Possible, but you need proof: projects, a portfolio and basic certifications. Many entry roles are at SES companies (engineers placed at client sites). Understand that model before you sign.

02 Prepare: best practices

1. Be honest about your Japanese

At most Japanese-speaking companies, JLPT N2 is the usual minimum and N1 helps a lot, especially for client-facing work or Bridge SE roles. Some international tech companies work in English, but there are fewer of them and competition is strong. The JLPT tests reading and listening, so also practice speaking and writing in 敬語 (polite language): interviews and entry sheets need it.

2. Pick a lane

"IT" is too broad. Decide whether you want frontend, backend, infrastructure, data, QA, Bridge SE and so on, and what kind of company: 自社開発 (in-house products), 受託開発/SIer (building systems for clients) or SES (placement at client sites). Job titles in Japan are not standardized, so always read the 仕事内容 (job duties) and required skills.

3. Build proof, not only credentials

Projects matter more than ever. A good project shows what problem you solved, how you built it (and how you used AI tools), and what happened. Keep your GitHub tidy, write a short README in English and, if you can, Japanese. A blog or short write-ups help interviewers understand how you think.

4. Get a Japanese IT certification

IPA's national exams are widely recognized: ITパスポート (IT basics), 基本情報技術者 (FE, the classic engineer entry exam) and 応用情報技術者 (AP). They show Japanese technical vocabulary as well as knowledge. For the AP exam, I keep an English vocabulary guide on GitHub.

5. Understand the visa early

Most developers work on the 技術・人文知識・国際業務 ("Engineer / Specialist in Humanities / International Services") status. In general it requires a degree or Japanese 専門学校 diploma related to the job, or enough years of relevant work experience; certain IT exams such as the IPA exams can also count in some cases. Requirements are detailed and change, so confirm with the Immigration Services Agency or your employer's HR.

6. Make your online presence tell one story

Your LinkedIn, GitHub, portfolio and 履歴書 should agree: same dates, same titles, same story about what you do. Recruiters compare them. Then network with intention: communities, meetups and referrals build trust faster than cold applications.

Common engineering roles in Japan

Japanese titleRoleWhat they do
フロントエンドエンジニアFrontend EngineerWeb interfaces and user experience (HTML, CSS, JavaScript, React, Vue, TypeScript).
バックエンドエンジニアBackend EngineerServer-side logic, APIs and databases (Python, Java, Node.js).
フルスタックエンジニアFull-Stack EngineerBoth frontend and backend; some companies also expect network knowledge.
インフラエンジニアInfrastructure EngineerServers, networks and IT infrastructure (Linux, Nginx, networking).
クラウドエンジニアCloud EngineerCloud architecture and automation (AWS, Azure, Google Cloud).
DevOpsエンジニアDevOps EngineerCI/CD, monitoring and infrastructure as code (Docker, Kubernetes, Terraform).
組み込みエンジニアEmbedded EngineerSoftware for vehicles, industrial equipment and IoT (C/C++, RTOS).
社内SEInternal Systems EngineerInternal IT systems, employee support and vendors. Some roles include development, some don't.
ブリッジSEBridge SE (BrSE)Connects Japanese clients and offshore teams: clarifies requirements and coordinates projects.
システムエンジニア(SE)Systems EngineerRequirements, system design, documentation and coordinating development.
QAエンジニアQA EngineerTest planning and execution, test automation (Selenium, Playwright).
SRESite Reliability EngineerReliability through monitoring, incident response and automation.

03 The new-graduate 就活 timeline

For a 4-year university, job hunting starts in your 3rd year, about 18 months before you start work. On a 2-year 専門学校 course, it all happens in your first year, so start early. The official schedule below is the government-requested guideline; many companies, especially IT, foreign-owned and start-up companies, move earlier.

A typical 4-year-university 就活 calendar

Months are approximate and vary by company.

Mar 1 · 広報解禁 Jun 1 · 選考解禁 Oct 1 · 内定式 Apr 1 · 入社 AprJulOct JanAprJul OctJanApr 3rd year4th year Self-analysis & research Summer internships Autumn/winter & early selection 説明会 & entry sheets Interviews & offers Self-analysis and industry research: April to February Summer internships: usually held August to September (apply around April to June) Autumn/winter internships and early selection: October to February Info sessions and entry sheets: March to May Interviews and informal offers: March to July, peaking around June
  1. 3rd year · spring–summer

    自己分析・業界研究

    Self-analysis (strengths, values, episodes) and industry research. Apply for summer internships (applications around April–June, held around August–September). Internships increasingly lead directly into selection.

  2. 3rd year · autumn–winter

    Autumn & winter internships

    More internships, OB/OG visits (talking to alumni at companies) and early selection at IT, foreign-owned and start-up companies. Start SPI practice now.

  3. March 1 · 1 year before graduating

    広報解禁 — entries open

    Companies officially open recruiting on job sites. 説明会 season begins, and you submit entries and entry sheets.

  4. March–May

    ES, tests & early interviews

    Entry sheets, aptitude tests (SPI etc.), group discussions and first-round interviews. Many students already have 内々定 (informal offers) before June.

  5. June 1

    選考解禁 — official selection

    The official start of interviews and offers. Final interviews and 内々定 peak around now.

  6. October 1

    内定式 — formal offer

    The formal offer ceremony. International students: plan the change of residence status with the company (see section 09).

  7. April 1

    入社 — first day

    Everyone starts together, usually with several weeks or months of new-graduate training.

04 説明会: company info sessions

A 説明会 is where a company explains its business, work and hiring process. It can feel like a formality, but it is often the first step of selection: some companies only open entry or skip a step for people who attended.

  • 合同説明会 (job fairs): many companies in one place. Good for discovering companies you didn't know.
  • 個別説明会 (company sessions): one company, deeper information, often online.
  • Book through job sites (マイナビ, リクナビ) or the company's recruiting page. Popular sessions fill up fast.

How to get the most out of it

  • Read the company website first, so your questions aren't answered on page one.
  • Take notes. They become your 志望動機 (reason for applying) later.
  • Ask one specific question: tech stack, team size, how new engineers are trained, how much coding juniors actually do.
  • Dress: リクルートスーツ is the safe default for traditional companies. "服装自由" (free dress) usually means smart casual, not a T-shirt. Many IT companies are relaxed.
  • Online: test your camera and mic, use a plain background, keep your camera on and use your real name.

05 Entry sheets & the SPI

The entry sheet (ES / エントリーシート)

An ES is a company-specific application form with short essay questions, usually 200–400 Japanese characters each. Interviewers read it and ask about it, so keep a copy of everything you submit.

ガクチカ

What you worked hard on as a student

One episode: the situation, your goal, the problem, what you did, and the result with numbers. Clubs, part-time jobs, research and personal projects all count. A coding project is a strong choice for engineers.

自己PR

Your strength

Name one strength, prove it with an episode, then explain how it helps in this job. Being bilingual is good, but show what you did with it, such as bridging two teams.

志望動機

Why this company

Why this industry, why this company (not its competitors), and what you want to do there. Use what you learned at 説明会 and on the website.

ES best practices

  • 結論から: state the conclusion first, then the reason and episode (PREP or STAR structure).
  • Use about 80–90% of the character limit or more. Very short answers look unmotivated.
  • Write in です・ます style consistently, and avoid spoken expressions.
  • Write 貴社 for "your company" in documents; say 御社 when speaking.
  • Be specific: numbers, your role, what changed. Don't exaggerate; you'll be asked about it.
  • Ask a native speaker, your school's career center or a mentor to check your Japanese.

An ES answer skeleton

結論 私が学生時代に力を入れたことは、〇〇です。

状況・課題 当時、〇〇という課題がありました。

行動 そこで私は、〇〇を提案し、〇〇に取り組みました。

結果 その結果、〇〇が〇%改善しました。

学び・活かし方 この経験から〇〇を学び、貴社でも〇〇に活かしたいと考えています。

The SPI and other aptitude tests (適性検査)

Many companies use an aptitude test to filter applicants early. The most common is Recruit's SPI. It isn't hard, but it is fast, so practice is what makes the difference.

PartWhat it testsTips
言語 VerbalWord relationships, meanings, sentence order, reading comprehensionThe hardest part for non-native speakers. Learn the common question types and practice reading quickly.
非言語 Non-verbalJunior-high-level math: logic (推論), probability, profit and loss, speed, tablesYour best place to score. Learn the patterns from a prep book and practice with a timer.
性格検査 PersonalityWork style and personalityAnswer honestly and consistently. Similar questions repeat to check consistency.
English / 構造的把握力Optional sections some companies addCheck which sections your target companies use.

Test formats

  • テストセンター: at a test center or online with monitoring. You can often reuse your result for other companies, so once you get a good score, keep it.
  • WEBテスティング: at home on your own computer.
  • ペーパーテスティング and インハウスCBT: on paper or a computer at the company's office.

Other tests you may meet

  • 玉手箱: web test with very tight time limits; common at large companies.
  • CAB: designed for IT and programming roles: mental arithmetic, patterns, instruction tables and codes. Worth practicing if you apply to SIers.
  • GAB and TG-WEB: other aptitude tests some companies use.
  • Coding tests for engineers: paiza, AtCoder-style problems, HackerRank or a take-home assignment.

06 The interview flow

A typical new-graduate flow is below. Mid-career is shorter and more technical (see section 08). Expect each step to take about a week or two.

  1. Entry on a job site or the company page
  2. 説明会 info session
  3. ES / 履歴書 document screening
  4. 適性検査 SPI, CAB or coding test
  5. GD group discussion (some companies)
  6. 一次面接 HR or young engineers
  7. 二次面接 managers, often technical
  8. 最終面接 executives: motivation and fit
  9. 内々定 informal offer

Questions you will almost certainly get

  • 自己紹介: introduce yourself in about one minute.
  • 志望動機: why this company and this role?
  • ガクチカ / your projects: expect "why?" follow-up questions 3–4 levels deep.
  • Strengths and weaknesses, with an episode each.
  • For international candidates: "Why Japan?" and "How long do you plan to work in Japan?" Give a sincere, concrete answer.
  • Your career in 5–10 years.
  • Other companies you are interviewing with (他社の選考状況). Be honest and keep it short.
  • 逆質問: "Do you have any questions?" Always prepare 2–3. Ask about the work, team and growth, not things on the website.

Engineer-specific interviews

  • Explain one project end to end: the problem, design decisions, what was hard and what you would change.
  • Be ready to read your own GitHub code with the interviewer.
  • Practice thinking aloud in Japanese during coding questions.
  • "I don't know, but here is how I'd find out" is a good answer.

Manners that still matter

  • Arrive 5–10 minutes early (not 30). For online interviews, join a few minutes early.
  • Knock, say 「失礼いたします」, and sit down only when told 「どうぞ」. Bag on the floor next to your chair.
  • Answer with the conclusion first, then explain.
  • Online: camera at eye level, quiet room, plain background, look at the camera when you speak.
  • A short thank-you email afterwards is optional but leaves a good impression.

07 Writing a 履歴書 & 職務経歴書

The 履歴書 is a standard-format personal history that every applicant submits. The 職務経歴書 is a free-format work history that mid-career applicants add. Follow each company's instructions first; these are the common conventions.

Sample 履歴書 layout: title and date, name with furigana, photo box, contact details, education and work history table ending with 以上, licenses, motivation and preferences. 履 歴 書 2026年 11月 2日現在 ふりがな やまだ はなこ 氏名山田 花子 現住所 〒000-0000 写真3 × 4 cm 年月学歴・職歴 学歴 〇〇高等学校 入学 〇〇専門学校 卒業 職歴 株式会社〇〇 入社 現在に至る 以上 免許・資格 日本語能力試験N1 合格 志望動機・自己PR 本人希望記入欄 貴社の規定に従います。 1 2 3 4 5 6
  1. Name with ふりがな, as on your residence card
  2. Recent photo, about 3 × 4 cm
  3. 学歴 then 職歴, one line per entry and exit
  4. End with 「以上」, right-aligned
  5. Official names of licenses
  6. Usually 「貴社の規定に従います。」

履歴書: field by field

  • FormatUse the JIS-style form or the Ministry of Health, Labour and Welfare sample format (2021), where gender is optional. Typed (PC) is widely accepted, especially in IT; handwrite only if asked.
  • DateThe date you submit it (posting date if mailed, interview date if you bring it). Use 西暦 (2026) or 和暦 (令和8年) consistently throughout.
  • Name & ふりがなWrite your name exactly as on your residence card, with the reading in ふりがな or フリガナ as the form says.
  • PhotoAbout 4 × 3 cm, taken within the last 3 months, plain background, neat clothes. No selfies or edited photos.
  • 学歴 EducationUsually starting from high school entrance or junior-high graduation. One line per entry and exit (入学 / 卒業; 卒業見込み if you haven't graduated). For schools abroad, add the country and the official name.
  • 職歴 Work historyEach 入社 and 退社 with the company's full name. End with 「現在に至る」 if employed, then 「以上」 right-aligned. New graduates write 「なし」; long-term internships can go in the self-PR.
  • 免許・資格 LicensesOfficial names with the month obtained, e.g. 日本語能力試験N1 合格, 基本情報技術者試験 合格. Oldest first.
  • 志望動機・自己PRShort and tailored to the company. Reuse your ES thinking, but don't copy the same text everywhere.
  • 本人希望記入欄Usually 「貴社の規定に従います。」 Only write real conditions here, such as a required change of residence status.
  • FinishingIf handwritten, no correction fluid: rewrite the page. If digital, send a PDF named like 氏名_履歴書.pdf. Keep a copy for interview prep.

職務経歴書: for mid-career

Usually A4, 1–3 pages. The most common layout lists jobs with the newest first (逆編年体) or the oldest first (編年体):

  1. 職務要約: a 3–5 line summary of your career.
  2. 活かせる経験・知識・技術: what you bring.
  3. 職務経歴: for each project, the period, role, what you did, results, tech stack and team size.
  4. テクニカルスキル: languages, frameworks, cloud, tools.
  5. 資格・語学: certifications and languages.
  6. 自己PR: how your strengths fit the role.

Best practices

  • Show results with numbers: team size, % improvement, time saved.
  • Make your role clear: what you did vs what the team did.
  • Protect confidentiality: describe clients by industry ("a large entertainment web platform"), not by name, and never include internal system names or confidential figures.
  • Tailor the summary and self-PR to each job posting.
  • Keep dates and titles consistent with your 履歴書 and LinkedIn.

08 Mid-career & moving from abroad

Where to find jobs

  • Recruitment agents (転職エージェント): free for candidates because the company pays the fee. They help with documents, interview prep and salary negotiation. Choose ones that know IT.
  • Scouting sites: companies contact you (e.g. BizReach, Findy, LinkedIn). Keep your profile complete and current.
  • English-friendly job boards such as TokyoDev and Japan Dev.
  • Referrals (リファラル): communities and meetups. Build trust first; don't ask a stranger for a referral the first time you talk.

The mid-career flow

  1. Document screening (履歴書 + 職務経歴書, sometimes GitHub).
  2. カジュアル面談: an informal chat. Officially not a selection step, but still make a good impression.
  3. Coding test or take-home assignment.
  4. Technical interview, then a final interview (often 2–3 rounds in total).
  5. オファー面談: the offer meeting, where you review the conditions (next section).
  6. Resign from your current job and hand over your work. Check your contract and work rules: one month's notice is common.

Already on a work visa and changing employers? Generally you don't need a new visa for the same kind of work, but you must notify Immigration within 14 days. Check the official site for current rules.

09 After the offer

Read the conditions

労働条件通知書

Check the annual salary breakdown, bonuses, 固定残業代/みなし残業 (overtime pay already included, and for how many hours), probation period, work location, remote-work rules and the job duties.

Accept politely

内定承諾

Reply by the deadline. If you need more time to decide, ask early and honestly. If you decline, do it quickly and politely; the Japanese tech community is smaller than you think.

Sort out your status

在留資格

International students usually change from "Student" to a work status before the April start, with documents from the company. Start as soon as the company is ready. Keep part-time work within your permitted hours until then.

10 Checklist, glossary & resources

My preparation checklist

Tick items as you go. Your progress is saved only in this browser.

就活 glossary

就活(就職活動)
Job hunting
新卒 / 中途 / 既卒
New graduate / mid-career / graduated but not yet employed
自己分析・業界研究
Self-analysis / industry research
OB・OG訪問
Visiting alumni who work at a company
ES(エントリーシート)
Company-specific application form
ガクチカ
"What you put effort into as a student"
GD(グループディスカッション)
Group discussion exercise
逆質問
Your questions for the interviewer
内々定 / 内定
Informal offer / formal offer
お祈りメール
Rejection email ("we pray for your success")
SIer / 自社開発 / 受託 / SES
System integrator / in-house product / contract development / engineer placement
試用期間
Probation period
固定残業代
Overtime pay included in salary for a set number of hours

Useful resources

Links are for convenience, not endorsements. I'm not affiliated with any of these services.

One last thing You don't have to do everything. Pick your priorities, and keep going.