10 min read
You're not confused because the concept is hard. You're confused because most templates treat the top line like one slot when parsers read two. The headline should aim at the posting. The job title on your employer row should stay payroll-truth. Swap them or merge them and Greenhouse buckets you next to candidates who actually held the string you invented.
Check your resume for free against one target req this week. You'll often see a matched headline keyword while the Experience block still opens with a coordinator title from three years ago. That's not a density problem. It's a placement problem. Job searching is already draining. This page tells you which line to change without lying to payroll or the parser.
Below is a diagnostic, not a template dump. Symptom first, three causes, how to tell which one's yours, fixes with before/after pairs from four roles, and a copy-paste block for tonight.
Quick Wins
- Write headline from the posting title band. Keep payroll title on the employer row only.
- Delete duplicate title lines under your name. One headline, one employer title per job.
- Rewrite bullet one so it proves the headline scope with a tool the req names.
- Export plain text. If two different titles appear before Experience, parsers already disagree with you.
The symptom: right experience, wrong bucket
The file lands in triage looking like a career changer when you're not one. Or it ranks for coordinator reqs when you've run a team for two years. You didn't fail keyword research. You gave the parser two title signals and it picked the wrong one.
Headline and employer title serve different jobs. Headline answers what req family you're aiming at this week. Employer title answers what payroll would confirm if someone called HR tomorrow. When those strings fight, parsers attach posting keywords to a line that isn't tied to dated experience. Recruiters see mismatch before they reach bullet one.
A composite data analyst keeps payroll title Business Analyst on the Acme row but renames the top of the file Senior Data Product Owner because the posting says so. Greenhouse stores Senior Data Product Owner as current title with no employer anchor. Workday search for Business Analyst misses them. Search for Product Owner surfaces them without proof in the date block. Both searches lose the same candidate.
I've screened stacks of these in Workday and Greenhouse, and the top block that survives is boring on purpose: name, one headline aimed at the req, contact line, then Experience with payroll titles on each row.
Edge case: internal promotion where payroll title updated but headline still says your old band. Update the employer row first. Headline second. Edge case: contract roles with vendor title strings that don't match duty scope. Headline may carry target language while employer row keeps vendor payroll truth plus a bullet that explains scope.
Read how automation changed resume standards for format rules that keep title lines parser-readable. This page is the placement question: which string belongs above your name versus on the employer line.
Resume headline vs job title: three causes parsers misread
Most bucket errors trace to one of three causes. Headline treated as payroll title. Payroll title used where posting language belongs. Two title lines competing above Experience. Work through them in order.
Cause 1: Headline treated as payroll title
Creative headlines are fine when they're clearly marketing copy. Parsers are not subtle. The first bold line after your name often becomes current job title in the preview pane. If that line says Customer-Centric Growth Leader and your employer row still says Account Manager, the ATS stores Growth Leader with no dates.
How to tell this is yours: Open the Greenhouse or Workday preview after upload. If current title shows your headline while employer name is blank or wrong, cause one is active. Plain-text export helps: if the headline line sits alone without dates underneath, parsers will treat it as title.
Before: Top line only: Strategic HR Business Partner Driving Culture and Retention
After: Headline: HR Business Partner | Employee Relations and Workforce Planning
Employer row: HR Generalist, Northwind Services | March 2020 to Present
Before: Top line: Full-Stack Engineer | React, Node, AWS, Docker, Kubernetes, GraphQL
After: Headline: Full-Stack Software Engineer | React and Node
Employer row: Software Developer, Lattice Apps | June 2021 to Present
Fix: Short headline with posting title band plus one specialty. Move stack proof to bullet one. Keep payroll string on the employer row with Month Year dates on the same line.
Cause 2: Payroll title used where posting language belongs
The opposite miss: you never add headline language because HR's generic title feels safer. Specialist and Associate on every application while reqs ask for Senior Revenue Analyst or Lead UX Designer. Parsers rank exact title matches. You stay invisible in the right search while surfacing in the wrong one.
How to tell this is yours: Compare your top line to three target postings. If payroll title is generic and none of the posting title bands appear above Experience, cause two is active. Another tell: ctrl-f the req title in your file and get zero hits above bullet one.
Before: Name block then Experience opens: Specialist, Contoso Ltd | 2019 to Present
After: Headline: Senior Marketing Analyst | B2B Demand Generation
Employer row unchanged except bullet one now proves analyst scope
Before bullet: Updated campaigns and reported weekly metrics.
After bullet: Owned pipeline reporting for a 6-person demand gen team in HubSpot and Looker, tying $3.8M sourced pipeline to channel mix decisions each quarter.
Fix: Add headline with honest seniority band from the posting family. Do not change payroll title on the employer row unless HR actually changed it. Let bullet one prove the headline with scope, tool, and outcome.
Cause 3: Two title lines fighting above Experience
Templates stack a headline and a subtitle and a summary title before the first job row. Parsers pick one at random. Recruiters see three strings and trust none. The worst version repeats the posting title twice with different employers missing.
How to tell this is yours: Count title-like lines between name and first employer. More than one headline row means cause three. If summary opens with another job title string, that's a fourth conflict.
Before: Line 1: Product Manager. Line 2: Senior Product Manager | Agile | Roadmaps. Line 3: Summary title: Technical Product Owner.
After: Line 1: Senior Product Manager | B2B SaaS Platform. Summary: three sentences, zero new titles. Employer row: Product Manager, Helios Inc | January 2022 to Present.
Fix: One headline under name. Summary without titles. Each employer row carries one payroll title, company, location, dates, then bullets.
How to tell which cause is yours
Run a three-minute triage. Upload or paste plain text into a doc. Highlight every title-like string above Experience. If headline reads like marketing and preview title is wrong, start with cause one. If headline is missing and payroll title is generic, cause two. If you count three or more title strings, cause three.
Mixed cases happen. Generic payroll plus stacked headline lines is common on Canva exports. Fix stack order first, then add posting language to a single headline, then rewrite bullet one.
Copy-paste two-line block
Posting title band: [paste from req]
Headline: [posting band] | [one specialty you can prove]
Payroll employer row: [payroll title], [Company] | [Month Year] to Present
Bullet 1: [verb] [scope] using [tool from posting], [outcome from real work]
Plain-text check: only one title-like line above Experience besides contact
Preview check: current title in ATS matches employer row, not headline alone
Paste the block into a doc, fill against one posting, then drop lines into your master file. Read why resume customization beats mass applying before you reuse the same headline on every family without changing bullet one.
When headline vs title placement is not the blocker
You're targeting a band you cannot prove. Headline says Director while every bullet shows IC tasks. Placement will not fix level fit. Apply to roles your scope supports.
Your format broke on upload. Two-column templates move headline into a side cell. Parsers read it as footer text. Single-column export first, then headline edits.
You changed headline but not bullet one. Parsers may rank the string. Recruiters still ctrl-f proof in Experience. Headline without a dated bullet is an empty promise.
Payroll title actually matches the posting. When HR already gave you Senior Software Engineer and the req says the same, skip headline gymnastics. Spend time on bullet one instead.
Background check risk. If headline title never existed on payroll or references, fix it before apply. Honest scope language beats invented titles every time.
Score the top block before you mass apply
Run the updated file through the free ATS checker with the posting pasted in. You want posting title bands showing under Experience and headline, not only in Skills. If preview title still disagrees with your employer row, fix order before you send ten copies.
Use job match score on a second req in the same family. If score moves when headline changes but payroll row stays truth, you've aimed correctly. If score jumps only when you inflate payroll title, roll back and fix bullets instead.
When the posting asks for a letter and your headline story changed, draft structure with the cover letter generator, then replace generic lines with the same scope proof you put in bullet one.
Two-line order tonight
Resume headline vs job title is not pick one and delete the other. Headline targets the posting. Employer title stays payroll-truth on the dated row. Mix them and parsers bucket you wrong even when bullets are strong.
Open the req you want most. Write one headline from its title band. Leave payroll title on the employer line. Rewrite bullet one to prove the headline. Export single column. Run the checker once. That's the whole fix for most misfires at the top.
You don't need a clever brand line. You need two honest strings in the right slots so humans and parsers stop arguing about who you are before they read bullet two.
Read more
Frequently asked questions
You can mirror honest scope in a headline when you already operate at that level, but keep payroll truth on the employer line. If payroll says Business Analyst and you run senior product analytics work, headline can read Senior Product Analyst while the Acme Corp line still says Business Analyst with dates. Never invent a title you never held. Parsers match headline strings to reqs. Humans verify against the employer block in background checks.
Not always. Headline is allowed to aim at the posting family. The employer line should match what HR would confirm on a reference call. When both lines say the same inflated string, parsers may rank you higher short term and recruiters flag mismatch later. When headline says target scope and employer line says payroll truth with scoped bullets, both sides stay honest.
Upload parsers often grab the first large text block after your name as current title, whether you meant it as headline or job title. If that line says Creative Problem Solver while Experience still opens with Coordinator, you get sorted into a bucket that does not match either string. One headline line plus one payroll title per role row beats two competing title lines at the top.
Headline is one line under your name. Summary is three to four lines of proof under that. Do not repeat the headline in the summary. Put posting keywords in headline once, then bullet one under your current job carries the evidence. Summary without bullets is still weak in Workday triage.
Generic payroll titles are common. Headline carries target language: Revenue Operations Specialist or Senior Marketing Associate when scope supports it. Keep Specialist on the employer row. Add scope in bullet one so the headline is not standing alone. A headline with no proof line still parses as fluff.