Application Documents
How to write an English resume for foreign companies in Japan
The English resume is not a translated shokumukeirekisho: one to two pages, verb-first bullets with numbers, and keywords matched to the job description.
What you can use right away
- An English resume is one to two pages of evidence, not a translation of your Japanese documents.
- Every bullet starts with a strong verb and ends with a number or concrete outcome.
- Mirror the job description's keywords — screening software and busy recruiters both search for them.
Stop translating — the formats carry different cultures
A rirekisho includes a photo, birth date, and family details; an English resume must include none of these — no photo, no age, no gender, no marital status. Include name, contact details, a three-line summary, work experience in reverse-chronological order, skills, and education. One page for under ten years of experience, two pages maximum.
The deeper difference is cultural: Japanese documents describe duties and context politely; English resumes state claims and back them with evidence. "I was in charge of the payment system as a member of the backend team" becomes "Led redesign of the payment API serving 2M transactions/day, cutting p99 latency 60%."
Verb-first bullets with numbers
Every experience bullet follows one shape: strong verb + what you did + measurable result. Led, designed, built, migrated, reduced, automated. Kill the weak openers — "worked on", "helped with", "was responsible for" — they hide whether you did the work or sat near it.
The number does not need to be revenue. Latency, error rates, release frequency, hours saved, team size, user counts all work. If a bullet has no number after honest effort, state the before-and-after concretely: "Replaced manual deploy checklist with CI pipeline; deploys went from feared to daily."
Try this checklist
- Rewrite every bullet to start with a verb and end with a number or concrete outcome.
- Delete "worked on", "helped", and "responsible for" from the entire document.
- Cut to two pages maximum by removing your oldest or least relevant roles first.
Match the job description's keywords
Many foreign companies run resumes through applicant tracking systems, and every recruiter skims with the job description's vocabulary in mind. If the JD says "Kubernetes", "distributed systems", and "mentoring", and your resume says "container orchestration", "large-scale backend", and "guiding juniors", you lose matches you deserve.
Pull the ten most important keywords from each JD — technologies, methodologies, role words — and make sure the ones that are true of you appear verbatim in your summary or bullets. This is per-application tailoring: the resume you send to an infrastructure role and a product team role should not be identical.
The three-line summary and the skills section
Open with a summary a screener can absorb in ten seconds: years and domain, biggest scope or achievement, and what you are strong in. "Backend engineer with 8 years in payments and e-commerce. Led API platform serving 10M MAU across a 6-engineer team. Strong in performance tuning and cloud migration."
The skills section is a scannable list, grouped (Languages / Infrastructure / Tools), honest, and free of decade-old technologies you no longer want to work with — listing a skill is an invitation to be interviewed about it.
One source of truth for both languages
Maintaining a shokumukeirekisho and an English resume in parallel goes wrong when they drift — different numbers for the same project is a red flag any bilingual interviewer will catch.
InterviewTrail AI's Career Memory keeps each project's facts — scale, role, stack, outcomes — in one structured place, so both documents draw on identical material and the JD match analysis shows which experience to emphasize per application.