# A translated job title can change the whole assessment | OnPebble

Canonical: https://www.onpebble.ai/blog/multilingual-resume-review/

A worked translation example showing how to preserve original terms, check responsibility and avoid turning a fluent translation into an unsupported hiring claim.

By Pebble editorial. Updated 2026-10-05.

Product interfaces and candidate examples are illustrative. Pebble recommends; your team makes hiring decisions.

# A translated job title can change the whole assessment

By Pebble editorial Updated October 5, 2026  4 min read

## Does “manager” mean somebody managed people?

A procurement coordinator’s resume arrives in French. A working English translation turns a title containing “responsable” into “manager”. The reviewer starts looking for people-management experience.

The title alone does not establish that responsibility. In this invented example, the passage describes supplier follow-up. Check whether the person supervised people, owned a process or coordinated an activity. This is not a universal translation rule for the French term.

Scroll sideways to read the full table.

Invented resume passage and working translations

| Version | Text |
| --- | --- |
| French source | Responsable du suivi fournisseurs. Je suivais les livraisons des fournisseurs et signalais les retards au responsable des achats. |
| Working English translation to review | Supplier follow-up manager. I tracked supplier deliveries and reported delays to the purchasing manager. |
| Context-preserving English wording | Responsible for supplier follow-up. I tracked supplier deliveries and reported delays to the person responsible for purchasing. |
| Corrected assessment note | The passage describes tracking deliveries and reporting delays. It does not state whether the applicant supervised people. Ask who made supplier decisions and whether anyone reported to them. |

Both English versions are working translations for this example. “Responsible for” keeps the title open where “manager” may suggest a formal management role. The surrounding sentence supports tracking and reporting; it does not settle the applicant’s authority. A bilingual review and a focused question can clarify that distinction.

Keep the original title beside the translation. Ask who made supplier decisions and whether anybody reported to the applicant. That answers the role question more directly than debating which English title sounds most senior.

The original term responsable and working translation manager lead to a question about supervision, process ownership and coordination.
An ambiguous title in the invented example; the surrounding responsibilities need checking.

## Keep the original, extracted text and translation distinct

First check that extraction read the document correctly. Then check the translation. Only then assess the claim against the opening’s requirements. A table or column error can attach a sentence to the wrong role before translation even starts.

Scroll sideways to read the full table.

Checking the responsibility claim

| Layer | What to inspect |
| --- | --- |
| Original passage | The title and the surrounding responsibility description |
| Extracted text | Whether the right sentences remain connected to the right role |
| Working translation | Whether “manager” added an unsupported responsibility |
| Review note | Supplier coordination described; people-management responsibility needs clarification |

A fluent translation can still lose a negative, change a date range or overstate ownership. Read the words that would change the next decision. Keep uncertainty in the note until somebody can resolve it.

## Preserve the terms that carry the meaning

Keep employer, product and qualification names traceable to the original. Show a translated label alongside the source term when it helps. Do not silently convert a qualification into a local equivalent; verify an equivalence through an appropriate authoritative process.

Google’s glossary documentation describes controls for domain-specific terms and named entities. Microsoft documents ways to exclude content from translation, including HTML-only tagging methods. These are available translation controls, not guarantees of resume accuracy or claims about Pebble features.[[google-glossary]](https://www.onpebble.ai/blog/multilingual-resume-review/#source-google-glossary)[[microsoft-preserve]](https://www.onpebble.ai/blog/multilingual-resume-review/#source-microsoft-preserve)

For recurring terms in your roles, keep a small reviewed record: source wording, interpretation, context, reviewer and date. A glossary can make terminology consistent. It cannot tell you whether this particular candidate owned the work.

## Ask for help on the sentence that matters

When a central passage is ambiguous and the team cannot verify it, use a qualified bilingual reviewer or translation professional. Supply the source and job context through an approved data-sharing route. Ask what is ambiguous, not just for a smoother English sentence.

Another machine translation or a back-translation can expose a disagreement. Agreement between outputs is not independent proof that the original was understood. If the team still cannot resolve the passage, choose a focused clarification or appropriate human review.

Do not infer ability from nationality, a name or the language of the application. Nor should awkward English in a working translation become evidence that the person cannot coordinate suppliers. That is the translation service’s output, not an observed work sample.

## Return to the work the opening needs

For this coordinator opening, the questions concern tracking dependencies and handling changed supplier requirements. Keep those criteria steady while clarifying the wording. If language proficiency is itself needed, define it separately and assess it through a job-related method.

OPM’s structured-interview guidance describes common questions and rating standards. Use consistent core work questions when clarifying translated claims, with appropriate interpretation or other process support.[[opm-interviews]](https://www.onpebble.ai/blog/multilingual-resume-review/#source-opm-interviews)

There is no basis here to assume equal AI screening quality across languages. Check the actual language pairs, documents and review expertise in your process. The corrected note should preserve what the passage supports and name the question the translation could not settle.

## Sources and further reading

- [Google Cloud Translation: Creating and Using Glossaries](https://docs.cloud.google.com/translate/docs/advanced/glossary)Reviewed October 4, 2026

- [Microsoft Azure Translator: Prevent Content Translation](https://learn.microsoft.com/en-us/azure/ai-services/translator/text-translation/how-to/prevent-translation)Reviewed October 4, 2026

- [OPM: Structured Interviews](https://www.opm.gov/policy-data-oversight/assessment-and-selection/structured-interviews/)Reviewed October 4, 2026

## Keep reading

[All articles](https://www.onpebble.ai/blog/)

[3 min read

### “Human reviewed” should mean somebody checked the application

Read article](https://www.onpebble.ai/blog/human-review-ai-screening/)[3 min read

### The screening task needs the project example. Does it need the whole file?

Read article](https://www.onpebble.ai/blog/candidate-data-ai-hiring/)[3 min read

### Try AI screening on one opening before you roll it out

Read article](https://www.onpebble.ai/blog/ai-screening-pilot/)

## Review applications with Pebble Screen.

See how opening requirements and AI resume assessments come together for human review.

[Explore Screen](https://www.onpebble.ai/screen/)