7 min read · Recruiter screen
Two Greenhouse tabs. Same req. Same years on paper. One candidate gets a phone screen tag in thirty seconds. The other sits in maybe until Friday. Nobody printed both PDFs. The compare pane did the work, and you won't see why until you read what imported.
Before you tweak another skills row, check your resume for free against the posting you're targeting. You need to know whether bullet one and your headline title actually import clean in a side-by-side view, not whether Word looks fine on your laptop.
Below is what corporate recruiters scan when two files land in the same shortlist. It's not a personality contest. It's a four-field header read, then a scroll decision. Fix those fields tonight and you'll stop losing ties you didn't know were ties.
Quick Wins
- Mirror the posting title in your headline when your scope supports it.
- Rewrite bullet one with an action verb, object, and scoped outcome from your real work.
- Run a plain-text copy test so Skills doesn't import above your current job.
- Line up month-year dates on the latest role so the span math is obvious.
Side-by-side view in the ATS
Greenhouse opens a compare layout when a hiring manager shortlists two or more applicants on the same req. Workday shows a similar split panel in candidate review. You're not looking at your designed PDF. You're looking at parsed fields the system extracted from the upload.
Typical panes include candidate name, location, headline title, current company, application date, source tag, and the first experience block the parser read. Attachments sit behind a link. On a fast screen, recruiters skip the PDF when the summary already shows a gap or title mismatch.
Match score badges sort a long stack. They don't settle a tie in compare mode. Once you're paired, the human eye goes to headers and bullet one. Two-column layouts scramble that view when Skills import above your current title.
Four fields compared before anyone gets called
On a shortlist of two, these four imported lines get read in order. Miss on one and the phone screen note goes to the other file.
| Field | What recruiters check | Loses the tie when… |
|---|---|---|
| Headline title | String match to req title or accepted adjacent label | Internal nickname or inflated seniority with no proof |
| Current employer | Brand recognition, domain fit, competitor overlap | Unfamiliar shop with no domain cue in bullet one |
| Latest role dates | Tenure length, gap math, contract vs full-time pattern | Overlapping dates, missing months, unexplained gap |
| Bullet one | Action, scope, outcome tied to posting themes | Passive opener, duty list, or tools with no result |
Bullet one is the tiebreaker more often than candidates expect. Two platform engineers with the same years and the same tools in Skills can split on whether the top bullet names cluster scope, on-call load, or deploy outcomes. The loser still listed Jenkins twelve times. The winner named one pipeline change with a result.
For date formatting that keeps span math readable in Workday, see month-year vs year-only on resume dates .
How job titles get ranked against the req
Recruiters don't philosophize about your internal branding. They ctrl-f the req title string against what imported into the headline field. Exact or near-exact matches float to the top of a mental sort. Adjacent functional titles need proof in bullet one. Inflated titles need extra scrutiny.
Exact match: posting says Senior Product Manager and your headline says Senior Product Manager. Fast pass if dates and bullet one back it up.
Adjacent match: posting says Account Executive and your employer called you Client Partner. Pass possible when bullet one uses revenue scope, quota language, or deal size that matches the req.
Inflated match: posting says Manager and your headline says Director with no team size in any bullet. Compare mode flags this against a second candidate who kept the accurate title and showed lead scope in bullet two.
Deeper title logic lives in how recruiters interpret job titles . Read that before you rename yourself for a single req.
When I stop scrolling through a stack
Scroll speed matters because most corporate reqs still carry more applicants than interview slots. A recruiter isn't reading every bullet on every file. They're hunting for a reason to advance or discard before the next meeting starts.
I've screened paired files in Greenhouse where both candidates listed the same tools, and stopped on the one whose bullet one named a bounded outcome while the other still opened with responsible for cross-functional collaboration.
Other stop signs: parse errors, unexplained gaps, hybrid location conflicts, and referral tags on a rival when you applied cold. Weak lines in bullet four won't rescue a file after a vague bullet one.
What splits two similar files
When headers and bullet one look close, secondary signals decide. These show up in the ATS chrome around the resume, not always in your PDF.
- Location and work authorization: hybrid rules and sponsorship needs filter before anyone debates skill depth.
- Source tags: referral or internal transfer labels can move one name ahead when both summaries parse clean.
- Domain overlap: same title at a direct competitor beats a generic services shop when employer names get skimmed first.
Pre-apply checklist
Run this sequence on the exact file you'll upload. Compare mode reads imported text, not your intent.
Before: Skills block lists Terraform, Kubernetes, Jenkins, Docker, Ansible, Python, AWS, GCP, monitoring, Agile, and DevOps culture. Bullet one says Managed CI/CD pipelines and supported production environments.
After: Skills block is shorter. Bullet one says Migrated eighteen services from manual Jenkins deploys to GitHub Actions with canary gates, cutting failed prod releases from six per month to one. Terraform appears in the bullet, not twelve times in isolation.
Before: Headline title says Platform Engineer while the posting asks for Senior DevOps Engineer with no scope proof in bullet one.
After: Headline mirrors Senior DevOps Engineer when scope supports it, and bullet one names cluster hardening with a scoped MTTR or deploy metric from your real on-call work.
Copy-paste: compare-mode pre-upload check
{`1. Paste upload into Notepad. Skills must not appear above current job title.
2. Mirror posting title in headline when scope supports the label.
3. Rewrite bullet one: verb + object + one honest outcome tied to the req.
4. Confirm month-year dates on latest role; fix overlaps and unexplained gaps.
5. Re-upload and skim parsed summary as if you're the second candidate in a tie.`}
- Copy the posting title into your headline when your scope supports the label.
- Rewrite bullet one with action, object, and one honest outcome tied to the req.
- Confirm month-year dates on the latest role; fix overlaps and unexplained gaps.
- Paste the upload into Notepad or TextEdit; Skills must not appear above your current job.
- Match the portal file type: DOCX when allowed, text-based PDF when not.
- Trim Skills to tools you used in the last three years; drop buzzword padding.
- Skim employer name and location lines for typos that break trust in compare view.
How recruiters compare candidates quickly isn't a mystery once you treat the ATS summary as the first resume a human sees. Nail the four header fields, prove scope in bullet one, and you'll stop losing silent ties to plainer files that simply imported cleaner.
Check bullet one before you upload
Open the posting side by side with your resume file. Highlight three must-have themes from paragraph one of the req. If none of them appear in bullet one, rewrite that line before you touch Skills.
Check your resume for free on the bytes you'll attach. Parsing errors show up before keyword scores do. Fix layout first so compare mode imports your title and dates in the right order.
Then run job match score against the same posting to see whether your proof lines land on the themes recruiters ctrl-f in a stack. Use the score to adjust bullet one, not to inflate a skills grid.
When the portal also asks for a letter and your resume already proves fit, generate a cover letter only if the field is required or you need one context line the resume cannot show in ten seconds.
Do this now: Rewrite bullet one. Paste into plain text. Upload only when title, dates, and top bullet read clean in that order.
Win the compare pane, not the PDF beauty contest
How recruiters compare candidates quickly boils down to imported headers and bullet one in Greenhouse or Workday. Two similar files split on title fit, date math, and whether the top bullet shows scope or just tools.
Run the pre-apply checklist on the file you'll actually upload. Plain layout, honest title alignment, and one proof-heavy bullet beat a keyword-stuffed Skills block every time two summaries sit side by side.
This won't override a hard requirement you don't meet. It stops qualified files from losing a thirty-second tie because the compare pane imported your skills column before your job title.
Read more
Frequently asked questions
Not on the first pass. In Greenhouse and Workday, the compare view shows parsed headers, current employer, dates, and the first few experience lines. Full scroll happens only after someone clears that header screen. If bullet one is vague, the rest of the file may never open.
No. Match scores help sort a long stack, but when two files sit next to each other, recruiters look for proof in bullet one, not a longer skills list. A keyword grid without scope in Experience often loses to a shorter file with one honest metric in the top bullet.
Align only when your real scope supports it. Mirror the posting's functional label in your headline or add the employer's official title in parentheses. Do not jump a seniority band you never held. Recruiters rank exact title matches first, then adjacent titles with proof, then inflated labels.
Parse errors, date gaps without context, title inflation, and bullet ones that start with responsible for instead of an action. Referral tags and internal transfers can also end the scroll early for good reasons. Fix layout and bullet one before you worry about keyword density.
Copy your upload into a plain-text editor and read top to bottom. If contact lines duplicate or skills import before your current title, the ATS summary will look scrambled in compare mode. Run a free format check on the exact bytes you'll attach, then tailor bullet one to the posting.