Research-backed · Updated 2025

Resume tips that
actually get you hired.

Not the generic "use action verbs" advice you've already read. This is how ATS systems actually parse your resume, what recruiters genuinely look for in 7 seconds, and the exact writing framework that increases callback rates by up to 40%.

Apply these tips now
75% of resumes never reach a human
7 seconds average recruiter scan time
40% more callbacks with quantified bullets
99% of Fortune 500 use ATS

01 · ATS & parsing mechanics

How ATS systems actually read your resume

Most resume advice treats ATS like a buzzword. Here's what's actually happening under the hood — and why it changes everything about how you write.

99%

of Fortune 500 companies use ATS to filter applications before a human reviews them.

Jobscan, 2025

75%

of resumes are rejected by ATS before a recruiter ever opens them — mostly due to formatting and keyword gaps.

Gitnux Research

88%

of employers report losing qualified candidates because ATS filtered them out incorrectly.

ResumeAdapter

The 4 stages every resume passes through

01

Text extraction

The ATS converts your file into raw text using OCR. Multi-column layouts get read left-to-right across both columns, jumbling your work history. Graphics, images, and text in headers/footers are either skipped or garbled. A two-column resume can make the system think you had zero months of experience — because it merged your date column with your education column.

02

Section identification

The parser looks for known section headers: 'Work Experience', 'Education', 'Skills'. Creative headers like 'My Journey' or 'Where I've Been' confuse parsers that rely on pattern recognition. If your skills section is labelled 'Things I'm Good At', it may never get indexed.

03

Entity extraction

The system pulls out specific data: job titles, company names, dates, technologies, credentials. Modern systems (Workday, Greenhouse, Lever) use NLP — so 'Python programming' and 'Python development' are now treated as equivalent. But 'stakeholder management' and 'client relations' may not be. Use the exact terminology from the job description where you can.

04

Scoring & ranking

Your resume gets a match score against the job requisition. In most systems, a recruiter only reviews candidates above a certain threshold. If 400 people applied and you scored in the bottom half, your resume is functionally invisible — even if you're technically qualified. Aim for 75%+ keyword match before submitting.

The header/footer trap — a real example

A study found that ATS was unable to identify contact information 25% of the time when it was stored in the document header or footer. If your name, email, or phone number is inside a Word document header, many systems will never parse it. You become "Anonymous Applicant" in the database.

Fix: Put ALL contact information in the main body of the document, not in a header/footer region.

ATS systems you'll encounter (and their quirks)

WorkdayEnterprise companies, banks, hospitals

Strictest parser. Hates tables and columns. Now has AI screening for skills alignment and career trajectory.

GreenhouseTech companies, startups, scale-ups

More tolerant of PDFs. Includes candidate scoring with AI that evaluates skill progression across roles.

LeverMid-size tech and SaaS companies

Good PDF handling. Focuses heavily on keyword density relative to job description.

Taleo (Oracle)Large enterprises, government contractors

Oldest architecture. Extremely strict about formatting. Will fail completely on complex layouts.

iCIMSLarge corporations, retail, healthcare

Parses well but requires standard section headings. Creative headers will cause mislabelled sections.

02 · Formatting

Formatting that actually works

Fancy designs look great as screenshots. They get destroyed by ATS parsers. Here are the exact rules grounded in how parsers actually process documents.

Single column only

Multi-column layouts cause parsers to read left-to-right across columns, mixing your work history with education dates. One continuous column, top to bottom. No exceptions.

No tables or text boxes

Tables scramble data. Text boxes create invisible islands of content. Skills listed inside a table may never be indexed. Use plain bullet lists instead.

Nothing in headers/footers

25% of ATS systems fail to parse header/footer content. Contact info, page numbers, watermarks — all must stay in the main body of the document.

Safe fonts only

Calibri, Arial, Georgia, Times New Roman, Helvetica. Decorative or script fonts cause text extraction failures. 10–12pt body, 14–16pt for your name.

Standard section headers

'Work Experience' not 'My Journey'. 'Skills' not 'Things I'm Good At'. Parsers use exact pattern matching for section identification — deviate and they mislabel your content.

Safe bullet symbols only

Standard bullets (•) or dashes (–) only. Checkmarks (✓), stars (★), arrows (→), custom symbols — these cause encoding issues or get misread as text characters.

Do

  • Save as .docx (Word) unless PDF is explicitly requested — .docx parses most reliably across all major ATS
  • Use standard date formats: 'Jan 2022 – Mar 2024' or '01/2022 – 03/2024'
  • Left-align or center-align contact info in the main body of the document
  • Use 0.5–1 inch margins and 10–12pt body font with readable line spacing
  • Test by pasting into a plain text editor — if it scrambles, the ATS will too

