Why I Reject Resumes with Perfect Formatting Sometimes

POLISH OVER PROOF — READ AS A REVIEWER:

I open the resume. It's beautiful:
- A two-column template
- A skill bar chart (Python 90%,
  SQL 85%, AWS 75%)
- An icon for every section
- A professional photo

Then I read the bullets:
• "Responsible for data pipelines"
• "Worked on the cloud migration"
• "Helped with dashboards"

What I think:
- "This is a template."
- "The skill bars are self-assessed
  and meaningless."
- "There's no evidence anywhere."
- "The polish is covering for the
  substance."

Verdict: rejected.

What the formatting hides:
❌ No numbers: pipelines, migration,
  dashboards — how many?
❌ No ownership: "responsible for,"
  "worked on," "helped with"
❌ No outcomes: what changed?
❌ The skill bars are a guess, not a
  measurement

What I do next:
- I don't ask for an interview.
- I don't try to read past the template.
- I move to the next resume.

Why it's rejected:
- The formatting is doing the work
  the evidence should do
- A beautiful resume with no numbers
  is a brochure, not a case
- The polish signals effort, not skill

ATS FIGHT — READ AS A REVIEWER:

The resume arrives as a beautifully
designed PDF:
- A two-column layout
- Text in tables
- Icons for contact info
- A graphic header

What the ATS sees:
- "John Doe" as an image, not text
- Skills scattered across columns
- Dates parsed incorrectly
- The job title missing from the
  extracted text

What I think:
- "I can't find the job title."
- "The skills section is fragmented."
- "The dates don't match the roles."
- "I'll have to reject this on
  parse quality."

Verdict: rejected before the human
sees it.

What the formatting hides:
❌ The ATS can't parse tables
❌ The ATS can't read icons
❌ The ATS can't read text in images
❌ The ATS can't follow two-column
  layouts

What I do next:
- The candidate never reaches a human.
- The formatting worked against them.

Why it's rejected:
- The ATS is the first reader
- A beautiful design that the ATS
  can't parse is a rejection
- Substance plus ATS-safe formatting
  beats beauty alone

HIDES THE NUMBER — READ AS A REVIEWER:

The resume is beautifully formatted.
Every bullet is the same length, the
same font, the same indentation.

• "Built data pipelines for the analytics
  team."
• "Managed cloud infrastructure."
• "Created dashboards for stakeholders."

What I notice:
- The formatting is so even that
  nothing stands out.
- There's no number to stop on.
- Every bullet is the same weight.

What it hides:
❌ How many pipelines? 3? 300?
❌ How much infrastructure?
❌ How many dashboards? For how many
  stakeholders?
❌ What changed because of them?

What I do next:
- I skim for 6 seconds.
- I find nothing to score.
- I move on.

The fix — put a number in every bullet:
• "Built 14 Airflow pipelines feeding
  3 analytics dashboards, cutting
  report latency from 6 hours to 20
  minutes."
• "Managed 240 pods across 6 EKS nodes,
  cutting cloud spend 18%."
• "Built 8 executive dashboards in
  Looker, used weekly by 40 stakeholders."

Why the fix works:
✅ The number stops the eye
✅ The outcome shows impact
✅ The formatting serves the evidence

HIDES OWNERSHIP — READ AS A REVIEWER:

The resume uses a consistent bullet
format: past-tense verb, object, period.
Every bullet looks identical.

• "Responsible for the data warehouse."
• "Worked on the migration."
• "Participated in code reviews."
• "Led the team."

What I notice:
- "Led the team" looks exactly the same
  as "Participated in code reviews."
- The formatting hides the difference
  in seniority.
- I have to read every bullet to find
  the one that shows ownership.

What it hides:
❌ "Responsible for" is a duty, not an
  ownership story
❌ "Worked on" is a task, not a result
❌ "Participated" is a passenger role
❌ "Led" is the only ownership bullet —
  and it's buried

What I do next:
- I ask: "What did you specifically
  own?"
- If the candidate can't answer, the
  resume goes in the reject pile.

The fix — make ownership the bullet:
• "Owned the data warehouse migration:
  42 tables, 6 upstream sources, zero
  downtime over 3 weekends."
• "Led the code review process for 4
  services; cut production bugs 34%."
• "Mentored 2 junior engineers;
  both promoted within 12 months."

Why the fix works:
✅ Ownership is named
✅ The number makes it specific
✅ The outcome shows impact

