THE RADARYNO NOTEBOOK

Write a Resume in the Job Description Language

A resume should use the language of the offer while staying faithful to the candidate’s career notes. This guide covers a complete workflow: identify the target language, select relevant evidence, handle missing information, draft the document, and check the final files. It also separates language adaptation from country-specific compliance. The Radaryno Resume Kit can create an HTML and PDF resume, plus an optional cover letter, in the offer language while keeping files and generated documents on the buyer’s computer.

01

Identify the offer language and audience

Read the complete job description before translating or rewriting any resume section. Look for the language used in the responsibilities, requirements, application instructions, and employer communications. If the text is mixed, identify which language carries the main instructions and whether the employer requests documents in a particular language. Note the intended audience, such as a recruiter, hiring manager, or local office, but do not infer country-specific rules from language alone. Record the target language as a drafting decision. This keeps the workflow focused on communicating the existing career record clearly rather than prematurely changing titles, technical terms, or compliance details.

02

Prepare the verified source notes

Gather the buyer’s career notes and separate facts from interpretation before selecting content. Facts may include employers, dates, responsibilities, tools, projects, education, and documented outcomes. Interpretation includes assumptions about what an employer might value or how a phrase should sound in another language. Keep those categories distinct. Select only evidence connected to the offer’s duties and requirements, while retaining enough context to avoid overstating ownership or scope. If a note is incomplete, flag it instead of silently repairing it. This source review gives the language adaptation a stable factual base and makes later comparisons easier.

03

Map meaning before drafting sentences

Build a short meaning map between the offer and the selected career evidence. For each important responsibility, identify the closest verified experience and state the limit of the match. For instance, experience assisting with onboarding should not become experience leading onboarding unless the notes support that claim. Keep the mapping at the level of meaning rather than copying every phrase mechanically. This is also the point to identify gaps, such as an unstated proficiency level or an unfamiliar requirement. The workflow should report those gaps and ask for clarification when needed, not fill them with likely-sounding language.

04

Draft the resume in the target language

Write the resume in the offer language using the selected facts and the meaning map. Preserve names, dates, employers, scope, and evidence unless the buyer confirms a correction. Translate for natural reading, but avoid adding claims merely because they sound customary in the target language. Keep the document single-column and easy to read, with a clear relationship between the offer and the selected experience. If an optional cover letter is prepared, apply the same factual boundary. Do not invent motivation, employer knowledge, language ability, or achievements to make the prose more persuasive.

05

Review gaps and request clarification

Compare the draft with the offer again after writing it. Check whether each required qualification is supported, unsupported, or unclear. A supported item can be described using the verified notes. An unsupported item should not be presented as completed. An unclear item may need a question for the buyer, such as the exact proficiency level, responsibility scope, or approved wording for a title. Keep the gap report separate from the resume so unresolved questions do not appear as facts. This review is about completeness and honesty, not about forcing a match where the evidence does not support one.

06

Check the generated files and record the application

Review the completed HTML and PDF from the reader’s perspective. Confirm that the target language is consistent, the text matches the verified source notes, and the layout remains single-column and ATS-friendly. Check headings, dates, repeated terminology, page breaks, and selectable text. Review the optional cover letter separately for unsupported claims or language drift. Then record the application details and document version in the local application tracker. The kit does not submit applications, search for jobs, or contact employers, so submission and communication remain the buyer’s responsibility.

Choices to make before preparing an offer-language resume
DecisionUse this approachAvoid this approachReason
Target languageFollow the language used by the offer and its instructionsAssume the employer’s country determines the languageThe posting may request a different language from the location
Source evidenceUse verified career notes and relevant experienceAdd plausible details that are not in the notesLanguage adaptation must not become factual invention
Unclear requirementReport the gap or ask for clarificationTranslate uncertainty into confident wordingReaders need to distinguish evidence from assumptions
Document outputReview both HTML and PDF textTrust visual appearance aloneText selection and wording should remain accurate
Local complianceCheck country-specific expectations separatelyTreat translation as legal or compliance adviceLanguage and local application conventions are different tasks

A fictional worked scenario for checking the workflow

  1. A fictional candidate has career notes written in English and finds an offer written in French. The offer requests customer onboarding, reporting, and collaboration with regional teams. The candidate identifies French as the target language, marks the relevant notes, and leaves unrelated technical work out of the first draft.

  2. The candidate compares the selected notes with the offer without changing the underlying facts. A phrase about supporting customer onboarding can be expressed naturally in French, but the candidate does not claim ownership of the entire onboarding process. A missing language proficiency level is recorded as an unresolved gap rather than guessed.

  3. The draft is reviewed for meaning in both languages. Dates, employers, responsibilities, and evidence remain consistent with the source notes. The candidate checks the HTML and PDF versions, confirms that the text can be selected, and removes any sentence that sounds stronger than the documented experience.

  4. The final review separates language quality from country-specific expectations. The candidate may seek local guidance for conventions not covered by translation, while keeping the resume grounded in the same verified career record. The application details and document versions are then recorded locally in the application tracker.

Put it into words

Before and after

Fictional examples: not real people.

Before

English source note: Supported customer onboarding by preparing account information and answering setup questions.

After

Target-language draft: Translate the note naturally while preserving the supporting role; do not change it to leading or owning onboarding.

Before

Offer requests a language proficiency level not stated in the career notes.

After

Record the missing level and ask for clarification instead of assigning a fluent, professional, or native label.

Before

Source notes mention collaboration with regional teams but do not identify the regions.

After

Keep the collaboration claim general unless the buyer confirms the regions or provides additional evidence.

A few details

Frequently asked questions

Does translating a resume change the underlying career facts?

It should not. Translation may change sentence structure, word order, and idiomatic phrasing, but employers, dates, responsibilities, scope, and evidence should remain accurate. If a natural translation appears to strengthen a claim, compare it with the source notes and choose wording that preserves the original meaning. Ask the buyer when the intended meaning is unclear.

What should I do when the offer language is unclear?

Review the main description, application instructions, portal fields, and any stated document requirements. If those sources conflict, record the uncertainty and ask the employer or buyer for clarification. Do not choose a language solely from the employer’s location or name. A clear drafting decision at the start prevents inconsistent sections later.

Can the workflow create a resume in a language different from my career notes?

Yes. The Radaryno Resume Kit can write an HTML and PDF resume in the offer language from the buyer’s career notes. The notes and generated documents stay on the buyer’s computer. Local storage does not mean that AI inference is offline, however; access to an AI provider is separate from the one-time kit purchase.

How should missing language proficiency information be handled?

Treat it as a gap. Do not infer a proficiency level from the fact that the candidate is applying to an offer written in that language. Ask for the level or use only wording the buyer has confirmed. If the information remains unavailable, leave the claim out rather than presenting an unsupported qualification.

Does language adaptation cover country-specific resume rules?

No. Adapting wording to the offer language is separate from checking country-specific application expectations. Review local guidance independently when the destination has requirements about documents, personal information, dates, or professional conventions. The language workflow can preserve facts and produce readable files, but it should not be treated as legal or compliance advice.

Where are applications and generated documents kept?

Files and generated documents stay on the buyer’s computer, and the kit includes a local application tracker for recording application details and document versions. The kit does not submit applications, search for jobs, or contact employers. A buyer still needs to manage submission and employer communication separately. Local file storage also does not imply offline AI inference.

RADARYNO RESUME KIT

Your experience, selected for each offer.

A downloadable kit for Claude Code or Codex. Gaps stay visible.

See the kit