Translator portfolio guide: language pairs, specializations and samples

Most people who hire a translator can't read the language you're translating from. That makes their decision unusually hard. They can't easily judge your work, so they look for other signals: a clear language pair, real expertise in their subject, credible samples and evidence that you handle deadlines and confidential material well. A portfolio puts all of that in one place. This guide covers how to present language pairs and directions, choose specializations, share samples you have permission to use, describe credentials and tools, and talk about the work without stating rates.

How clients and agencies read a translator portfolio

Translation buyers come in a few kinds: agencies and project managers who hire freelancers regularly, direct clients such as companies or law firms, and individuals who need a single document handled. They read differently, but they all check the same things first:

1. Language pair and direction. Do you translate into the language they need?
2. Specialization. Do you understand their subject well enough to get the terminology right?
3. Proof of quality. Samples, credentials, testimonials.
4. Reliability. Turnaround, communication, confidentiality.
5. Practicalities. Tools, file formats, how to get a quote.

Your first screen should answer the first two at a glance. For example: "Spanish to English translator specializing in medical device documentation and clinical research. Native English speaker based in Canada." An agency project manager can decide in seconds whether to keep reading.

Language pairs and directions

This is the most important line on your portfolio, so be precise.

State the direction

Write each pair with its direction: "French to English," not "French and English." Many professional translators work only into their native or strongest language, and clients and agencies often expect that. If you genuinely work in both directions, say so, and be honest about which is stronger.

Separate translation from interpreting

If you do both, list them separately. Interpreting has its own modes, such as consecutive, simultaneous, remote and on-site, and its own settings, such as conferences, community, legal or medical. A client booking an interpreter for a hospital appointment wants to see that experience specifically.

Before and after

Before:

"Fluent in English, German and Italian. Translation and interpreting services."

After:

• Translation: German to English and Italian to English. I translate into English only.
• Interpreting: English and German, consecutive and remote, mainly for business meetings and site visits.

The second version tells a buyer exactly what you can do and what you can't, which makes you easier to hire.

Fewer, clearer language pairs look more professional than a long list. If you'd hesitate to deliver a technical document in a pair tomorrow, leave it off.

Choosing and showing specializations

Specialization matters more in translation than in many fields. A strong general translator can still mishandle a patent claim, a clinical protocol or a financial statement if they don't know the subject.

Pick two or three areas where you have real depth, and explain where that depth comes from:

• Previous career: "Before translating, I worked for six years as a mechanical engineer."
• Education: a degree or courses in the subject.
• Volume of work: "Most of my work over the last four years has been software interfaces and help documentation."
• Ongoing learning: subject-specific training or reading you keep up with.

For each specialization, list the kinds of documents you handle. "Legal: contracts, terms and conditions, court judgments, company formation documents" is far more useful than "Legal translation."

If you're still building a specialization, it's fine to say so. Clients respect honesty, and an inflated claim in a technical field is easy to expose.

Samples you have permission to share

Samples are where translators often get stuck, because most client work is confidential and belongs to the client. Never publish a client's text without clear permission. Here are safer options.

Ways to build a sample set

• Ask past clients. Some will allow you to share a short excerpt, especially of material that's already public, such as a published website, brochure or annual report.
• Use public-domain or openly licensed texts. Translate a passage from a public report, an older literary work or openly licensed material in your specialization. Note the source and its license.
• Translate your own source texts. Write a realistic mock document, such as a product description or a short contract clause, and translate it.
• Volunteer work. Translations for nonprofits or open projects, shared with the organization's agreement.

How to present a sample

Show the source and target side by side or one after the other, so a reader who knows both languages can check them. Keep each sample short, a few hundred words is usually enough. Add a brief note:

• What it is: "Extract from a public product safety leaflet."
• Pair and direction.
• Challenges: terminology, tone, a cultural reference you adapted, a formatting constraint.
• Your choices: why you translated a key phrase the way you did.

That note does a lot of work. A client who can't read the source can still see how carefully you think about meaning, audience and terminology.

A sample note

"This marketing extract used a wordplay on a regional dish that wouldn't make sense to an English-speaking audience. Rather than translating it literally, I kept the playful tone with a different food reference that suits the same audience, and flagged the change for the client in a comment."

For more on writing about work you can't fully show, the guide on how to write a case study covers confidential projects.

Credentials and certifications

Translation credentials vary a great deal between countries. Some places have sworn, certified or court-appointed translators with legal standing; others rely on professional association membership, university degrees or exams.

Keep this section factual:

• Degrees and qualifications in translation, interpreting or languages, with the institution.
• Certifications or accreditations, named exactly as the issuing body names them, with the language pair they cover.
• Professional association memberships, at the level you actually hold.
• Sworn or certified status, only if you hold it, and only for the jurisdiction where it applies.

Requirements for official translations, such as documents for immigration, courts or government offices, depend on the country and the receiving authority. Don't promise that your translation will be accepted somewhere; tell clients to check what the receiving organization requires, and describe what you can provide, such as a signed statement of accuracy, in general terms.

CAT tools and technical skills

Agencies in particular want to know which computer-assisted translation tools you use, because their projects often arrive as packages from specific tools. List:

• CAT tools you use regularly, and whether you own a license or work in the client's platform.
• Terminology management: building and maintaining glossaries and termbases.
• Quality assurance: the checks you run for consistency, numbers and tags.
• File formats you handle comfortably, such as office documents, PDFs, website files or subtitle formats.
• Machine translation post-editing, if you offer it, described clearly as a separate service.

Be honest about depth here too. If a project manager sends you a package expecting you to know a tool well, you need to deliver. Writing a skills section has more ideas on presenting tools usefully.

Rates, turnaround and how to work with you

You don't need to publish rates. Translation pricing depends on the language pair, subject, length, format and deadline, so most translators prefer to quote per project. Instead, tell clients what you need from them to give a quote: the file, the target audience, the deadline and any reference material.

Do share:

• Typical turnaround in general terms, and that urgent work may be possible by arrangement.
• Your working hours and time zone.
• Your process: translation, self-review, and whether you work with a second reviewer.
• Confidentiality: that you'll sign a confidentiality agreement, and how you store and delete files.

Make the request for a quote easy. A short line such as "Send me the document and your deadline, and I'll reply within one working day" removes friction for a busy project manager.

Testimonials

Because clients can't easily judge your work themselves, other people's words carry extra weight. A line from an agency project manager about accuracy and deadlines, or from a direct client about how their foreign-language customers responded, is valuable. Ask permission, quote exactly and describe the person if they'd rather not be named. Testimonials and references covers how to ask.

Putting it together

A strong translator portfolio is precise. State your language pairs with their direction, separate translation from interpreting, and choose a few specializations you can back up. Share short, permitted samples with notes on your choices, list credentials exactly as issued, and describe your tools and process. Leave rates for the quote, but make it easy to ask for one.