Don't

  • Use two-column layouts, sidebars, or graphic-heavy templates — they get parsed in the wrong order
  • Put contact info, your name, or important details inside Word headers/footers
  • Use tables for skills sections — the cells may be ignored entirely
  • Submit a scanned PDF or image-based PDF — these are unreadable to text-based parsers
  • Use seasonal or vague date formats: 'Winter 2022', 'Q1 2023', 'Early 2020s'

Visual examples

See the difference side by side

Real annotated resume mockups showing exactly what separates a rejected resume from one that lands interviews. Switch between scenarios to explore each mistake type.

Formatting disasters

Multi-column layouts, tables, and headers/footers that break ATS parsing — the most common reason qualified candidates are filtered out.

What NOT to do
ATS Score: 24/100
Word Header Region ⚠ ATS cannot read this area
AJ

CONTACT

📧 alex@email.com

📱 555-0142

📍 New York

🔗 linkedin.com/in/alex

SKILLS

★★★★☆ JavaScript

★★★☆☆ Python

★★★★★ React

★★☆☆☆ Docker

HOBBIES

🎸 Guitar

⚽ Football

📚 Reading

ALEX JOHNSON

OBJECTIVE

Results-oriented software developer with strong technical skills and a passion for technology seeking an exciting new opportunity to leverage my expertise and make a positive impact at a dynamic company where I can grow professionally.

MY JOURNEY 🚀

Software Developer — TechCorp Inc

2021 - Present

  • • Was responsible for developing features
  • • Helped team with various coding tasks
  • • Worked on improving the application

WHERE I STUDIED 🎓

B.Sc Computer Science, State University, 2021

References available upon request.

What TO do
ATS Score: 91/100

Alex Johnson

alex.johnson@gmail.com · (555) 014-2000 · New York, NY · linkedin.com/in/alexjohnson

Professional Summary

Senior Software Engineer with 6 years building scalable web applications at fintech companies. Shipped 4 production products serving 500K+ users. Specialises in React, Node.js, and AWS — with a track record of reducing page load times by 40–60% across every role.

Work Experience

Software Engineer — TechCorp Inc

Jan 2021 – Present

  • Reduced API response time by 67% by refactoring to async queries and adding Redis caching, improving UX for 200K daily users
  • Led migration to microservices (Go + Kubernetes), cutting deployment time from 45 min to 8 min
  • Mentored 3 junior engineers — all promoted within 12 months

Skills

JavaScript · TypeScript · React · Node.js · Python · AWS · Kubernetes · PostgreSQL · Redis · Docker

Education

B.Sc Computer Science — State University

2021

Problems in the bad example

  • Two-column layout causes ATS to merge sidebar + work history into gibberish
  • Headshot wastes space and causes bias — illegal to consider in many countries
  • "MY JOURNEY 🚀" won't be recognised as "Work Experience" by any ATS parser
  • Contact info stored in Word header region — missed by 25% of ATS systems
  • Star ratings for skills are meaningless to ATS and look amateurish to recruiters

What the good example does instead

  • Single-column layout — ATS parses cleanly, top to bottom, correct order every time
  • Contact info in the main document body — not inside a Word header/footer
  • Standard 'Work Experience' heading — ATS pattern-matches this instantly
  • Skills listed as plain text keywords — exactly how ATS indexes and matches them
  • Only relevant sections — no photo, no hobbies, no references clutter

ATS score impact — this scenario

Bad example
24/100
Good example
91/100
Build a resume that looks like the right sideATS-safe format included · Free

03 · What to write

Content: what to write — and what to cut

Recruiters spend an average of 7 seconds on an initial scan, using a specific visual pattern. Here's what they actually look for, and what wastes their time.

7 sec

Average initial resume scan time. Eye-tracking research from Ladders shows recruiters look at: name, current title, current company, dates, previous title, education.

Ladders Eye-Tracking Study

6 sec

Is enough to reject. 1 in 5 recruiters will reject a candidate in under 60 seconds — many in under 6 — due to immediate red flags.

The Undercover Recruiter

40%

Increase in interview callbacks when bullet points contain quantified achievements vs vague duty descriptions.

Interview Guys Research

The professional summary: your 6-second hook

The summary is the first thing a recruiter reads. It must answer three questions in 3–4 lines: who you are, what you bring, and why you're different. Objective statements ("Seeking a challenging role...") are dead — they tell employers what you want, not what you offer.

Weak

Results-oriented software engineer with a passion for technology seeking an exciting new opportunity to leverage my skills.

