How to Write a Professional Summary (With Examples)
Published · 9 min read
A professional summary is two to four lines at the top of your resume that tell the reader what you are and what you have done. You need one if your track record is not obvious from your job titles alone. If it is obvious, you can skip it, and sometimes you should.
That last part is the bit nobody says. A summary is not a mandatory field. It is prime real estate you are choosing to spend on prose instead of on another line of experience, and it is worth spending only when the prose does a job the experience section cannot.
Do You Actually Need a Summary?
Ask one question: if the reader skipped straight to your first job entry, would anything important be missing?
For a lot of people with a straight career line, the honest answer is no. If your last three roles say nurse and you are applying for a nursing job, a summary saying "experienced nurse" is a speed bump. Either cut it, or make it earn its place by naming the specialty, the setting, and the scale nobody can infer from a title.
There are four situations where a summary genuinely pays for itself:
- Your job titles undersell you. Internal titles are often meaningless outside the company. "Associate II" hides the fact that you ran a €2M portfolio.
- You are changing fields. The reader needs a reason to keep reading past a job history that looks like the wrong one. The summary is where you supply it.
- You have a gap, a relocation, a visa status, or a return to work. One calm line at the top stops the reader constructing a theory.
- You have a lot of history. Fifteen years of roles need a frame, or the reader assembles your story themselves, in the wrong order, from the bottom of page two.
If none of those apply to you, a skills section and strong experience bullets will serve you better than a paragraph.
Summary or Objective: Which One Are You Writing?
They get treated as interchangeable. They are not, and the difference is direction.
A summary points backwards. It compresses what you have already done: your field, your level, your proof. An objective points forwards, stating the kind of role you want and what you hope to do there.
Objectives have a bad reputation because most are written from the candidate's side of the desk. "Seeking a challenging position where I can grow my skills" tells an employer what you want from them, on a document whose entire purpose is to tell them what they get from you.
The objective is not dead, though, just narrow. It works when you have little history to summarise and your direction is the only useful information you have: a first job, a graduate scheme, a genuine field switch. Even then, write it as a statement of fit rather than a wish. Name the specific role, name what you bring to it, and drop the word "seeking".
Tip: If you can write one sentence about your past that would make a hiring manager keep reading, write a summary. If you truly cannot, write two lines of objective and put the effort into your projects and coursework instead.
What Makes a Summary Worth Its Space?
One rule covers almost everything: a summary earns its space only if it says something the rest of the resume cannot say.
Everything below it is already a list of facts: employers, dates, titles, bullets. A summary that restates those facts spends your best position on a duplicate. It should instead do one of the three things a list cannot:
- Aggregate. Bullets show individual wins. A summary adds them up: total years, combined budget, markets covered, headcount across roles.
- Frame. A list has no argument. A summary says which experience is the relevant one for this job, and why the rest still counts.
- Explain. A list cannot answer the question the reader is silently asking: why the gap, why the pivot, why a lawyer is applying for a compliance role.
If your draft does none of those three, delete it. You lose nothing.
How Do You Build the First Clause?
The first clause is the whole game, because it gets read even when the rest does not. It should be a noun phrase naming what you are, in the vocabulary of the job you are applying for. Not "a motivated individual with a passion for numbers" but "Financial analyst, six years in SaaS". Not "a dedicated professional in the healthcare field" but "Registered nurse, ICU and post-op, seven years across two teaching hospitals".
Then put a real number in, if a real one exists. A number gives the reader something concrete to hold and signals that you measure your own work. It does not have to be revenue: team size, ticket volume, patient load, portfolio value, uptime, markets covered, class size, headcount trained. Anything countable that a colleague would recognise as true.
If no honest number exists, do not manufacture one. An invented figure is the one mistake here that can cost you the job later, when an interview question lands on it. Reach for specificity instead: name the tool, the system, the regulation, the client type, the certification. Specific and unquantified beats quantified and false.
Why Is "Results-Driven Professional" Worse Than Nothing?
Because it cannot be false. That is the test: try to imagine a candidate who would describe themselves as the opposite. Nobody writes "results-indifferent professional with poor attention to detail". A claim every applicant can make carries no information, so the reader learns to skip it, and the words after it get skipped too.
So it is not neutral. It is negative, in three ways. It costs you the strongest line on the page. It trains the reader to skim the block instead of read it. And it tells them, accurately, that you did not tailor this document, because a phrase that fits every job was clearly not written for theirs.
Apply that test to the whole draft. Cross out every phrase a bad candidate could also write; what is left is your actual summary. Usual casualties: results-driven, detail-oriented, dynamic, proven track record, passionate, team player, excellent communication skills, self-starter.
Tip: Replace the adjective with its evidence. "Detail-oriented" becomes "reconciled month-end for eleven entities with no restatements in three years". The adjective was a summary of the evidence. Give them the evidence.
What Does a Good Summary Look Like?
Four worked examples below. Every number, tool, and employer detail in them is invented for illustration. Do not copy the figures. Copy the shape, then fill it with your own true facts.
Example 1: The Experienced Hire
"Supply chain manager with nine years in cold-chain logistics for grocery retail. Currently manage a 34-site distribution network across three countries, running S/4HANA and Manhattan WMS. Cut spoilage write-offs from 4.1% of shipped value to 1.6% over two years by rebuilding the temperature-exception workflow. Looking for a regional operations role with responsibility for network design."
What it does: names the field and sub-field in the first eight words, aggregates scale no single bullet contains, names the actual systems, and gives one measured result with a before and an after. The closing line is the only forward-looking sentence a summary needs.
Example 2: The Career Changer
"Six years as a pharmacy technician, now moving into clinical data. Built and maintained the dispensing-error tracker for a 12-branch chain, which meant writing the SQL queries and the monthly reporting myself. Completed the Google Data Analytics certificate in March 2026 and have since done two volunteer analysis projects for a regional patient charity. Bringing the domain knowledge that takes new analysts in healthcare about a year to acquire."
What it does: it does not pretend the pivot is not happening. It states it in line one, then spends every following sentence on whether the pivot is credible. The strongest evidence comes from the old job, not the certificate. The final line is an argument, not a boast: it says why the old field is an asset rather than a detour.
Example 3: The First Job
"Recent civil engineering graduate (BEng, 2:1, University of Leeds) applying for the site engineer graduate scheme. Final-year project modelled drainage load for a 6-hectare brownfield site using Civil 3D and MicroDrainage; it was marked 78 and used as a teaching example the following year. Two summers on site with a groundworks contractor, CSCS card held. Comfortable on a site from day one."
What it does: this is closer to an objective, which is correct here, because the direction genuinely is the news. But it is a specific objective. It names the scheme, then backs it with the three things a graduate has that differentiate: a real project with real software and a real mark, real site time, and the card that lets them legally be on site.
Example 4: Returning After a Gap
"Payroll specialist, eleven years, returning to full-time work after two years as a full-time carer. Previously ran monthly payroll for 900 employees across UK and Ireland on Sage People, including the 2022 migration off Iris. Refreshed on current legislation through the CIPP Payroll Technician certificate completed in June 2026. Available immediately."
What it does: names the gap in one clause, without apology, then moves past it. The reader's real concern with a returner is currency, not absence, so the summary answers currency directly with a dated refresher. "Available immediately" is worth the two words it costs.
Can You Show a Weak Version Next to a Rewrite?
Two pairs, each the same fictional candidate with the same underlying facts, executed differently.
Rewrite 1: A Marketing Manager
Weak: "Results-driven marketing professional with a proven track record of success in fast-paced environments. Skilled in digital marketing, content strategy, and team leadership. Passionate about building brands and driving growth. Seeking a challenging role at a forward-thinking company."
Rewritten: "B2B marketing manager, seven years, all of it in industrial software. Own demand generation for a €14M ARR product line: paid, content, and the two-person team that runs it. Rebuilt the lead scoring model in HubSpot last year, which took sales-accepted leads from 22% of MQLs to 41% without increasing spend. Want to do the same thing one level up, across a portfolio."
The weak version is four sentences and zero facts, every phrase of which survives being applied to any marketer alive. The rewrite gives up the adjectives and buys, at the same word count, a sector, a tenure, a budget scale, a team size, a named tool, a measured change, and the next step.
Rewrite 2: A Customer Support Lead
Weak: "Dedicated customer service professional with excellent communication skills and a strong commitment to customer satisfaction. Experienced in handling high volumes of customer enquiries and resolving issues efficiently. Team player who works well under pressure."
Rewritten: "Support lead for a fintech app with 200,000 monthly active users. Run a team of six across two time zones on Zendesk, handling roughly 3,400 tickets a month at a median first-response time of 41 minutes. Wrote the macro library and the fraud-escalation playbook the team still uses. Ex-fraud analyst, which is why the escalation path is good."
Look at the last sentence. It is the framing move: it takes an earlier job that would read as unrelated history and turns it into the reason one specific claim is credible. No list of bullets can perform that operation.
How Long Should It Be, and Where Does It Go?
Two to four sentences, or roughly 40 to 90 words. The upper bound is physical rather than stylistic: a block longer than about four lines stops looking like a summary and starts looking like a paragraph, and a paragraph on a resume invites skipping. Shorter is fine. A two-sentence summary with two facts beats a padded four-sentence one, and struggling to reach four sentences tells you something about whether you need the section.
Placement is simpler than it looks: directly under your name and contact details, above everything else. That is the only position that makes sense, because a summary read after the experience section is a summary of something the reader has already read.
- Label it "Summary" or "Professional Summary". A conventional heading is safest for both a human skimming and a parser deciding which section this is.
- Write in first person with the "I" dropped: "Manage a team of six", not "I manage" and not "Manages".
- No headshot, no skill bars, no italic serif flourish. The summary block is text.
- Rewrite the first clause and one fact per application. The rest can stay. It is the highest-leverage tailoring you can do in two minutes.
- Write it last. You cannot summarise a document that does not exist yet, which is why summaries written first are the vaguest part of the resume.
What Should You Do Next?
Open your resume and do this in order. Ask whether anything in your summary is missing from the rest of the page. Cross out every phrase a weaker candidate could also have written. Check whether one honest number survives. Then rewrite the first clause so it names, in the employer's own words, the thing you are.
If what is left is under two sentences and contains no facts, you have learned something useful: cut the section and give the space to your experience. That is a real answer, and a better outcome than another paragraph of results-driven professional.