How to Write a CV Summary (With Examples)
The summary is the first thing a recruiter reads and the first thing they skip when it is empty words. It sits at the top of your CV, two or three sentences, and its only job is to make the reader want the rest. Done well, it frames everything below it. Done badly, it wastes the most valuable space on the page.
A good summary is not a life story and not a list of adjectives. It is a short, specific pitch for one role.
What a Summary Is For
Two readers reach your CV, in order. Software parses it, then a person skims it in a few seconds. The summary is written for the person. It answers three questions fast:
- Who are you, professionally?
- What have you actually done?
- Why do you fit this role?
If your summary does not answer those, it is decoration.
The Three-Part Formula
Keep it to two or three sentences and follow this shape:
1. Who you are + how much experience. 2. Your strongest, most relevant proof. 3. What you are aiming at, matched to the role.
Weak:
Hard-working and motivated professional looking for a challenging opportunity to grow and add value to a dynamic team.
That could describe anyone. It names no role, no skill, no proof.
Strong:
Backend engineer with 5 years building high-traffic APIs in Go and Python. Cut checkout latency by 35% at a fintech serving 2M users. Looking to bring that reliability focus to a payments-infrastructure team.
The second one is specific: a role, real skills, a measured result, and a clear target. A recruiter knows in one read whether to keep going.
Match It to the Job
A summary should change with the job you are applying for. The same experience can be framed for different roles by leading with the proof that matters most to each one.
Say you have done both data work and backend work. For a data role, lead with the pipelines and the scale. For a backend role, lead with the services and the latency. You are not inventing anything. You are choosing which true thing to put first.
This is the heart of tailoring: select and sharpen real facts for the role, never fabricate. A summary that claims what you cannot back up falls apart in the interview.
Quick Fixes That Help
- Cut empty words: "hard-working", "motivated", "team player", "results-driven". They prove nothing.
- Put a number in the middle sentence. One real metric beats three adjectives.
- Name the role or field. A summary aimed at everyone lands with no one.
- Keep it to three sentences. If it runs longer, it is a paragraph, not a pitch.
A Template You Can Adapt
[Role] with [X years] in [field/stack]. [One concrete achievement with a number]. [What you want, matched to the role].
Fill it with your own true facts, reorder by what the job values most, and you have a summary that earns the read.
Let the Tool Frame It for the Job
Writing a fresh summary for every application is slow. myCVpath reads your full history and the specific job posting, then produces a summary that leads with your most relevant proof for that role, drawing only on what is already true in your CV. You keep one master CV, and each application gets a summary aimed at its job.