ATS Resume Guide: Pass the Bots, Win the Human Read

By Diane Pruett, Lead Career Strategist · Updated June 26, 2026 · ~38 min read

What an ATS actually does

An applicant tracking system is the software that receives, stores, and organizes the applications a company gets. Its core job is mundane: take your file, pull the text out of it, and slot that text into structured fields (name, contact details, work history, job titles, dates, skills, education) so a recruiter can search and sort the pile later. Think of it as a filing clerk with a database behind it, not a bouncer at a velvet rope. When a recruiter searches "registered nurse" plus "telemetry" plus "BLS certified," the ATS returns the candidates whose parsed text contains those strings. That's the whole mechanism for the overwhelming majority of systems most companies run.

The persistent myth is that a robot reads your resume, assigns it a score out of 100, and silently auto-rejects anything below a threshold. A handful of high-volume employers do use knockout questions ("Do you have a valid driver's license?" "Are you authorized to work in this country?") and some use ranking features. But the idea that 75% of resumes are "rejected by the bots before a human sees them" is a stubborn piece of internet folklore with no credible source behind it. In reality, the vast majority of resumes that reach an ATS are seen by a person. The software decides how cleanly and findably your information shows up, not whether you deserve the job.

That distinction changes everything about how you should write. You are not trying to trick an algorithm or hit a secret quota of buzzwords. You have two concrete jobs. First, make sure the parser extracts your text accurately and files it in the right fields, so you appear in the searches you should appear in. Second, make sure that when a busy recruiter pulls you up, spending six to eight seconds on a first pass, they can instantly see why you fit. Nail both and the "ATS problem" mostly evaporates. The rest of this guide is a practical method for doing exactly that, section by section, with templates you can copy.

ATS myths that cost people interviews

Before the tactics, clear out the bad advice, because most of what circulates online is either outdated or invented, and acting on it actively hurts you. Here are the myths our strategists debunk most often, and what's true instead.

The format that parses clean

Formatting is where the most interviews are quietly lost, not because the content was weak, but because the parser scrambled it or the recruiter couldn't scan it. The good news: the safe format is also the format humans prefer. You don't trade beauty for function; the disciplined version is simply better on both counts. Here are the rules that decide whether you parse cleanly, in order of how often they matter.

1. One column, always

Two-column templates — a slim sidebar of skills and contact details beside a wide main column — look elegant on screen. But many parsers read the page left-to-right across the full width, line by line. When they hit a row that spans both columns, your sidebar text gets interleaved into your job history, and the output is a scrambled mess: "Skills: SQL Senior Analyst Tableau Northwind Corp Python led a team of…". Stack everything in a single column, top to bottom, and the parser reads it in the order you intended. This one change prevents more parsing disasters than any other.

2. Standard, recognizable section headings

Parsers map your content to fields by recognizing conventional labels. Use "Work Experience" (or "Professional Experience"), "Education," "Skills," "Certifications," and "Summary." Do not get creative with "Where I've Made My Mark" or "My Journey So Far," because a parser doesn't know those mean "experience," so it dumps the content into a generic bucket or drops it from the searchable fields entirely. Save your voice for the bullets; keep the headings boring and machine-legible.

3. Real text, never images

Everything that matters must be selectable text. A name rendered inside a logo, a skills bar chart, a rating of "★★★★☆ Excel," or an entire resume exported as a PNG from a design tool contains zero machine-readable text, so the parser sees a blank where your qualifications should be. The simplest test in the world: open your resume and try to highlight your name and a few skills with your cursor. If you can't select it as text, the ATS can't read it. Skip graphics, icons, progress bars, photos, and decorative charts entirely.

4. Standard fonts, simple structure

Use a common, legible font — system sans-serifs and the classic serifs are all safe. Sizes between 10.5 and 12 points for body text, a little larger for your name and headings. Use real bullet characters from your word processor, not hand-typed asterisks or wingding symbols. Avoid tables for layout (they parse unpredictably), text boxes (often skipped), and putting contact details in the page header or footer region, which some parsers ignore. Keep your name, email, phone, city/state, and LinkedIn URL as plain text lines in the body at the very top.

Keyword strategy: match, don't stuff

Keywords are where good intentions turn into desperate-looking resumes. The principle is simple and the execution is disciplined: mirror the genuine, concrete terms from the posting, and prove each one inside a real accomplishment. Recruiters and the search filters they run look for specific strings: the hard skills, tools, certifications, methodologies, and job titles named in the job description. If the role says "Kubernetes," write "Kubernetes," not "container orchestration platform." If it says "project management," use that exact phrase somewhere true. The search box matches literal text, so the literal text needs to be present.

