Beating the ATS Without Sounding Like a Robot

Most large employers run every résumé through an applicant tracking system before a recruiter ever sees it. The ATS doesn't care about your design taste — it parses your document into structured fields, scores it against the job description, and ranks you in a queue. If you don't make it past the parser, the rest of your résumé might as well not exist.

What the parser actually reads

• Plain text inside standard sections: Experience, Skills, Education.
• Job titles, company names, and date ranges in conventional formats.
• Keywords that match the job description's nouns and verbs.
• Standard file types — PDF generated from a text source, not an image.

What confuses the parser

• Multi-column layouts. Many parsers read left-to-right, top-to-bottom and merge columns into nonsense.
• Text rendered inside images, icons, or graphic charts.
• Headers and footers — some parsers ignore them entirely.
• Creative section names like 'My Journey' or 'What I Bring'.

Use the job description as a dictionary

Read the JD twice. The first time, highlight every concrete noun (technologies, frameworks, domains). The second time, highlight every verb that describes the work (built, scaled, migrated, owned). Your résumé should use the same words for the same concepts. Don't write 'JS' if the JD says 'JavaScript'. Don't write 'distributed systems' if the JD says 'microservices'.

The single-column rule

If you remember nothing else: use a single-column layout, plain section headers, and a sans-serif font. You can still design an attractive résumé inside those constraints. The most senior engineers in the industry usually have the plainest résumés.