Quick Answer
An international CV must answer four questions in the first ten seconds: how many years of experience do you have, what industries have you worked in, what skills you bring, and what makes you different from every other candidate with the same job title. Structure it as a results-focused summary, reverse-chronological experience with company context, and quantified bullet points — then adapt length and personal details to the target market (US, UK, or EU).
Free resource
Skip the formatting headaches. Use our single-column, ATS-compatible CV template — pre-structured with the section order covered in this guide.
Open the Overleaf CV Template ↗The 4 questions your CV must answer in 10 seconds
Before a recruiter reads a single bullet point, your CV should already answer four questions — and if it cannot, it is working against you. After reviewing dozens of CVs from mid-to-senior tech professionals, the same four gaps appear again and again: missing years of experience, no industry context, an unclear skill set, and no USP (unique selling point — what makes you different from every other candidate with the same job title).
The 4 questions every international CV must answer
- How many years of experience do you have? State it explicitly — '7 years', '12+ years', not 'extensive experience'.
- What industries have you worked in? Fintech, healthcare, SaaS, e-commerce — a recruiter scanning 200 CVs needs this in three words.
- What skills do you bring? Your core stack and specialisation, not a 40-item list of every tool you have ever touched.
- What is your USP? The one thing that separates you from every other candidate with the same job title and years of experience.
Watch Out
If a recruiter cannot answer all four questions after reading your summary section, the rest of your CV is unlikely to recover the application. The summary is not optional — it is the argument; everything below it is the evidence.
❌ Fails all four questions
"Hi! My name is [Candidate], and I've been building my career in development for over 7 years. I create responsive and intuitive interfaces, paying special attention to cross-browser compatibility. I'm committed to continuously learning and improving my skills, and I know how to build positive cross-functional communication." This is a real summary from a real CV. The candidate has 7 years of experience and genuine technical range — but the CV doesn't show it. There is a greeting instead of a headline, no industry context, no company scale, no measurable outcomes, and no USP.
✅ Answers all four questions
"Senior engineer with 20+ years building high-volume, highly scalable and reliable systems, much of it on Microsoft Azure and the .NET / C# / ASP.NET Core stack. Ex-Microsoft (Microsoft GSA) and five-time Microsoft MVP (2019–2024). My core strength is production reliability at scale — designing for resilience, fault tolerance, and graceful degradation so large distributed systems stay up under load. Most recently I led backend, platform, and AI-engine development for an AI-powered go-to-market platform." Years of experience: stated. Stack: named. Credential: proven, not claimed. USP: 'production reliability at scale' — a phrase no other candidate can copy word-for-word.
Key takeaway
The difference between these two summaries is not the candidate's experience — it is the decision to prove expertise rather than describe it.
CV vs resume: what each market actually expects
The word 'CV' means different things in different countries, and submitting the wrong format to the wrong market is a signal that you do not know the local conventions — before anyone reads a single bullet point.
| Market | What they call it | Length | Photo? | Personal info | Key convention |
|---|---|---|---|---|---|
| 🇺🇸 US tech | Resume | 1–2 pages | Never | No age, DOB, marital status | Achievement-focused; no personal statement — use a 2–3 line summary instead |
| 🇬🇧 UK tech | CV | 2 pages | No | No DOB required | Personal statement (4–6 lines) at top; 'References available on request' at bottom |
| 🇩🇪 Germany / Austria | Lebenslauf | 2–3 pages | Expected | DOB, nationality standard | Formal structure; photo top-right; Europass format accepted |
| 🇫🇷 France | CV | 1–2 pages | Common | Nationality often included | Concise; photo common; skills section prominent |
| 🇳🇱 Netherlands / Belgium | CV | 1–2 pages | Optional | Varies by industry | Europass recognised; English CVs widely accepted in tech |
| 🌍 International / remote | CV or Resume | 1–2 pages | No | No personal info | Use US resume conventions unless the JD specifies otherwise |
When in doubt about the market: use a clean 2-page CV with no photo, no DOB, and a 4-line summary — it is safe for UK, EU, and most international applications.
Interview tip
If a US job posting asks for a 'CV', check whether it is an academic or research role. If it is a standard tech role, they are using 'CV' loosely and expect a resume: 1–2 pages, achievement-focused, no personal statement.
For most non-native English speakers applying to US or UK tech companies, the practical answer is: maintain one master document and create two versions — a 1-page (or tight 2-page) US resume and a 2-page UK CV. The content is 80% identical; the differences are length, the summary style, and a few formatting conventions.
How to write a summary that proves expertise instead of claiming it
The summary section is where most international CVs lose the application. The most common mistake is writing a self-assessment — a description of what kind of person you are — instead of a case for hiring you. Every sentence in a strong summary either states a fact or names an outcome.
Three rules for a summary that works
- No pronouns, no greetings. Cut 'Hi', 'I', 'My name is'. A CV is a document, not a message. Every 'I' you remove makes room for a fact.
- Name your stack and your scale. 'Senior engineer' means nothing without context. 'Senior engineer with 8 years in high-traffic SaaS on AWS and Go' is a fact a recruiter can act on.
- End with your USP in one sentence. This is the line that no other candidate can copy — it names the specific kind of problem you are best at solving.
Phrases that claim vs phrases that prove
- ❌ 'Strong communication skills' → ✅ 'Led cross-functional teams of 8–12 across three time zones'
- ❌ 'Passionate about clean code' → ✅ 'Reduced production incident rate by 40% through systematic test coverage and code review standards'
- ❌ 'Committed to continuous learning' → ✅ 'AWS Certified Solutions Architect; completed internal ML platform migration in Q3 2023'
- ❌ 'Team player with leadership experience' → ✅ 'Grew and managed a backend team from 3 to 11 engineers over 18 months'
💡 The USP sentence — how to write it
Ask yourself: what is the specific kind of problem I am unusually good at solving? Not 'I am a good engineer' — that is the baseline. Think: 'production reliability at scale', 'migrating legacy monoliths to microservices without downtime', 'building ML pipelines from prototype to production in regulated industries'. One phrase that is genuinely yours. Write it as the last sentence of your summary.
Summary templates by seniority
- Mid-level (4–7 YOE): '[X] years building [type of product] in [industry], specialising in [stack]. Most recently [specific project or outcome]. Strong track record in [USP area].'
- Senior (8–14 YOE): '[X]+ years designing and shipping [type of system] at scale — [named stack], [named industry]. [One credential or notable outcome]. Core strength: [USP in 5–8 words].'
- Staff / Principal (15+ YOE): '[X]+ years architecting [type of system] across [industries/companies]. [Credential or recognition]. Known for [USP] — [one concrete example of what that means in practice].'
How to rewrite responsibilities as results
The single most common problem in tech CVs from non-native English speakers is that experience bullets describe tasks, not outcomes. A task tells the recruiter what you were assigned to do. A result tells them what happened because of you — and that is the only thing that matters.
Insight
Rewrite every bullet by asking: 'What changed because I did this?' If nothing changed, the bullet should either be cut or reframed around the impact it enabled.
| Before (task) | After (result) | What changed |
|---|---|---|
| Building new internet-banking services using React and TypeScript. | Built new internet-banking services using React and TypeScript, supporting 20M+ global users at 99.9999% uptime. | Added scale and reliability — same work, now it's evidence |
| Responsible for improving application performance. | Reduced API response time from 2s to 200ms by introducing Redis caching layer, cutting server costs by 30%. | Named the method, the magnitude, and the business impact |
| Worked on microservices migration. | Led migration of 14-service monolith to microservices over 6 months with zero downtime, enabling 3x faster release cycles. | Named the scope, the constraint, and the outcome |
| Mentored junior developers. | Mentored 4 junior engineers; 2 promoted to mid-level within 12 months. | Quantified the cohort and the outcome — not just a soft claim |
If you cannot quantify exactly, use magnitude: 'reduced load time from 2s to 200ms' or 'serving 10M+ daily active users' — an honest estimate is better than a vague description.
The bullet formula for tech roles
- Strong verb + what you built/changed + with what technology + at what scale or with what result
- Example: 'Designed and shipped a real-time fraud detection pipeline (Kafka, Python, Spark) processing 500K events/day, reducing false positives by 22%.'
- If you have no number: name the magnitude. 'High-traffic', 'enterprise-scale', 'reduced from X to Y', 'serving N users' all work.
- Start every bullet with a past-tense action verb: Designed, Built, Led, Migrated, Reduced, Increased, Shipped, Architected, Optimised, Deployed.
Watch Out
Avoid the passive voice in bullets. 'Was responsible for' and 'Worked on' hide your contribution. 'Led', 'Built', 'Designed' claim it directly — and that is what international recruiters are trained to scan for.
Why your company name means nothing to an international recruiter
A company name that is well-known inside your home market is invisible to a recruiter in London or San Francisco. One short phrase in parentheses changes that completely — and it takes ten seconds to add.
| Before | After | What the recruiter now knows |
|---|---|---|
| Tochka | Tochka (Largest neo-bank in CIS, $20M MRR) | Scale, industry, and market position — in 7 words |
| Yandex | Yandex (Russia's largest tech company, 100M+ monthly users) | Comparable to working at a major US tech company |
| Kaspi | Kaspi (Kazakhstan's leading fintech super-app, NYSE: KSPI) | Listed company, fintech, regional market leader |
| Grab | Grab (Southeast Asia's largest super-app, NYSE: GRAB) | Public company, consumer tech, regional scale |
| Internal startup name | Stealth fintech startup (Series B, $40M raised, 50-person eng team) | Stage, funding, and team size — critical context |
Add context to every company that is not a global household name. The format is: Company Name (one-line description). Keep it under 10 words.
Interview tip
For well-known global companies (Google, Amazon, Microsoft, Meta, Stripe), no parenthetical is needed. For everyone else — including well-known regional names — add the context. When in doubt, add it.
ATS-ready template: structure, sections, and formatting rules
Most tech CVs fail ATS (Applicant Tracking System — the software that parses and scores CVs before a human sees them) not because of content, but because of formatting. Two-column layouts, tables inside experience sections, and embedded graphics all cause parsing failures. The safest format is a single-column, plain-text-compatible PDF.
Recommended section order (international tech CV)
- Header: Full name · Location (city, country) · Email · LinkedIn URL · GitHub (if relevant) · No photo (US/UK/international)
- Summary / Professional Statement: 3–6 lines. Answers the four questions. No pronouns.
- Technical Skills: Grouped by category (Languages, Frameworks, Cloud/Infra, Tools). No skill bars or ratings.
- Experience: Reverse chronological. Company name + context + dates + title. 3–5 bullets per role, results-focused.
- Education: Degree, institution, year. One line per qualification unless you are within 2 years of graduation.
- Certifications / Awards (optional): Named credentials only — AWS, GCP, CKA, Microsoft MVP, etc.
- Projects (optional for senior roles): 1–2 lines each. Link to GitHub or live URL where possible.
Formatting rules that protect ATS compatibility
- Single column only. Two-column layouts break most ATS parsers — the right column is often read as a separate, disconnected document.
- Standard section headings: 'Experience', 'Education', 'Skills' — not creative variants like 'My Journey' or 'What I've Built'.
- No tables inside experience sections. Use plain bullet points.
- No skill bars, progress rings, or rating graphics. They mean nothing to a human and nothing to a parser.
- Font: 10–12pt, standard serif or sans-serif (Calibri, Arial, Garamond, Georgia). No decorative fonts.
- Export as PDF — but check the PDF is text-selectable, not a scanned image.
- File name: FirstName-LastName-CV.pdf — not 'My CV Final v3 UPDATED.pdf'.
For a ready-to-use LaTeX template built specifically for international tech applications, open this Overleaf template and make a copy: Overleaf International Tech CV Template. It is single-column, ATS-compatible, and pre-structured with the section order above. If you prefer not to use LaTeX, Jake's Resume on Overleaf is the most widely used ATS-safe alternative — single-column, standard headings, no graphics.
Interview tip
LaTeX CVs are widely accepted in tech and academia. For non-technical corporate roles, a Word or Google Docs export may be safer — check whether the job portal accepts PDF before submitting.
How to tailor your CV for each role in 30 minutes
A master CV is a document you never send. It contains every role, every bullet, every credential — your complete record. What you send to each application is a tailored version: the same facts, reordered and rephrased so the most relevant experience surfaces first. The goal is not to change what you have done — it is to speak the language of the specific job description.
The 30-minute tailoring workflow
- Read the job description and highlight the 5–8 most repeated phrases. These are the keywords the ATS is scanning for and the recruiter is looking for.
- Check your summary: does it use the same language as the JD? If the JD says 'distributed systems' and your summary says 'scalable backend', change it.
- Reorder bullets within each role: put the bullet most relevant to this JD first. Recruiters read the first bullet of each role; they often skim the rest.
- Add any missing keywords naturally — never stuff them. If the JD mentions Kubernetes and you have used it, add it. If you have not, do not.
- Check your skills section against the JD's required stack. Remove tools that are irrelevant to this role; they dilute the signal.
- Re-read the summary as if you were the recruiter. Does it answer: years of experience, industry, stack, USP? If not, fix it before sending.
💡 Using AI to tailor faster — and where to be careful
A Claude or ChatGPT prompt can do the keyword-matching and rephrasing step in under a minute. The key rule: give the AI your master CV and the job description, and instruct it to reorder and rephrase only — never to invent experience, inflate outcomes, or add skills you do not have. A tailored resume works because it presents your real experience in the recruiter's language; a fabricated one fails at the first technical question. For a detailed prompt that produces ATS-friendly LaTeX output, see the full walkthrough at trythestack.co: How to tailor an engineering CV with Claude.
Watch Out
Always do a final human review of any AI-tailored CV. AI tools occasionally introduce awkward phrasing, misattribute technologies, or over-smooth your voice. The CV must still sound like you — a recruiter who calls you for a screen will notice immediately if the document and the person do not match.