How to extract the right keywords

1. Read the posting twice. First for fit, then with a highlighter. Mark every hard skill, tool, certification, methodology, and the exact job title.
2. Sort into must-haves and nice-to-haves. Terms in the "Requirements" or "Qualifications" section and repeated terms are the must-haves. Prioritize those.
3. Pull 8–12 concrete terms. Focus on nouns a recruiter would actually type into a search: "SQL," "HIPAA," "Salesforce," "GAAP," "Series 7," "ICU," "Figma," "demand forecasting."
4. Confirm you genuinely have each one. Never list a skill you can't speak to in an interview. A keyword you can't defend is a trap, not an advantage.
5. Place each term where it's true. Put it in a skills line for coverage and inside a bullet that shows you using it for a result.

The exact-match details that trip people up

Parsers and search filters are often literal to a fault. Spell out an acronym and include the acronym — "Search Engine Optimization (SEO)" — because a recruiter might search either. Match the posting's word form: if it says "managed," having "management" elsewhere is fine, but make sure the literal requirement phrase appears. Watch British vs. American spelling ("optimisation" vs. "optimization") and mirror the posting. And use the employer's job title, not your company's quirky internal one: if you were a "Growth Ninja" but the market calls it "Marketing Manager," lead with the standard title and note the internal one in parentheses if you like.

The reliable method, then, is this: pull the eight to twelve concrete skills from the description, verify you truly have them, and weave each into a bullet that shows the result. "Cut deployment time 40% by automating our Kubernetes rollout pipeline" beats a lonely "Kubernetes" floating in a skills blob, because it satisfies the filter and proves the skill to the human. Coverage plus evidence — that's the whole game.

Section-by-section breakdown

Here's exactly what each part of the resume should contain, in the order it should appear, with the parsing and human-reading goals for each. This is the skeleton every template later in the guide is built on.

Contact header

Plain text at the very top of the body, never in the document's header/footer region. One line for your name (largest text on the page), then a line with city and state (no full street address needed), phone, professional email, and your LinkedIn URL written out. Skip the headshot, date of birth, and marital status in most markets; they invite bias and add no parseable value. If you have a portfolio or GitHub relevant to the role, include the full URL.

Professional summary (3–4 lines)

A short paragraph, not an "Objective." State who you are, your years and area of experience, two or three of your strongest relevant skills, and one headline result. This is prime real estate for the exact job title and top keywords, and it's the first thing the recruiter reads. Example: "Senior data analyst with 6 years turning messy data into decisions for fintech teams. Expert in SQL, Tableau, and demand forecasting; built a churn model that cut attrition 18%."

Skills

A compact, comma-separated list of hard skills and tools, the keyword anchor of the resume. Group sensibly if long (e.g., "Languages: …", "Tools: …"). Keep it to genuine, role-relevant capabilities; this is not the place for "team player." Twelve to twenty concrete skills is plenty. Every important keyword here should also appear, proven, in your experience bullets.

Work experience

The heart of the resume, in reverse-chronological order (most recent first). For each role: job title, company, location, and dates ("Mar 2022 – Present") on a clear line, then three to six accomplishment bullets. Lead with impact, not duties. Use the employer-standard job title. Include enough context that a recruiter understands scope (team size, budget, region, scale) without a wall of text. We'll drill into bullet-writing in the next section.

Education

Degree, institution, and graduation year (or expected year). New grads put this near the top; experienced professionals put it after experience. List relevant coursework, honors, or GPA only if it strengthens your case or you're early-career. Don't list high school once you have a degree.

Optional sections that earn their place

• Certifications & licenses — critical in regulated fields (nursing, finance, IT security). List the exact credential name and the issuing body; these are high-value search terms.
• Projects — gold for career changers, new grads, and technical roles. Treat each like a mini-job with a result.
• Publications / patents / speaking — for academic, research, and senior technical profiles.
• Languages — list the language and proficiency level when relevant to the role or market.

Writing bullets a human will read

Once you parse cleanly, the resume still has to win a human skim. This is where most resumes are dull and forgettable, a list of duties that could describe anyone in the role. The fix is a repeatable formula and a relentless focus on results.

The accomplishment formula