EVIDENCE FIRST — READ AS A REVIEWER:

Before formatting, the candidate writes:

"Built 14 Airflow pipelines feeding 3
dashboards. Cut report latency from 6
hours to 20 minutes. Used 2.4TB/day."

Then formats it:
**Built 14 Airflow pipelines** feeding 3
dashboards.
Cut report latency from **6 hours to 20
minutes**.
Processed **2.4TB/day**.

What I notice:
- The number is bolded, so my eye stops
  there.
- The bullet has a verb, a number, and
  an outcome.
- The formatting serves the evidence.

What it fixes:
✅ The number is the first thing I see
✅ The outcome is specific
✅ The formatting makes the evidence
  easier to read

What I do next:
- I score the bullet.
- I read the next one.
- The resume moves to the shortlist.

Why the fix works:
- The evidence is written before the
  formatting
- The formatting highlights the evidence
- The reviewer can score the bullet
  in 2 seconds

FORMAT FOR ATS — READ AS A REVIEWER:

Before formatting, the candidate checks:

1. Is it a single column?
   ✅ Yes — no two-column layout.

2. Are the headings standard?
   ✅ Yes — Experience, Education, Skills.

3. Is the text selectable?
   ✅ Yes — no text in images.

4. Are there tables or icons?
   ✅ No — plain text.

5. Does the file name match the convention?
   ✅ Yes — Firstname_Lastname_Role.pdf.

What the ATS sees:
- The job title, parsed correctly
- The skills, extracted
- The dates, matched to the roles
- The education, in the right section

What I notice:
- The resume parses cleanly.
- The formatting is plain, but the
  content reaches me.
- The evidence is there.

What it fixes:
✅ The ATS can parse the resume
✅ The candidate reaches a human
✅ The plain formatting doesn't hurt

Why the fix works:
- The ATS is the first reader
- Plain, ATS-safe formatting gets the
  resume through
- The evidence does the rest

The rule:
- Format for the ATS, not for the
  gallery
- Substance first, style second
- Plain can be strong

Resume Substance Checklist:

BEFORE YOU FORMAT, CHECK THE SUBSTANCE:
☐ Every bullet has a number
☐ Every bullet has an ownership verb
☐ Every bullet has an outcome
☐ The strongest bullet is first
☐ The summary names the role and a
  number
☐ The skills list is 12–15 items, aligned
  with the JD

AFTER YOU FORMAT, CHECK THE PARSE:
☐ Single column
☐ Standard headings
☐ Selectable text
☐ No tables, no icons for content
☐ No skill bars, no photos
☐ File name follows the convention

RED FLAGS IN YOUR OWN RESUME:
❌ "Responsible for" without a number
❌ "Worked on" without an outcome
❌ "Helped with" without ownership
❌ A skill bar chart
❌ A two-column layout
❌ A photo
❌ Every bullet the same length and
  weight

THE SUBSTANCE TEST:
Read every bullet and ask:
1. "Is there a number?"
2. "Is there an ownership verb?"
3. "Is there an outcome?"

If any answer is no, rewrite the bullet
before you format the resume.

Why this works:
- Formatting can't fix a bullet without
  evidence
- Numbers stop the eye; duties don't
- Ownership is what the reviewer is
  scoring
- ATS-safe formatting gets the resume
  through

30-DAY SUBSTANCE PLAN:

Week 1 — Audit the bullets
☐ Print the resume
☐ Highlight every bullet with a number
☐ Highlight every bullet with an
  ownership verb
☐ Highlight every bullet with an
  outcome
☐ Mark the bullets with none of the
  three

Week 2 — Rewrite
☐ For each bullet with no number, add
  one
☐ For each bullet with no ownership,
  replace the verb
☐ For each bullet with no outcome, add
  what changed

Week 3 — Format for ATS
☐ Remove tables, columns, and icons
☐ Remove skill bars and photos
☐ Use a single column with standard
  headings
☐ Test the parse with an ATS checker

Week 4 — Test and iterate
☐ Get 2 peer reviews
☐ Track the callback rate over 20
  applications
☐ If it's below 5%, the substance needs
  work, not the formatting
☐ Iterate on the top third of page 1

Signs it's working:
✅ Every bullet has a number
✅ Every bullet has an ownership verb
✅ Every bullet has an outcome
✅ The strongest bullet is first
✅ The resume parses cleanly
✅ Recruiters ask about a specific bullet
✅ Callbacks improve