Every company runs on a private language. After a few years inside one, you stop hearing it: the project is "Atlas", the reporting tool is "the Hub", your team is "GTO-3" and your title reads like a riddle. Then you write your CV in that language, send it to a stranger, and wonder why nobody calls.
Your reader has never been inside your building
The person screening your CV has never sat in your stand-ups. They do not know that "Atlas" was the move of 40 warehouses onto a new stock system, or that "the Hub" is a spreadsheet with three macros. They may not even work in your sector. An agency recruiter can screen a logistics role in the morning and a banking role after lunch.
So every word on the page has to work for a reader with zero context. Internal language fails that reader twice. First, it hides the achievement: "delivered Atlas Phase 2" says nothing about scale, outcome or skill. Second, it makes you look like someone who has never noticed the world beyond their employer, which is the last impression you want to leave.
One clarification. Explaining what your employer does, in a line under the company name, is a separate job with its own guide. This article is about the words inside your bullet points.
The words that never leave the office
Most internal language falls into four families, and each needs a slightly different fix.
Project codenames
"Led Project Phoenix." "Core member of Falcon." Codenames are fun inside a company and empty outside it. Replace the name with what the project actually was.
- Before: "Delivered Phoenix on time and under budget."
- After: "Moved 1,200 customer accounts from an old billing platform to a new subscription system, on time and 8% under budget."
If the codename was public (a product launch the press covered, say), you can keep it in brackets after the description. Otherwise, drop it.
Tool nicknames and homegrown systems
Teams rename tools constantly. Salesforce becomes "the Pipe", an internal dashboard becomes "Lighthouse", a macro becomes "the Robot". On a CV, name the real product where there is one and describe the function where there is not.
- Before: "Built reports in Lighthouse."
- After: "Built weekly sales reports in an internal dashboard (built on Power BI) used by 30 regional managers."
A homegrown tool is still real experience. Give it a category ("an in-house ticketing system") so the reader can place it.
Team codes and org-chart shorthand
"Analyst, GTO-3, EMEA OPS." The reader needs the function and the scope, not the box on the chart.
- Before: "Analyst, GTO-3."
- After: "Analyst in the global trade operations team (customs and shipping compliance for 14 countries)."
Watch for acronyms that exist elsewhere with a different meaning. Inside your firm "CS" might be credit services. To most readers it is customer success, and to a graduate recruiter it is computer science.
In-house titles
Some titles exist in exactly one company: "Partner Enablement Lead", "Customer Happiness Hero", "Level 4 Engineer". You cannot change the title your employer gave you, and you should not invent a better one. You can add a plain-language gloss.
- "Partner Enablement Lead (sales training for resellers)"
- "Customer Happiness Hero (second-line customer support)"
The official title stays, so a reference check matches. The bracket does the translating.
The stranger test
This is the most useful check I know. Take one bullet from your CV, send it to a friend who works in a completely different field, and ask them to explain back what you did. Not whether it sounds impressive. What you actually did.
If they cannot, the line fails. The usual results:
- They stop on a word and ask what it means. That word is jargon.
- They describe the activity but not the result. You have buried the outcome under process language.
- They guess something else entirely. Your shorthand means a different thing outside, which happens more often than people expect.
Do it for your summary and top five bullets, and you will start to hear your own jargon in the rest.
The solo version: read the line aloud and imagine a curious teenager asking "meaning what?" after every noun. If you cannot answer in plain words, rewrite it.
Industry acronyms: keep them, but write both forms once
Not every acronym is a problem. Some are the standard vocabulary of your field, and stripping them out makes you look less qualified, not more. An accountant who never writes IFRS, a health and safety officer who avoids COSHH, a developer who types "application programming interface" in every line: all of them sound slightly off to a specialist.
The line to draw is between industry acronyms, shared by every employer in your sector, and internal acronyms, known only inside your company. Keep the first group. Translate the second.
For industry acronyms, use one rule: write the full term and the acronym together the first time, then use the short form after that.
- "Prepared group accounts under International Financial Reporting Standards (IFRS)..." and later just "IFRS".
- "Led the move to a new enterprise resource planning (ERP) system..." and later just "ERP".
This does two jobs at once. A reader from a neighbouring field gets the meaning on first contact. And an applicant tracking system, or a recruiter typing a search, finds you whether they search for the long form or the short one. Building a complete keyword list for a specific job ad is a bigger subject, covered in our guides to ATS keyword optimisation and skill synonyms. The point here is narrower: never leave a meaningful acronym in only one form.
So should you spell out abbreviations on your resume everywhere? No. Once per document is enough. And a handful of acronyms are so universal that spelling them out looks odd: CEO, HR, KPI, PDF. If a recruiter from outside your sector would know it without thinking, leave it alone.
Switching sectors: when your vocabulary gives you away
Jargon costs the most when you change industries. Inside your sector, a little shorthand shows you belong. Outside it, the same shorthand tells the hiring manager you are a visitor who has not learned the local language yet.
Some lines that need translating on the way out:
- Retail to e-commerce operations: "Managed shrink and OSA across 12 stores" becomes "Cut stock loss and kept on-shelf availability above target across 12 stores."
- Teaching to corporate learning: "Differentiated instruction for a mixed-ability KS3 cohort" becomes "Built training for groups with very different starting levels, around 90 learners a year."
- Hospitality to B2B customer success: "Handled VIP arrivals and comps" becomes "Looked after high-value guests and decided on goodwill gestures within a fixed budget."
Notice the second half of the trick. The "after" versions borrow the nouns the new sector uses. To find them, read ten job ads in your target field and write down the words that keep coming back. The full CV for switching industries has its own guide, and so does translating military experience for a civilian employer. The principle underneath is the same: write in the reader's vocabulary, not your old employer's.
A ten-minute edit pass before you send
Once your CV is drafted, run this pass.
- Highlight every capitalised word and every acronym. Codenames, product names, team codes, abbreviations. This is your suspect list.
- Sort each one. Industry standard (keep, spell out once), public product name (keep), internal (translate or delete).
- Rewrite the internal items as what you did, at what scale, with what result.
- Check the first use of each industry acronym carries the full form beside it.
- Run the stranger test on your summary and top five bullets.
- Reread the job ad and compare your words with the ones the employer uses.
If you build your CV from your LinkedIn profile, with a tool like Postulit for example, run the same pass on the profile. Internal codenames tend to creep into LinkedIn job descriptions first and get copied straight across.
The reader of your CV has never worked where you work. Every word that only makes sense inside your company is a word that costs you.
Today, pick your three most important bullets, hand them to someone outside your field, and rewrite every line they cannot explain back to you. It will do more than another round of formatting.