Step-by-step workflow
ATS optimization = clean parsing + job-aligned language + proof.
You can’t “hack” your way into an interview, but you can remove parsing friction and align your resume with the role’s requirements—without keyword stuffing.
Fastest reality test (MIT CAPD): Save your resume as a
.txt file (or paste into Notepad). If text is missing or out of order, fix formatting before touching keywords.Before you optimize (format first)
ATS-safe layout
- Single column
- No tables, text boxes, shapes, icons, or graphics
- Contact info in the document body (not header/footer)
- Standard headings: Summary, Skills, Experience, Education
Parsing failure causes (real ATS)
- Files that are too large (Greenhouse parsing fails above 2.5MB)
- Tables, headers/footers, columns
- Graphics/photos/word art
- Spaced-out letters (e.g., N A M E)
Step 1: Deconstruct the job description
Split the posting into three buckets:
Bucket A
Must-haves
Eligibility, certifications, core tools, minimum years.
Bucket B
Responsibilities
What you’ll actually do—often the real search/filter terms.
Bucket C
Preferred
Nice-to-have tools, domains, and methodologies.
Step 2: Extract keywords (must-have vs nice-to-have)
Keyword categories to capture
Title
Use the exact role name from the posting.
Hard skills
Tools, platforms, languages, systems.
Domain terms
Frameworks, compliance, product vocabulary.
Outcome language
Conversion, pipeline, latency, close cycle, retention.
Don’t guess synonyms. Match spelling from the JD. If you use acronyms, include the spelled-out version once (e.g., “Google Analytics 4 (GA4)”).
Step 3: Place keywords in high-signal sections
Zone 1
Headline + Summary
Target title + 2–4 core skills + domain.
Zone 2
Skills
Exact tool names, grouped (Languages / Tools / Platforms).
Zone 3
Experience bullets
Best zone: keywords + evidence + outcomes.
Step 4: Write proof bullets (not tasks)
Use this formula:
Proof bullet formula
Action + keyword/tool + what changed + metric + scope
Examples (copy the pattern)
Automated monthly close checks using Excel + Power Query, reducing reconciliation time by 22%.
Implemented CI/CD with GitHub Actions, cutting deployment time from 45 to 12 minutes and reducing rollback incidents.
Optimized SEO pages and internal linking, improving non-branded organic traffic by +18% in 90 days.
Step 5: QA (parser + human scan)
- Parser check: single column; no tables/columns/text boxes; contact info in the body.
- Plain-text test: paste into Notepad (or save as .txt) and verify nothing is missing or out of order.
- Keyword check: exact job title + top hard skills appear in Summary + Skills + bullets (truthfully).
- Human scan: top 2 wins are visible in the first half-page.
- Consistency: dates, titles, and company names are easy to read and consistent.
Sources
- Greenhouse Support: “Unsuccessful resume parse” (official parsing failure causes; 2.5MB parsing limit). View source
- MIT CAPD: “Make your resume ATS-friendly” (plain-text test; avoid tables/text boxes/graphics; avoid keyword spam). View source