Strong

Senior Software Engineer with 7 years building distributed systems at fintech scale. Led migration of monolithic payment platform to microservices architecture serving 4M daily transactions. Expertise in Go, Kubernetes, and PostgreSQL — with a track record of reducing p99 latency by 60%+ across 3 consecutive roles.

Software Engineer summary — includes title, years, specialty, and a headline achievement

Weak

Dynamic marketing professional with extensive experience in various marketing disciplines, looking to contribute to a growing team.

Strong

B2B Marketing Manager with 8 years driving pipeline growth for SaaS companies. Generated $2.4M in qualified pipeline in 2024 through integrated SEO and demand gen campaigns. Specialises in HubSpot, content strategy, and conversion rate optimisation across enterprise and mid-market segments.

Marketing Manager summary — specific vertical, channel expertise, and revenue impact

Words that actively hurt your resume

These words appear on millions of resumes and signal to recruiters that you're taking a mass-production approach. Over 50% of recruiters say clichés cause immediate rejection. Remove every one of these and replace with specific, verifiable evidence.

Results-orientedTeam playerHard workerGo-getterPassionateDynamicMotivated self-starterProven track recordThink outside the boxDetail-orientedStrategic thinkerSynergyLeverageValue-addExperienced professionalStrong communicatorWorks well under pressure

The rule: every quality you claim must be demonstrated, not stated. Instead of "strong communicator," write "Presented quarterly roadmap to 200+ stakeholders across 3 time zones, receiving 94% satisfaction score." The evidence does the work — you don't need the label.

What to include vs. cut ruthlessly

Almost always include

  • Contact info (in body, never header)
  • Professional summary (tailored per role)
  • Work experience (reverse chronological)
  • Skills section (hard skills + tools)
  • Education (institution, degree, year)
  • Certifications that are role-relevant
  • LinkedIn URL and portfolio/GitHub

Usually cut

  • Objective statement (replace with summary)
  • References or 'References available on request'
  • Headshot / photo (in US, Canada, UK)
  • Marital status, age, nationality (in most countries)
  • Jobs older than 10–15 years (unless highly relevant)
  • High school details (once you have a degree)
  • Hobbies (unless directly relevant to the role)
  • Generic soft skills without evidence

04 · Bullet points

The STAR & XYZ method for bullet points

Every bullet point should answer: what did you do, how did you do it, and what changed because of you? Here's the framework with real examples.

STAR vs XYZ — knowing when to use each

STAR (Situation → Task → Action → Result) gives full context. XYZ (Accomplished X, as measured by Y, by doing Z) is the compact bullet version. Use XYZ for most bullets; use full STAR when context matters for a complex achievement.

XYZ Formula (use for most bullets)

Accomplished [X],
as measured by [Y],
by doing [Z]

Best for: concise, scannable bullet points. 15–25 words. Lead with the strongest number.

STAR Method (use for 2–3 key bullets)

Situation → context
Task → your role
Action → what you did
Result → measurable outcome

Best for: complex achievements that need context. Can span 1–2 bullets. Don't label the acronym explicitly.

Weak

Responsible for improving application performance and working on the API layer.

Strong

Reduced API response time by 67% (p99: 2.1s → 0.7s) by refactoring synchronous database calls to async batch queries and adding Redis caching across 12 high-traffic endpoints.

Software Engineer — leads with quantified result, then method

Weak

Managed a portfolio of enterprise accounts and exceeded targets.

Strong

Grew enterprise ARR by $1.8M (138% of quota) by rebuilding stalled deals using a consultative discovery framework and introducing quarterly business reviews with C-suite stakeholders.

Sales role — revenue first, then approach

Weak

Helped improve employee satisfaction and reduce turnover in the company.

Strong

Reduced voluntary attrition from 22% to 11% in 12 months by redesigning the onboarding programme, introducing 90-day check-ins, and partnering with managers on structured career pathing conversations.

HR / People Ops — retention metric, then strategy

Weak

Helped the team improve communication and collaboration on projects.

Strong

Introduced async-first communication protocols (Loom + Notion) for a 14-person engineering team spanning 4 time zones, eliminating 6+ hours of recurring weekly meetings and unblocking cross-team deliverables faster.

When you can't quantify — use scope and qualitative outcome instead

Strong action verbs by function

Start every bullet with a past-tense action verb. Never start with "Responsible for" — it signals you're describing a job description, not an achievement.

Leadership

DirectedSpearheadedChampionedOrchestratedMentoredScaled

Growth / Revenue

GeneratedGrewDroveAcceleratedConvertedUpsold

Building / Engineering

