KissResume.com
Guides → Formatting that survives the parser

Résumé formatting that survives the parser

A practical explainer · about 8 minutes

A résumé does two jobs before a human ever reads it. First, a parser pulls your text into fields — name, employer, title, dates, skills. Then a recruiter skims the result for ten or fifteen seconds. Beautiful design that confuses the parser fails the first test, and a wall of dense text fails the second. The good news is that the formatting choices that keep a parser happy are the same ones that make a page easy for a tired person to scan. You do not have to choose between machine-readable and human-readable. You build one clean document that serves both.

File type: .docx, text-based PDF, never a scan

Follow what the posting asks for first. If the application form says "upload a PDF," send a PDF. If it says Word, send a .docx. When you get no instruction, a .docx is the safest default because nearly every applicant tracking system parses it cleanly, and many of them were built around Microsoft's format. A PDF is fine too, as long as it is text-based — meaning you can open it, select a sentence, and copy it as words rather than as a picture. Export directly from your word processor to get that. The one file to never send is a scanned image or a photo of a printed page saved as a PDF. To a parser that is a blank rectangle, and your carefully written experience disappears.

One column beats two

A single-column layout is the most reliable structure you can choose. Parsers read in a logical top-to-bottom order, and a single column matches that flow exactly. Two-column designs — the kind that tuck skills or contact details into a narrow sidebar — force the parser to guess which column comes first. Some read straight across the page, splicing your sidebar into the middle of a job description. Your information is all there; it just arrives scrambled. Save the elegant two-column look for a portfolio site. On the résumé, keep everything in one column running down the page.

Not sure your layout survives the trip? KissResume tells you whether your current layout parses cleanly and can apply a clean, ATS-safe template without rewriting your facts. Open the app to check yours.

Fonts and size

Pick one standard, widely available typeface and use it throughout. Arial, Calibri, and Georgia all render predictably and read well at small sizes. Set body text between 10 and 12 points; drop below 10 to cram more in and you make the page hostile to read. Headings can run a couple of points larger and bold. Avoid decorative, script, or "creative" fonts — they look distinctive on your screen, but if the reader's machine does not have the font installed it substitutes something else, and your spacing collapses. A boring, legible font is doing its job.

Section order and standard headings

Parsers look for headings they recognize, so name your sections in plain language: Contact, Summary, Experience, Education, Skills. Clever labels like "Where I've Made an Impact" mean nothing to the software trying to file your work history under "Experience." A conventional order works for most people: contact details at the top, a short summary, then experience, education, and skills. Early in your career, education can sit above experience; once you have a few years of work, experience leads. The point is that both a human and a machine can find each section in two seconds.

Keep contact info in the body

Put your name, phone, email, city, and LinkedIn or portfolio link in the main body of the document, near the top. Do not place them in the page header or footer. Many parsers skip the header and footer region entirely, which means your contact details can vanish — the recruiter likes your experience and then has no way to reach you. Type the contact line directly onto the page where the parser is guaranteed to read it.

Consistent dates and bullet points

Choose one date format and hold to it everywhere. "Mar 2021 – Jun 2023" across every entry is far better than mixing "March 2021," "03/2021," and "2021." Consistency helps the parser line up your employment timeline and signals care to the reader. Under each role, write achievements as bullet points, not paragraphs. Bullets parse into clean discrete items and let a recruiter scan your results without wading through prose. Start each one with a strong verb and, where you can, an outcome. Three to five bullets per recent role is plenty.

Length: quality over cramming

If you are early in your career, aim for one page. Mid-career and senior professionals can use two. The number that matters is not the page count but the strength of what fills it. Two pages of sharp, relevant accomplishments beat one page squeezed to a six-point font with the margins removed. Likewise, do not stretch a thin history across two pages with padding. Use the space your real experience justifies and stop there.

Margins and white space

Keep margins around half an inch to one inch. White space is not wasted space — it gives the eye somewhere to rest and makes each section distinct. A page packed edge to edge reads as cluttered and is harder for both the parser and the recruiter to break into parts. If you need more room, cut weak content rather than shrink the margins.

What to avoid: tables, boxes, icons, photos

Tables, text boxes, multi-column blocks, and graphics are where parsers stumble most. Text inside a table cell or a floating box often gets read out of order or dropped. Skill bars and rating dials carry no machine-readable meaning — "Python ●●●●○" tells the software nothing. Icons in place of labels (a little phone glyph instead of the word "Phone") can confuse the parse. Lay everything out as plain text in normal paragraphs and lists. This connects to how the underlying systems work, covered in how ATS systems read your résumé.

Photos are a regional question. In much of the United States, the United Kingdom, Canada, and Australia, a headshot is discouraged — it can raise bias concerns, and many systems are not built to handle the image. In parts of continental Europe, the Middle East, and Asia, a photo is conventional and sometimes expected. Match the norm of the market you are applying in, and when an application is run through automated screening, leaving the photo off is the safer choice.

Name the file so it makes sense

Save the file with your name and what it is: Firstname-Lastname-Resume.pdf. A file called "resume_final_v3.docx" or "Document1.pdf" gets lost the moment a recruiter downloads a folder of applicants. A clear, named file is easy to find and looks deliberate.

Quick checklist

← Back to all guides