Ditch the two-column template. Build a CV machines read.
Sidebars, tables and text boxes look sharp on screen and fall apart in the parse. Here's what to build instead.
What an ATS actually does with your beautiful layout
Before a recruiter ever sees your CV, software converts the file into plain text. That conversion follows the document's underlying structure, not the picture on your screen. A two-column layout is stored as a table or a stack of text boxes, so the parser reads across the page instead of down it, and your job titles end up glued to unrelated skill labels.
The damage is quiet. Nothing bounces, no error appears, and you never find out that three years of experience landed in a field marked Other. When a recruiter searches the database for a job title plus a tool you actually use, you don't come back, because the words sit in the PDF but never made it into the record built from it.
Clean structure fixes this, and it costs you nothing in looks. One column, standard headings, dates on the same line as the role, contact details in the body rather than the header, and text you can select with your cursor. Typography and white space still do the design work. The parser simply stops guessing.
Three things that break during the parse
Sidebars scramble the reading order
A parser reads a table row by row. Your skills column gets stitched into your job history, line by line.
Headers and footers get skipped
Contact details in the page header often never reach the record. A recruiter can like your CV and still not reach you.
Image PDFs hold no text at all
Export a flattened image from a design tool and the parser finds a blank page. No keywords, no matches, no callback.
The layout rules that survive every screening system
One column, top to bottom
Every section stacked in reading order. No sidebar, no floating panel, no clever grid the parser has to unpick.
Plain headings, standard words
Call it Experience, not My Journey. Standard section names are what the parser looks for and what recruiters skim for.
Text, never pictures
No icons for phone and email, no skill rating dots, no company logos. If it isn't selectable text, it doesn't exist.
Dates that stay with the role
Job title, company and dates on one line. Split them across boxes and your experience reads as undated.
Design habit, real cost
What each habit costs you, and what to do instead
| Design habit | What it costs you | Do this instead |
|---|---|---|
| Skills in a sidebar | Skills merge into job descriptions or drop out of the keyword index | One Skills section in the main flow, comma separated |
| Dates inside text boxes | Roles appear with no dates, so your history reads as unverified | Put dates on the same line as the job title |
| Contact details in the header | Phone and email get stripped and nobody can call you | First lines of the document body, as plain text |
| Icons instead of labels | The parser sees a picture where your email address should be | Write the word: Email, Phone, LinkedIn |
| A photo | Eats space you need for results and skews the parse | Use those lines for a two-sentence summary |
| PDF exported as a flat image | The file carries no readable text, so you score nothing | Export a text-based PDF, then select the text to check |
Build the version the parser reads correctly
Bring your current CV or start from blank. You get a clean single-column file that still looks like someone designed it.
Questions job seekers ask about CV layout
Do two-column CVs really get rejected by an ATS?
Not rejected outright, but degraded. Most systems parse your file into fields, and a two-column layout built on tables makes that parse unreliable. Your details still sit in the PDF, yet the record a recruiter searches may be missing dates, skills or whole roles. A single-column file removes the risk and costs you nothing in visual quality.
Can a single-column CV still look good?
Yes, and it takes less work than the template did. Design with typography instead of boxes: a clear name block, generous white space, bold role titles, a light rule between sections, consistent spacing. Recruiters give the first scan a few seconds, and a calm single column reads faster than a colourful grid ever will.
How do I tell whether my current CV parses correctly?
Open the PDF, select all the text and paste it into a plain text editor. Read the result from top to bottom. If the order jumbles, if dates drift away from job titles, or if nothing pastes at all, the parser sees the same mess you do. A free HRLens analysis shows it with a fix list attached.
Should my CV include a photo?
In most markets, no. A photo adds nothing a recruiter can search on, takes space you need for results, and in places with strict anti-discrimination practice it can get your CV quietly set aside. A few regions still expect one, so check local norms. When in doubt, leave it out and sharpen your summary instead.
Is PDF or Word safer for applicant tracking systems?
A text-based PDF is the safe default: it holds your layout and modern parsers handle it well. The real failure case is a PDF exported as an image from a design tool, which contains no readable text at all. Some portals still ask for .doc or .docx, so keep a Word version ready and follow the posting.