ArchitectedEngineeredDeployedAutomatedRefactoredShipped

Analysis / Strategy

SynthesisedModelledForecastedIdentifiedDiagnosedBenchmarked

Process / Operations

StreamlinedRedesignedStandardisedReducedEliminatedOptimised

Collaboration / Communication

NegotiatedFacilitatedPresentedPartneredCoordinatedInfluenced

What to do when you can't find a number

Q: You improved something but don't know the exact %?

A: Estimate responsibly. 'Reduced processing time from ~4 hours to under 30 minutes' is honest and specific without a false precision.

Q: Your role is creative or qualitative?

A: Use scope. '8 published case studies averaging 3,200 monthly readers' is more concrete than 'produced content'. Scale, reach, and frequency all count.

Q: You managed people or projects?

A: Size always works. '$2.3M budget', '14-person cross-functional team', '6 simultaneous enterprise deployments' — scope is a metric.

Q: You're early career with limited experience?

A: Coursework, projects, volunteering, and internships all have outcomes. 'Delivered capstone ML project achieving 91% accuracy on 50k-record dataset' beats 'completed machine learning course'.

05 · Length & structure

Length, section order, and what goes where

The one-page rule is officially dead for most professionals. Here's the real data on length by experience level — and the section order that maximises recruiter attention.

Length by experience level

1 page

0–3 years (entry level, new graduate)

One focused page. No padding. If you can't fill a page honestly, that's fine — don't stretch. Use projects, coursework, internships, and volunteer work to fill relevant content.

1–2 pages

3–7 years (mid-level)

One strong page often beats two mediocre pages. But if you have substantial, relevant achievements across multiple roles, a tight two-pager is completely acceptable — and a ResumeGo study found two-page resumes were chosen 2.3× more often.

2 pages

7–15 years (senior professional)

Two pages is the standard. A single page at this level can look suspiciously thin, as if you're hiding a lack of progression. Page 1 hooks; Page 2 deepens.

2–3 pages

15+ years (executive, director+)

Leadership roles require demonstrating strategy, impact, and people management at scale. That takes space. Board service, transformations, and global scope are expected. Every line must still earn its place.

3–10+ pages (CV)

Academia / Research / Medicine

Different document type entirely — a CV, not a resume. Includes publications, grants, conference presentations, clinical rotations. Standard resume rules don't apply.

The optimal section order

Recruiters scan in a predictable Z-pattern, spending most time in the top third of page one. Put your highest-value content there. Here's the section order that maximises that attention.

1
Contact information Name, email, phone, location (city/country only), LinkedIn, GitHub or portfolio link.
2
Professional summary 3–4 lines. Role-specific. One headline achievement. Zero clichés. Swap for an objective only if you're a career changer.
3
Work experience (reverse chronological) Most recent role first. 3–5 bullets per role. Focus on achievements not duties. Include dates in MM/YYYY format.
4
Skills Hard skills, tools, languages, frameworks. Group logically. Remove generic soft skills. Keep it scannable.
5
Education Degree, institution, year. GPA only if 3.5+ and within last 3 years. Move above work experience if you're a new graduate.
6
Certifications Role-relevant only. Include issuer and year. Skip expired or irrelevant certifications.
7
Projects (optional) Especially valuable for tech and design roles. Include live links, stack, and what you built. Treat each project like a mini-job with achievement bullets.

06 · Tailoring

Tailoring your resume for each application

Sending the same resume to every job is the #1 mistake. Here's a repeatable system for customising in under 20 minutes — without rewriting from scratch.

The 20-minute tailoring system

01

Extract keywords from the JD

Copy the job description into a text editor. Highlight every hard skill, technology, tool, credential, and role-specific phrase. These are your target keywords. Modern ATS systems use NLP, so 'Python development' and 'Python scripting' may match — but 'stakeholder management' and 'client relations' often won't. Use their exact phrasing where you can do so authentically.

02

Update your professional summary

This is the single highest-impact edit. Match your title to their job title. Mirror their language for your specialisation. Weave in 1–2 of their priority keywords. This takes 5 minutes and dramatically improves your ATS score for that specific role.

03

Reorder and adjust bullet points

Bring your most relevant achievements to the top of each role. If they're hiring for someone who can manage stakeholder communication and you have a great bullet for that, move it to position 1 or 2 under that job. Don't rewrite — reorder and lightly rephrase to match their terminology.

04

Add missing keywords to your skills section

If you genuinely have a skill they've listed and it's not on your resume, add it. Don't lie — but don't omit either. Legitimate skills you've been using but haven't listed are the easiest wins. Also check: do they use 'Google Analytics' or just 'analytics'? Match the exact term they use.

