Why Your Resume Isn't Getting Interviews: 7 ATS Killers + Fixes

Killer 1: Two-column layout

Symptom: the resume looks elegant in the editor, with a sidebar on one side and the main content on the other. The ATS reads top-to-bottom, left-to-right, and produces a parse where the candidate's email is sandwiched between the second and third bullet of the most recent role.

The 30-second fix: switch to a single-column template. In Curriq, every template is single-column by design. In other tools, look for a "single column" or "ATS-safe" toggle. If the only fix is to migrate to a different template, do it; the format change matters more than the visual cost.

Why this is killer #1: about 40% of failed resume parses we see in coaching come from two-column layouts. Even when the parse "works", the field assignment is wrong (job titles in the skills field, for example), which reduces match scores against the posting.

Killer 2: Contact info inside a header, footer, or text box

Symptom: the candidate's name, email, phone, and LinkedIn URL are positioned at the top of the page using a Word "header" element or a positioned text box. The ATS skips headers and footers in many older systems, and parses text boxes as separate documents in many newer ones. Result: the parse comes out without contact info, and the ATS cannot route the application.

The 30-second fix: put the contact info as plain text, in the body of the document, in the first section. Format: name on its own line at the top, then a single line with email, phone, location, LinkedIn URL separated by middle-dot or pipe characters.

Killer 3: Icons in section headers

Symptom: a small briefcase icon next to "Experience", a graduation cap next to "Education", a screwdriver next to "Skills", an envelope and phone icon before contact info. They look professional in the editor. They render as Unicode glyphs the ATS does not recognize, and on bad scans they corrupt the line.

The 30-second fix: remove every icon from the document. Plain text section headers. The contact info line uses the labels themselves (or just the data) without icons.

Trade-off: visual minimalism. The replacement gain: parse reliability across every ATS in 2026. Worth it.

Killer 4: Non-standard section names

Symptom: the resume's section headers say "My Journey", "What I Bring", "Career Highlights", "Areas of Expertise". Each of these phrases is fine human English. None of them are what the ATS section detector is trained on. When the section detector fails, all the bullets in that section land in the wrong field, and the resume scores poorly against the posting.

The 30-second fix: rename to the canonical labels. Use exactly: Summary (or omit), Experience, Education, Skills, Certifications, Projects, Publications, Languages. Cute is the wrong goal.

Killer 5: Tables for layout

Symptom: the resume uses a 1x2 table to position the candidate's photo on the left and the contact info on the right. Or a multi-row table for the skills section with three skill columns. Or a table for the education entry with degree, school, and dates.

The 30-second fix: convert tables to plain text. The skills can be a comma-separated list. The education entry can be a single line. The contact info can be one line of pipe-separated values.

Exception: tables for genuinely table-shaped data (a publications list with title / journal / year columns, a certifications list with cert / year). If the data is naturally tabular, keep the table; the ATS handles those fine. If the table is positioning content, kill it.

Killer 6: Photo on the resume (US / UK / CA / AU)

Symptom: the resume includes a profile photo at the top. The ATS may parse it (most do, by stripping the image), but the human screen at companies that follow anti-bias hiring practices flags or rejects resumes with photos. Many large US, UK, Canadian, Australian companies explicitly instruct recruiters to discard resumes with photos at the screen stage.

The 30-second fix: remove the photo for any application in US / UK / Canada / Australia. Keep the photo only for Germany / Austria / Switzerland / parts of Spain / Italy / Asia where it remains the local convention.

Curriq detail: 6 of the 20 templates support a profile photo (visionary, navigator, emerald, apex, momentum, blueprint). For US-targeted roles, switch to one of the 14 photo-free templates.

Killer 7: Date format with em dashes or month-only ranges

Symptom: dates appear as January 2024 — Present with an em dash, or Jan - Mar without a year, or currently instead of Present. Each of these confuses ATS date parsers. The role then gets logged with a missing or wrong date range, which lowers recency scoring.

The 30-second fix: use the canonical format Jan 2024 - Present or Jan 2024 - Mar 2025. Plain ASCII hyphen, three-letter month abbreviation, four-digit year, "Present" exactly (capital P, no italic).

The 8th killer (bonus, not in the title)

Wrong file format. Submitting a .docx when the posting says PDF, or vice versa. Submitting a .pages file (Apple-only) anywhere. Submitting a JPEG of a resume. Each of these breaks the ATS. Always submit a PDF unless the posting explicitly requests .docx; in that case, export from Word with embedded fonts.

The 30-minute total fix

The seven killers are mechanical. The full fix flow:

1. 0-5 min: diagnose. Open the current PDF. Check each killer in order.
2. 5-10 min: if multiple killers apply, switch to a fresh ATS-friendly template. This is faster than fixing them inline.
3. 10-25 min: migrate content into the new template. Keep the same bullets; the killers are about format, not content.
4. 25-30 min: verify. Upload the new PDF to a free parser. Confirm the parse is clean.

What to expect after the fix

Callbacks usually pick up within 1 to 2 application cycles (5 to 10 applications) after fixing format issues. The first signal is usually an automated "received" email from the company's ATS that says the application made it through to the recruiter (you can tell because the email mentions specific role details, not a generic confirmation).

If 20+ applications still produce no callbacks after fixing all 7, the issue is no longer the resume's format. The candidate-side checks at that point:

• Role fit. Is the seniority of the postings genuinely matched? Applying to senior PM roles with 3 years of experience is a fit problem, not a resume problem.
• Application channel. Cold applications via the company's portal yield 1-3% callback rates. Warm intros from a current employee yield 25-40% callback rates. The 10x lift comes from the channel, not the resume.
• Tailoring. Generic resumes for 30+ roles versus tailored resumes for 8 to 10 roles tends to outperform on callback rate. See how to tailor a resume for a specific job posting.

The verification check

After the fix, run this 5-step verification:

1. Open the new PDF in Preview / Acrobat. Select all text. Copy. Paste into a plain text editor. Confirm content reads in the right order.
2. Upload the PDF to Jobscan, Resume Worded, or Skillsyncer's free parser. Confirm name, email, phone, all roles parse correctly.
3. Send the PDF to your own email. Open it on a phone. Confirm rendering on mobile preview.
4. Search the PDF for the word "leveraged". Replace if found.
5. Confirm the document is exactly 1 or 2 pages, not 1.5.

What this guide does not cover

Format issues are about 60% of "resume not getting interviews" problems we see in coaching. The other 40% are content issues: weak bullets, missing keywords, generic summary, wrong seniority signal. For content fixes, see how to write a resume with AI in 2026. For per-job tailoring, tailor a resume for a specific job posting. For the format spec in detail, ATS-friendly resume templates.