How to write a résumé headline that points at the job you want next
Your name goes at the top of your résumé. The line right under it is your headline, and most people do one of two things with it: leave it blank, or paste in their last job title and move on.
Both are a waste. A recruiter gives the top of your résumé a few seconds before deciding whether to keep reading. The headline is the first real line they land on. When you're changing careers, it's doing more work than anything else on the page, because it's where you tell the reader what you're aiming at before they've read a single bullet.
I've changed industries three times. The first time, I got the headline wrong, and I didn't understand why until much later.
What a résumé headline actually is
The headline is the short line under your name and contact info that labels you for the reader. One line. Ten to twelve words at most. Something like:
Project Manager — 5 years delivering civil and facilities projects on schedule and under budget
That's it. It's not your summary. The summary is the two-to-four sentences below it that make your case. The headline is the label; the summary is the argument. If your headline and your summary say the same thing in the same words, one of them is dead weight — cut the repeat.
A headline is also not an objective statement. "Seeking a role where I can grow" tells the reader nothing and asks them to do you a favor. A good headline makes a claim about what you already are, aimed at where you're going.
The mistake I made
My first career change was out of heavy civil — highways and bridges — into project management. I updated my résumé, and at the top I wrote the honest description of where I'd been: Civil Engineer.
It was true. It was also the wrong line. A hiring manager reading for a project-management role saw "Civil Engineer" and had to do the translation themselves — read down my bullets, figure out that a civil engineer on a highway job is running schedules, budgets, subcontractors, and inspections, and decide for me that this added up to project management. Most readers won't do that work. They'll see a title that doesn't match the job and move to the next résumé.
The fix wasn't to invent a title I hadn't earned. It was to name the job I was going for and let my real work back it up:
Project Manager — civil and facilities projects, promoted within 90 days
Same person, same experience, one honest line. But now the reader doesn't have to guess what I'm applying for.
Write for the job you want next, not the one you're leaving
This is the whole rule for a career-change headline. Your headline should point forward, at the target role, and every word in it has to be defensible by the résumé underneath.
Four things keep it honest and readable:
- Lead with the target role. If the posting says "Project Manager," your headline says "Project Manager," not "Project Lead" or "Operations Professional." Use the words the job uses.
- Back it with proof, not adjectives. A scope, a number, a result. "5 years," "a 12-person team," "promoted within 90 days," "cut a vendor contract by 40%." One concrete thing beats three words like "seasoned," "dynamic," or "results-driven."
- Keep it true. A headline is a claim, not a wish. If the résumé below can't support the line, the line is fiction and a sharp reader will catch it in the interview. Aim at the next role; don't skip past the experience you actually have.
- Keep it short. One line, roughly ten words. The headline earns the reader's attention for the summary. It isn't the summary.
A simple formula
If you're staring at a blank line, start here:
[Target role] — [the strongest true proof you have for it]
For a career-changer, the second half is where your transferable experience does its job. You name the destination, and you fill the proof slot with the real, adjacent work that makes the destination believable. Some honest examples of the shape:
- Customer Success Manager — 6 years in retail management, led a 12-person team to the region's top service scores
- Data Analyst — operations background, built the reporting that cut monthly close from 5 days to 2
- UX Researcher — 8 years teaching, redesigned a course around how students actually learn
None of those invent a year of experience. Each one points the reader at a new lane using something that's already on the page.
Tailor the headline to each posting
Here's the part people skip: the headline is not write-once. It's the line you should change most often, because it's the line most tied to the specific job. The same background can honestly support "Project Manager" for one posting and "Facilities Project Engineer" for another. Read the job description, take the exact title and the two or three words that repeat in it, and make your headline match — as long as it stays true to your experience.
That's slow to do by hand for every application, which is a big part of why I built ResumAI. It tailors your résumé to each job description — headline included — by matching your real experience to the posting's language instead of handing you a title you can't defend in the room. And because it scrubs your name, contact details, and current employer before any AI model sees the draft, tailoring for a dozen jobs doesn't mean leaking your job search to a dozen places. The point isn't to write a better lie faster. It's to stop wasting the best line on your résumé.
The test
Put your headline next to the job title in the posting and read them together. If a stranger couldn't tell from that one line that you're aiming for this job, rewrite it. If the line claims something your bullets don't prove, cut it back until it's honest.
Get that one line right and you've done the hardest translation work in a career change up front, where the reader actually sees it — instead of hoping they do it for you.
Thank you for reading. If you're mid-pivot right now, you're not behind. You just have some translating to do, and the headline is where it starts.
— Scot