8 min read
You're not choosing an ATS like you'd pick a phone plan. The employer already did. Your job tonight is to match the resume file they'll accept to the parser quirks that stack exposes on senior IT files: long tenure blocks, certification grids, architecture keywords, and two pages of proof.
Same resume, three portals, three different scrambled profiles. That's normal when you're still exporting from a template built for human skim, not field mapping. You don't need forum rankings. You need a side-by-side read of what each system tends to garble on US senior technology resumes.
Check your resume for free on the exact export you'll upload. Parsing tradeoffs are easier to see when broken field order shows up on the same screen as the posting keywords.
Below you'll get a comparison table, platform-specific traps, and a decision rule for PDF vs DOCX once you've spotted Workday, Greenhouse, or Lever on the apply link. No crown for a vendor. Just formatting choices you can act on before your next batch of applications.
Why the same senior IT file parses three ways
Enterprise IT resumes carry more surface area than entry-level files. Multiple employers across fifteen years, cloud migrations, on-call rotations, vendor lists, and certification blocks. Parsers do not read that history as a story. They chop plain text into name, employer, title, dates, and description fields.
Workday often runs inside large US employers with rigid apply forms. Imports favor linear body text and standard section labels. Header and footer contact lines are a recurring failure point on Word exports.
Greenhouse powers many mid-size tech companies and high-growth teams. Recruiters search parsed text heavily. Sidebar skill rails and summary blocks stored before experience can reorder what search sees first.
Lever blends ATS and CRM workflows at scale-ups and product-led companies. Two-column templates and project tables often stitch rows across the page on import, which makes contractor-heavy IT histories look like overlapping jobs.
None of that means you're underqualified. It means the container still carries habits each importer reads differently. Flatten once, then tweak export format per posting instead of maintaining three designed versions.
For what happens after upload in a major tenant, read why your resume looks different after upload in Workday . The comparison here starts from that same parsed-profile view, not from vendor marketing pages.
Workday vs Greenhouse vs Lever parsing quirks for senior IT resumes
Use this table as a field map, not a scoreboard. You're looking for the first row that matches a symptom you've seen after upload, then fixing layout on one master file.
| Parsing quirk | Workday | Greenhouse | Lever |
|---|---|---|---|
| Contact block | Word header/footer contact often drops; email field blank in preview | Text boxes and centered banners parse late or skip | Footer-only phone lines duplicate or vanish on two-page files |
| Skills vs current title | Skills cloud above jobs can populate skills before experience fields fill | Left sidebar stacks often appear before name in plain-text order | Keyword tags in a top rail can import as uncategorized text |
| Dates on long tenures | Table layouts split Month Year from employer on multi-page IT histories | Right-column date cells attach to wrong job when rows wrap | Two-column employer/date rows merge across the page on import |
| Certification blocks | Icon rows and badge graphics export as blank glyphs | Compact cert grids read as one paragraph without line breaks | Three-column cert tables shuffle issuer names away from credentials |
| Contractor-heavy history | Client names inside sub-bullets may not map to employer field | Project tables flatten into one block; titles lose employer context | Short gigs in two columns look like overlapping full-time roles |
| Typical file preference | PDF when DOCX blocked; plain text-based PDF over design exports | DOCX often survives when PDF contact lines scramble | Either works when single-column; fix columns before choosing format |
Workday: enterprise forms and strict field order
Workday apply flows often show parsed fields after upload in larger tenants. Compare your source line by line. When email is blank but bullets imported, the contact block lived in a Word header, not the body stream.
Before: Name and phone in a Word header; AWS and Kubernetes in a top skills table; jobs listed with dates in a narrow right column.
After: Contact on lines two through four in the body; tools in bullets under each employer; each role on one line: Company | Title | Mar 2019 to Present.
Greenhouse: search reads parsed text order
Recruiters type Boolean strings against extracted text. When your sidebar skills import before your name, search hits look like your headline stack is your job title. That's a formatting order problem, not a missing keyword problem.
I've screened senior infrastructure profiles in Greenhouse where a left-rail skill list imported above the candidate's name, and the hiring manager assumed the person was still a generic "tools list" instead of a staff-level owner.
Lever: two pages OK, two columns not
Two pages is normal for senior IT when every line is proof. Lever still reads top to bottom. A page break mid-role plus a skill cloud at the top of page two can make the cloud look like a new title block.
Group consulting clients under one umbrella employer line with client names inside bullets. Linear dates beat a project matrix when the parser merges columns.
Copy-paste block: senior IT upload skeleton
Rebuild into this shape before you compare uploads
Ravi Okonkwo Staff Platform Engineer [email protected] | 555-014-8821 | Austin, TX EXPERIENCE Northstar Health, Staff Platform Engineer, Jan 2021 to Present • Led EKS migration for 140 microservices, cutting deploy failures 18% in Q2 • Owned Terraform modules shared across 6 product teams SUMMIT CLOUD SERVICES, Senior SRE, Jun 2017 to Dec 2020 • Built on-call runbooks for a 24x7 payments stack with 99.95% uptime target CERTIFICATIONS AWS Solutions Architect Professional, 2023 | CKA, 2022 SKILLS Kubernetes, Terraform, Python, Prometheus, incident response
Paste your real bullets under each employer row. Keep Month Year dates on the same line as company and title. Do not reintroduce columns to fit certifications on one page.
For PDF vs Word tradeoffs after layout is clean, see PDF vs Word resume for ATS .
Senior IT layout habits that hit each stack differently
Senior candidates often add structure to fit depth. These habits are logical for human readers and painful for field mappers.
Architecture diagram thumbnails. Zero extractable text. Workday and Lever skip the image layer entirely, leaving a gap where scope proof should be.
Technology summary tables before experience. Greenhouse plain-text order may open with forty tools before your current title. Move stack proof into bullets under the job where you used it.
Multiple short contract rows in two columns. Lever imports can stitch left and right cells into one nonsense row. List sequential employers in one column with client names nested in bullets.
Resume-length certification grids. Three-column cert layouts shuffle on import. A simple list with credential, issuer, and year parses more reliably across all three portals.
Before: PDF exported from a designed template with a colored sidebar and icon skill meters.
After: Single-column DOCX or text-based PDF with typed skill names and body contact lines only.
Fancy containers fail the same way on every stack. Read why fancy templates break ATS if your designed export still fails the paste test after you flatten columns.
Test the export before you batch apply
Run the Notepad paste test on your master file first. Name in the first three lines, contact complete, each job title beside its employer and dates. If that fails, no ATS brand will save the upload.
Then pass the same export through the free ATS checker with the posting pasted in. You're checking field order and missing nouns, not chasing a single vendor score.
Applying to several senior roles this week? Generate a cover letter in the same plain formatting so both documents stay readable in one portal session.
Which file to upload when you see Workday, Greenhouse, or Lever
Use this decision rule after the paste test passes on a single-column master. You're picking export format and minor layout tweaks, not rewriting fifteen years of work.
- Workday on the apply link: Upload a text-based PDF when the form blocks DOCX or when your Word header contact keeps dropping. Move email and phone into the body first. Keep section labels standard: Experience, Education, Certifications.
- Greenhouse on the apply link: Prefer DOCX when PDF scrambles contact or promotes sidebar skills above your name. Put Skills after Experience unless the posting is entry-level. Lead with your current title in the first job block.
- Lever on the apply link: Flatten two-column layouts before choosing PDF or DOCX. Group short contracts under umbrella employers. Save a second export only when one portal rejects the file type, not because Lever "likes" a different design.
- Brand hidden or unknown: Default to single-column DOCX, run the paste test, and upload once where parsed preview fields appear. Log which field broke first and fix that habit on the master before you clone exports.
Before: Three styled resume versions labeled Workday, Greenhouse, and Lever with different fonts and columns.
After: One plain master plus renamed exports: Lastname_Upload.pdf for Workday reqs and Lastname_Upload.docx when Greenhouse parses PDF contact lines wrong.
The employer's stack is fixed. Your file format isn't. Match export choices to the parsing quirk you can see, and the same senior IT story stops looking like three different candidates.
Read more
Frequently asked questions
No platform wins on every file. Workday, Greenhouse, and Lever each map the same PDF into different fields when your layout fights the parser. The useful comparison is which habit breaks first on the stack your target employer runs: header contact in Workday, sidebar skills in Greenhouse, or two-column rows in Lever. Fix that habit on one master file instead of chasing a mythical best ATS.
Follow the portal's allowed list first. Export both formats from the same single-column source and run the Notepad paste test on each. Upload whichever copy keeps your current title, employer, and Month Year dates on one line per role. Workday enterprise tenants often accept only PDF. Greenhouse frequently allows DOCX. Lever varies by company. Format choice does not rescue a two-column template underneath.
Yes, when the file is a plain single-column export with standard headings and linear dates. You do not need three designs. You may need small export tweaks: a PDF for a Workday req that blocks DOCX, or a DOCX when Greenhouse parses your PDF with scrambled contact lines. Keep one content master and rename the export per posting after the paste test passes.
Open the apply link in a private window and read the URL and footer on the careers subdomain. Workday URLs often include myworkdayjobs.com. Greenhouse uses boards.greenhouse.io or a company subdomain with greenhouse in the path. Lever shows jobs.lever.co or a lever.co embed. When the brand is hidden, upload a plain test file to one role and check whether parsed preview fields appear before you batch apply elsewhere.