Translator Portfolio: Samples and a Complete Example
Build a translator portfolio around clear language pairs, a complete bilingual sample, and the decisions behind your work. Explore Pedro Fuente's finished website.

Javier Martínez Samblas
Founder of Self · AI-powered resume-to-website platform

A translator portfolio should help a client understand your language direction, specialty, and translation choices. When client work is confidential, an original sample lets you demonstrate those skills with a complete source text, target text, and short commentary.
Self's portfolio website builder turns your CV into a professional website with your services, experience, and projects already organized. Pedro Fuente's page shows how an English-to-Spanish translator can present a focused practice and give clients a direct contact route.
A finished translator portfolio: Pedro Fuente

Explore Pedro Fuente's website · Download Pedro's CV text (English)
His selected projects cover a contact-import flow and a reporting tutorial. The first includes interface strings, help content, a glossary, and commentary. That gives the visitor something more useful than a list of industries or tools.
Choose a sample you can publish
Start with a small task in the specialty you want to sell: a software setup flow, product description, visitor guide, or short article. Write an original brief or choose a source whose reuse terms cover your intended translation and publication.
Keep the rights check together: use client work with permission covering the exact excerpt and attribution, or publish an original or appropriately licensed sample. The ATA Code of Ethics includes protecting confidential information; its portfolio guidance recommends showing source and target work and obtaining client permission for assignment links.
Set a brief before translating
Language direction
Example
Audience
Example
Task
Example
Tone
Example
Constraint
Example
Deliverables
Example
| Part | Example |
|---|---|
| Language direction | English into Spanish for Spain. |
| Audience | Account administrators importing contacts for the first time. |
| Task | Map CSV columns, choose how to handle duplicates, and import contacts. |
| Tone | Direct instructions and concise interface labels. |
| Constraint | Date examples must keep the order accepted by the importer. |
| Deliverables | 18 interface strings, two help sections, and a 12-term glossary. |
Show the source, translation, and decision
Match each column to a field.
Spanish for Spain
Why this wording
Keep existing contacts.
Spanish for Spain
Why this wording
Use dates such as 2026-06-15.
Spanish for Spain
Why this wording
| English source | Spanish for Spain | Why this wording |
|---|---|---|
| Match each column to a field. | Asigna un campo a cada columna. | A direct action with natural Spanish word order. |
| Keep existing contacts. | Conservar los contactos existentes. | An infinitive suits an option label; instructions use forms such as Asigna. |
| Use dates such as 2026-06-15. | Usa fechas como 2026-06-15. | The functional date order stays the same as the product requirement. |
The glossary links the interface to the help content: campo for field, columna for column, and contacto for contact. Reuse those terms in the instructions so a user can connect the guide with the screen without learning a second set of labels.
Download the complete bilingual sample (TXT). It contains all 18 strings, both help sections, the glossary, and four commentary notes. The sample remains English-to-Spanish so you can compare the actual wording.
Turn the sample into a short project case
Pedro's case can be summarized in one paragraph: I localized a contact-import flow for Spanish-speaking account administrators. I defined terminology, translated 18 strings and two help sections, and documented decisions about action labels, word order, and date formats. The deliverable is a source-to-target comparison with a glossary and contextual notes.
That paragraph names the audience, ownership, scope, and output. Follow it with the sample, then use the reporting tutorial as a second case showing how you handle longer instructions and maintain product terminology.
Brief
What to write
My role
What to write
Sample
What to write
Decisions
What to write
Output
What to write
| Element | What to write |
|---|---|
| Brief | Language direction, audience, medium, and task. |
| My role | Translation, research, revision, or collaboration you owned. |
| Sample | A focused source excerpt beside the finished translation. |
| Decisions | Two or three choices about terminology, tone, or constraints. |
| Output | What you delivered and how the reader can inspect it. |
Make your services easy to understand
Lead with the language direction and target market. English-to-Spanish software localization is a clearer service than multilingual communication solutions. Name the content you handle, such as interface copy, help articles, or product updates, and connect each service to a relevant case.
Place experience, education, and tools after the selected work. A client can then understand the offer before reading the background.
Build the rest of your freelance portfolio around the services and projects a similar client would hire you for.
Create your translator portfolio with Self
Upload your CV, choose Minimalistic, and customize the introduction and project descriptions in Studio. Add the bilingual excerpt to the project description and link a complete sample for readers who want more detail. Keep a professional contact action beside your services.
Explore Pedro Fuente's website · Create my translator portfolio with Minimalistic
Translator portfolio questions
Yes. An original sample can show how you interpret a brief, research terms, and produce a finished translation. Identify it as an independent project and make its intended audience clear.
Start with two or three focused samples that support your main service. For example, pair an interface flow with a help article to show both concise labels and connected instructions.
Explain the choices in each case and list relevant tools in the skills section. A glossary excerpt or contextual note makes terminology work visible; a tool name supplies useful background.