Non-native English speaker: clarity without losing voice

Andrei, a backend engineer with eight years in Bucharest and Berlin, targeted UK remote roles. His technical depth was strong — distributed systems, Kubernetes, Go — but his CV used long passive sentences and mixed UK/US spelling. Some bullets were accurate yet hard to scan in six seconds. Knockout filters still searched for terms like “on-call” and “incident response” that appeared only indirectly.

Challenges

• Grammar correct but wordy — recruiters skimmed past outcomes
• Spelling mixed organise/organize across sections
• Acronyms never expanded on first use
• Fear of “sounding too AI” slowed edits

Approach

Andrei picked UK spelling consistently for UK employers. He used analysis against each job description to find missing terms, adding them only where his incident runbooks and SRE rotation justified them. Suggested rewrites shortened sentences; he rejected any that removed specific stack names. A native-speaking colleague reviewed tone once; software handled the repetitive passes.

Outcome

Screen-to-interview rate improved over a six-week sample of applications — modest but meaningful. He still invested in spoken interview practice; CV work did not fix accent bias or visa sponsorship filters some employers hide in knockout questions. Honesty about limits matters.

See how to write a CV and keyword matching guide. Run your CV through Cvaluate with a UK job description.