Recruiters spend 7 seconds on a first scan of your resume. The professional summary sits at the top. It's the first thing they read and the biggest factor in whether they keep going. Yet most summaries are either missing entirely or filled with generic phrases that say nothing. Here's how to write one that makes them stop and read.
Summary vs. objective: which one to use
A resume objective ("seeking a challenging role where I can grow") is outdated. It describes what you want. A professional summary describes what you offer. Recruiters don't care what you want. They care what you bring to the role. Always write a summary, never an objective.
The only exception: if you're a recent graduate or career changer with very limited experience, a brief objective-adjacent summary that explains your pivot is acceptable, but it should still focus on your skills, not your desires.
The 3-sentence formula
A strong professional summary has three components:
- Who you are: job title + years of experience + domain/industry
- What you're best at: 2-3 core skills or specializations, using keywords from the target JD
- What you deliver: one specific result or differentiator that proves your value
Product Manager, 5 years experience
Before: Experienced product manager with a passion for building products that users love. Strong communicator and team player with experience in agile environments. Looking to join a dynamic company where I can make an impact.
After: Product Manager with 5 years building B2B SaaS products at Series A-C companies. Specialized in 0-to-1 product development and growth loops. Most recently grew DAU 3x in 8 months by rebuilding the activation flow for a 40K-user platform. Expert in cross-functional alignment, product analytics (Amplitude, Mixpanel), and roadmap prioritization.
Examples by career level
Entry-level / recent graduate
Marketing graduate
Before: Recent marketing graduate seeking an entry-level role. Eager to learn and contribute to a team.
After: Marketing graduate with 2 internships in social media management and content strategy. Grew TikTok account for a student-run brand to 8,000 followers in 4 months using trend-led content and A/B testing. Proficient in Google Analytics, Hootsuite, and Canva.
Mid-career professional
Software Engineer, 6 years
Before: Software engineer with 6 years of experience in web development. Strong skills in React and Node.js. Team player with excellent communication skills.
After: Full-Stack Engineer with 6 years building scalable web applications for fintech and e-commerce. Led the migration of a monolithic Rails app to microservices, reducing deploy time from 45 minutes to 8 minutes and cutting production incidents by 60%. Expert in React, Node.js, PostgreSQL, and AWS.
Career changer
Teacher transitioning to instructional design
Before: Former teacher with 8 years of experience looking to transition into a corporate learning role.
After: Instructional designer with 8 years designing and delivering curriculum for 400+ students. Transitioning to corporate L&D, currently completing an ATD certificate and have built 3 e-learning modules in Articulate Storyline as portfolio projects. Strong at translating complex content into structured, engaging learning experiences.
Change your summary for every application. The job title in your summary should match the job title you're applying for, exactly. If the posting says "Senior Product Designer" and your summary says "UI/UX Designer", you're leaving keyword points on the table.
What never to include in a summary
- 'Passionate about...': everyone is passionate. Show it, don't claim it.
- 'Hard worker', 'team player', 'results-driven': buzzwords that mean nothing without proof
- 'Responsible for' or 'duties included': this is a summary, not a job description
- Personal information: age, marital status, photo, nationality (unless required in your country)
- More than 5 sentences. If it goes past 5 lines, it won't be read.
How long should a professional summary be?
3-5 sentences. 50-100 words. It should be scannable in under 10 seconds. Write in third-person style (no "I") but don't include your name. The recruiter can see it at the top of the page.
If you find yourself writing a long summary, you're probably including duties instead of achievements. Cut anything that doesn't directly answer: "Why should we hire this specific person for this specific role?"