Resume formatting mistakes cost interviews quietly. When an applicant tracking system (ATS) reads your resume badly, nobody tells you. The recruiter sees a record with your name misspelled, two jobs merged into one, or a blank skills field, and moves to the next record. You hear nothing.
This post is a checklist of file and layout choices that can cause that, with a fix for each. For how the software works and which popular claims are myths, see what an applicant tracking system does with your resume. The short version: systems store your file, try to read it into fields, and let a person search what they stored. Each employer configures its own, and you cannot see the settings.
Quick answer
Send a file with real text in one column, standard section names, your contact details in the body of the page, and dates in one pattern. Follow any file type the application asks for. Then copy all the text out of the file and paste it into a plain text editor. If the paste reads in the right order, you have fixed most of what you can fix.
The check
Go through these in order. Each one has a reason, and the reason is the useful part.
- Use a file with real text. A scan or a photo of a page has no text for software to read. If you can select a word with your cursor, the text is real. If you cannot, export again from the original document.
- Follow the file type the application asks for. If it says PDF or Word, use that. If it does not say, a PDF exported from a word processor is a safe default, and a plain DOCX is the second choice. Rules differ by employer, so read the instructions on the form.
- Remove the password and any edit lock. A locked file may refuse to open in the system, and the recruiter will see an error where your resume should be.
- Use one column. Software reads text in an order. A two column layout can read straight across the page, so a job title lands next to the wrong employer.
- Avoid tables for layout. A table used to line up dates on the right is read row by row, which can separate a date from its job. Put the date on the same line as the title, after a comma.
- Keep contact details in the body. Some systems skip headers and footers. If your name and email live only there, the record may have neither.
- Use standard headings. “Experience”, “Education” and “Skills” are recognised. “My journey” and “What I bring” give a parser nothing to match.
- Write dates in one pattern. “Mar 2021 to Aug 2023” on every line. Mixed forms such as “Spring 2021” or “21-23” are harder to read, and they can look like a gap that is not there.
- Keep skills as words. A row of icons or five dots beside a skill is an image. Write “SQL, Excel, report writing” as text. If you use a short form, spell out the full name once.
- Use plain bullets and a common font. Decorative bullet characters can turn into stray symbols after reading. A standard font avoids missing characters, especially with accented letters in names and places.
- Write links out. If a link matters, such as a portfolio, show the address as text and also link it. A printed or converted copy shows the text even when the link dies.
- Name the file for a person. “Firstname-Lastname-Resume.pdf” helps a recruiter who downloads twenty files. “Resume final v7 REAL.pdf” does not.
None of these is a guarantee. They remove the failures with a known cause.
What the recruiter sees
Each mistake has a visible result on the other side.
| Mistake | What can appear in the recruiter’s record | Fix |
|---|---|---|
| Scanned page | An empty record, or only your name typed into the form | Export from the original document |
| Two columns | Lines from two jobs mixed into one | One column |
| Contact details in the header | No email or phone | Move them into the page |
| Dates in a table | Jobs with no dates, or dates on the wrong job | Date on the title line |
| Skill icons or bars | An empty skills field | Skills as words |
| Unusual headings | Experience filed under the wrong section | Standard headings |
You will never see this record yourself. The paste test below is the closest you can get.
Which file types do hiring systems accept?
Each system sets its own list, and the form usually says it. As one example, Greenhouse, a hiring system that companies use to post jobs and take applications, lists .doc, .docx, .pdf, .rtf and .txt for resumes and cover letters, up to 100 MB. Its article does not say which of those it reads into fields, so a large or unusual file is still a risk even when the upload succeeds. Keep the file small and plain, and use the type the form names.
The copy and paste test
This test takes a minute and tells you more than any online scanner.
Open the file you plan to send, select all, copy, and paste into a plain text editor. Read the result from the top. Your name, email and phone should appear. Each job should keep its title, employer and dates together, in order. Headings should be on lines of their own. Special characters should look like letters, not boxes.
If the paste is scrambled, the cause is usually a column, a table or a text box. Rebuild that part in the simplest form and test again.
Illustrative: the person and the jobs are invented. A two column resume pasted into a text editor came out like this:
Priya Nair Skills
Data Analyst SQL, Excel
Northwind Foods 2021 to 2024
Languages English, TamilThe left column (name, title, employer) and the right column (skills, dates, languages) were read across, line by line. The dates now sit beside “Northwind Foods” by luck, but “Skills” sits beside the name. After a rebuild in one column, the paste reads:
Priya Nair
priya@example.com
Experience
Data Analyst, Northwind Foods, Jan 2021 to Mar 2024
Skills
SQL, ExcelEvery fact is where a reader expects it, and a parser has a fair chance of filing each one in the right field.
What not to do about it
Do not hide keywords in white text or tiny type. It is easy to expose, because the text appears when a recruiter pastes your document, and it reads as an attempt to deceive. Do not rebuild your whole design around a guess about one system either. If a design matters in your field, such as visual work, send the plain resume to the application and link to your portfolio as text.
Check once for the reverse problem. A resume that parses perfectly and says nothing specific still loses. Formatting gets the file read. The bullets get you the call.
Questions people ask
PDF or Word?
Use what the form asks for. If it does not say, a PDF exported from a word processor keeps your layout, and a plain DOCX is the second choice. Never send a scanned PDF.
Can I use colour?
Yes, for headings or a thin line. Colour is not the problem. Columns, tables, text boxes and images are.
Should I add a photo?
Follow the custom of the country and the employer. A photo carries no text for a system to read, so it never helps parsing.
Do I need two versions of my resume?
Only if your field values design. Keep a designed version for people and a plain one for application forms.
What we know and what we do not
When you upload a resume to Zorlya, it accepts PDF, DOCX, RTF, ODT and plain text up to 10 MB, and it refuses a file with no readable text, such as a scan, so an empty file never replaces your profile. Zorlya’s own PDF builder has an ATS layout that puts each heading on its own line and lists skills as one comma separated line, with no tables, because tables read badly when text is pulled out. That layout is a convenience for building a file. Whether any employer’s system reads it well is something we cannot see, so run the paste test on it too. We do not know which system an employer uses or how it is set up, and nobody outside the employer does.