The summary is the first thing a recruiter reads and often the only thing they read closely before deciding to keep going. Done well, it frames who you are, what you are good at, and what you are targeting in a few seconds. Done badly, it wastes the most valuable space on your resume with generic adjectives. The goal is not to describe your personality — it is to position you for a specific role.
What a strong summary contains
A useful summary usually answers three questions: what are you (your professional identity and level), what are you known for (one or two concrete strengths or results), and what are you aiming at (the type of role). It is written in a confident, factual voice and avoids empty phrases like 'hard-working team player'.
Keep it to three or four lines. Anything longer starts to compete with your experience section, which is where the evidence actually lives.
Experienced professional: before and after
Before: 'Motivated and detail-oriented professional with a passion for results and excellent communication skills seeking a challenging new opportunity.' This could belong to anyone in any field.
After: 'Operations manager with 8 years in e-commerce logistics, known for cutting fulfilment errors and scaling teams through peak season. Looking to lead warehouse operations for a high-growth retailer.' The second version names the role, the domain, the results, and the target.
Career changer: lead with transferable value
Career changers should not hide the pivot — they should frame it. Name where you are coming from, the transferable strength, and where you are going.
Example: 'Former secondary-school teacher moving into instructional design, combining five years of curriculum building with new UX-writing and e-learning tool skills. Focused on creating clear, learner-first training content.' It turns a career gap in the new field into a credible story.
Entry-level and student: use proof you have
With little formal experience, anchor the summary in your field of study, relevant projects, and the role you want. Recruiters for junior roles expect potential, not a long history.
Example: 'Final-year computer science student with hands-on projects in Python and React, including a capstone app used by 200 classmates. Seeking a junior front-end developer role to build accessible web products.' Concrete detail beats confident-sounding fluff every time.
Summary formula
- Answer three things: what you are, what you are known for, what you target.
- Name the role and domain — a summary that fits everyone fits no one.
- Back it with one concrete result or project, not adjectives.
- Keep it to three or four lines and rewrite it for each type of role.