Every strong bullet has the same bones: strong verb + what you did + quantified result (+ how). Lead with an action verb, name the concrete thing you did, and attach a number that shows the impact. The number is what separates a memorable bullet from wallpaper.

Find a number for everything

"But my work isn't measurable" is almost never true. If you don't have a clean metric, quantify scope, frequency, or scale: how many people, how often, how large, how fast, what percent, what rank, against what deadline. "Resolved customer issues" becomes "Resolved 60+ customer tickets per week while maintaining a 95% satisfaction score." Even soft contributions have shape: "Onboarded and mentored 5 junior hires, three of whom were promoted within a year."

Strong verbs to start bullets

Rotate among precise verbs and avoid repeating the same one: Led, Built, Launched, Drove, Cut, Grew, Designed, Orchestrated, Negotiated, Streamlined, Delivered, Scaled, Reduced, Increased, Rebuilt, Owned, Spearheaded, Resolved, Forecasted, Secured. Avoid limp openers like "Responsible for," "Helped with," "Worked on," and "Tasked with," because they describe presence, not impact.

Before & after rewrites

Principles stick when you see them applied. Below are real-pattern rewrites — the kind of fixes our strategists make every day — showing how a flat, duty-listing resume becomes a sharp, parseable, results-led one.

Example 1 — Customer support specialist

What changed: standard heading and a real dated title for the parser; duties became quantified accomplishments for the human; "Customer Support Specialist" mirrors the posting's title.

Example 2 — Career changer (teacher → project coordinator)

What changed: a summary reframes transferable skills in the target role's language ("coordinated," "stakeholders," "managed budget"); custom heading replaced with standard ones; vague traits became evidence.

Example 3 — Software engineer

What changed: "various technologies" became named, searchable keywords (Go, Python, Redis, Kubernetes); generic tasks became quantified engineering outcomes the recruiter's filter and a hiring manager both reward.

Copy-paste resume templates

Here are three ATS-safe skeletons you can copy directly into a blank document and fill in. They're single-column, standard-headed, plain-text-friendly, and ordered for both the parser and the human. Replace the bracketed prompts with your details, keep the structure, and you're 80% of the way there.

Template A — Experienced professional

[FULL NAME]
[City, ST] · [Phone] · [professional@email.com] · linkedin.com/in/[handle]

PROFESSIONAL SUMMARY
[Title] with [X] years in [field]. Expert in [skill 1], [skill 2],
and [skill 3]. [One headline result with a number].

SKILLS
[Skill], [Skill], [Skill], [Tool], [Tool], [Methodology], [Cert],
[Skill], [Skill], [Skill], [Tool], [Skill]

WORK EXPERIENCE
[Job Title] — [Company], [City, ST]            [Mon Year – Mon Year]
- [Verb] [what you did], [quantified result]
- [Verb] [what you did], [quantified result]
- [Verb] [what you did], [quantified result]

[Job Title] — [Company], [City, ST]            [Mon Year – Mon Year]
- [Verb] [what you did], [quantified result]
- [Verb] [what you did], [quantified result]

EDUCATION
[Degree], [Major] — [Institution]                          [Year]

CERTIFICATIONS
[Exact credential name] — [Issuing body], [Year]

Template B — New grad / early career

[FULL NAME]
[City, ST] · [Phone] · [professional@email.com] · linkedin.com/in/[handle] · github.com/[handle]

SUMMARY
[Degree] graduate seeking [target role]. Skilled in [skill 1],
[skill 2], [skill 3]. [Strongest project or internship result].

EDUCATION
[Degree], [Major] — [University], [City, ST]               [Year]
Relevant coursework: [Course], [Course], [Course]
[Honor / GPA if 3.5+]

SKILLS
[Skill], [Skill], [Tool], [Tool], [Language], [Framework], [Skill]

PROJECTS
[Project Name] — [Tech used]                               [Year]
- [Verb] [what you built], [result or scale]
- [Verb] [what you built], [result or scale]

EXPERIENCE
[Role / Internship] — [Company], [City, ST]    [Mon Year – Mon Year]
- [Verb] [what you did], [quantified result]
- [Verb] [what you did], [quantified result]

Template C — Career changer

[FULL NAME]
[City, ST] · [Phone] · [professional@email.com] · linkedin.com/in/[handle]

SUMMARY
[Transferable identity] moving into [target role]. [X] years of
[transferable strength] in [prior field]. Proven in [target-role
skill 1], [skill 2], and [skill 3].

