6 min read
Myth versus reality: you don't lose because a robot hated your font. You lose because the row shows the wrong title, scrambled employers, or a failed knockout before anyone opens the file.
You're not failing a secret percentage test on the first click. You're failing a ten-second scan on structured fields that may never match your Canva design.
Check your resume for free on the same export you'll upload. Fix the row story before you argue with keyword lists.
Tonight you'll walk the checklist below against one target posting and one portal preview if the employer shows it.
Quick Wins
- Set headline or target title to the posting title string verbatim.
- Keep current employer and dates contiguous in a single-column file.
- Answer knockout questions before you polish bullet synonyms.
Why the ATS row beats your PDF on the first pass
Applicant tracking systems exist to move hundreds of applies into a sortable list. Recruiters live in that list during intake. Workday, Greenhouse, Lever, and iCIMS skin the UI differently, but the job is the same: show me who looks like this req without opening fifty PDFs.
The row is built from parsed resume fields plus application answers. Cover letters and portfolios may sit in other tabs, but the first sort key is usually employer, title, and dates on the profile.
What recruiters see in ATS before opening your resume is that composite: a name line, a title cell, tenure hints, location, source, status, and sometimes a match chip. Attachments are behind a second click recruiters only spend when the row already fits the mental model of the role.
Before: You optimize margin spacing in the PDF while the portal preview shows Skills above Experience.
After: You flatten columns, reorder sections, and re-upload until employer lines pair with bullets.
For the next screen after filters, see what recruiters actually see after ATS screening so you know what changes once you're in the reviewed pile.
What recruiters see in ATS before opening your resume: field checklist
Run this table against one apply tonight. You're auditing the row, not the aesthetic resume.
| Field | Shows in queue | Fix tonight |
|---|---|---|
| Name and contact | Header row, click target | Plain text lines, no icons |
| Current title | Sort and filter key | Match posting title string |
| Last employer | Credibility at a glance | Legal company name, dated |
| Tenure on latest role | Stability signal | Month/year on same line as employer |
| Location | Hybrid or onsite filters | Align with posting geography |
| Knockout answers | Auto reject flags | Read every dropdown twice |
| Match or status chips | Sort inside the pool | Fix row before chasing chips |
Copy-paste header order so parsers read employers before long skill lists:
Contact
Headline (posting title)
Summary (2–4 lines)
Professional Experience (newest first, dates on employer line)
Skills (short)
Education
Before: Skills grid fills the first screen; current job starts mid-page two in preview.
After: Current employer and bullet one finish in the top third of page one.
Before: You rely on a match chip while the title cell says "Consultant" for a "Program Manager" req.
After: You rename the headline to the posting title and prove program scope in bullet one.
I've skipped opening attachments in Taleo when the row showed a freelance title as current while the req was full-time W-2 product work. The PDF might have explained it on page two; the row already told the wrong story.
Application timestamps and source tags also show in the row (referral, agency, career site). You cannot rewrite source after submit, but you can avoid duplicate profiles that split your history across two rows.
Recruiters sometimes filter on application stage before they ever sort by match. New applies sit in an unreviewed bucket; stale rows drop when the req pauses. Refreshing the same file weekly without changing the row rarely moves you up if the title cell still mislabels your scope.
Internal mobility and referral flags can surface as icons beside your name. Those icons do not replace a readable employer line; they only nudge a recruiter who already has capacity to open attachments that hour.
Pair with what recruiters look for first in ATS when you want scan-order detail on the same queue.
Row mistakes that stop the attachment click
- Two-column templates that import employers out of chronological order.
- Graphics used as section headers so Experience imports after Education.
- Multiple concurrent jobs listed without a clear "current" primary role.
- Knockout answers that contradict the resume (sponsorship, clearance, onsite).
- Uploading a new resume without deleting an old profile that still surfaces in search.
Before: You chase a higher match chip with synonym stuffing.
After: You fix title, employer pairing, and knockout truthfulness, then tailor bullets.
Layout traps overlap with resume sections ATS reads first when you're rebuilding section flow from scratch.
Preview the row before you submit
Paste into Notepad, read aloud top to bottom, and compare to any employer preview. If you stumble before current role, fix order before synonyms.
Run the ATS check on the bytes you'll attach so employers stay paired with dates.
Check job match score against the posting text after the row fields look honest, not before.
Generate a cover letter only after the profile row imports cleanly and you need a short human tab for a pivot or gap.
Win the row, then earn the PDF open
What recruiters see in ATS before opening your resume is the contract you sign with their calendar. Make title, employer, and dates honest in the parsed view, clear knockouts, then polish bullets inside the attachment they'll finally open.
Save a screenshot of portal preview when the employer offers it. Comparisons beat memory on the next rewrite.
When the row looks right and silence continues, the gap is often level or req closure, not another font change. Move on with a clean file ready for the next posting.
Phone screens still start from the same row data your recruiter saw yesterday. Keep headline, employer, and dates aligned across every re-upload so you are not fighting two versions of your story in the same req.
If a friend can name your current title from the portal preview alone, you've done enough row work for tonight. Polish bullet verbs after that checkpoint passes.
Read more
Frequently asked questions
On the first pass, usually no. They see a candidate row built from import: current title, last employer, tenure, location fields, and match or status chips. The attachment opens after that row earns a click. A pretty PDF can still produce an ugly row.
Title mismatch against the req, blank employer cells, or knockout answers that fail work authorization or location rules. Keyword lists in a Skills tab rarely save a row when the headline does not map to the posting title string.
Many req setups show a match or ranking hint, but not every employer exposes it to recruiters the same way. Treat chips as a sort aid inside the pool that already passed filters, not a promise that a human will open your file.
Paste the resume into a plain text editor and read top to bottom. Compare order to any portal preview the employer exposes. If employers and dates land in the wrong blocks, fix layout before you tweak synonyms.