Your Foreign Job Title Doesn't Translate: How to Fix It on Your Resume

Your actual title back home doesn't exist in US job postings, and that mismatch is quietly costing you interviews.

Back home, your title might have been Assistant System Engineer, Scientific Officer, or Senior Associate. You did real work under that title — you built features, managed a P&L, ran a lab. On your US resume, that exact title reads as noise. A recruiter skims past it because it doesn't map to anything they're hiring for, and the applicant tracking system (ATS) doesn't surface your profile for the searches that would have matched your actual experience, because the keyword it's matching against simply isn't in your title field.

The fix isn't inflating your title or hiding it. It's translation: mapping what you actually did, day to day, to the closest recognized US title for that work, using the language recruiters and ATS systems search for, while keeping your original title visible so nothing on the page looks invented. This guide walks through how to do that mapping, where it matters beyond just getting past a keyword filter, and the mistakes that make international resumes look either underqualified or exaggerated.

Why a literal translation backfires

Corporate titling systems abroad and in the US solve different problems, so a word-for-word translation often lands wrong in both directions.

Large IT-services firms in India, for example, use internal grade ladders — Assistant System Engineer, System Engineer, Senior Software Engineer — that track tenure and pay band more than they track actual seniority of work. Someone two years in might already be leading a small module independently, while the title still reads "Assistant." Public-sector and PSU titles (Scientific Officer, Section Officer, Deputy Manager) describe civil-service pay grades that have no US private-sector equivalent at all. UK graduate schemes hand out "Graduate Engineer" or "Analyst" titles that don't reflect the technical depth of the role. BPO and shared-services titles like "Team Leader" frequently describe a senior individual contributor, not a people manager.

None of that is a problem when a hiring manager reads your resume top to bottom and evaluates the bullet points. It becomes a problem the moment your resume enters an ATS, because most of these systems weight the job title field heavily when matching candidates to a requisition. If the requisition says "Software Engineer II" and your resume says "Senior System Engineer" with no recognizable synonym nearby, you may never surface in that search — regardless of how well your actual experience fits. For more on what ATS software does and doesn't do with your resume, see our guide on building a US resume that works beyond just beating the ATS.

Two places this actually matters when you need sponsorship

For candidates who will eventually need visa sponsorship, the job title question shows up twice, at two different stages, and it's worth keeping them separate.

First, at the application stage. Recruiters and ATS filters are matching your resume's title and keywords against the requisition — this is a pure discoverability problem, and it's the one you can control directly by rewriting your resume.

Second, once an employer is preparing to sponsor you. If a role heads toward an H-1B, the employer files a Labor Condition Application (LCA) with the Department of Labor that assigns a specific job title and Standard Occupational Classification (SOC) code to the position, and that code drives the prevailing wage level the role is measured against. USCIS then evaluates whether the position qualifies as a specialty occupation based on the actual duties described in the petition — not the title on your resume. You don't choose the LCA title; your employer and their immigration counsel do, based on the role they're hiring you into. But a resume, LinkedIn profile, and offer letter that describe wildly different seniority levels for what's supposed to be the same job is the kind of inconsistency that invites extra scrutiny later, including if your title changes and the role needs an LCA amendment down the line. If you want to understand how specialty occupation is actually assessed, our guide to responding to a specialty occupation RFE walks through what USCIS is actually testing for. None of this is a reason to under-describe your work — it's a reason to describe it accurately and consistently everywhere it appears.

Some fields carry this even further, where the job title itself is closely tied to how sponsorship-eligible the role looks on paper. Our breakdown of job titles and H-1B sponsorship in biomedical engineering is a good example of how title precision interacts with a specific field's sponsorship landscape.

How to find your US equivalent title

Work through this in order rather than guessing at a translation:

1. List your actual duties, not your employer's internal title. Write down what you did on a typical week, in plain language, before you think about what to call the role.
2. Search O*NET (onetonline.org), the US Department of Labor's occupational database, using those duties. O*NET maps real-world work to standardized SOC titles and will usually surface two or three candidate titles.
3. Cross-check against live postings. Search LinkedIn and company career pages for the exact title O*NET suggests, at companies doing similar work, including companies with a track record of H-1B sponsorship if that's your target list. If the postings describe work that matches yours, you've found your title.
4. Check the keyword variants. The same job is often posted under two or three different titles across companies (Data Analyst vs. Business Intelligence Analyst, DevOps Engineer vs. Site Reliability Engineer). List the variants and pick the one that appears most often for your target companies, or use the most common one in your summary and the next-most-common as a secondary keyword elsewhere on the resume.
5. Sanity-check the seniority level. Compare years of experience and scope (individual contributor vs. lead vs. manager) in the postings you found against your own — don't just match function, match level too.
6. Keep the original title visible. Add it in parentheses next to the US title so the mapping is transparent, not hidden.