SKILLS
[Target-role skill], [Transferable skill], [Tool], [Skill],
[Cert in progress], [Skill], [Tool], [Skill]

RELEVANT EXPERIENCE
[Prior Title, reframed] — [Company], [City, ST]  [Mon Year – Mon Year]
- [Verb] [achievement framed in target-role language], [number]
- [Verb] [achievement framed in target-role language], [number]

ADDITIONAL EXPERIENCE
[Title] — [Company]                            [Mon Year – Mon Year]
- [Verb] [achievement], [number]

EDUCATION & TRAINING
[Degree] — [Institution]                                   [Year]
[Bootcamp / course / certification toward new field]       [Year]

The 12 most common ATS-resume mistakes

These are the errors we see most often when a member's self-built resume isn't landing interviews. Each one is quick to fix once you know to look.

1. Two-column layouts and sidebars that scramble when parsed. Go single-column.
2. Creative section headings the parser can't map. Use standard labels.
3. Skills as graphics — bar charts, star ratings, icons — that contain no readable text. Use a text list.
4. Contact info in the header/footer region, which some parsers skip. Put it in the body.
5. Duties instead of accomplishments. Lead with results and numbers.
6. No keywords from the posting, so you never surface in searches. Mirror the genuine terms.
7. Keyword stuffing / white text, which reads as deceptive. Match and prove instead.
8. Quirky internal job titles ("Growth Ninja") no recruiter searches for. Use the standard title.
9. Saving as an image, .pages, or scanned PDF. Use a text-based PDF or .docx.
10. Typos and inconsistent date formats that confuse parsers and signal carelessness. Proofread.
11. A generic resume sent to every job. Tailor the summary, skills, and top bullets each time.
12. Walls of text with no white space. Use bullets, clear headings, and breathing room.

File type, naming & the apply form

Two practical details decide whether your perfectly formatted resume even arrives intact.

PDF vs. .docx

A text-based PDF exported from a word processor is safe for essentially every modern ATS and preserves your layout for the human reader, so it's the right default. Use .docx when the application form specifically asks for Word, or when you know the employer uses an older system. Never submit a scanned PDF, an image export (.jpg/.png), an Apple Pages file, or anything where the text isn't selectable. When in doubt, follow the posting's instructions to the letter; doing what's asked is itself a screening signal.

File naming

Save the file as Firstname-Lastname-Resume.pdf. It's instantly clear to the human downloading a folder of fifty applications, and it looks professional. Avoid "resume-final-v7-REALLY-final.pdf" and version numbers.

The application form itself

Many systems auto-fill fields from your parsed resume and then ask you to confirm, which is your chance to fix any field the parser got wrong. Don't leave required fields blank, answer knockout questions honestly and completely, and if there's a free-text "why this role" box, use it briefly and specifically. If you can paste plain text, that pasted version is exactly what the parser sees, so make sure it reads cleanly.

Tailoring without rewriting everything

Tailoring every application sounds exhausting, but it's the single highest-return habit in a job search, and it's faster than it looks once you have a strong base resume. The trick is that you only adjust three things per role.

1. The summary. Swap in the exact target job title and the two or three skills the posting emphasizes most. Two minutes.
2. The skills line. Reorder and lightly edit so the must-have terms from this posting appear and lead. One minute.
3. The top two or three bullets of your most relevant role, so the accomplishments that matter most to this employer are read first. Five minutes.

That's roughly an eight-minute tailoring pass that dramatically improves both keyword match and human relevance, without rebuilding the resume. Keep a master resume with every accomplishment, then cut and reorder for each role rather than writing from scratch. This per-role tailoring is exactly the work a managed job search takes off your plate — a Marqee strategist tailors materials for every application and submits on your behalf, which is how members go from a trickle of replies to a steady flow of interviews.

How ATS systems differ — and why "one ATS hack" is a myth

People talk about "the ATS" as if it were a single program with one secret rulebook. It isn't. Dozens of different systems are in use, and a given employer's setup depends on their size, industry, and how their recruiters configure it. That's precisely why universal "tricks" don't work, and why the durable strategy is clean text plus honest keywords, which wins across all of them. Understanding the rough categories helps you stop chasing hacks and write for the common denominator.

Notice that every row points back to the same two fundamentals: parse clean, and match the genuine terms. There is no employer type where two-column graphics, invisible keywords, or a quirky title helps you. Build one disciplined resume and it travels everywhere.

How to quantify achievements when "nothing is measurable"

