The top of your resume — the four lines under your name — does more work than any other section. Recruiters spend 6-8 seconds on the first scan, and most of that time lands here. Choosing between a summary and an objective, and writing it well, is one of the highest-leverage edits you can make.
Summary or Objective: How to Choose
The decision is about story. A professional summary says "here is what I have done and the results I produced" — it works when your experience already proves you're the right candidate. A career objective says "here is what I am moving toward and why I fit this role" — it works when your experience needs framing.
| Situation | Use | Why | Length |
|---|---|---|---|
| 3+ years in the same field | Summary | Results sell better than goals | 3-4 lines |
| Recent graduate | Objective | Signals direction and motivation | 2-3 lines |
| Career changer | Objective | Explains the pivot and transferable value | 3-4 lines |
| Returning after a gap | Hybrid | Reconnects past results to current intent | 3-4 lines |
| Senior leader (director+) | Summary | Track record is the credential | 4-5 lines |
| Tight one-page resume | Skip | Bullets carry the story already | — |
Summary Formula
Line 1 — role + years + specialty: "Senior product manager with 9 years scaling SaaS platforms from seed to Series C."
Line 2 — flagship outcome: "Led a 3-team launch that grew ARR from $4M to $18M in 14 months."
Line 3 — domain or methodology: "Deep experience in B2B fintech, API-first product strategy, and quantitative discovery."
Line 4 — target alignment (optional): "Seeking to apply this playbook to a vertical-SaaS Series B or C team."
Objective Formula
Line 1 — role being targeted: "Aspiring data analyst transitioning from financial operations."
Line 2 — transferable proof: "Built 30+ Excel and SQL models that automated $1.2M in monthly reconciliation."
Line 3 — training or credential: "Completed the Google Data Analytics Certificate and 4 capstone projects in Python."
Line 4 — value to the employer: "Eager to apply analytical rigor to product analytics at a growth-stage startup."
Common Mistakes
- Vague adjectives. "Hardworking, results-driven, passionate" — every applicant claims these.
- What you want vs what you offer. Objectives that only say "looking for an opportunity to grow" give the employer nothing.
- Repeating the resume. The summary should preview, not duplicate, your bullets.
- Stale role title. If you're applying to "Staff Engineer" roles, don't lead with "Software Developer."
- Too long. Anything over five lines becomes invisible.
Get the Opening Line Right
ResumeKit's builder includes role-tuned summary templates with live word counts.
Open Resume Builder →