You do not need perfect English to work in an international organisation

Many people read a vacancy for an international organisation and stop at the language line.

"Excellent command of English."

"Fluency in English is required."

"Strong written and oral communication skills."

For a non-native speaker, those phrases can sound like a warning: this job is for someone who writes like a native speaker, speaks without an accent, and never hesitates over a preposition.

That is not how most international organisations actually work.

English matters. It can matter a lot. But in many roles, the real requirement is not perfect English. It is professional English: clear enough to be trusted, precise enough to avoid confusion, and flexible enough to work across countries, accents, drafting styles, and institutional habits.

If you are waiting until your English feels flawless before you apply, you may be waiting for a standard that the workplace itself does not meet.

The working language is not a literature exam

International organisations use English because they need a shared working language. That does not make every office a native-speaker environment.

The English used in these organisations is often practical, repetitive, and procedural. People write notes for clearance. They draft minutes. They prepare comments in tracked changes. They send short emails about timelines, missions, budgets, procurement, indicators, risk registers, travel, partner inputs, and review cycles.

Good institutional English is usually less about elegance than about reducing ambiguity. The European Commission's own guide, How to write clearly, exists because official writing can become heavy even inside institutions that employ professional translators, editors, lawyers, and policy staff. Clear writing is a discipline. It is not an automatic gift that native speakers bring into the building.

This is one reason the language requirement in a vacancy should be read carefully. "Fluent English" does not always mean "native-like English". "Excellent English" does not always mean "literary English". In many professional roles, it means that you can do the job without your communication becoming a risk.

Can you understand the instructions? Can you explain the status of your work? Can you write a note that your manager can forward after light editing? Can you join a meeting, ask for clarification, and record the decision correctly? Can you read a policy document, a project agreement, or a results framework without missing the point?

That is a serious standard to meet. It is also very different from perfection.

International English is already multilingual

Spend time in a UN agency, EU body, development bank, climate fund, humanitarian organisation, or international NGO, and you will hear many forms of English.

You may hear French-influenced English: "I will assist to the meeting", "the actual situation" meaning the current situation, or sentence structures that carry more nouns than an English editor would choose.

You may hear Spanish-influenced English: "we need to make a follow-up", "actualize the document", or a rhythm that follows Spanish word order while still being completely understandable.

You may hear Eastern European-influenced English: fewer articles, more direct verb choices, or phrases such as "responsible for coordination of project activities" where a native editor might add "the" or rearrange the sentence.

These are not jokes. They are normal evidence of a multilingual workplace. People carry structures from their first language into English. Native English speakers carry their own habits too: idioms that confuse others, unclear phrasal verbs, regional expressions, and long sentences that sound polished but hide the point.

In practice, good colleagues adapt. They slow down. They repeat. They write the decision in the chat. They ask, "Do you mean X or Y?" They learn which words cause trouble. They avoid slang when the room is international. They do not expect everyone to sound the same.

The shared language is English, but the working culture is multilingual.

Even the vacancies are not perfect

There is another useful reality check: the vacancy texts themselves are not always perfect English.

In vacancy text processed by dotint.careers, you can find small slips like these. The excerpts below are from real vacancies in our database:

• "the working loaction will be in..."
• "learning & developement (LnD) evaluation standards"
• "MAIN RESPOSIBILITIES"
• "Advices on the design and conduct..."

None of these examples makes the vacancy impossible to understand. None of them means the organisation is unserious. They show something more ordinary: international recruitment text is written, copied, formatted, translated, edited, and re-edited by humans from all over the world, in their own imperfect English.

That matters for candidates because many people judge their own English much more harshly than the system judges itself.

If a vacancy can contain "loaction" and still be a real vacancy, your application does not need to sound like an Oxford essay. It needs to be accurate, relevant, and readable.

What your English really needs to do

For many international roles, English is tested through ordinary professional tasks.

You need to read the vacancy correctly. This sounds basic, but it is one of the first filters. Many weak applications fail because the candidate has not understood the role. They describe broad interest in the organisation instead of the specific work: grants, procurement, safeguards, social protection, data analysis, monitoring and evaluation, humanitarian access, audit, legal drafting, partnerships, or project finance.

