Collect the source evidence
Gather the current resume, career notes, project descriptions, and the offer language before changing any technical wording. Mark every tool, platform, programming language, database, methodology, document type, and process that carries meaning. Include the sentence around each term, because context often shows whether a word names a product, activity, skill, or outcome. Treat the source evidence as the boundary of what the translated resume may claim. If a term appears only in a draft and not in the supporting notes, flag it for review instead of treating it as established fact.
Build a terminology ledger
Create a simple ledger with one row for each important technical term. Record the source term, its category, the intended meaning, a proposed target-language equivalent, and the evidence that supports it. Useful categories include product name, programming language, platform, process, document, method, and broad skill. This structure prevents inconsistent choices across the profile, experience entries, skills section, and optional cover letter. It also makes deliberate preservation acceptable: a product name may remain unchanged while the surrounding verb and explanation are translated.
Decide what to preserve
Keep product names, programming languages, repository services, and other proper technical names in their established form unless the source itself uses a recognized localized name. Translate the surrounding explanation when a clear equivalent exists in the target language. For concepts with several possible equivalents, choose the wording that matches the sentence and the candidate’s actual responsibility. Avoid expanding an abbreviation unless the source supports the expanded meaning. Do not turn a narrow technical activity into a broad capability, and do not turn exposure or collaboration into ownership.
Check terms against the offer
Read the offer language beside the terminology ledger, but use the offer to guide relevance rather than to add unsupported experience. When the offer uses a different name for a related concept, compare definitions and surrounding duties before selecting wording. A match is valid only when the candidate’s source evidence supports the same technical meaning. If the relationship is partial, use a narrower phrase or leave the term out. This review should also catch false equivalences, such as treating monitoring as observability or a deployment script as a complete delivery platform.
Review the generated documents
After the language version is drafted, inspect the full HTML and PDF resume rather than reviewing the ledger alone. Check that a preserved product name has not been altered by translation, that technical terms are consistent across sections, and that sentence structure does not change the implied responsibility. Review any optional cover letter separately so it does not introduce a technical claim absent from the resume or career notes. The Radaryno Resume Kit can write the resume and optional cover letter in the offer language from the buyer’s career notes, while reporting gaps and asking rather than inventing. Files and generated documents stay on the buyer computer; AI provider access remains separate from that local storage.
| Source term | Decision | Reason | Illustrative target wording |
|---|---|---|---|
| PostgreSQL replication | Preserve the product name and concept | The product name identifies a specific database technology | PostgreSQL replication |
| CI pipeline | Translate the concept only when the target language has a clear equivalent | The term describes a process rather than a product | Pipeline d’intégration continue |
| Kubernetes | Preserve the product name | The name identifies a specific platform | Kubernetes |
| Incident response runbook | Check the surrounding sentence | The phrase may describe documentation, procedure, or ownership | Incident response runbook |
Worked terminology review
fictional:true. A candidate’s source notes say, “Built a CI pipeline with GitHub Actions to run tests and publish container images.” The first pass records GitHub Actions as a product name, CI pipeline as a process, and container images as a technical concept. No term is changed simply because another language has a more familiar general expression.
fictional:true. The target wording keeps GitHub Actions unchanged, uses the established local equivalent for continuous integration, and preserves container images rather than replacing it with software packages. The sentence is then compared with the source note to confirm that building the pipeline, running tests, and publishing images are all still represented.
fictional:true. A final reviewer checks whether the translated wording suggests ownership that the source does not support. If the notes say the candidate configured an existing pipeline, the resume should not say the candidate designed the organisation’s entire delivery system. Terminology accuracy includes responsibility and scope, not only vocabulary.