11 min read
You've got solid tenure and the portal still shows a blank employer column. That's not because you didn't work there. It's because the parser read your header line as one long string, and it won't fix itself on the next upload.
Most resume advice talks about keywords in bullets. It skips the boring line above the bullets, the one that should carry the company name. When that line breaks, everything under it loses context.
Before you tweak bullet three again, check your resume for free on the PDF you plan to upload. If employer fields are empty or your title landed inside the company box, fix the header block first. Humans notice when the work history panel does not match the file they opened.
Below you'll see why parsers garble employer names, the cases where a symbol or acronym is still correct, and what to change on your experience section tonight so the next apply shows the right company in the ATS sidebar.
Quick Wins
- Put company name alone on line one of each job block.
- Match payroll spelling for symbols like ampersands and periods.
- Move city and state off the employer string.
- Export PDF and read the portal preview employer column.
What the parser does to employer lines
ATS software does not see your resume the way you do. It strips formatting, guesses field boundaries, and maps text into columns labeled employer, title, start date, and end date. Company names are not magical entities to the parser. They are the first chunk of text on a line until a rule says stop.
When you merge employer and title on one line with a comma or pipe, Greenhouse may shove the whole string into employer and leave title empty. Recruiters who filter on title then miss you even when the words are on the page.
Symbols matter because parsers tokenize on punctuation. A healthcare administrator who writes St. Mary's Regional on the same line as Clinical Ops Manager can end up with employer St and a mangled remainder. The human reader fixes it in two seconds. The import does not.
Contract and consulting blocks make this worse. A data engineer lists Apex Solutions / Client: Major Retail Bank on one line. The ATS stores Apex Solutions / Client: Major Retail Bank as the employer, so a recruiter searching for the bank brand never sees the match. The work happened. The field name did not.
Parent companies and renames trip people up after mergers. You still work for the brand customers know, but your W-2 shows the parent. Use the name a recruiter would type into a search box, then add a short clarifier in plain text if you need both.
International characters and dual-language names can flatten to question marks in older parsers. If your official name uses accents, keep the ASCII form on the US resume you upload unless the portal preview shows the accented version correctly.
This will not make a weak profile strong. It stops a strong profile from looking like you skipped employers when the sidebar is empty.
When titles and dates collapse too, read why ATS merges your job titles and dates into one line . When the whole file misimports, start with resume formatting errors that break ATS parsing .
How to format company names so ATS doesn't misread them on each job block
Treat each role as four plain lines: employer, title, location, dates. No tables, no text boxes, no icons. Run the checks in order on your current resume before you tailor bullets for a new posting.
Step 1: Copy the official employer string
Open your offer letter, last pay stub, or the About page on the company site. Paste the employer name into line one exactly, including Inc., LLC, or LLP if that is how they sign contracts. Do not shorten to a nickname your manager used in Slack.
Before: Northwind Logistics (they call themselves NWL internally)
After: Northwind Logistics LLC on line one, with title and dates below
Step 2: Separate title and city from the name
Line two is job title as posted internally or on your badge. Line three is City, ST. Line four is Month Year to Month Year. If you must save vertical space, put City, ST on line two after a pipe on the title line, never inside the employer string.
Before: Beacon Health | RN Case Manager | Boston MA | 2019-2024 on one line
After: Beacon Health Partners on line one, RN Case Manager on line two, Boston, MA on line three, dates on line four
Step 3: Handle consulting and agency roles honestly
If the agency paid you, the agency is the employer field. Put the client in the first bullet or in a short subtitle line under the agency name, not mixed into the employer token. Recruiters who hired through that agency pattern will search the agency. Hiring managers who care about the client brand read bullet one.
I've screened stacks of these in Workday, and the files that import clean use boring four-line headers even when the work was flashy.
Step 4: Preview the employer column in the portal
Upload to a test application or use the employer's preview if they offer one. Scroll the parsed work history. Each employer should match line one from your file. If you see title words in the employer box, split the lines and export again.
Copy-paste block: four-line job header
Copy-paste employer block (repeat per role)
[Legal employer name exactly as on W-2]
[Job title as on internal org chart or posting]
[City, ST]
[Month Year] to [Month Year or Present]
Edge case: you worked two brands under one parent. Pick the brand you want recruiters to filter on for line one. Add a second line in smaller plain text only if the preview still maps employer correctly. If the portal cannot hold two lines, put the secondary brand in bullet one.
Edge case: acquisition mid-tenure. Show the current legal name on line one and note the former brand in the first bullet if that brand is what the req mentions. Do not list two employers for one continuous job unless payroll actually changed.
Before: Software engineer merged employer and client as FinCore @ RetailCo on one line.
After: FinCore Technologies on line one, Senior Software Engineer on line two, bullet one starts with Client: national retail account handling checkout APIs.
Franchises deserve the same discipline. Line one should be the franchise entity on your paycheck, not the national chain slogan, unless your req targets the chain and your paperwork matches that name.
Academic medical centers love long names. Resist squeezing the school, hospital, and department into employer. Put the paid entity on line one and department context in bullet one so filters on health system names still work.
Military and federal titles confuse civilian parsers when rank rides on the employer line. Agency or branch belongs on line one. Rank belongs in title or bullet text, spelled out in plain language civilians search.
Startup renames are common. If the career page still shows the old name, mirror that old name for past dates and the new name for current dates only when payroll legally changed. Otherwise keep one employer string for the whole tenure.
Save a version of your master resume where every employer line is locked. Tailor bullets in copies so you do not accidentally shorten a name while rushing a midnight apply.
When a posting asks you to paste employers into separate form fields, copy from line one of each block instead of retyping from memory. Typos there create duplicates that look like job hopping.
If you worked remotely for a company far from your home address, city line is still where you paid tax, not where headquarters sits. Recruiters compare location fields across candidates. Keep city honest and separate from employer.
Name formatting that breaks imports
Stuffing employer, title, and dates on one line to save space. You save a quarter inch and lose the employer column entirely.
Replacing and with ampersand when the legal name uses and. Follow the paycheck, not the logo guess on a billboard.
Using internal project codes as the company name. Project Phoenix is not an employer. Put the paying entity on line one.
Before: Listed JPM on the header because friends call it that.
After: Used JPMorgan Chase & Co. on line one for the years at that bank.
Putting URLs or social handles in the employer field. Parsers treat slashes and @ signs as breaks. Keep links in contact info only.
Relying on logos or images instead of text. A logo is invisible to text parsers. Spell the name.
Job searching is already slow. Fixing employer lines once beats reapplying with a file that still parses wrong.
Tools after the employer field is clean
Once line one imports correctly, run parse and fit checks on the export you will submit. Clean employer text does not rescue a two-column template.
Run the free ATS checker on your single-column PDF. Confirm employer and title fields populate before you spend an hour on bullets.
Paste the posting into score your job match after headers are stable. Match score is pointless if work history columns are empty.
If the application asks for a short note, use the cover letter generator only after employer lines match the form. Mention a client brand in the letter when the posting cares about that brand, not in the employer field unless they paid you directly.
Do this now: Open your last upload preview. If any employer field is blank, fix line one on that role and re-export before you tailor again.
Your next upload
Parsers are literal. They reward plain employer lines, honest spelling, and headers split from titles. You do not need a fancier template. You need a file where the company column matches what you actually put on line one.
- Copy employer names from payroll or the official site, not memory.
- Split title, city, and dates away from the company string.
- Preview work history in the portal after every export.
- Lock employer lines in your master file before you tailor bullets.
Pick the req you care about most. Fix the worst-parsing role first. Run a free ATS check on the PDF. Submit once the employer sidebar looks boring and correct.
You cannot keyword-stuff your way past an empty employer field. You can make your tenure visible to the filters recruiters actually use when they narrow a stack from five hundred to fifty.
When you are tired, it is tempting to leave a messy header because the bullets are strong. Strong bullets without a company name look like freelance projects scattered across a page. Clean headers first, then polish bullet verbs.
Keep a screenshot of a successful preview next to each saved version. Boards change parsers. Your memory of what worked in March does not update when the portal upgrades in September.
If a friend asks why their brand-name internship vanished in Workday, send them the four-line block instead of debating fonts. Most fixes are structural, not cosmetic.
Employer formatting feels minor until you watch a recruiter sort by company and your file is missing from the filter. After you fix line one once, every future tailor gets faster because the skeleton already imports.
Pair this habit with the Workday checklist in optimizing resumes for Workday ATS when you apply through large employers. The same plain-text rules protect both company names and dates.
Read more
Frequently asked questions
Match the legal branding when you know it. If the logo says AT&T, write AT&T on line one of the job block. If you are unsure, use the name on your offer letter or pay stub. Do not invent a cleaner version that drops symbols the parser may need to stay attached to the letters.
Use the abbreviation only when recruiters in your field would search it that way. IBM and GE are fine. A three-letter internal nickname for a regional firm is not. Put the full name on line one and the common ticker or acronym in parentheses only when that acronym is how the company appears on LinkedIn and in job postings.
Keep city and state on their own line or after a pipe on the same line as the job title, not glued into the employer string. Workday often stores employer and location in separate columns. When city rides inside the company field, keyword searches for the real employer miss you.
Bolding does not teach the parser where the name starts. Clean line breaks and plain text do. Save bold for the human skim if you must, but export a single-column PDF and confirm the employer column populates in the portal preview before you rely on styling.