You need to write a focused application. The English does not need to be beautiful. It does need to connect your experience to the vacancy. Short, concrete sentences often work better than ambitious language. "I managed a EUR 2.4 million donor-funded project with quarterly reporting to three partners" is better than "I possess a profound passion for impactful international cooperation."

You need to communicate in a team. That means emails, comments, meeting notes, status updates, and questions. A colleague should be able to understand what you did, what you need, what is blocked, and what decision is required.

You need to handle feedback. International writing is collaborative. A document may pass through technical reviewers, managers, legal officers, communications staff, donors, government counterparts, and translators. Being edited is not a humiliation. It is part of the work.

You need to avoid dangerous ambiguity. If you are writing about money, deadlines, eligibility, legal commitments, security, medical instructions, procurement, or political sensitivities, clarity is not optional. In those contexts, "almost clear" may not be enough. But the solution is usually disciplined drafting, checking, and asking for confirmation, not waiting to become native.

When English really is the job

There are roles where the bar is much higher.

If the job is speechwriting, editing, public information, external communications, legal drafting, interpretation, translation, publishing, media relations, senior advocacy, or high-level negotiation, English may be part of the product itself. A communications officer drafting public statements in English will be judged differently from a procurement specialist writing internal notes. A legal officer drafting treaty language will face a different standard from a programme officer coordinating field inputs.

Some senior roles also require more polished English because the person represents the organisation externally. The issue is not accent. It is the ability to speak and write with precision under pressure, in rooms where words carry institutional weight.

So the argument is not "English does not matter". It does.

The argument is: do not apply the highest possible English standard to every role. Read the role. Ask what communication actually does in that job.

Do not undersell yourself in language fields

Many candidates are too modest in their P11, CV, or profile language fields.

If your English is genuinely basic, do not pretend otherwise. A role that requires fluent English will probably not be a good match yet. You may fail screening, assessment, interview, or the job itself.

But if you have studied in English, worked in English, written reports in English, joined meetings in English, handled clients or partners in English, or used English every week for years, be careful before you label yourself "basic" or "intermediate" out of insecurity.

Different organisations use different labels: working knowledge, good command, advanced, fluent, excellent, mother tongue. They do not always map cleanly to CEFR levels. But your self-description should reflect what you can actually do.

A practical way to think about it:

• If you can only handle simple everyday exchanges, do not call it fluent.
• If you can work professionally in English but make mistakes, do not call it basic.
• If you can write and speak reliably in your field, say so plainly.
• If writing is weaker than speaking, improve the writing rather than hiding the whole language.
• If you need proofreading for formal documents, that is normal in many offices. Mention your working level honestly and keep improving.

This is also where tools like dotint.careers can help in a modest way. Language requirements are real requirements, and a profile that says "basic English" should not be treated as equivalent to a vacancy asking for fluent English. But matching should not turn "fluent" into a fantasy of native perfection either. The useful question is whether your declared language level matches the work the vacancy describes.

Your accent is not the problem

A strong accent can make communication harder if people cannot understand you. That is worth working on. Intelligibility matters.

But an accent itself is not a defect. International organisations are full of accents. A French accent, Nigerian accent, Indian accent, Brazilian accent, Polish accent, Egyptian accent, Japanese accent, Ukrainian accent, or German accent does not make a person less professional.

What helps is not trying to erase your voice. What helps is learning to speak at a usable pace, pronounce key technical terms clearly, pause at the right places, and check understanding when the topic is important.

The same is true in writing. You do not need to develop a native literary style. You need control over the things that affect trust: structure, verbs, dates, numbers, roles, evidence, and decisions.

Apply before perfection

The international job market is already difficult enough. Do not add a private rule that says you may only apply once your English is flawless.

Improve your English. Read vacancy notices closely. Build a bank of phrases for your field. Ask someone to review your CV. Use shorter sentences. Remove vague claims. Practise explaining your work out loud. Learn the words that matter in your sector: procurement, safeguards, disbursement, evaluation, adaptation, protection, compliance, audit, stakeholder engagement, results framework, or whatever your field requires.

But do not confuse improvement with permission.

You do not need perfect English to work in an international organisation. You need enough English to do the work, keep improving, and be understood when it matters.

That is still a high bar. Are you there or not yet?