11 min read
You've spent an hour polishing the PDF. The recruiter didn't open it. They passed in list view because your parsed row showed the wrong title, a blank location field, and a red flag on a required certification. You're not losing to a mystery algorithm. You're losing to a profile row built on upload.
Check your resume for free on the same file before you assume the attachment saved you. On US corporate reqs in Workday and Greenhouse, recruiters often scan a parsed profile row first: name, current title, employer, city, and match flags. The PDF is step two, not step one, and you can't fix a row you haven't checked.
Below you'll see what that row is judged against, before/after pairs across different roles, what weak parsed profiles share, and a copy-paste employer line you can use tonight. Job searching is draining. This page is about making the list view accurate, not debating whether ATS is fair.
If you've been tweaking keywords while your sidebar still parses as your job title, flip the order. Layout fixes come before tailoring. You can't keyword-stuff your way out of a row that says your top role is Salesforce Admin when you're a project manager.
And when the portal asks for a cover letter after upload, don't paste lines that repeat the same scrambled profile. Generate a cover letter from the corrected resume text so the note matches the employer order you fixed in Word.
Quick Wins
- Put title, employer, and Month Year dates on one line per role.
- Move city and phone into the body under your name, not the header.
- Flatten two-column templates before you upload to Workday or Greenhouse.
- Open the portal preview if it exists and read the row, not only the PDF.
The bar a recruiter list row must clear on US ATS
Workday, Greenhouse, Lever, and iCIMS all build a candidate profile when you upload. Recruiters working US corporate reqs often live in that list view for the first pass. They sort, filter, and pass before they click your attachment.
The standard your parsed row is judged against: name readable, current or most recent title matching the req function, employer name attached to that title, location that matches the role's geography or remote rules, and match flags that don't flash red on must-have requirements.
A composite data analyst whose skills sidebar parses first looks like their current job is Python, SQL, and Tableau. The real employer drops to row four. Same person, same career. Different screen because layout drove parse order before any human opened the file.
What recruiters see before opening your resume is rarely the designed PDF. It's the fields the ATS extracted. When those fields disagree with your attachment, recruiters trust the row they can sort on. I've passed on strong PDFs when the parsed title was blank or the location field showed a different state than the req allowed.
Read why manual resume review is almost gone for the wider filter story. This page is the list view row and what to change in Word before upload.
Naming Workday or Greenhouse is allowed. Claiming how they rank candidates internally is not. This teardown sticks to what you can observe: parsed title, employer pairing, location, and requirement flags on the screen recruiters actually use.
Edge case: you're applying remote but your resume lists a city the req tags as out of region. The row may show a location mismatch flag even when your bullets say open to remote. Put Remote or the target metro on the contact line when the posting allows it.
Edge case: you're a contractor with three short gigs this year. The parser may only surface the first employer in the row. Lead with the role most relevant to the req so the list view headline matches the function you're targeting.
What recruiters see before opening your resume: before/after row pairs
Each pair shows what the recruiter row tends to display, then the export fix. Swap in your employers and titles. Illustrative roles only.
Pair 1: Marketing manager, skills sidebar wins
Before: List row shows title Google Analytics, HubSpot, SEO. Employer field blank or reads Certifications. Location parses from a footer.
After: Row shows title Digital Marketing Manager, employer RetailCo, location Austin, TX. Skills live inside dated bullets under that employer.
Recruiters scanning a performance marketing req never open the PDF when the row says your job is HubSpot. Flatten the column, then tailor bullet one.
Pair 2: Software engineer, GitHub link becomes the title
Before: Footer holds github.com/handle on every page. Row shows title github.com/handle or a stray URL. Employer line missing.
After: github.com/handle on line three under email in the body. Row shows title Software Engineer, employer FinTechCo, dates Jan 2022 to Present.
Footers parse late or early depending on the ATS. A recruiter row with a URL where the title should be reads as incomplete before they click anything.
Pair 3: Nurse, license block replaces title
Before: ACLS and RN license sit in a table above Experience. Row shows title ACLS Certified or Registered Nurse under Skills.
After: RN license on line two under name. Row shows title Staff RN, employer County General, unit type in bullet one with Month Year dates.
Before: Med-surg, telemetry, 6:1 ratio; managed acute care patients.
After: Staff RN, Med-Surg/Telemetry, 32-bed unit, 6:1 ratio; precepted 4 orientees and maintained fall-rate below unit average in FY24 at County General.
Pair 4: Project manager, quota callout detaches
Before: Right rail text box: FY24 quota 118%, $2.1M closed. Main column lists employers without metrics. Row shows attainment with no company.
After: Row shows title Senior Project Manager, employer LogiCo. Quota and attainment sit in bullet one under that employer with Month Year dates.
Side callouts don't map to employer fields. Recruiters can't tell which role earned the number when the row shows a floating metric.
Pair 5: Customer support lead, summary box drops
Before: Gray text box summary floats beside the name. Row shows blank summary and title Customer Service when the req asks for Support Team Lead.
After: One-line summary under contact as normal body text. Row shows title Support Team Lead, employer SaaSCo, with Zendesk and CSAT in bullet one.
Floating objects often never reach the profile field recruiters skim. Plain body text under your name does.
Pair 6: Operations analyst, dates separate from employer
Before: Dates sit in a left margin column. Row shows title Operations Analyst with employer 2019 to 2023 or a blank company field.
After: Mar 2019 to Jun 2023 · OpsCo · Operations Analyst on one line. Row pairs title, employer, and tenure correctly.
Margin dates break employer pairing in multiple ATS builds. Recruiters read a gap or a nonsense employer string and move on.
Copy-paste employer line for a clean parsed row
Paste this at the top of each role block and replace bracketed lines:
[Month Year] to [Month Year or Present] · [Employer] · [Title matching the req function]
[Bullet with verb, scope, tool, and outcome tied to this employer]
[Second bullet with a req keyword in the first eight words]
Export PDF from a single-column Word file. Open the portal preview if Workday or Greenhouse offers one. Upload when the row shows the right title and employer before you tweak keywords again.
See resume rejected by ATS when the row looks right but you still never hear back. Parsing is step one. Fit is step two.
What weak recruiter list views still share
Trusting the PDF because it looks fine on your screen. Recruiters may never open it. The parsed row already buried your current role under Skills.
Stuffing keywords into a sidebar after a failed upload. More text in the wrong column makes the title field worse, not better. Flatten first, then tailor bullets.
Repeating contact info in header, footer, and body. Duplicates fight for the same fields. Pick one body block and delete the rest.
Using creative section headers. My Journey and Where I've Been don't map to Experience in most parsers. Standard labels are boring on purpose.
Skipping the preview on mobile. Wait until you can open the desktop list view once. A scrambled row is harder to fix after submit on some reqs.
Assuming match score alone gets you opened. Sort order helps. A wrong title or location flag still kills the click.
Leaving the req title only in the cover letter. If the row doesn't show that title string, the letter may never get read. Mirror the posting language on the employer line for your current role when bullets prove it.
Uploading a scan of a printed resume. OCR guesses characters. Employer names and titles are the first fields to break in the row.
Verify the parsed row before you hit submit
Run the export through the free ATS checker with the job description pasted in. You're confirming employer-title pairing and whether skills landed in Experience, not chasing a perfect score.
Then score your job match on the same plain-text order. Keywords only help after the ATS can attach them to the right job line. A high match on a scrambled row still loses to a readable lower score.
Fix the parsed row tonight
What recruiters see before opening your resume on US ATS is the profile row, not your designed PDF. Title, employer, location, and match flags decide whether anyone clicks the attachment. Flatten to one column, pair dates with employers, and read the portal preview when it exists.
Pick the next req on your list. Apply the copy-paste employer line. Run a free ATS check. Open the list view if the portal shows one. Upload when the row matches the function you're targeting.
This won't fix applying to roles you're not qualified for. It does stop qualified candidates from losing screens because the parsed title said HubSpot while their project management PDF sat unopened.
When you need a clean base file, build your resume in a single-column layout before you tailor for the posting. Parse order first. Keywords second.
Read more
Frequently asked questions
No. On high-volume US reqs, many recruiters start in the ATS list view built from your upload. They see parsed name, current title, employer, location, and match flags before they click the attachment. If that row looks off, the PDF may never open.
Typical rows include candidate name, most recent job title, current or last employer, city and state, application date, and keyword or requirement match indicators. Some systems add education, years of experience, or knockout question answers. The exact layout varies by ATS and employer setup.
Parsing pulled the wrong line. Sidebars, tables, and header contact blocks often push a skills list or certification into the title field. Fix export order in Word before you tailor keywords. A clean single-column file usually maps title and employer correctly.
Yes. Put your target title on the employer line for your current role, keep Month Year dates on the same line as the company name, and move contact info into the body. Those three edits change the parsed row more than a new font ever will.
It influences sort order, not the final hire. Recruiters still pass on high scores when the title or location looks wrong for the req. A readable row with moderate keyword overlap often beats a high score attached to a scrambled profile.