The most common objection to results-led bullets is "my job doesn't have numbers." Almost every role does, and you just have to know where to look. The goal isn't to invent precision you don't have; it's to add honest scope and scale so a recruiter can picture the size and impact of your work. Here are the four families of metrics, with prompts to mine your own history.

The four metric families

• Money — revenue influenced, costs cut, budget owned, savings generated, deals closed. "Managed a $1.2M budget"; "cut vendor spend 14%."
• Time — faster, sooner, on deadline, frequency. "Reduced onboarding from 3 weeks to 8 days"; "shipped weekly."
• Volume / scale — how many people, customers, tickets, transactions, locations, square feet, data. "Served 4M daily requests"; "supported 120 staff across 6 sites."
• Quality / outcome — satisfaction, error rate, retention, ranking, promotion, compliance. "Lifted CSAT to 4.8/5"; "cut defects 30%."

Mine your past roles with three questions: How much? How many? Compared to what? If you genuinely can't get an exact figure, an honest estimate framed as approximate ("~50 tickets/week," "roughly 30% faster") is far stronger than a vague duty — just never fabricate. The point is to give the reader scale, not false precision.

Special cases: gaps, changes, relocation and visas

Real careers aren't tidy. Here's how to handle the situations that worry people most — in a way that parses cleanly and reassures the human, without over-explaining.

Employment gaps

Use plain year ranges in your dates; parsers handle them fine. If a gap is long, name it briefly and without apology — "Career break (caregiving), 2024–2025" as a short dated entry, or one calm line in your summary. Recruiters see gaps constantly; a confident, honest framing beats a suspicious blank. For more, see our guide on telling a credible career story.

Career changes

Lead with a summary that states your target role in its own language, then reframe past accomplishments using the target field's vocabulary (as in Template C above). Group your most relevant experience first under a "Relevant Experience" heading if a strictly chronological order buries your best fit. Add bridging credentials — a course, certification, or project — to show momentum toward the new field.

Relocation and remote roles

If you're targeting a city you don't live in yet, you can list the target metro with "(relocating)" or simply your current city plus a line in the summary stating your openness to relocate or work remotely. Don't fabricate a local address. For remote roles, make "remote" presence explicit so you surface in those searches.

Visa and international candidates

Use the standard, locally recognized job titles and spellings for the market you're applying to, and translate credentials into their local equivalents where helpful. Keep work authorization statements honest and answer authorization knockout questions accurately. Our guidance for visa and international talent goes deeper on visibility and access.

Beyond the resume: keep your story consistent

Your resume doesn't apply in a vacuum. Recruiters cross-check it against your LinkedIn and any cover letter, and parsers index those too. Consistency is its own ranking and trust signal.

• LinkedIn parity. Your job titles, employers, and dates should match your resume exactly. Mismatches read as red flags and can cost you a callback. Mirror your strongest keywords in your headline and About section — LinkedIn is itself a searchable database recruiters mine. See our personal branding guide.
• Cover letters. When asked, keep it short, specific, and keyword-aware without repeating the resume verbatim. Name the role, show you understand the problem, and connect one or two proof points.
• Consistent entity details. Same name spelling, same contact info, same title conventions everywhere. It helps both human trust and the systems that index you.

This whole-search consistency is part of what a Marqee strategist manages end to end: aligning your resume, profile, and outreach so every surface tells the same strong story. Combine it with interview preparation and you're not just passing the ATS, you're built to convert the interviews it leads to.

The 7-minute pre-submit checklist

Run this before every application. It's the same parse-then-read discipline our strategists apply to every resume before we submit on a member's behalf.

• Paste test. Copy all the text from your resume into a blank document. If anything is out of order, missing, or scrambled, the parser sees it that way too — fix the layout.
• Contact check. Name, email, phone, and city/state are plain text at the top of the body — not in a header, footer, or text box.
• Keyword sweep. Cross off each must-have skill from the posting against your skills line and bullets. Add any genuine ones you missed.
• Title match. Your most relevant role uses the standard, searchable job title.
• Numbers present. Every top bullet has a metric — percent, count, dollar, or time.
• One/two pages. One page under ten years' experience, two beyond; strongest material in the top third.
• File & name. Saved as a text-based PDF (or .docx if asked), named Firstname-Lastname-Resume.pdf.

