Write for the software and the human

What an ATS really does

An applicant tracking system is a database with a parser bolted to the front. When you upload a file, it tries to work out which text is your name, which is an employer, which is a date range, and which is a skill. Then a recruiter searches or filters that database.

That is the whole mechanism, and it explains most of what follows. The systems are not clever and they are not out to get you. They are pattern-matchers doing a mundane job on inconsistent input, and they fail in boring, predictable ways.

The myth worth killing first: most systems do not automatically bin resumes below a score. What happens is duller and worse — your resume parses badly, your five years at a company end up attached to the wrong field, and you never surface in the search the recruiter runs.

The five things that actually break parsing

1. Two columns. By far the biggest one. A parser reads in document order. When a sidebar sits beside the main body, that order can interleave — your skills end up inside a job title, dates attach to the wrong employer. This is why every template here is a single column, including the ones that look like they have a sidebar.
2. Text inside images. A header saved as a graphic takes your name and contact details out of the machine-readable text entirely. Some parsers run OCR; most do not.
3. Tables holding your job history. Table cells are read in an order that depends on the parser. Use them for nothing that matters.
4. Headers and footers. Some parsers skip them completely. Your phone number should never live in a page footer.
5. Invented section names. "My Journey" instead of "Work Experience" costs you the field mapping. Be boring here.

What the parser cannot do for you

A clean layout gets your content into the database correctly. It does not put the right words in it. Ranking is largely keyword matching against the job description, which means the single highest-value ten minutes you can spend is this: open the job posting, list the nouns that appear in it — tools, methods, certifications, responsibilities — and check honestly which ones are true of you and missing from your resume.

Add the true ones, in the place they belong. If you managed vendor contracts and the posting says "vendor management", say vendor management. This is not gaming the system; it is speaking the same language as the person who wrote the posting.

And skip the white-text-keyword-stuffing trick you may have read about. It is detected, and where it is not detected it produces a resume the human then reads as nonsense.

The one page format question

PDF or Word? Send PDF unless the application form specifically asks for .doc or .docx — a few older systems still parse Word more reliably, and when a portal tells you what it wants, believe it. The builder here exports both.

How this builder handles it

• Every one of the 20 templates is a single column of real, selectable text with conventional headings.
• Type size adjusts to how much you have written, so a full page stays readable rather than being crushed to fit.
• The live ATS score flags what is missing while you write — the quantified results, the action verbs, the LinkedIn URL people forget.
• Exports at A4 with print margins, and to Word when a portal insists.

Already have a resume? Run it through the resume checker before you rewrite anything — it will tell you whether your problem is formatting or content, and those need different fixes. If it is content, the worked examples are the faster route.

Questions people actually ask