Why the summary carries so much weight
Sitting directly under the header, the summary is the first prose a reader hits, on a page that is often skimmed in a matter of seconds. It either earns a slower read from there or it does not. Its job is to orient a reader who does not yet know your title, seniority or domain, in the fewest possible words.
It is not a cover letter in miniature and not a short biography. It should state facts - role, years, focus area - rather than opinions about yourself. Words like "hardworking" or "passionate" read as filler precisely because they are unverifiable and appear on nearly every resume.
Summary versus objective
An objective statement says what you want: "Seeking a position in software engineering where I can grow my skills." That made sense decades ago, when a paper application could land anywhere. Today the posting already tells the reader what role you are applying for, so an objective spends the top of the page restating information they already have.
A summary says what you offer instead, and leads with evidence rather than intent. The one case where an objective-style line still earns its place is a genuine career change, where the top of the page needs to explicitly name the target role and the transferable strength behind it, because the work history below will not make that connection obvious on its own.
How to actually write one
Three parts: your role plus years or domain, one or two concrete strengths named as a skill or a scope rather than a trait, and - only if it is genuinely true - one measurable anchor from the work itself, such as a team size or a system's scale. Leave that last part out entirely rather than inventing a number to fill it.
Write the summary last, after the experience section is drafted. It should compress what is already true on the page below it - writing it first, before that material exists, is usually what produces vague filler in the first place.
A worked example
A weak summary: "Hardworking professional with strong communication skills seeking to leverage my experience in a dynamic environment." Every phrase in that sentence could describe almost any candidate for almost any role - it gives a reader nothing they can act on or verify.
A stronger rewrite, for a fictional candidate: "Backend engineer with six years building payment infrastructure in Node.js and Postgres, most recently leading the migration of a monolith service into three independently deployable APIs." It names the domain, the stack, and a seniority signal - leading a migration - all facts a reader can verify against the experience section right below it.
Frequently asked questions
- How long should a summary be?
- Two to three sentences, roughly 50 words or fewer - long enough to state your role, experience and one strength, short enough to be read in the few seconds a first pass on a resume actually gets.
- Can I skip the summary entirely?
- Yes, for a very early-career resume with little yet to summarize, that space is often better spent on education and projects instead. Add a summary once there is a real pattern of experience worth compressing into a couple of sentences.
- Should the summary be different for every job I apply to?
- The strengths you lead with should shift toward whatever a specific posting emphasizes, even when the underlying facts about you do not change. See the how-to-write-a-resume guide for tailoring the rest of the page the same way.