The systems are not your enemy — sloppy formatting is. Get the parse right and the keywords honest, then let your accomplishments do the convincing. If you'd rather not run this on every application yourself, that's the entire point of Marqee: real career experts find the roles, tailor your materials per posting, run recruiter outreach, discover warm referrals, and submit on your behalf — so you stop applying and start interviewing. Explore our resume optimization service, see real member results, or browse more in the guides library and blog.

A full worked example: posting to tailored resume

Let's put the whole method together on one realistic posting. Seeing the moves in sequence makes them stick — and you can run the identical process on any job you apply to.

Step 1 — The posting (excerpt)

Marketing Manager — DTC Brand
We need a Marketing Manager to own paid acquisition and lifecycle.
Requirements:
- 4+ years in growth or performance marketing
- Hands-on with Meta Ads, Google Ads, and email (Klaviyo)
- Strong in SQL and analytics; comfortable with A/B testing
- Experience managing a budget and reporting on ROAS/CAC
- Bonus: managed an agency or junior marketer

Step 2 — Extract the genuine keywords

Highlighting the concrete, searchable terms gives us: Marketing Manager, performance marketing, Meta Ads, Google Ads, email, Klaviyo, SQL, analytics, A/B testing, budget, ROAS, CAC, agency management. Each is a noun or phrase a recruiter could type into a search. We confirm we truly have each one before using it.

Step 3 — Write the tailored summary

The tailored version states the exact target title and folds in seven of the posting's must-have terms (naturally, because they're all true) and lands a headline result.

Step 4 — Build the skills line and prove it in bullets

SKILLS
Meta Ads, Google Ads, Klaviyo, SQL, A/B testing, lifecycle email,
ROAS/CAC analysis, budget management, Looker, agency management

EXPERIENCE
Senior Growth Marketer — Lumen DTC, Austin, TX     2021 – 2026
- Scaled Meta and Google Ads from $40k to $115k/mo while improving
  blended ROAS from 2.1x to 3.6x through weekly A/B testing
- Rebuilt Klaviyo lifecycle flows, lifting email revenue 44% and
  cutting CAC 19% across 8 lifecycle journeys
- Managed a $1.4M annual budget and a contracted creative agency,
  reporting ROAS/CAC to leadership in a weekly SQL-backed dashboard

Every must-have keyword now appears and is proven inside a quantified accomplishment. The parser finds the strings; the hiring manager sees the impact. That's a tailored, ATS-ready, human-winning resume — produced in well under fifteen minutes from a strong base.

The phrasing library: words that work (and words to cut)

Small word choices change how strong a bullet reads. Keep this library beside you while you write.

Strong action verbs by purpose

Phrases to cut on sight

• "Responsible for…" → name the action: "Led," "Owned," "Built."
• "Helped with…" / "Assisted with…" → state your specific contribution and its result.
• "Worked on…" → say what you produced and the outcome.
• "Duties included…" → delete entirely; lead with an accomplishment.
• "Team player," "hard worker," "detail-oriented" → unprovable adjectives; show them through results instead.
• "Synergy," "go-getter," "results-driven" as filler → replace with an actual result.

Advanced parsing edge cases

For the perfectionists, and for anyone whose clean-looking resume still seems to parse oddly, here are the subtler traps and how to avoid them.

• Special characters and ligatures. Fancy bullet glyphs, em-dashes inside dates, and decorative dividers can occasionally garble. Stick to standard bullets and simple hyphens or en-dashes in date ranges.
• Dates the parser can read. Spell months ("Jan 2022 – Mar 2026") rather than relying on "’22–’26." Use "Present" for current roles. Consistent formatting across every entry helps the parser compute tenure.
• Acronym + spelled-out pairs. Include both forms once — "Certified Public Accountant (CPA)" — so either search term matches.
• Tables for content. Even single-column resumes sometimes hide skills inside an invisible table grid; some parsers read table cells out of order. Lay out skills as plain comma-separated text lines instead.
• Headers, footers, and text boxes. Contact details and key text placed in the document's header/footer region or inside a floating text box may be skipped. Keep everything important in the main body flow.
• Hyperlinks. Write the visible URL ("linkedin.com/in/yourname") rather than hiding it behind linked text like "click here," so the address survives as readable text.
• Multiple columns of dates. Right-aligning dates with tabs is fine; using a separate column or table for them is where order can scramble. Test with the paste check.

The universal safety net for all of these is the paste test from the checklist: copy your resume into a blank document and read it top to bottom. If it reads cleanly to you as plain text, it will to the parser too. That single five-second habit catches nearly every edge case above.

Frequently asked questions