How to write an ATS-friendly resume

Applicant tracking systems do not admire design. They extract plain text from your file, map it to fields like employer and job title, and compare that text to the posting. Recruiters may never see your resume if the parser drops whole sections because they lived inside a table, icon, or text box.

That is why the safest layout is boring on purpose: one column, left-aligned body text, standard section names, and no graphics pretending to be content. Verum exports the same structure you edit — Summary, Experience, Education, Skills — so what you preview is what the parser receives.

Parsing quality varies by employer, but the failure modes repeat: multi-column layouts, headers and footers with contact info only, skill clouds as images, and creative section titles like “Where I shine” instead of “Skills.” Avoid those and you are already ahead of a large share of applicants.

Use Summary (or Professional Summary), Experience (or Work Experience), Education, and Skills. Certifications and Languages are optional add-ons when you truly have them. Do not hide experience under “Projects” unless each project has the same company, role, and date pattern as a normal job.

Repeat the job title you are targeting in the summary only if it matches work you have actually done. ATS keyword matching looks for literal strings; humans look for credibility. Both punish fiction.

Keep subsection order stable: most recent role first, degree highest-first, skills as a simple list or comma-separated line — not a chart. Verum templates never insert icon fonts or column breaks for this reason.

Paste the job description into a notes file and highlight recurring tools, domains, and verbs. Before adding a keyword to your resume, ask: have I used this in a job, course, or shipped project? If yes, weave it into a bullet you can defend in an interview. If no, skip it.

Synonyms matter. Postings say “JavaScript”; your resume might say “JS.” Good ATS setups count both; cheap ones do not. When both terms are honest for you, include the form used in the posting once in Skills and once in a bullet.

Keyword stuffing hurts humans and can trigger filters. Two natural mentions beat ten forced ones. Verum scores keyword coverage and flags missing terms, but copy suggestions always say “only if true for you.”

One page is fine early-career; two pages is normal for ten-plus years. The danger is not page count but information density: tiny fonts, zero margins, or 25 bullets for one role. ATS length scores often penalize extremes — too thin looks incomplete, too long hides matches.

Aim for three to five bullets per recent role, each bullet one line on the PDF where possible. Older roles can shrink to two bullets or a single line. Education stays compact unless you are a new graduate.

Use the free word counter on Verum to check total word count before export. Pair it with the ATS demo to see whether length score moves when you trim filler adjectives, not facts.

PDF is the default send format. DOCX is acceptable when the employer asks for Word. Avoid PNG or JPEG resumes entirely. Verum generates single-column PDFs with embedded text — not scans — so parsers can read them.

Name files predictably: Firstname-Lastname-Role.pdf. Inside the doc, keep hyperlinks minimal; plain text email and LinkedIn URL in the header is enough.

When you tailor for a specific posting, save a copy per company. Version history inside Verum lets you compare what changed without merging fiction into your master profile.

Confirm every role has company, title, and dates. Run an ATS score against the pasted listing. Read bullets out loud — if you stumble explaining a metric, remove or rephrase it with a fact you own.

Spell-check Skills the way the posting spells them. Remove graphics, columns, and text boxes. Export PDF and open it: select-all text in a reader. If selection skips sections, fix the source, not the filename.

Register free on Verum to generate from your real profile, score against saved job posts, and export ATS-safe PDFs without inventing experience.

Applying across borders adds formatting noise: date order, phone formats, and whether to include a photo. Verum keeps photos optional and dates consistent (month year) so parsers in US and EU markets read the same file. When the posting is in English, export English headings even if you wrote bullets in another language during drafting — align section titles with what the employer expects.

Bilingual candidates sometimes maintain two master profiles: one for local employers and one for international remote roles. Do not mix languages within a single bullet unless the job explicitly asks for it. Skills can list tools in English while experience stays in your working language if that matches how you would interview.

If you must submit both a local CV and an ATS resume, generate two exports from the same truthful profile rather than maintaining contradictory histories. Version snapshots show what changed between locales without inventing new employers.

Tailoring means adjusting summary emphasis, reordering bullets, and adding honest keywords — not rewriting your employment timeline per company. After three iterations for similar roles, you likely have a stable template. Further edits yield diminishing returns unless the posting introduces a hard requirement you genuinely meet.

Batch applications to the same title (e.g., backend engineer) can share one tailored resume with company-specific cover letters. Use the job tracker to record which version went where so follow-up emails reference the correct file.

If ATS score stays low after honest edits, the gap may be experience level, not formatting. Applying up-stack occasionally is fine; mass-applying to senior roles with junior history wastes time. Score, keyword match, and your own read of Tier 1 requirements should gate the send button.

Keep a short personal checklist saved outside the resume: visa status if relevant, notice period, and portfolio password — those belong in forms or email, not hidden ATS fields.