How to Write a LinkedIn Summary That Gets Replies
The 3-paragraph summary framework that converts recruiter-scanners into recruiter-messagers. With before/after rewrites and a live demo you can try.
Founder, TryApplyNow
Your LinkedIn summary has one job: convert a recruiter who found you via search into a recruiter who sends you an InMail. They already know your title and skills - those are what made you show up. The summary's job is to answer the one question they're asking: "is this person open to work that matches what I'm recruiting for?"
LinkedIn headline visibility
Full-Stack Engineer → Senior Full-Stack Engineer
Current headline
Full-Stack Engineer | Tech Enthusiast
Click "Analyze" to see how this headline ranks in LinkedIn Recruiter search.
The 3-block summary framework
Block 1: Role + years + domain + 4-5 keywords (2-3 sentences)
The first ~300 characters are what LinkedIn previews on recruiter search results. These sentences have to do triple duty: rank for keywords, answer "what do you do?", and hook the reader to expand.
Template:
[Target-role-aligned title] with [N] years building [what] for [domain/vertical]. Specialize in [one specialty], working primarily in [2-3 keywords].
Example:
Senior Full-Stack Engineer with 6 years building B2B SaaS platforms on Next.js and TypeScript. Specialize in end-to-end vertical ownership - from Postgres schema design to React UI performance.
Block 2: One specific achievement with a metric (2-3 sentences)
Recruiters don't read the summary for personality. They read it for proof of capability. One specific, measurable achievement is worth 10 generic claims.
Template:
At [company/context], [what I did] - [outcome + metric]. [One more concrete line that shows range or leadership.]
Example:
At Acme ($20M ARR B2B SaaS), led the frontend migration to Next.js 14 + React Server Components, cutting LCP from 4.1s to 1.2s and bundle size 58%. Mentored 3 mid-level engineers through promotion cycles in 2024-2025.
Block 3: What you're looking for next (1-2 sentences)
This is the sentence that converts scanners into InMailers. Be explicit. Recruiters' time is short; an ambiguous "open to new opportunities" doesn't help them decide whether to contact you.
Template:
Looking for [target level] [target role] roles at [target type of company] working on [target domain]. Open to remote and [city/region].
Example:
Looking for staff/principal full-stack engineer roles at Series B-D B2B SaaS companies working on developer-facing or infra- adjacent products. Open to remote and SF Bay Area.
What kills recruiter replies
- Buzzwords ("passionate," "results-driven," "self-starter"). Recruiters scroll past these in under a second. Empirically, removing buzzwords from About sections lifted recruiter response rates 15-25% in our platform's cohort data.
- Vague claims without proof ("I'm passionate about building great products"). Recruiters need specifics - company, product, metric, timeframe.
- Humble-bragging ("Grateful to have been named top performer"). Direct claims with evidence work better than modest framing with implications.
- Irrelevant personal details (pets, hobbies, college sports). Fine in small doses at the end; not in the keyword-weighted first 500 chars.
- No explicit "what I want next". Leaves recruiters guessing and most don't reach out.
Three full before/afters
Software Engineer
Before (visibility 38, response rate ~1/quarter):
I'm a passionate, results-driven software engineer who loves to build great products. I've worked at several companies on a variety of interesting projects. Always learning and looking for new challenges.
After (visibility 87, response rate ~3/month):
Senior Backend Engineer with 7 years building distributed systems on Go + Kubernetes for B2B SaaS products. Specialize in reliability and latency work.
At Acme (~$40M ARR), led migration of billing service from monolith to 4 microservices (gRPC + Postgres), cutting deploy time 18min → 3min and unblocking independent team iteration.
Looking for staff-level backend or platform-engineering roles at growth-stage startups. Open to remote and NYC.
Product Manager
Before (visibility 41):
Product Manager with MBA. Passionate about great user experiences. Previously worked at several startups and a large tech company.
After (visibility 89):
Senior Product Manager with 5 years in B2B SaaS, specializing in growth PM and funnel experimentation.
At Stripe, owned the activation funnel - ran 14 quarterly experiments lifting new-merchant activation 31% in 9 months. Previously shipped checkout redesign at Acme that moved conversion 21% on $14M ARR surface.
Looking for principal PM roles at Series C-D fintech or developer-infra companies. Open to remote.
Marketing
Before (visibility 39):
Marketing professional with experience across multiple industries. Passionate about storytelling and brand-building.
After (visibility 86):
Senior Growth Marketer with 6 years scaling B2B SaaS - performance marketing, PLG experimentation, and SEO-driven demand gen.
At HubSpot, owned $1.2M annual paid budget across Google, Meta, and LinkedIn, hitting $180 CAC target for 8 consecutive quarters. Built SEO program from 12k to 140k monthly organic visits in 14 months.
Looking for senior/director growth marketing roles at Series B-D B2B SaaS. Open to remote, SF, and NYC.
Speed it up
If you paste your current About section into the LinkedIn headline generator, it returns 3 headline variants AND a rewritten About section in one pass - about 10 seconds. The rewrite follows the 3-block framework above, tuned to your target role + top skills.
Either way - manual rewrite or AI - the structure is the same: role + proof + what's next. Recruiters message the profiles that do all three in the first 500 characters.