Put your working language pairs where they can be found

A translator resume should answer a basic question quickly: which languages do you translate from and into? Write the direction explicitly, such as Spanish to English, rather than listing Spanish and English under a general Languages heading. If you work in both directions, say so only when you can support both with real experience.

Use a headline or short profile to name the pair and the kind of material you have handled. A simple model is: Spanish-to-English translator with experience adapting customer help articles and reviewing terminology against a client glossary. Replace the details with your own work; a language pair alone does not tell an employer what you have translated.

  • Headline: name your primary translation direction and relevant content area.
  • Languages section: distinguish translation direction from general speaking proficiency.
  • Multiple pairs: prioritize those requested in the posting instead of crowding the first line.

Match the posting to the material you actually know

A job may involve product instructions, marketing copy, subtitles, internal guides, or customer support content. Read the posting for both the language pair and the content type, then move your closest projects toward the top of the resume. Experience translating one kind of text does not automatically establish expertise in another.

If the role calls for specialized or regulated material, do not imply a credential, approval, or subject-matter qualification you do not hold. Show the relevant projects you can discuss, name any verified training accurately, and let the employer assess fit. For a general role, clear evidence of audience, accuracy checks, and handoff is more useful than a long list of topics.

Describe translation work as a process and deliverable

Under each role or project, state what you translated, for whom or for which audience, and what you did to make the final text usable. Separate translation from editing, proofreading, terminology research, and localization when those were distinct tasks. A bullet should describe your contribution rather than claiming that you improved quality without evidence.

For example, an applicant who did this work could write: Translated Spanish help-center articles into English, checked recurring product terms against the approved glossary, and revised drafts after editor feedback. That is a model, not an achievement to copy. Use your real language pair, document type, review steps, and outcome; add volume or turnaround numbers only if you can verify them.

  • Material: articles, interface strings, training guides, captions, or another real document type.
  • Action: translated, edited, reviewed, researched terminology, or coordinated revisions.
  • Handoff: delivered a reviewed file, updated a glossary, or resolved queries with a reviewer.

Choose a layout that makes varied projects readable

If you worked as an employee, keep the employer, title, and dates clear, then select a few representative assignments beneath that role. If you were self-employed, group related client projects under one freelance entry and label the relationship honestly. Do not present a client as your employer or split every short assignment into a separate job unless that helps explain the timeline.

Early-career translators can use coursework, volunteer work, or personal projects when those are accurately labeled. Briefly identify the source material and audience, then explain which parts you translated and how you checked your draft. Unpaid or practice work can demonstrate a process, but it should not be described as commissioned professional work.

List tools and samples with context and permission

A tools line can include software, terminology resources, or document formats you actually used. Name a tool only when you could explain a task you completed with it. If a posting asks for a platform you have not used, do not add it as a keyword; show comparable workflow experience where relevant.

A sample may be helpful when the employer requests one, but client ownership and confidentiality matter. Link to published work you are permitted to share, or prepare an original sample using material you have the right to translate. Label the source language, target language, audience, and your role. Do not post a client draft, private data, or an unapproved before-and-after comparison.

Check the resume against the application before exporting

Compare your headline, language pairs, selected projects, and skills with the exact posting. Verify that the language direction is consistent in every section, dates and client relationships are accurate, and any sample link opens as intended. Avoid unexplained abbreviations in the most important lines so a general recruiter can still follow your work.

Preview the final PDF to catch broken characters, awkward wrapping of language names, and links that disappear in export. CreateResume can help you organize a role-specific resume draft, preview its layout, and prepare PDF-ready output. The claims, permissions, and sample selection still need your own review.

  • Can a reader identify the translation direction and content type at a glance?
  • Does every project bullet describe work you actually performed?
  • Are samples shareable, accessible, and relevant to this application?