Quick Answer
Write a resume that passes the 15-second scan: one page if you have under 10 years of experience, bullet points not paragraphs, and every line leading with a result rather than a duty. For non-native English speakers, the additional work is making sure your phrasing sounds natural and senior — not translating your job description word for word from your first language.
The 15-second test: what recruiters actually do with your resume
Recruiters do not read resumes from top to bottom on the first pass — they scan them, and they decide within roughly 10 to 15 seconds whether to keep reading. Your resume has one job: make your value obvious within those seconds. Every decision you make about what to include, what to cut, and how to format it should serve that single goal.
For non-native English speakers, this creates a specific problem. Many candidates write resumes the way they would write a formal document in their home country — dense, comprehensive, and structured around duties and titles. That approach fails the 15-second test even when the underlying experience is strong. The recruiter's eye lands on a wall of text, finds nothing instantly memorable, and moves on.
Insight
The question is not 'does my resume contain all my experience?' It is 'does someone scanning it for 15 seconds immediately understand what I am good at?'
Before you rewrite a single line, read your current resume as if you are a recruiter who has never met you. Set a 15-second timer. What do you learn? If the answer is 'mostly job titles and dates,' the structure needs to change — not the experience behind it. If you want a deeper grounding in how English-language interviews are structured before you get to the resume itself, Mockly's guide on what to expect in English interviews covers the full hiring process and helps you see the resume as one step in a longer sequence.
How long should your resume be, and how should it be structured?
One page is the right target if you have fewer than 10 years of experience. Two pages can work for more experienced professionals with multiple relevant roles — but only if both pages earn their place. A longer resume does not signal more experience; it signals an inability to prioritise, which is itself a signal recruiters notice.
Key takeaway
A shorter resume forces you to include your strongest work. A longer one buries it.
Standard sections, in the order recruiters expect them
- Name and contact details — email, LinkedIn, GitHub or portfolio if relevant. No photo, no date of birth, no marital status (standard in US and UK; different conventions apply in some other markets).
- A short professional summary — 2–3 lines maximum. This is not an objective statement ('I am looking for a role where...'); it is a positioning statement ('Backend engineer with 6 years in distributed systems, most recently at a fintech scaling to 10M users').
- Work experience — in reverse chronological order. Company, title, dates, then bullet points.
- Skills — a short, scannable list of technologies, languages, and tools. Not a paragraph.
- Education — degree, institution, year. Brief unless you are early-career.
- Projects or open-source contributions — only if they strengthen your application (see the section on what to include).
Interview tip
If trimming a few lines would bring your resume from two pages to one, trim them. Recruiters do not reward completeness — they reward clarity.
One structural mistake that is especially common among candidates from certain regions: putting education at the top, above work experience. In US and UK tech hiring, education goes at the bottom unless you are a recent graduate with no significant work history. Putting it first signals that you consider your degree more relevant than your work — which reads as junior, regardless of your actual level.
How to write bullet points that show impact, not just duties
Your job title already tells recruiters what you were expected to do. What they actually want to know is what changed because of your work. This is the single most important writing shift in the whole resume, and it is also the place where non-native speakers most often get stuck — because describing duties is grammatically simple, and describing impact requires a different sentence structure entirely.
What is an impact bullet?
A bullet point that names an action you took, then connects it to a measurable or observable outcome — not just a description of what your role involved.
| Duty bullet (weak) | Impact bullet (strong) |
|---|---|
| Managed software projects and coordinated with developers. | Led a 4-engineer team to deliver a customer portal 2 weeks ahead of schedule, reducing support tickets by 35%. |
| Responsible for database performance. | Optimised query performance on a PostgreSQL database serving 2M daily users, cutting average response time from 800ms to 120ms. |
| Worked on the mobile app. | Rebuilt the iOS checkout flow, increasing conversion rate from 61% to 74% over 3 months. |
| Helped with CI/CD pipeline improvements. | Redesigned the CI/CD pipeline, reducing deployment time from 45 minutes to 8 minutes and eliminating a class of flaky test failures. |
The strong version names what you did, then names what changed. The weak version describes your job description.
Three questions to ask yourself for every bullet point
- What changed because of this work? (Faster, cheaper, more reliable, more users, higher revenue, fewer errors — any of these count.)
- Can I attach a number? Revenue generated, costs reduced, time saved, users served, error rate dropped, satisfaction score improved. Even a rough estimate ('roughly 30% faster') is more useful than no number at all.
- Would a recruiter who knows nothing about my company understand this sentence? If the bullet relies on internal jargon or a product name that means nothing outside your company, rewrite it.
Watch Out
Avoid the phrase 'responsible for' — it is the clearest signal that a bullet is describing a duty, not an achievement. Replace it with a strong past-tense verb: Led, Built, Reduced, Shipped, Redesigned, Automated, Migrated, Increased.
Strong opening verbs for tech resume bullets
- Engineering: Architected, Implemented, Optimised, Migrated, Refactored, Automated, Deployed, Debugged, Scaled
- Leadership: Led, Mentored, Coordinated, Defined, Established, Hired, Aligned
- Product / data: Launched, Analysed, Modelled, Prioritised, Shipped, A/B tested, Reduced, Increased
- Cross-functional: Collaborated, Presented, Negotiated, Delivered, Drove
Keep each bullet to one or two lines. If you find yourself writing three lines to explain a single achievement, split it into two bullets or cut the background context. Recruiters do not need to understand the full history of a project — they need to understand what you did and what it produced.
English language patterns that make strong engineers sound junior
This is where the non-native speaker's resume often diverges from a native speaker's — not in the experience, but in the phrasing. Several very common patterns in resume English signal lower seniority or lower confidence to a recruiter, even when the underlying work was genuinely senior.
| Pattern to avoid | Why it reads as junior | Stronger alternative |
|---|---|---|
| "I was responsible for..." | Passive framing; sounds like a job description, not an achievement | Start with a verb: "Led...", "Built...", "Reduced..." |
| "Helped with..." or "Assisted in..." | Implies you were a supporter, not a contributor | "Contributed to...", or better: name your specific contribution directly |
| "Worked on the team that..." | Distances you from the outcome | "As part of a 5-person team, led the backend implementation of..." |
| "Have experience in..." (in the summary) | Vague; does not tell the recruiter what level or what outcome | "6 years building distributed systems in Go and Kubernetes" |
| "etc." at the end of a list | Looks unfinished and informal | End the list or complete it — never use "etc." |
| "Good communication skills" or "team player" | These are filler phrases every candidate uses; they add no signal | Remove entirely, or demonstrate with a concrete example |
Every one of these patterns is a translation artifact — they come from trying to write English the way formal documents are written in many other languages. They are easy to fix once you know to look for them.
Interview tip
After you finish your resume, do one pass specifically looking for these six patterns. Fixing them takes 20 minutes and changes how senior you read on paper.
Grammar notes specific to resume English
- Tense: Use simple past tense for previous roles ('Led', 'Built', 'Reduced'). Use present tense for your current role ('Lead', 'Build', 'Own'). Mixing these in the same role looks careless.
- Articles: In resume bullet points, native English speakers routinely drop 'a' and 'the' at the start of bullets. 'Led migration of monolith to microservices' is standard — not 'Led the migration of the monolith to microservices.' Both are grammatically acceptable; the shorter form is conventional.
- Prepositions: 'Experience in Python' is standard; 'experience of Python' is not used in US or UK tech resumes. 'Worked on the API' is correct; 'worked at the API' is not.
- Numbers: Write numbers as digits in bullets ('Reduced latency by 40%', 'Managed a team of 8 engineers'). Spelling out numbers ('forty percent') is unusual in resume bullet points and slows scanning.
If you are unsure whether a specific phrase sounds natural, the most reliable test is to read it aloud. Awkward phrasing almost always sounds awkward before it looks awkward. If you find yourself pausing or rephrasing as you read, rewrite that line.
What to include when your experience doesn't fit a neat job history
Many non-native speaker candidates leave their strongest work off their resume because they assume it does not count — a side project, a university project, a hackathon, an open-source contribution, a startup that did not launch, freelance work, or volunteer engineering. This is a mistake. Recruiters at US and UK tech companies care less about where the experience came from than what it demonstrates about your abilities.
Experience worth including even if it wasn't a full-time job
- Side projects — especially if they have users, a GitHub repo with stars, or a measurable outcome
- Open-source contributions — name the project and describe your specific contribution, not just 'contributed to open source'
- Hackathon projects — if you built something real, describe it as you would a work project
- Freelance or contract work — treat it as a role: client type (not necessarily the name), what you built, what the outcome was
- University or postgraduate projects — relevant if they involved real technical depth, especially for candidates earlier in their career
- Volunteer technical work — building tools for NGOs, community projects, or internal tools for a sports club all count if they demonstrate relevant skills
Key takeaway
The test is not 'was this a paid, full-time role?' The test is 'does this demonstrate a skill or achievement that is relevant to the job I am applying for?'
One specific situation that comes up often for non-native speakers: experience from your home country that you are not sure translates. It does. A senior engineering role at a well-known company in India, Brazil, Eastern Europe, or anywhere else is a senior engineering role. Write it the same way you would write any other role — company name, your title, dates, bullet points with impact. Do not downplay it or leave it off because you are not sure whether the company is known in the US or UK.
Interview tip
If you are unsure whether to include something, ask: does this help tell my professional story, or does it dilute it? If it strengthens the picture of your skills, include it. If it is just filling space, cut it.
Which resume layout works best for non-native speakers?
Use a simple, clean layout — not a designed one. Resumes with graphics, icons, charts, timelines, or multiple colour columns look impressive at a glance, but they are harder to scan, often fail applicant tracking systems (ATS), and draw attention to the design rather than the content. Unless you are applying for a visual design role, clarity beats creativity every time.
What is an ATS?
An Applicant Tracking System is software that many companies use to parse and filter resumes before a human sees them — heavily designed resumes often fail to parse correctly, meaning your application may be filtered out automatically.
What a good resume layout looks like
- Font: A standard serif or sans-serif — Georgia, Garamond, Calibri, or Arial. Size 10–12pt for body text, slightly larger for your name and section headings.
- Margins: Standard (around 2cm / 0.75 inch on each side). Shrinking margins to squeeze in more content is a signal that you need to cut content, not margins.
- White space: Enough that the page does not look dense. White space makes bullet points easier to scan.
- Section headings: Clear and consistent — EXPERIENCE, EDUCATION, SKILLS. Bold or slightly larger than body text. No decorative lines or icons.
- Dates: Right-aligned, consistent format. Either 'Jan 2021 – Mar 2023' or '2021–2023' — pick one and use it throughout.
- No photo, no headshot: Standard in US and UK applications. Including one is unusual and can introduce unconscious bias you do not want.
Avoid
Two-column layouts with a sidebar. Infographic-style resumes with skill bars or pie charts. Multiple colours or background shading. Tables used to create visual structure. Embedded images or logos.
Use
Single-column layout, top to bottom. Bold section headings, plain body text. Bullet points with consistent indentation. PDF format when submitting (preserves formatting across systems). A template from Google Docs or a clean Word template — nothing more complex.
One layout mistake that comes up specifically for non-native speakers: translating a CV format from a country where longer, more detailed CVs are the norm (Germany, France, parts of Asia) into an English-language resume. The content expectations are genuinely different. A UK or US tech resume is shorter, more achievement-focused, and less formal in structure than a German Lebenslauf or a French CV. Adapting the format is not a compromise — it is what the recruiter expects.
What recruiters are actually scoring in the first pass
Most resume advice describes what to put in. This section makes the hidden scoring rubric explicit — what a recruiter is actually evaluating in those first 15 seconds, and what a positive or negative signal looks like for each dimension.
| What they look at | Positive signal | Negative signal |
|---|---|---|
| Relevance of most recent role | Title and company name are immediately recognisable as relevant to the open role | Most recent role is unrelated, or the title is ambiguous ('Associate' with no context) |
| Seniority signal | Bullet points name outcomes and ownership ('Led', 'Architected', 'Owned') | Bullets describe duties or use passive framing ('Responsible for', 'Helped with') |
| Measurable impact | At least one number per role — percentage, users, time saved, revenue | All bullets are descriptive with no quantification |
| Scannability | Clean layout, short bullets, white space — value visible in 15 seconds | Dense paragraphs, long bullets, cluttered design — recruiter gives up |
| Language quality | Consistent tense, natural phrasing, no filler phrases | Mixed tenses, awkward prepositions, 'responsible for', 'etc.' |
| Length appropriateness | One page (under 10 years) or two tight pages (senior) | Three or more pages, or one page crammed with 8pt text |
A recruiter is not grading you on effort — they are pattern-matching for signals of seniority, relevance, and impact. Make those signals obvious.
Watch Out
Language quality is the one dimension where non-native speakers are most likely to lose points they have earned. A senior engineer who writes 'responsible for managing of the database systems' signals lower seniority than their actual level — not because their English is bad, but because resume English has specific conventions that differ from general professional writing.
Free Interview Guide
Browse the free interview guide library first
No card needed. Practical, tech-interview-specific English guides — then start your free trial or book a single $40 pay-as-you-go session when you're ready for live coaching.
Browse the GuidesHow to check your resume before you send it
Checking your own resume is hard — you know what you meant to say, so you read what you intended rather than what is actually on the page. These four checks are designed to get around that problem.
The four-pass review
- The 15-second scan. Set a timer. Read your resume as a recruiter who has never met you. After 15 seconds, stop. Write down the three things you learned. If those three things are not your strongest achievements, the structure needs to change.
- The verb audit. Go through every bullet point and underline the first word. If any of them are 'Responsible', 'Helped', 'Assisted', 'Worked', or 'Was', rewrite that bullet before anything else.
- The number check. For every role, count how many bullets include a number (percentage, count, time, money). If any role has zero numbers, find at least one. If you genuinely cannot quantify an outcome, use a relative description: 'significantly reduced', 'the primary contributor to', 'the first implementation of this kind in the team'.
- The read-aloud test. Read every bullet point aloud. If you pause, stumble, or rephrase as you read, that sentence needs rewriting. Awkward phrasing is almost always audible before it is visible.
💡 One extra check for non-native speakers
After you finish, do a single-purpose pass looking only for the six language patterns listed in the earlier section: 'responsible for', 'helped with', 'worked on the team that', 'have experience in' (in the summary), 'etc.', and soft filler phrases like 'good communication skills'. These are the patterns that most reliably lower the perceived seniority of a resume written by a non-native speaker — and they are all fixable in under 30 minutes.
If you want a second opinion from someone who has actually reviewed resumes in the hiring process, Mockly's CV review service returns detailed, actionable feedback within 24–48 hours — covering language, structure, and how your experience is positioned for the specific market you are targeting. You can access it through a start a 7-day free trial of Premium, which also includes feedback on five named dimensions — grammar, pronunciation, vocabulary, structure, and impact — across every mock interview you run.
Interview tip
Once your resume is in good shape, the next question is how to talk about it in an interview — specifically how to describe your career timeline clearly in English. The guide on free interview guides covers verb tenses for your career timeline, which is the most common grammar gap in self-introductions.
How to know your resume is working
- You are getting recruiter screens from roles you apply to (not just automated rejections).
- Interviewers ask follow-up questions about specific achievements rather than asking you to explain your background from scratch.
- The conversation in the interview picks up where your resume left off — the recruiter already understands your level and is testing depth, not establishing basics.
- You can answer 'walk me through your resume' in under two minutes without losing the interviewer's attention.