How do I write a resume summary?
State who you are professionally, the experience most relevant to this role, and one specific contribution you can support. One sentence can work for a simple introduction; two or three may help when there is more to explain. These are writing options, not required lengths. A summary is optional: if it only repeats the document, you can go straight to your strongest evidence.
Harvard's resume guidance recommends specific, factual language and emphasizing the skills the employer values. Those principles inform the examples here; our suggested summary structure is an editorial approach, not a Harvard-prescribed sentence count.
What belongs in a summary
- Who you are: role or field, stated plainly — "Customer service representative", not "dynamic people person".
- Relevant scope: years or setting only where they help — "six years in medical-surgical units", "retail and online support".
- One supported highlight: an achievement with a figure you can stand behind, or a clear description of the work if a figure would be invented.
Leave out buzzwords ("results-driven", "go-getter"), first-person pronouns if the rest of your resume omits them (consistency matters more than the convention), and claims the resume body does not support. A summary that promises what the bullets do not show invites doubt, not interest.
Before and after
These are fictional teaching examples, not customer results. The second revision demonstrates an option without numerical claims.
| Before | After, if supported by your experience | Why it is clearer |
|---|---|---|
| “Hardworking professional seeking a challenging position where I can utilize my skills.” | “Customer service representative with five years across phone and chat support. Maintained a 94% customer satisfaction score while handling 40+ contacts daily, and trained six new agents on the ticketing system.” | Names the role, setting and checkable results rather than only what the applicant wants. |
| “Excellent communicator and problem solver.” | “Customer service representative who coordinated delivery exceptions with carriers and kept customers informed until resolution.” | Identifies the work and audience without inventing a metric. |
Replace every detail with your own supported experience. Use a numerical result only when you can explain its source and scope; the resume body should support the summary.
Adapting it to your situation
- Career change: one clause connecting the prior field to the new one — "customer support team lead moving into implementation consulting, with five years of translating client requirements into working configurations." Then let the experience section carry the evidence. See our career-change guidance.
- Early career: describe coursework, projects and supervised placements instead of employment you do not have. Our first-resume guide covers this, and the new graduate nurse example shows how clinical placements and pending licensure are labeled.
- Returning after a gap: skip the gap narrative in the summary. State your current professional identity and let the dated entries do the rest; the gaps guide covers when a note is useful.
How does the summary change with career stage?
Use the same evidence discipline while changing the kind of evidence. These are fictional examples:
Student: "Business student with part-time retail experience and volunteer event coordination. Built an Excel inventory model for an operations course and maintained schedules for a campus donation drive." The student sample supports each phrase with an entry and identifies the course dataset as fictional.
Graduate engineer: "Computer science graduate with a software engineering internship and a team capstone building a campus booking application. Implemented reservation conflict detection in PostgreSQL." The graduate engineering sample separates coursework from employment and states the applicant’s part in the team project.
Experienced engineer: "Backend engineer with nine years building and operating order-management services. Own technical design and release planning for a shared API platform, with recent work on retry safety and staged migrations." The senior engineering sample supports the ownership claim with decision and operational evidence.
The summary should not upgrade a student placement into a job, a team result into sole ownership, or an in-progress credential into a qualification held. An accurate summary without a numerical result is useful.
Match it to the application
When you are applying to several roles, keep a base summary and save each tailored version with the rest of that resume. Follow the multi-application tailoring workflow to select relevant evidence and preserve what you send to each employer.
Read the posting first. If it names a specialty, a tool or a credential you genuinely have, the summary is a reasonable place for that exact term. That is accurate mirroring, not keyword stuffing: include the term because it describes your experience, and support it below. The free resume checker flags summaries that are missing or outside a 15–120 word range; the weight behind that check is explained in our methodology.
That range is ResumeForU's own content-checklist heuristic, not an ATS requirement or an employer standard. A useful short summary, or an appropriate resume without one, may not satisfy that check. Do not add filler or an unnecessary summary just to increase the score.
Place it where it helps
The summary sits directly under your contact details, so everything in it should be something you want read first. Compare templates and layouts with your real content in place — you can switch ResumeForU templates without retyping anything — and check the exported file before sending, following the PDF and Word comparison.