Most freshers assume every resume they submit gets read by a human. Often, it doesn't — not at first. Larger companies and even many mid-size ones run resumes through an Applicant Tracking System (ATS) before a recruiter sees anything. If your resume format confuses the software, it can get filtered out or garbled before a real person ever looks at your qualifications — regardless of how strong your actual profile is.

What an ATS is actually doing

An ATS parses your resume file into structured text — pulling out your name, contact details, work history, education, and skills into fields it can search and filter. Recruiters then search that parsed data for keywords relevant to the role. The problem: ATS parsing is not as smart as a human reader. Formatting that looks perfectly clean to your eye can turn into scrambled, unreadable text on the ATS's side — and a resume the system can't parse correctly effectively becomes invisible in a keyword search, even if a human would have found it impressive.

Formatting mistakes that actually break parsing

  • Tables and multi-column layouts. Visually appealing, but many ATS systems read left-to-right, top-to-bottom in a single stream — a two-column layout can interleave your work experience and education into nonsense.
  • Text inside images or graphics. A skills section rendered as a fancy graphic with icons is invisible to an ATS entirely — it can only read actual text.
  • Headers and footers. Some systems skip header/footer content completely — don't put your contact information there.
  • Unusual fonts and heavy styling. Decorative fonts can parse as garbled characters. Stick to standard fonts (Arial, Calibri, Times New Roman) in a plain, single-column layout.
  • Saving as an image-based PDF. If your PDF was exported from a design tool as flattened images rather than actual text, an ATS reads nothing at all. Always test by trying to select and copy text from your own PDF — if you can't select it, an ATS can't read it either.

The keyword problem

Beyond formatting, ATS systems and the recruiters using them typically search for specific keywords from the job description — tools, technologies, specific skills, exact role titles. A resume that says "worked with databases" scores worse in a keyword search than one that names the actual database (MySQL, PostgreSQL) if that's what the job description mentions. This doesn't mean stuffing your resume with keywords that don't apply to you — it means describing your genuine experience using the same specific terms the role is actually asking for, where that's honestly accurate.

Weak (vague, generic): "Worked on a project involving data and made a dashboard for the team."

ATS-friendly and specific: "Built a Power BI dashboard analysing sales data for a college project, using SQL to query and clean the underlying dataset."

The simple test

Before submitting anywhere, save your resume as plain text (or copy-paste it into a plain text editor) and read it. If sections are jumbled, dates are missing, or your skills section has vanished, an ATS is very likely seeing the same broken version — and no amount of genuine qualification fixes a resume the system can't correctly read.

Keep your resume as a single-column layout, standard section headings ("Work Experience," "Education," "Skills" — not creative renamed versions), a real text-based PDF (not an exported image), and your contact details in the main body, not a header or footer.

Once your resume clears that first filter, the next filter is a real conversation — and that's where practising your answers out loud before the real interview makes the difference between a strong resume that doesn't convert and one that actually gets you the offer.