A CV header line actually says what you do when it names a role and a focus specific enough that a reader does not need the rest of the page to work out what kind of candidate they are looking at, rather than repeating a generic job title on its own. "Software Engineer" tells a reader almost nothing beyond the broadest possible category; "Backend engineer focused on payments infrastructure" tells them what to expect from the rest of the CV before they have read another word. The header line is not the place for a full sentence or a claim about your career story, that belongs to the summary further down the page; its one job is to say clearly what you do, as specifically as a single short line allows.
What the header line's job actually is
The header line sits directly under the name at the top of the CV, and it is the first piece of real information a reader sees after the name itself, before a summary, before any experience entry, before anything else on the page. Because it is read first and read fastest, it carries a disproportionate amount of weight for how quickly a reader forms an initial impression of what kind of candidate they are looking at. A vague header line wastes that position; a specific one uses it to do real work, orienting the reader before they invest any more time in the rest of the document.
Why a vague headline slides past a reader
A header line that only repeats a job title category, "Software Engineer", "Marketing Manager", "Project Coordinator", tells a reader almost nothing they could not already guess from the target role itself, since that is presumably the role they are hiring for in the first place. It answers a question the reader was not really asking, since the job title alone is rarely the piece of information that actually differentiates one candidate from another applying for the same role. A specific header line answers a more useful question: not just what category of work you do, but which part of that category, which tools, which kind of problem, or which scale of work you actually focus on within it.
A simple formula: role, focus, one qualifier
A header line that stays specific without becoming a full sentence usually follows a simple shape: a role, a focus area within that role, and at most one further qualifier, such as a scale, an industry, or a particular strength. "Backend engineer focused on payments infrastructure" names the role and the focus in six words. "Marketing manager specialising in lifecycle email for subscription products" adds one further qualifier, the kind of product, on top of the role and focus. The formula deliberately stops well short of a sentence; a header line that tries to also explain your career story or list three separate specialisations at once stops reading as a header line and starts reading as a compressed summary in the wrong place on the page.
A few mistakes that undermine a specific headline
Stacking three or four qualifiers into one line, "Senior backend engineer, cloud-native, distributed systems, payments and fraud", undoes the formula's own logic, since a reader cannot hold that many separate ideas from a single skimmed line the way they can hold one role and one focus. An internal-only title, a company-specific grade or band name that means nothing outside that one employer, reads as a specific detail to the person who wrote it and as unreadable jargon to anyone else, so it is worth translating into language a reader outside the company would actually recognise. A header line borrowed wholesale from a job posting's own title, rather than one that reflects what the candidate actually does, tends to read as slightly hollow too, since it says what the reader wants to hear rather than what is specifically true about the person writing it. Each of these mistakes shares the same root cause: reaching for more words, or someone else's words, instead of the one clear role and focus that the formula already asks for.
Where the full summary picks up from here
The header line's job ends at naming what you do; explaining why that matters, what you bring to it, or how your background supports it belongs to the summary underneath it, not to the header line itself. Resume summary examples covers that fuller paragraph in detail, including how to build a summary that earns the reader's attention once the header line has already told them what kind of candidate they are looking at. Keeping the two separate, a short, specific header line above a fuller summary below it, means neither one has to do the other's job, and a reader gets a fast orientation first and the fuller case for hiring you second.
Illustrative example: a header line rewritten from vague to specific
Before, vague and generic: "Software Engineer." After, specific with a role, a focus and one qualifier: "Frontend engineer focused on accessible, design-system-driven interfaces." The rewritten version still fits comfortably on one short line, but it tells a reader considerably more about what kind of engineer they are looking at before they read a single bullet point further down the page, without drifting into a full sentence or a claim that belongs in the summary instead.
Build yours
A specific header line takes a few minutes to get right and does real work at the very top of the page before a reader has invested any time in the rest of the CV. Read through how to write a resume for the structure the rest of the document should follow, then open your CV and rewrite the header line first, before anything else on the page.