The team
Our Technical Translators, Named and Documented
Techniwords publishes the technical translators who open your files, with their degrees, their years on plant floors and in design offices, and the certifications you can verify. You will know who translated your document and who revised it before delivery.
Eight published profiles: degree, industry background, years, sectors, document specialties. Read them before you send a file.
Your project manager filters by industry and document type first, then by language pair. Never the other way round.
The translator drafts, a second specialist revises against the source. That pairing is not an upgrade you pay extra for.
Why We Publish Our Technical Translators
Ask most vendors who will handle your service manual and the answer comes back as a category: a qualified native linguist, a subject-matter expert, a resource from our vetted pool. Nobody in that sentence has a degree you can read or a career you can weigh. On a product brochure the vagueness costs little. On a procedure that tells a technician how to isolate a 480-volt drive before opening a cabinet, it removes your only chance to judge the supplier before the work happens.
People who buy technical translation are engineers, documentation managers, and quality leads. They assess a supplier the way they assess a component, by reading the datasheet. So we wrote the datasheets. Each profile on this page states what the person studied, what they built or maintained before they became a linguist, which certifications they hold, and which document families cross their desk week after week.
Naming people also changes how the work gets done. A translator whose public page claims mastery of lockout procedures or PLC screens raises a query rather than inventing a term. Accountability travels with a name.
The Bar Every Certified Technical Translator Clears Here
Whether a linguist appears on this page or works in our wider network, four requirements apply before a first paid assignment:
- Technical formation. An engineering degree, or documented years in a plant, a lab, a design office, or a patent practice. Fluency in two languages qualifies nobody for this work on its own.
- Native target language. Translators write into their mother tongue, in the regional variant your readers actually use, whether that is Mexican Spanish for a Gulf Coast crew or Brazilian Portuguese for a distributor in São Paulo.
- Credentials on record. ATA certification where the association examines the pair and direction, plus the documented competence records our ISO 17100-compliant quality workflow requires for everyone else.
- A narrow, active specialization. Each translator stays inside two or three industries, so their vocabulary moves when those industries revise their standards.
Everyone signs a nondisclosure agreement covering your files, your product names, and whatever they learn about your operation along the way.
The Eight Specialists Behind Our Core Language Pairs
These linguists carry most of the volume in the pairs our US clients request most often. Each profile goes into the documents they handle, how they build terminology, and the kind of project that lands on their desk.
Miguel Ferrer
English → Spanish (US & Latin American)
BS Mechanical Engineering. ATA-certified, English into Spanish. 16 years. Industrial machinery, oil & gas, EHS: user manuals, SDS, lockout/tagout procedures, safety signage.
Anke Hoffmann
English ↔ German
Dipl.-Ing. Electrical Engineering, RWTH Aachen. 18 years. Automotive, industrial automation, machine tools: engineering drawings, PLC/HMI strings, service manuals, VDA and IATF documentation.
Wei Zhang
English ↔ Chinese (Simplified)
MS Chemical Engineering, Tianjin University. 14 years. Chemical processing, plant engineering, electronics manufacturing: SDS under GHS and GB 30000, P&IDs, commissioning dossiers, factory SOPs.
Yuko Tanaka
English ↔ Japanese
BS Electrical Engineering, Tohoku University. 15 years. Electronics, semiconductors, patents: patent specifications, technical datasheets, test reports, JIS-referenced documentation.
Claire Moreau
English ↔ French (France & Canadian)
MEng Aeronautical Engineering. 12 years. Aerospace, defense, rail: AMM and CMM excerpts, AS9100 quality documentation, CDRLs, Canadian bilingual labeling compliance.
Ji-hoon Park
English ↔ Korean
BS Electronic Engineering, KAIST. 13 years. Semiconductors, batteries and ESS, displays: cleanroom SOPs, equipment manuals, IQ/OQ/PQ protocols, KS-standard references.
Ana Beatriz Souza
English ↔ Portuguese (Brazilian)
BS Chemical Engineering, UFRJ. 15 years. Oil & gas, mining, pulp & paper: drilling programs, HSE plans, NR-normative compliance including NR-12 and NR-33, equipment datasheets.
Marco Rossi
English ↔ Italian
MS Mechanical Engineering, Politecnico di Milano. 17 years. Packaging machinery, food processing equipment, machine tools: operator manuals, CE Machinery Directive files, spare parts catalogs, HMI strings.
How a Project Finds Its Translator
Discipline comes before language. A Spanish linguist who has never read a piping and instrumentation diagram has no business translating one, however graceful the prose. When your files arrive, the project manager identifies the industry, the document family, and the standards in play, then shortlists the linguists who have already worked that ground. The language pair narrows the shortlist afterward, along with the regional variant your readers need.
Volume and deadline settle the rest. A single 20,000-word maintenance manual usually goes to one translator so the voice stays even from chapter to chapter. A four-language launch on a fixed date runs as parallel teams sharing one termbase, an arrangement laid out step by step on our project workflow page.
Want to know who would get your job? Say so when you send documents for pricing. We will name the translator and the reviser we would assign, and summarize their background, before you commit to anything.
Nobody Delivers Alone
A second qualified linguist compares every translation against the source, segment by segment. The reviser holds the same credentials as the translator and usually works the same industry, so the check covers meaning and terminology rather than commas alone. The eight people above revise for one another constantly, which is part of why their glossaries agree across projects that share equipment.
Revisers see what authors cannot. After six hours inside a document, a translator reads what they meant to write. A colleague opening the file cold reads what is on the page, catches the missing negation in a warning, and questions the two spellings a component name picked up between chapters.
Past the Eight: the Wider Network
Eight linguists cannot cover a world of engineering, and we say so plainly. Around this core sits a long-standing network of certified specialists working in more than 60 languages, recruited against the same four requirements and held to the same two-linguist rule. Several of the profiled eight came through that network before they took on core-pair volume.
If your pair is unusual, or your discipline sits outside the sectors listed above, ask. We will either name the person who would take it or tell you we are the wrong supplier. Send your documents and you will have an itemized quote, plus the proposed team, within one business hour.
Questions About Our Translators
Who will actually translate my document?
A named specialist chosen for your industry and document type, plus a named reviser. In our core pairs that is usually one of the eight linguists profiled on this page. Ask at quoting stage and we will identify both people, with their backgrounds, so you can approve the pairing before work starts.
Are your technical translators certified?
Where certification exists for the pair and direction, yes. Miguel Ferrer holds ATA certification for English into Spanish, for example. The American Translators Association does not examine every combination, so for the remaining pairs we rely on engineering degrees, verified industry experience, and the documented competence records our ISO 17100-compliant process requires.
Do you use employees or independent translators?
Both. A small core team handles project management, terminology, and quality control, and works with independent specialists who have partnered with us for years. Employment status changes nothing about the vetting, the nondisclosure agreement, or the requirement that a second linguist revise the work.
Can I talk to the translator directly?
On larger or ongoing programs, yes. We set up a call between your engineers and the assigned linguist at kickoff, which usually settles more terminology in thirty minutes than a week of written queries. On shorter jobs the project manager relays questions in batches, and the query sheet always comes back with the delivery.
How does someone become a Techniwords translator?
Send credentials and a sector focus to info@techniwords.us. We look at the technical background first, then set a paid test in the candidate's declared specialty, revised by the linguist who already covers that field. New arrivals work alongside a senior reviser on their first projects before taking solo assignments. We recruit narrowly and rarely, so expect a slow answer rather than a fast one.