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.
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.
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.
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.
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.
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.
| Decision | Use this approach | Avoid this approach | Reason |
|---|---|---|---|
| Target language | Follow the language used by the offer and its instructions | Assume the employer’s country determines the language | The posting may request a different language from the location |
| Source evidence | Use verified career notes and relevant experience | Add plausible details that are not in the notes | Language adaptation must not become factual invention |
| Unclear requirement | Report the gap or ask for clarification | Translate uncertainty into confident wording | Readers need to distinguish evidence from assumptions |
| Document output | Review both HTML and PDF text | Trust visual appearance alone | Text selection and wording should remain accurate |
| Local compliance | Check country-specific expectations separately | Treat translation as legal or compliance advice | Language and local application conventions are different tasks |
A fictional worked scenario for checking the workflow
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.
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.
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.
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.