Resume writing
Professional summary examples that are not filler
Most summaries are three lines of adjectives that describe nobody. Here is what to write instead.
Read enough resumes and the summaries blur into one paragraph:
Motivated and results-driven professional with excellent communication skills and a proven track record of success in fast-paced environments. Passionate about delivering value and exceeding expectations.
Nothing in that is checkable, and nothing in it is only true of one person. It costs you four lines at the most valuable point on the page.
When to include one
A summary is worth space in three situations:
- Your titles do not describe your work. "Operations Analyst" could mean six different jobs. One line of positioning saves the reader guessing.
- You are changing direction. Your history points one way, the application points another. The summary is where you explain that, before it reads as a mismatch.
- You are senior. At that level the framing is part of the assessment.
If none apply — a straightforward career with self-explanatory titles — skip it. Two extra bullets on your current role do more.
The four things a good summary contains
- What you are, in the vocabulary of the field you are applying to
- How much, in years or scope
- One piece of specific evidence — a number, a named thing, a scale
- What you are pointed at next, if it is not obvious
Three or four lines, no pronouns, no adjectives you cannot evidence.
Before and after
Senior product manager
Before:
Experienced and passionate product leader with a proven track record of driving growth and delivering results in fast-paced, dynamic environments.
After:
Product manager, nine years in data-heavy B2B. Took two products from zero to eight figures of ARR and rebuilt a reporting platform used by 40k people daily, cutting time-to-first-insight 62%. Looking for a platform role where the hard part is the data model rather than the roadmap.
The second one has a field, a scale, two numbers and a stated preference. A hiring manager can decide something from it.
Recent graduate
Before:
Recent graduate seeking an entry-level position where I can utilise my skills and grow within a reputable organisation.
After:
Economics graduate (2:1, Manchester) focused on applied data work. Dissertation used 12 years of transport data to test a policy claim and found timetable padding explained 60% of the reported improvement. Python and SQL, looking for an analyst role where the output is a decision rather than a dashboard.
Evidence instead of aspiration. More on this in writing a resume with no experience.
Career changer, teaching to instructional design
Before:
Dedicated professional looking to transition into instructional design, bringing transferable skills from a background in education.
After:
Secondary teacher of eleven years moving into instructional design. Rebuilt a department's Key Stage 4 scheme of work for 6 staff and 240 students, lifting pass rates from 61% to 78% over two cohorts. Certified in Articulate Storyline; three portfolio modules built for adult learners.
"Transferable skills" is a claim. Curriculum design for 240 students plus a named tool plus portfolio work is the evidence.
Software engineer
Before:
Full-stack developer with experience in a wide range of modern technologies and a passion for clean code.
After:
Backend engineer, six years, mostly Go and Postgres at payments scale. Moved payments out of a Rails monolith into a service handling 4k req/s with a zero-downtime cutover across 11 regions, cutting p99 from 900ms to 210ms. Interested in systems where correctness matters more than throughput.
Note what is absent: no list of every framework. That belongs in the skills section.
Returning after a career break
Before:
Motivated professional returning to work after a career break, eager to contribute to a dynamic team.
After:
Finance manager, eight years in FMCG, returning after two years of full-time caring. Previously owned a GBP 40m cost centre and ran the annual planning cycle for 4 business units. Refreshed on the current stack — NetSuite, Power BI — and looking for a controller role in a mid-size business.
State the break plainly, then move to evidence. An unexplained gap invites a worse assumption than the truth.
Operations, ambiguous title
Before:
Operations professional with a strong background in process improvement and stakeholder management.
After:
Operations lead in third-party logistics — warehouse, transport and supplier performance across 3 sites and 140 staff. Cut cost-to-serve 14% in two years by renegotiating carrier mix and rebuilding the pick-path. Comfortable owning a P&L and a union relationship.
Words to delete
Every one of these can be removed without losing information:
motivated, passionate, dedicated, hardworking, results-driven, detail-oriented, dynamic, proven track record, team player, self-starter, go-getter, thinks outside the box, wears many hats, excellent communication skills, seeking a challenging opportunity
Everyone claims them, nobody can check them, and they are the words a reader's eye skips.
Tailoring in ten minutes
You do not need a new summary per application. Write one strong base version, then per posting:
- Swap the field noun to match the posting — "platform" versus "growth", "controller" versus "finance manager".
- Swap the one piece of evidence for whichever of your numbers is closest to what they are hiring for.
- Adjust the final clause to point at the role.
Ninety seconds, and it reads as written for them.
Formatting
Three or four lines as a single paragraph. Not bullets — bullets are for the experience section, and a bulleted summary reads as a second skills list.
Every template here has a summary block at the top; it is called Professional Summary by default and you can rename it to Profile or About if you prefer. It also lands differently by layout: Impact puts it in a tinted box with an accent bar, which is worth using if the summary is the strongest thing you have written.