Make a resume easy to read in common digital workflows and easy for a person to scan.
Greenhouse documents that its parser extracts candidate information and that formatting can sometimes be interpreted incorrectly. That is evidence about one platform’s parser, not proof of a universal ATS rule.
A practical method
- Read the employer’s application instructions and use the requested file format.
- Prefer a single clear column, conventional section names, and text rather than decorative symbols for key facts.
- Avoid placing essential details in headers, footers, text boxes, or images.
- Export, reopen, and select/copy the text to inspect order and completeness.
- Review visually at normal zoom; machine-readable should still be comfortable for a person.
Worked example: from first attempt to usable result
- Task: Make a resume easy to read in common digital workflows and easy for a person to scan.
- First output/attempt: A graphic-heavy layout places contact details and job titles inside icons, text boxes, and sidebars.
- Mistake/weakness: The layout looks polished but may convert unpredictably; a parser can misread some formatting, and people may struggle to follow the sequence.
- Human correction: Use clearly labeled headings, selectable text, simple reading order, conventional dates, and the file type requested. Keep a visually styled portfolio version separate if needed.
- Quality check: Copy all text into a plain-text editor and inspect order; verify that contact information, titles, dates, and bullets are intact. Open the exported file on another device. Illustrative extraction check: 4 key fields (name, title, dates, contact) appeared in the expected text order.
- Final usable result: A one-column resume with headings “Experience,” “Education,” and “Skills,” readable dates, and selectable text preserves the intended sequence after export.
- Resume bullet: Illustrative resume bullet (use only if true): “Checked resume text extraction and corrected misordered employment fields before submission.”
A beginner exercise you can complete today
Use a copy of your resume and perform a plain-text extraction check. Record any missing or reordered fields, fix one at a time, and save before/after files with a note of the changes.
Pass check: Keep the original file, exported file, copied text, portal preview, and a short correction log. Pass when name, dates, headings, and bullet order survive both export and the employer’s upload flow; if a field is blank, correct it manually and verify the saved application before submitting.
Frequently asked questions
Is PDF always bad for ATS?
No universal rule. Follow the employer’s file instruction and verify that your exported text is selectable and ordered correctly.
Are columns always unreadable?
Parsing differs by system. A simple structure reduces avoidable ambiguity, but test the actual upload preview when possible.
Decisions that change the approach
Think of an ATS-friendly resume as a robustly formatted document, not a secret keyword puzzle. A readable structure helps human review and can reduce parsing errors in systems that extract fields. Products and employer configurations differ, so avoid claims that all systems reject columns, PDFs, or specific fonts. Follow the portal’s stated instructions and verify the details it imports.
| Situation | What to inspect | Next decision |
|---|---|---|
| Information in an image | Text cannot be selected or extracted. | Put essential information in normal text. |
| Complex columns | Copied text appears in the wrong order. | Use a simple reading sequence and retest. |
| Portal field mismatch | Imported dates or employer are wrong. | Correct fields before final submission if allowed. |
If the employer asks for a PDF, use a text-based PDF, not a screenshot. If it requests DOCX, follow that. Do not add hidden text or white-on-white keywords; that is deceptive and can corrupt the record. A plain-text check cannot prove that every employer’s software will interpret the file identically, but it can expose basic extraction failures.
Test both the document and the application fields
Run two checks. First, copy all text from the exported file into a plain editor and compare its order with the visual page. For example, a graphic-heavy file might copy as “2022 2024 Support Lead” before the employer name; a simple one-column version should read “Support Lead — Harbor Office, 2022–2024.” Second, if the employer shows imported fields, compare title and dates with the attachment. A blank portal date is visible evidence of a field issue; it does not reveal a ranking method.
Repair the source, export again, and repeat the same checks. If a portal field can be corrected manually, confirm the value persists before submitting. Do not create a fake application or send a resume to an unknown score checker just to test parsing. Products and configurations vary; copied text and an employer-provided preview are practical checks, not a guarantee.
A practical next step
Use this after the file parses cleanly to check term accuracy. the resume-keywords guide. Use this if the copied text order fails because of layout. the resume-format comparison.
Test the actual export and upload path
“ATS-friendly” is not one universal layout standard. Greenhouse documents that its parser can interpret some resume content incorrectly; that is a reason to inspect an upload, not proof that every system rejects a design choice. Employers use different products, configurations, and human review steps. Follow the file type stated in the posting and simplify only where the simplification preserves readability and evidence.
Use a copy of your resume to run three checks. First, select and copy the PDF text into a plain editor; confirm the name, employer, title, dates, and bullet order survive. Second, inspect the page visually at normal zoom and verify headings, links, and page breaks. Third, if the portal offers a parsed preview, compare its employer, role, dates, education, and contact fields with the source document. The preview is not a hiring score; it is a chance to correct extraction errors before submission.
Expected test record: file name and type, whether text was selectable, any fields that were missing or reordered, the corrected portal values, and a final confirmation that the right document is attached. Keep a clean single-column version as a practical fallback if the upload cannot read a more complex layout. Do not delete relevant evidence merely because an online checker gives a speculative score.
If the upload system changes your entry, preserve the resume and a screenshot or note of the field that changed. Correct it in the form where possible, then ask the employer for help with a specific missing field. Avoid repeatedly uploading different designs without knowing what failed; make one controlled change at a time so you can identify whether the problem was layout, file type, or a portal field.
A final practical boundary
Keep layout advice proportional: ordinary headings and a clear reading order reduce ambiguity, but no font or column rule guarantees parsing across employers. If a visual portfolio resume matters in your field, maintain it separately from a straightforward upload copy and use the version requested by the employer. Test only a copy, preserve the source file, and avoid online converters that require uploading sensitive details to an unknown service.
If the application is already submitted
First check the confirmation page or email to see whether the employer allows edits. If the form remains editable, correct only the field you can verify against the resume and save the new confirmation. If it is locked, do not create duplicate applications unless the employer instructs you to. Send a concise note through the listed recruiting contact or portal-support channel that names the role, submission date, and specific field that appears wrong; attach a corrected resume only if the employer accepts updates. Keep the message and reply with the application record.
| Check record (illustrative) | Finding | Action |
|---|---|---|
| File: resume.pdf; text copied into plain editor | All four key fields present, but “Client Support Associate” follows the wrong employer after a two-column export. | Moved the role to a single-column section and re-exported. |
| Portal preview | Employer/title pair now matches the resume; no preview for education. | Verified education in the attached file; noted that the portal offered no preview. |
| Submission status | Locked after confirmation. | Sent one correction request to the stated recruiting contact; saved the sent message and confirmation. |
If no preview exists, stop after the document-level copy/select and visual checks; those checks assess the file, not the employer's hidden system. Never upload the same application repeatedly just to probe behavior.
Sources
- Greenhouse Support: Unsuccessful resume parse — Greenhouse says its parser extracts resume information into candidate fields and that formatting can sometimes be interpreted incorrectly; this is evidence about one system, not all ATS products. Checked 2026-10-17.
- Harvard College Guide to Creating a Strong Resume — Harvard recommends specific, active, fact-based resume language, tailoring to a position, clear organization, and checking how a PDF converts. Checked 2026-10-17.
- University of Michigan University Career Center: Resume Resources — Michigan recommends consistent scannable formatting, reverse chronology within sections, tailored experience, and bullets that add what/how/why or impact; its one-page suggestion is specifically for most undergraduates. Checked 2026-10-17.