10 min read
You spent an hour on layout. You hit Submit. Then silence while you wonder if anyone opened your file. They probably didn't open your file first. They opened the row the importer built from your upload. If that row shows blank phone, scrambled dates, or Skills detached from employers, your PDF design never gets a fair read.
Before you rewrite keywords for the third time, check your resume for free on the exact export you'll upload. You're looking for parser warnings on contact lines and Experience order, not a motivational score.
Job searching is hard enough without blaming yourself for a machine-readable failure you couldn't see in Word. Below: why the parsed row beats the PDF in daily triage, what Workday and Greenhouse show on screen, exceptions where the attachment matters, and what to fix before the next apply.
When the portal asks for a letter, don't paste your Skills block into paragraph one. Generate a cover letter that cites one employer name and date string from your parsed row so nothing contradicts on audit.
What recruiters actually see after you click apply isn't a mystery once you've opened the preview pane yourself. The rest of this page walks through Workday and Greenhouse field by field so you're not guessing what landed in their queue. You won't fix a silent apply by polishing fonts nobody opens first.
Quick Wins
- Paste your PDF into plain text before you trust the layout.
- Read the employer preview pane line by line when it exists.
- Type must-have skills into empty portal boxes.
- Move phone and email out of headers into body text.
Why recruiters work from the parsed row, not your design
Corporate ATS builds are databases with search, not inboxes of PDFs. When a req collects hundreds of uploads in a week, recruiters sort by date, location, clearance, and keyword inside imported fields. They do not open four hundred attachments from scratch on Monday morning.
The importer extracts name, contact info, employer lines, titles, dates, education, and skill tags into fixed columns. That structure powers filters. A missing phone field removes you from contactable candidates even when the PDF footer shows the number clearly.
That structured record plus your answers to knockout questions is what lands in the recruiter queue. Sponsorship, salary band, work authorization, and years-of-experience gates often live in form fields that never touch your resume file.
Humans still make hire and pass calls once a profile exists. Your job is to make sure the profile exists with the right fields filled. That is a formatting and form discipline problem more often than a secret ranking myth.
Salary expectation boxes and work-authorization questions are part of the same package recruiters see beside your resume row. Leaving them blank can stall the profile even when the PDF parsed. Answer every required field before you assume keywords failed.
Referral links sometimes pre-fill candidate data incorrectly. Compare the preview to your source after using a referral URL. A wrong email on a referral form creates a row you cannot see in your applicant dashboard.
Volume makes the gap feel personal. A corporate req can collect hundreds of uploads in a week. Recruiters sort by date and filter by location or clearance before they read bullet one. You're competing for attention inside a database, not against a single gatekeeper who read every line and hated your font.
Auto-rejection emails are rare in many workflows. Silence is the default when no one moves your row forward. That doesn't prove a robot deleted you. It often proves no one searched the field your file never populated.
For how import failures create silence before anyone reads bullets, see why ATS filters out most applicants . This page assumes your file uploaded and focuses on the recruiter screen after import.
Workday and Greenhouse: what shows on screen
Workday candidate profile
After submit, Workday attaches your upload to a candidate record tied to the req. Recruiters typically see a summary header with name, city, phone, email, and application date. Below that, tabs or sections list parsed work history, education, skills, and attachments.
Before: Two-column Canva PDF. Phone in footer. Dates in a narrow right column.
After: Single-column export. Phone and email in the first three body lines. Employer, title, January 2022 to March 2024 on plain rows the preview confirms.
Search inside Workday queries imported text. Keywords sitting in a table cell that detached from the employer row do not rank under the right job. Flatten layout before you argue about wording.
Headers and footers are repeat offenders. Some Workday builds skip them entirely. Move name, city, phone, and email into the top body lines. LinkedIn URL can stay on its own line below email when the posting expects it.
Graphics and icons in contact rows parse as blanks. A phone icon beside the number sometimes drops the digits. Use plain text labels: Phone:, Email:. Boring survives import.
Greenhouse candidate profile
Greenhouse shows parsed resume sections beside application answers. Recruiters move candidates through stages and leave notes on the profile, not on the PDF. Custom questions appear as separate fields: portfolio links, clearance, compensation, referral source.
Before: Attachment only. Skills box on the form left empty.
After: Same PDF plus skill box filled with exact tool names from the posting. Work history dates typed to match resume strings.
I've screened stacks in Greenhouse and Workday, and I open the parsed Experience row first, not the PDF attachment, because that's what search and filters use.
Fields recruiters scan in the first pass
On a fresh req triage, most recruiters scan contact completeness, current title, last employer, total years in relevant roles, location or remote answer, and whether must-have tools appear under dated Experience lines. Cover letters and portfolios come later when the row already looks viable.
Edge case: small employers on lighter ATS builds may lean on the attachment more. Still run the preview when offered. Parser rules overlap more than vendor marketing suggests.
Edge case: employee referrals sometimes pre-fill candidate data. Compare the preview to your source after using a referral URL. A wrong email on a referral form creates a row you cannot see in your applicant dashboard.
Edge case: mobile uploads from a phone photo or screenshot fail every time. Use a saved export from your laptop. Camera PDFs aren't readable imports and recruiters see blank Experience when they open your row.
Edge case: career gaps with honest Month Year boundaries still parse when the layout is flat. Don't hide gaps with year-only blocks that make the importer guess months. A labeled career break line beats a scrambled timeline that fails search.
When two fields overlap, fix parser order first, then portal form boxes, then knockout answers. A filled skill box on a two-column file still stores keywords under the wrong employer. Flatten, preview, then type portal fields.
Copy-paste block: ten-minute post-apply audit
1. Export the exact file you uploaded (PDF or DOCX)
2. Paste into Notepad: contact info present? Y / N
3. Experience before Skills in plain text? Y / N
4. Each employer has title + Month Year dates? Y / N
5. Portal preview matches source row by row? Y / N
6. Skill boxes filled with posting nouns? Y / N
7. Knockout answers honest and compatible? Y / N
If any N: fix layout or form before keyword edits
For file-type choices that change import order, read Word resume vs PDF resume for ATS . Pick the format the portal accepts, then test the export.
Recheck file size before upload. Some portals reject oversized PDFs without a clear error. Export at normal quality from Word instead of print-ready archives that stall mid-transfer. Under ten megabytes is a safe default for most corporate portals.
Save a screenshot of the preview pane when it looks correct. If a recruiter later sees a different layout, you'll have proof of what you submitted. Most disputes are honest parser drift, not conspiracy.
Track which import field broke in a simple log: contact, Experience order, skill box, or knockout answer. When screens start after a flatten pass, you know layout was the blocker on earlier silent apps. When screens stay silent after clean previews, shift time to stronger bullets and tighter req fit instead of more uploads.
For keyword placement after import is clean, see resume keywords for job applications . Wording tweaks only help once the row stores your Experience block.
When the PDF attachment still matters
The parsed row is first. The attachment is not never. These exceptions explain why recruiters sometimes open the file after all.
Import failure or partial parse. When Experience imported empty, recruiters open the PDF to salvage data or confirm you are not a spam apply. A broken import wastes their time and yours.
Before: Fancy sidebar layout. Importer stored Skills above Experience.
After: Flat single column. Preview shows employer before tool list.
Portfolio or writing samples. Design, UX, and some marketing roles expect links or PDF portfolios. Those sit as attachments or URL fields. They supplement the row; they do not replace contact and Experience import.
Executive or academic CV norms. Longer CVs with publications may get more attachment reading, but corporate reqs still run search on parsed fields first. Do not skip the preview because the document is long.
Dispute or audit. When a candidate claims the portal mangled their file, recruiters compare attachment to preview. Screenshot a clean preview when you submit so you have proof of what you sent.
Re-upload locks. Some employers attach the first file to your profile for every req on that build. Check the preview before a second upload creates duplicate rows. Export a corrected single-column file, verify in plain text, then submit once on a fresh req if the portal already stored a broken version.
Before: Blamed a secret robot after ten identical uploads of the same two-column template.
After: Flattened layout, filled portal fields, one upload, preview confirmed.
This will not fix applying to roles where honest knockout answers fail. It stops qualified files from vanishing because recruiters never got a searchable row with your email in it.
Believing a cover letter bypasses import rules sends the same file twice without fixing the row. Attach the letter when asked, but fix the resume profile first. Letters rarely backfill a blank Experience block.
Chasing every new ATS rumor on social media wastes time better spent on a plain-text paste. The failure modes in this article repeat across employers because parsers share the same limits, not because each company runs a unique secret test.
Verify import before the next application
Run your export and the posting through HireFlow's free ATS resume checker . Fix parser warnings, then confirm must-have terms appear in Experience on the scan readout.
When you are rebuilding from a broken template, build your resume in a single-column layout with contact fields in the body so the next export survives a plain-text paste.
Do this now: Plain-text paste, read preview, fill empty portal boxes, answer knockouts honestly, upload once.
What to do now
What recruiters actually see after you click apply is the profile the importer stored, not the version you designed in Word. Flatten broken layouts, fill portal fields, and confirm the preview before you tune keywords in Experience bullets.
- Paste your export into plain text tonight.
- Compare every preview row to your source file.
- Move contact info into the document body.
- Type skill nouns into empty form boxes.
- Submit one verified upload per req.
Open the next req you're targeting. Run a free ATS check , fix what the importer missed, and send a single clean application.
You already did the hard work building the experience. You're making it visible in fields recruiters can search. One verified upload beats five identical files that all import with the same blank phone number.
Read more
Frequently asked questions
Most corporate workflows open the parsed profile row first because search, filters, and sort lists run on imported fields. The PDF attachment is a backup when Experience imported blank or dates scrambled. Fix the preview pane before you assume keywords failed. A polished PDF with an empty phone field still drops you from contactable filters.
Workday stores candidate data in structured tabs: contact fields, work history rows, education, skills tags, and knockout answers from the form. Recruiters often see a summary strip with name, location, years of experience calculated from parsed dates, and application status. The original file may sit under attachments, but daily triage uses the imported rows.
Greenhouse shows a candidate profile with parsed resume sections on the left and application answers on the right. Recruiters filter by stage, source, and keyword matches inside parsed text. Custom application questions appear as separate fields, not inside your PDF. If you left skill boxes empty because the resume is attached, search may miss you even when the PDF looks fine.
Cover letters usually sit as a separate attachment or text field. They rarely populate the searchable Experience block. Recruiters may open them after your row passes initial filters, not when the profile imported with missing contact info. Put must-have terms in bullets and portal skill boxes first.
You preview the PDF in a reader. Recruiters work inside the ATS import. Two-column layouts, header contact lines, and tables often reorder text on import. Run a plain-text paste test and compare the employer preview pane line by line. What you see in Word is not what Workday stored.