Common foreign job titles and their US resume equivalents

Treat this as a starting point, not a lookup table to copy blindly — always verify against real postings for your specific field, since the same title can mean different things in different industries.

How to write it on your resume

Use a simple, consistent format across your resume and LinkedIn headline: US Title (Original Title) | Company | Dates. For example: "Backend Software Engineer (Assistant System Engineer) | Infosys | 2022–2025." This gives ATS and recruiters the searchable US title up front, while keeping full transparency about what you were actually called — which matters if a background check or reference call references your original title.

Keep the rest of the resume doing the real work: your bullet points, not the title, should carry the specific scope, technologies, and outcomes. A title translation fixes discoverability; it doesn't replace the evidence that you can do the job.

Common mistakes

• Word-for-word literal translation. Keeping an internal grade-ladder title (like "Senior System Engineer" for someone with two years of experience) because it sounds impressive, when US recruiters read it as a mismatch with your actual tenure.
• Inflating scope you didn't have. Calling yourself a "Manager" because you led a project, when you had no direct reports and no budget authority. This shows up fast in an interview and can undermine trust in the rest of your resume.
• Deflating a legitimately senior title out of caution. Some candidates under-translate a genuinely senior overseas role because they assume US recruiters won't believe it — don't erase real seniority; verify it against postings instead of guessing down.
• Inconsistency across documents. Using one title on your resume, a different one on LinkedIn, and a third in your outreach emails. Recruiters and future employers notice, and it undermines the exact credibility a title translation is supposed to protect.
• Ignoring keyword variants entirely. Picking only one US title and never checking whether your target companies actually use a different common phrasing for the same role.
• Ghost-writing the title alone and stopping there. A correct title gets you found; it doesn't get you hired. The bullet points still need to prove the title is accurate.

Frequently asked questions

How do I find the US equivalent of my foreign job title? Start with O*NET (onetonline.org), the Department of Labor's occupation database, and search by what you actually did each day rather than by your original title. Cross-check the SOC-coded title it returns against real job postings from companies doing similar work, then use whichever title recruiters and ATS systems in that field actually search for.

Should I keep my original foreign title on my resume at all? Yes, keep it visible in parentheses next to the US equivalent, something like Software Engineer (Assistant System Engineer). Dropping it entirely can look evasive, and a background check or reference call will surface your real title anyway.

Will translating my job title hurt my H-1B case later? The title on your resume is separate from the job title and SOC code your future employer chooses for the Labor Condition Application and any H-1B petition, and USCIS evaluates specialty occupation status based on actual duties, not resume wording. Consistency across your resume, LinkedIn, and offer letter is good practice, but the filing title itself is a decision for your employer and their immigration attorney.

What if my foreign title does not map to any single US title? Many roles, especially in generalist IT-services or public-sector systems, actually cover two or three separate US job functions. Pick the single US title that matches the majority of your actual responsibilities, then use your bullet points to describe the rest of the scope rather than cramming it all into the title line.

Is it dishonest to change my job title on my resume? No, as long as the new title accurately reflects the level and scope of work you actually performed. Translating Senior Software Engineer at an overseas outsourcing firm into a comparable US title describes the same job in language a US recruiter understands, which is different from inflating a title to claim seniority, budget, or people-management responsibility you never had.

Sources

• O*NET OnLine — US Department of Labor-sponsored occupation database for mapping duties to standardized US job titles and SOC codes
• USCIS Policy Manual, Specialty Occupation Guidance — how USCIS evaluates specialty occupation status based on job duties

Getting your title right gets your resume in front of the right people. Getting the rest of your search right — finding sponsor-friendly roles, tracking applications, and prepping for interviews where visa status comes up — is the harder, ongoing part. If you want help with that end-to-end, reach out to F1Jobs.