05

Run a plain-text test

Paste your resume into Notepad or TextEdit (plain text mode). If the structure collapses into an unreadable sequence of words, the ATS parser will have the exact same experience. Fix any formatting issues before submitting. This 2-minute test has saved thousands of applications.

LinkedIn consistency — the hidden rejection trigger

88% of recruiters check LinkedIn profiles during screening. Inconsistencies between your resume and LinkedIn — different dates, different job titles, different companies — create immediate red flags about your honesty and attention to detail. AI tools can now cross-reference these automatically.

Do

  • Match your job titles and dates exactly between resume and LinkedIn
  • Include your LinkedIn URL on your resume (without the 'www' prefix for cleanliness)
  • Update your LinkedIn headline to match the role you're targeting
  • Ensure your LinkedIn summary is consistent with your resume summary in tone

Don't

  • Have different employment dates on your resume vs LinkedIn
  • List a company on your resume that doesn't appear on LinkedIn at all
  • Use a different job title on each platform without explanation
  • Let your LinkedIn go stale — recruiters actively use it to verify your resume

07 · Silent killers

The 8 silent resume killers

These mistakes get you rejected without you ever knowing why. They don't trigger an automated message — the application just disappears. Here's what they are.

01

Keyword stuffing — the manipulation that backfires

Some candidates try to game ATS by hiding white keywords in white text, or packing every possible term into a skills section. Modern ATS systems in 2025 use context-based NLP that detects unnatural language patterns. Recruiters who do receive keyword-stuffed resumes immediately reject them. Keep any single keyword below 2% of your total word count. If you're genuinely qualified, natural writing will include the right terms.

02

An unprofessional email address

PartyAnimal1999@hotmail.com is a real example from a real recruitment survey. Your email creates a first impression before a recruiter reads a single word of your experience. If your current address isn't [firstname.lastname@gmail.com], create one today. This is a 2-minute fix that removes an immediate rejection trigger.

03

Unexplained employment gaps

Post-pandemic, gaps are far more accepted — but unexplained gaps still raise questions. You don't need to apologise for a gap, but you should account for it. 'Career break for caregiving' or 'Freelance consulting (2 clients, details available)' or 'Professional development: completed AWS Solutions Architect certification' all give context and kill the anxiety recruiters feel when they see blank time.

04

Inconsistent date formatting

Mixing 'Jan 2022' in one section with '01/2022' in another signals poor attention to detail — the very quality most roles require. Recruiters notice immediately. Pick one format and use it everywhere. ATS systems also calculate your years of experience from these dates, so vague formats like 'Winter 2022' can cause the parser to assign you zero experience.

05

Third-person writing and personal pronouns

Writing 'John managed a team of 12...' or 'I delivered three products in one quarter' — both are wrong. Your resume is implicitly written about you. Start every bullet with a verb. Never use 'I', 'me', 'my', or third-person. Writing in third person makes over 40% of recruiters immediately toss an application.

06

Lying, exaggerating, or skills you can't deliver

Professional background checks, LinkedIn cross-referencing, and technical screens now catch nearly every resume lie. Exaggerating a skill and then failing a technical interview is career-damaging — recruiters talk. The risk/reward is entirely upside-down. Only list skills you can demonstrate under pressure. If caught quickly, the recruiter wonders what else you exaggerated.

07

AI-generated content that reads as AI-generated

In 2025, 77% of hiring managers can identify AI-written resume content on sight. The tells: repetitive phrasing, overly formal language, generic achievements without specific numbers, sentences that start with 'I am a results-oriented...' Use AI as a drafting tool, then rewrite every output in your own voice. Add your real numbers, your real context, your real language. The AI draft is the starting point — not the submission.

08

Not reading the job description properly

Job descriptions contain a hierarchy: requirements near the top are non-negotiable, requirements near the bottom are nice-to-haves. Most candidates read the title and skim the rest. Read the full description. Look for the 'must-have' language vs 'preferred' language. If a job requires 'Series B experience' or 'SOC 2 compliance knowledge' and you don't have it, tailoring alone won't save you — but calling it out honestly in a cover letter often will.

08 · Pre-submit checklist

Your pre-submit checklist

Run through this before you hit Apply on any application. Each item represents a real rejection trigger that costs qualified candidates interviews every day.

ATS & Formatting

Content

Keywords & Tailoring

Final check

🎯

Now apply what you've learned.
Build a resume that gets through.

FluidBright applies every principle on this page automatically — ATS-safe format, keyword analysis, STAR-guided writing, and real-time ATS scoring.

Free forever · No credit card · ATS score included