Smart Mock Interview Logo
Get Started
Back to All Posts
Beat the ATS: Resume Formatting That Actually Works in 2025
Interview Tips

Beat the ATS: Resume Formatting That Actually Works in 2025

S

Smart Mock Interview

Table of contents

  1. What ATS actually does (and doesn’t)
  2. The formatting rules that still matter in 2025
  3. Structure: the safest section order
  4. Keywords (without keyword stuffing)
  5. Numbers > adjectives: impact bullets that parse and persuade
  6. Skills & tools: where and how to list them
  7. File format, naming, and metadata
  8. Common formatting pitfalls to avoid
  9. Before/after examples
  10. Copy-paste ATS-safe resume template
  11. Final pre-submission checklist
  12. How SmartMockInterview can help

1) What ATS actually does (and doesn’t)

Does:

  • Parses your file into text fields (name, headings, dates, employers, skills).
  • Indexes keywords and phrases from the job description.
  • Ranks candidates on “match” signals (keywords, seniority, tenure, recency).

Doesn’t:

  • Judge design aesthetics.
  • Understand icons, images, or text inside shapes.
  • Read intent between the lines—if it’s not written plainly, it’s invisible.

Goal: Make your resume easy to parse and easy to score.

2) The formatting rules that still matter in 2025

  • Font: Calibri, Arial, Helvetica, Verdana, or Times New Roman. 10.5–12 pt for body; 13–16 pt for headings.
  • Color & styling: Black text, minimal bold for headings/company/job titles. Avoid underlines except links.
  • Layout: Single column. No text boxes, tables, columns, headers/footers for core content.
  • Bullets: Use simple round bullets (•) or hyphens (-).
  • Dates: Use a consistent format, e.g., Jan 2022–Aug 2025. Include months.
  • Spacing: 0.5–1.0 line spacing; 0.5–1 inch margins.
  • Length: 1 page if <7–8 years’ experience; 2 pages acceptable for senior roles.
  • File size: Keep under ~1–2 MB.

3) Structure: the safest section order

  1. Name & Contact (top, plain text)
    • Name | City, Country | Email | Phone | LinkedIn | Portfolio/GitHub (if relevant)
  2. Professional Summary (2–4 lines; target the role title + 3–5 relevant keywords)
  3. Skills (grouped by category; see Section 6)
  4. Experience (reverse chronological; each role with 3–6 quantified bullets)
  5. Projects (optional but powerful; especially for career switchers/tech roles)
  6. Education & Certifications (include relevant certs and dates)
  7. Optional: Awards, Publications, Volunteering (only if relevant)

4) Keywords (without keyword stuffing)

How to find them:

  • Read the job description. Highlight repeated nouns (e.g., “stakeholder management,” “SQL,” “OKRs,” “Kubernetes,” “B2B SaaS”).
  • Capture variants/synonyms (e.g., “Excel” and “Microsoft Excel”; “OKRs” and “Objectives & Key Results”).

Where to place them:

  • Summary (role title + 3–5 core competencies).
  • Skills section (grouped; see below).
  • Experience bullets (contextual usage beats a raw list).
  • Project descriptions.

Golden rule: Use the employer’s phrasing at least once. If they say “customer success,” don’t only say “client success.”

5) Numbers > adjectives: impact bullets that parse and persuade

Bullet template:
Action verb + what you did + how + impact (quantified) + tool/keyword.

Examples:

  • “Reduced onboarding time 37% by building a playbook and self-serve help center in Notion, lowering support tickets per new user from 14 to 9.”
  • “Delivered £1.2M in annual savings by renegotiating vendor contracts and implementing usage-based pricing.”
  • “Cut average query runtime from 12s to 2.5s by adding indexes and rewriting SQL joins, enabling daily BI dashboards.”

Quantify even when data is fuzzy: use ranges, ratios, or frequency (“served 40–60 customers/week,” “met 100% of SLAs for 3 consecutive quarters”).

6) Skills & tools: where and how to list them

Do:

  • Group by type: Languages, Frameworks, Cloud/DevOps, Data, PM/Methodologies, CRM/Tools.
  • Keep to 12–24 total; prioritize what the JD demands.
  • Indicate seniority subtly (e.g., Advanced: SQL, Python | Working: dbt, Airflow).

Don’t:

  • Use “skill bars” or star ratings—ATS ignores visuals and humans distrust them.
  • Bury skills only in job bullets; also list them explicitly in the Skills section.

Example snippet:

Skills — Languages: Python, SQL; Frameworks: React, Node.js; Data: Snowflake, dbt; Cloud: AWS (Lambda, S3, ECS); Methods: Agile/Scrum, OKRs; Tools: Jira, Looker, Fivetran.

7) File format, naming, and metadata

  • When the posting is silent: DOCX is the safest for parsing.
  • If they explicitly ask for PDF: provide PDF—but also keep a DOCX on hand.
  • File name: Firstname-Lastname-Role-Company.docx (e.g., Aisha-Khan-Product-Manager-Fintech.docx).
  • Document properties (optional bonus): set Title and Subject to your role + keywords.

8) Common formatting pitfalls to avoid

  • ❌ Images, logos, icons (including phone/email icons)
  • ❌ Text inside tables, shapes, columns, or headers/footers
  • ❌ Fancy bullets, emojis, special symbols (✓, ★, ●●●)
  • ❌ Overdesigned templates with sidebars and color blocks
  • ❌ Multiple columns that break reading order
  • ❌ Hyperlink-only contact info without the visible text (include the full text and make it a link)

9) Before/after examples

Weak bullet (vague):

Managed onboarding for new customers.

ATS-smart, impact-driven:

Cut new customer time-to-first-value from 10 to 6 days by launching a guided onboarding and automated product tours (Pendo), improving activation rate from 42% to 58%.

Weak bullet (buzzwords only):

Data-driven leader with strong communication skills.

ATS-smart, evidence-based:

Led weekly KPI reviews with Sales, rebuilt SQL funnel queries to remove double-counting, and produced a Looker dashboard used by 45+ stakeholders, reducing reporting disputes by 80%.

10) Copy-paste ATS-safe resume template

Tip: Keep this single-column. Replace ALL CAPS labels. Do not add tables or sidebars.