How to write a candidate blurb a hiring manager will actually read

To write a candidate blurb, use five parts in this order: who the candidate is in one phrase, one result that proves it, how they meet this client's top must-have, why they want to move, and the logistics (availability, pay expectation, location). Keep it to three to five sentences, use facts the candidate gave you rather than adjectives, and write the fit line fresh for each client.

A blurb is the short pitch, not the full write-up. It sits at the top of a submittal email, in a shortlist table, in a speculative email about a candidate, or in your notes for a call. The full document behind it is the candidate submittal. This page is only about the few lines that decide whether the manager reads that document at all.

The five-part formula

The figures in these examples are invented for illustration. In a real blurb, every number comes from the candidate and should be something you could check in a reference.

Three lengths for three places

One line: hot lists and shortlist tables

[Title], [years / scope], [one result]. [Notice], [pay], [location].

Senior payroll manager, 4-state payroll for 1,100 staff, led a system
migration with no missed runs. 2 weeks, $95–100k, hybrid.

Three to five sentences: the email to the hiring manager

[Name] is a [who]. [Proof]. [Fit to your top must-have]. [Motivation].
[Logistics.] Full write-up and resume attached.

Maria is a senior payroll manager running multi-state payroll for a
manufacturer with about 1,100 employees. Last year she led their move to
a new payroll system across four states without a missed pay run. She
has owned the year-end process three times, which you said was where
your last hire struggled. She wants to run the function herself rather
than report into shared services. Two weeks' notice, looking for
$95–100k, and happy with your hybrid pattern. Full write-up attached.

Notice what that example does not contain: "dynamic," "results-driven," "great communicator." Each sentence holds a fact the manager can use to decide.

Anonymized: marketing a candidate to a company without a posted role

[Title] from a [type of employer, size]. [Proof without identifying
details]. [Why they fit a team like yours]. [Motivation]. [Logistics,
broad]. Full profile on request, with the candidate's agreement.

Remove the name, the employer, unusual job titles and any project that could be found with a search. Replace them with types and sizes. Get the candidate's agreement before you send it anywhere, and see the MPC marketing email template for consent, the do-not-send list and the rest of the email around the blurb.

Where the material comes from

A good blurb is written from the screen, not from the resume. The resume gives you titles and dates. The call gives you the proof line, the motivation and the logistics, and it is where the candidate says the thing that makes them sound like a person rather than a list.

Ask for it directly on the screen:

• "What's the piece of work from the last two years you'd most want a new manager to know about?"
• "What did it change? How would someone measure that?"
• "What made you start taking calls about new roles?"
• "What would make you say no to an offer, even a good one?"

Write down the answers in their words. If your screens are transcribed, pull the proof line from the transcript instead of from memory; Interview Signal's scorecards quote the candidate for this reason, and a quoted result is easier to stand behind when the manager asks about it.

Before and after

Both versions describe the same invented candidate, a backend engineer.

Before:

Highly motivated and passionate software engineer with 7+ years of
experience in a fast-paced environment. Strong communicator and team
player with a proven track record of delivering high-quality solutions.
Would be a great cultural fit for your team!

After:

Daniel is a backend engineer, seven years in, the last three on payments
at a fintech of around 200 people. He rebuilt their reconciliation
service so month-end close went from three days of manual checks to an
automated report the finance team runs themselves. That's the same
problem you described in the intake. He wants a smaller team where he
can talk to customers directly. Four weeks' notice; expecting
$165–175k; open to two days a week in the office.

The "before" version could describe almost any engineer. The "after" version could only describe Daniel, and it tells the manager why he is in their inbox.

Words to cut, and what to write instead

Write the fit line for this client

The fit line is the only sentence that changes between clients, and it does most of the work. Take it from the intake: the must-have the manager ranked first, or the problem they said the last hire could not solve. Then connect the candidate's proof to it in plain words.

• Weak: "Has relevant experience for your role."
• Better: "Has run multi-state payroll."
• Best: "Has owned the year-end process three times, which you said was where your last hire struggled."

If you cannot write a fit line for a client, that is useful information. You may be sending the candidate to the wrong place. Sending fewer, better-matched candidates is the main lever in improving your submittal-to-interview ratio.

Name the gap

If the candidate misses a must-have, say so in the blurb, in one clause, with what compensates for it. "No direct experience with your ERP, but has led two migrations onto similar systems" is credible. A manager who finds the gap themselves on page two stops trusting the blurbs that follow.

Several candidates in one email

When you send a shortlist of two or three, write every blurb in the same order: who, proof, fit, motivation, logistics. The manager can then compare candidates line by line instead of hunting for the notice period in one paragraph and the pay in another. Put the strongest candidate first and say why in a single sentence above the blurbs: "Maria is the closest match on year-end; Tom is stronger on systems but would need support on multi-state rules."

Keep the blurbs the same length. If one runs twice as long as the others, the manager reads it as the one you are pushing, whether or not you meant it that way.

Keep the blurb current

A blurb is not written once. Update it when anything in it changes: a new offer elsewhere, a shorter notice period, a revised pay expectation, or feedback from a first interview that sharpens the fit line. Store the latest version at the top of the candidate's ATS record, dated, so that anyone on the team who presents the candidate next uses the same facts. Two recruiters describing the same person differently to the same client is a quick way to lose that client's trust.

A checklist before you send

• Three to five sentences, or one line for a table.
• One proof line with a number or a scope, from the candidate.
• A fit line written for this client's top must-have.
• Motivation that answers "why would they move?"
• Notice, pay expectation and location or work pattern.
• Any gap named, with what compensates.
• No adjectives you could not defend in a reference.
• The candidate has agreed to be presented to this client.

Then call the manager before you send it if you can. The blurb is also your 30-second spoken pitch, and how to use it on that call is covered in how to present candidates to clients.