How Do I Translate My Job Title for an International Resume?
Short answer: don't translate it literally, and don't just copy the closest-sounding English title either. Job title systems are built around each country's own management structure, and the two rarely line up one-to-one. What actually gets you through screening is describing the scope of the role in terms a foreign recruiter recognizes — not finding the "correct" English word for your title.
Why job titles don't translate cleanly
Titles encode a local seniority ladder, and ladders differ by country. A title that signals "several years in, trusted with more responsibility, not yet managing people" in one country's structure may have no direct counterpart abroad — the closest English word can end up sounding either far more senior than the role actually was, or far less. Literal, word-for-word translation carries the shape of the original ladder into a market that uses a different one, and the mismatch is invisible to the person doing the translating but obvious to the recruiter reading it.
The two failure modes
Over-translating happens when a title that sounded impressive at home gets mapped onto an English title that implies people-management, budget ownership, or strategic authority the role never actually had. A recruiter who asks one follow-up question in an interview finds the gap immediately, and it reads as either confusion or exaggeration — neither helps you.
Under-translating happens when a genuinely senior role gets rendered into a flat, junior-sounding English title because the translation was done word-for-word instead of by seniority level. This one is more common and more costly: it can get a qualified candidate filtered out by an ATS or a recruiter's first-pass skim before anyone reads the actual accomplishments underneath.
What recruiters actually judge instead of the title
- Scope — how many people, if any, reported to you; how many teams or functions your work touched.
- Ownership — did you execute a plan someone else set, or did you set the plan yourself?
- Budget or revenue responsibility — a concrete number is more legible across borders than any title.
- Level relative to the team — were you the most junior, mid-level, or the most senior non-manager on the team?
A resume that answers these four questions clearly gets evaluated on the actual work, regardless of which English word ends up next to the job title.
A format that works across markets
Use the closest reasonable English title, then let the description underneath do the precision work: "Senior Analyst (original title: [local title]) — led a 3-person team, managed a $200K annual reporting budget, reported directly to the department head." The parenthetical is optional and mainly useful when your original title is well-known enough in your industry that recruiters familiar with your home market will recognize it; the scope description is what carries the weight everywhere else.
One title, many job postings, no single "correct" answer
Because there's no exact equivalent, the right English title for your role can reasonably shift slightly depending on which job posting you're applying to — matching the title language that specific employer already uses for that level, as long as the scope description underneath stays accurate. This is a different task for every application, which is exactly why copying the same resume everywhere tends to under- or over-sell the same role inconsistently from one posting to the next.
Where this gets hardest
Getting scope and seniority to read correctly in a second language, for a job market whose title conventions you didn't grow up with, is a genuinely hard writing problem — independent of how strong the underlying experience is. JobFit Rewrite rewrites your resume for one specific job posting, translating both the language and the seniority level accurately, for $19.