12 min read
You've polished bullets for an hour, but the recruiter opens a profile with a blank phone field. That's not karma. It's usually a header row, a Canva icon, or a two-column contact strip the parser skipped on the way to your experience section.
Check your resume for free after you fix the header. Parser dumps show missing email faster than guessing from a pretty template, and you won't catch a sidebar trap by squinting at the PDF preview alone.
Below: why parsers fixate on the top block, the layout exceptions that still work, copy-paste contact lines by situation, and what to change tonight before you upload again.
Job searching's already draining. You don't need another lecture on keywords. You need a header a tired coordinator can copy without opening your PDF twice, and that's the whole game for call-backs on day one.
Quick Wins
- Name on its own line, then phone, email, and city as plain text.
- Drop icons, tables, and text boxes from the contact strip.
- Type LinkedIn and portfolio URLs as visible characters, not buttons.
- Export PDF from Word or Google Docs, not a design tool, for uploads.
Why parsers treat your contact block like a separate document
Most US ATS products read top to bottom in one column. They hunt for patterns: a name line, a phone pattern, an email with @, sometimes a city and state. Anything in a floating text box, a page header, or a narrow sidebar often never joins the candidate record recruiters see in Workday or Greenhouse.
That mismatch hurts twice. Keyword scoring may still run on your experience, but coordinators schedule screens from the profile card. Empty phone fields slow everyone down, and some teams simply move to the next row when contact data is missing.
Design tools love icon rows and color bands. Parsers love 11-point Calibri on white. You can keep a designed version for humans at a career fair; the upload version should look like a typed memo at the top.
I've screened stacks of these in Workday and Greenhouse, and the file that clears parsing is almost always boring: full name, one US phone, one professional email, city and state, optional LinkedIn as plain text.
iCIMS and Taleo behave similarly even when the employer skin looks different. The lesson is not brand-specific magic. It's reading order. Contact data has to appear before section headings like Summary or Experience, and it has to live in the body, not the margin.
Some candidates hide email behind a mailto button styled like a badge. Recruiters see a blank field. Same story for phone numbers stored as images exported from a design app. If you cannot select the digits with your cursor in Word, assume the parser cannot either.
State abbreviations beat spelling out Indiana on a tight line. ZIP codes help coordinators confirm metro filters without guessing from city names alone. You are not mailing a package; you are giving structured geography parsers can sort.
Hyperlinks illustrate the gap. Word stores a URL behind blue text. Some parsers export only the display word, not the target. Typing linkedin.com/in/yourhandle without a field code gives parsers and humans the same string.
Remote candidates still need a location line recruiters can filter on. City and state are enough for most reqs. You are not hiding remote status; you are giving timezone and tax geography a anchor without publishing your apartment number.
For broader layout failures beyond the header, read why resume formatting breaks in ATS so you fix reading order once instead of patching one field at a time.
What to do now: resume contact info formatting that never breaks ATS (US)
Treat the header like a form, not a logo. These before/after pairs are templates for different situations. Swap in your details; keep the structure.
Default corporate upload (operations coordinator)
Before: Name tucked in a blue sidebar with phone icons and a QR code for LinkedIn.
After: Alex Morgan on line one. Phone: 404-555-0182 on line two. Email: [email protected] on line three. Location: Atlanta, GA 30303 on line four. LinkedIn: linkedin.com/in/alexmorgan on line five, all plain text.
Recent grad with campus and home cities
Before: Two addresses stacked with emoji pins and no clear primary phone.
After: Priya Nair. Phone: 512-555-0144. Email: [email protected]. Location: Austin, TX 78705. One number, one email, one city line the recruiter can filter on today.
Contract business analyst between clients
Before: Contact details only in the Word header so every page shows a logo.
After: Jordan Lee at the top of the body. Phone: 312-555-0171. Email: [email protected]. Location: Chicago, IL 60601. Header/footer cleared so parsers read the block once.
Nurse with compact license line
Before: License number jammed into the same table cell as phone and email.
After: Maria Santos on its own line. Phone and email on separate lines. Location: Phoenix, AZ 85004. License: RN Arizona #123456 on the next line as plain text, not inside a table grid.
Copy-paste block: five-line header
Copy-paste contact block (edit brackets)
[First Last] Phone: [###-###-####] Email: [[email protected]] Location: [City, ST #####] LinkedIn: linkedin.com/in/[handle]
Pipe-separated single lines can work when every token is labeled implicitly: Name | phone | email | city. Parsers sometimes merge pipes into one field, though, so stacked lines are safer when you have doubts.
Keep fonts standard: Calibri, Arial, Helvetica, or Times New Roman in black. Fancy script fonts on the name line occasionally OCR into garbage on scanned uploads.
If you must list two phones, put Mobile on the second line instead of cramming both into parentheses on one line. Coordinators dial the first number they see.
Professional email beats clever handles. plus-addressing in Gmail is fine for humans; if you worry about an older parser, use a simple alias without special characters for applications.
After the header, start Summary or Experience. Do not insert a horizontal rule made of underscore characters. Some parsers treat those as section breaks and skip the next line.
Save the file with a boring filename: FirstLast_Resume.pdf. The contact block still matters more than the filename, but recruiters search downloads by name when inboxes get messy.
When a posting asks you to paste into a plain text field, mirror the same order: name, phone, email, city. Mismatched order between PDF and form confuses coordinators even when both parse.
Veterans sometimes list a defense email and a civilian email. Pick one primary line for the resume header and mention the alternate in a cover note if the posting allows attachments. Two emails on one line without labels often map to the wrong field in Lever imports.
Sales roles sometimes want territory in the header. Add Region: Southeast US as a labeled line under location instead of folding territory into a clever tagline above your name. Parsers treat taglines as names when they sit on line one.
If you changed your name, put the legal name recruiters will background-check on line one and add a former name in parentheses only when you have room without crowding phone and email. Never bury the reachable phone under a nickname line.
When the usual rules bend (and when they do not)
Creative portfolios. Designers sometimes need a visual header for walk-in reviews. Upload the plain version to Lever or Greenhouse and hand the designed PDF to humans in the room. Same person, two files, two jobs.
International dialing. If you are applying to US employers from abroad, lead with +1 and the US number you will actually answer during their business hours. Do not bury a foreign mobile the coordinator cannot dial without a cheat sheet.
Clearance or federal forms. Some USAJOBS flows ask for address detail in the website, not on the resume attachment. Follow the form. Your PDF header can still stay minimal while the application carries the legal address.
Before: Pasted the entire LinkedIn URL with tracking parameters and utm tags.
After: Shortened to linkedin.com/in/handle with no query string so parsers and humans see the same path.
Before: Used a two-column Canva template because it looked modern.
After: Rebuilt as one column for uploads; kept the pretty version offline for networking.
Tables are not automatically evil, but contact tables inside templates often map phone into the wrong column on export. When in doubt, delete the table and type five lines.
This will not fix applying to roles you are not qualified for. It stops a qualified file from dying because nobody could call you from the ATS profile.
For file type choices after the header is clean, see PDF vs Word resume for ATS and export the format the posting names first.
Academic CVs sometimes run three pages with multiple affiliations. Corporate US uploads still want a short contact block on page one before publications. Move long lists down; keep the phone readable without scrolling.
Test the header before you mass apply
You should not trust your eyes alone. Word shows layout; parsers show text order. Run the same file you will upload through a checker that prints extracted fields.
Paste your target posting into score your job match after the header is fixed. Missing contact data wastes applies on reqs you were already qualified for.
Then open the free ATS checker on the PDF or DOCX you plan to submit. If name or phone comes back blank, rebuild the top five lines before you touch bullets.
Do this now: Open your resume, delete icons and text boxes from the contact strip, paste the five-line block from above, export, and run one parser check before your next application.
Bonus tip: compare plain-text paste from your PDF into Notepad or TextEdit. If phone and email disappear in the paste, the parser will struggle too.
When you rebuild from a template, build your resume in a single-column flow so you are not fighting margins at midnight.
Keep a screenshot of the parser output in your job search folder. When a recruiter says they cannot reach you, you can see whether the issue is formatting or a wrong digit you typed once.
Coordinators often work from mobile dashboards. A clickable tel link in PDF is nice for humans but optional. Plain digits matter more for search inside the ATS.
Re-upload the same corrected file when you fix a typo. Some systems version attachments; others overwrite quietly. Note the timestamp in your tracker so you know which parser run matches which submission.
Read how ATS matches resumes to job descriptions after contact fields parse cleanly. Matching logic cannot score bullets recruiters never see because the profile card was empty.
Fix the header, then argue about bullets
Resume contact info formatting that never breaks ATS (US) is not a design contest. It's a reading-order problem with a five-line solution at the top of the page.
- Plain text name, phone, email, and city before any section title.
- No icons, QR codes, or contact data locked in headers.
- URLs typed out; hyperlinks optional for humans, not required for parsers.
- Parser check on the exact file you upload.
Generate a cover letter when the posting asks for one, then run a free ATS check on the resume you attach. Both files should show the same name and email string.
If you are tempted to redesign the header again, sleep on it. Coordinators remember the file they could call, not the gradient behind your name.
And when a friend asks why interviews stalled, ask what their ATS preview shows for phone. Half the time the fix is ten minutes at the top, not another week on summary wording.
Save one master contact block in your notes app. Paste it into every template before you tweak bullets so digits never drift between versions.
Re-read your outgoing email signature too. If it disagrees with the resume header, recruiters trust the PDF they uploaded. Align both tonight.
You already did the hard part by earning the screen. Make sure the easy part, your phone number sitting on line two, is impossible to miss.
Read more
Frequently asked questions
For most corporate roles, city, state, and ZIP are enough. Full street lines add clutter and privacy risk without helping parsers in Workday or Greenhouse. Federal, clearance, or on-site roles that require residency proof may ask for more in the application, not necessarily on the PDF you upload. Match what the posting requests.
Yes, if the digits stay together. Formats like (617) 555-0198 and 617-555-0198 both parse when the line is plain text at the top. Avoid stuffing extensions, multiple numbers, or emoji icons on the same line. Label a second line as Mobile if you must list two phones.
Many parsers keep the visible text and drop the hyperlink target. Safer pattern: type linkedin.com/in/yourhandle as plain characters with no field code. Same rule for GitHub or a portfolio domain. Recruiters can copy-paste; parsers can read left to right.
Move it out of the sidebar for the file you upload. Put a single-column block at the top with your name on its own line, then phone, email, and location on separate lines or one pipe-separated line. Fancy templates can stay for networking PDFs; the ATS copy should be boring.