The LinkedIn About section: a structure that actually gets read past the fold
Most LinkedIn About sections are a wall of text no one reads. Here's a structure that earns the second paragraph.

On this page
The LinkedIn About section is the most over-written and under-read field on the platform. Half of profiles have something there. Less than a quarter of those get read past the first two sentences. The ones that do are almost always structured a specific way.
This isn't a personal-branding lecture. It's a structural question: what does a recruiter or hiring manager see in the four seconds they spend on your About section, and how do you make those four seconds work? This post is the answer.
What recruiters actually see
The mechanics matter. On desktop, the About section shows roughly 220 characters before a "see more" link. On mobile, it's closer to 130. Whatever you write after that is functionally hidden from anyone who hasn't already decided to read more.
This means the first sentence is not an introduction. It is the entire decision. If a recruiter sees "I am a passionate, results-driven professional with 10+ years of experience..." they will not click "see more." If they see "I'm the engineer who keeps your data pipeline from breaking at 3am — 8 years building observability for B2B SaaS," they will.
The strongest hooks have three properties: a concrete verb (build, run, lead, ship), a domain (B2B SaaS, growth marketing, climate fintech), and an angle that distinguishes you from the next ten profiles with the same job title.
The four-block structure
The four blocks of an About section that gets read
Structure- 0101Hook line (1-2 sentences, above the fold)
The first ~220 characters are the only thing visible before 'see more.' This is the entire decision: skip or read. Lead with what you do and one specific differentiator. Not 'passionate about technology' — 'I help fintech teams ship payments infrastructure that doesn't break at scale.'
- 0202Three-line story (problem you solve, who for, proof)
Past the fold, three short lines: what kind of problem you solve, who you solve it for, and one concrete proof point. Bullet-fragments are fine. The reader's question is 'is this person legible' — answer it fast.
- 0303Resume-summary remix (5-8 bullets)
Now you have permission for substance. Five to eight bullets of recent achievements — the same ones from your resume, but written for a human reader, not an ATS. Lead with the verb and the result.
- 0404Open-to signal (1-2 lines at the bottom)
What you're open to and how to reach you. 'Open to senior PM roles in B2B SaaS. DMs open — best by email.' This is where recruiters look after they've decided to message you. Don't bury it.
The four blocks above are the load-bearing structure. They map roughly to: hook, story, evidence, call to action. Each does a specific job.
The hook (block 1) is what we just covered: 1-2 sentences that survive the "see more" truncation. The story (block 2) is what justifies the click — three lines that establish what kind of problems you solve and who for. The evidence (block 3) is where the substance lives — bullets of recent achievements that look more like a resume summary than a personal essay. The CTA (block 4) tells the reader what to do next.
The order matters because reader behavior is sequential. People do not skim down to find the good part. They drop off when they get bored. If your hook is generic, no one ever sees the evidence. If your evidence is buried under three paragraphs of philosophy, recruiters give up before the bullets.
A worked example. Take a Senior Product Manager at a mid-stage SaaS company. The before:
I am a passionate product leader with a track record of driving cross-functional collaboration and delivering customer value. Over my 12+ years in technology, I have had the privilege of working with incredible teams to ship products that move the needle. I believe in user-centric design and data-driven decisions...
The after:
I run product for the platform team at [Series D HR-tech company] — APIs, integrations, and the developer experience that lets enterprise customers actually adopt us.
Twelve years in B2B SaaS, last six in PLG-flavored mid-market. Most recent ship: a public API that took our integrations from "trade-show demo" to 40% of new-revenue attribution in 9 months.
Recent work:
- Shipped public REST + webhooks API, now used by 110+ paying customers
- Led pricing redesign that lifted ACV 22% with no churn lift
- Built the cross-functional rituals that took launches from 6 to 2-week cycles
Open to staff PM and head-of-product roles at Series B-D B2B SaaS. DMs open — fastest by email.
The second version reads in 35 seconds and tells you exactly what to do with it. The first reads in 2 minutes and tells you nothing.
What reads as substance, what reads as noise
What reads as substance vs. what reads as noise
Side by side- Lead with the work — 'I run growth experimentation at a Series C HR-tech company.'
- Name the tools and stack you actually use.
- Cite one or two specific outcomes with numbers.
- Mention what you're not doing — 'not currently consulting.'
- Close with a concrete CTA — 'DMs open for roles in EU markets.'
- Open with 'I'm passionate about people and growth.'
- List every adjective in your performance review.
- Write 'results-driven, detail-oriented professional.'
- Say 'I love to learn' without naming what.
- End with a thank-you to LinkedIn for reading.
The compare table is a working filter for everything you've already written. Anything in the "noise" column is space you're paying for with reader attention. Cut it.
The largest category of noise is adjectives without referents — "results-driven," "detail-oriented," "passionate." These do not survive a recruiter's mental skim because they describe everyone who has ever applied for a job. The fix is to replace the adjective with a specific example: instead of "detail-oriented," write "the person who actually reads the change-log." Instead of "results-driven," write "shipped X with Y outcome."
The second category is performance-review language — "leveraged cross-functional collaboration to drive alignment." This does not read as professional. It reads as someone copying their self-review into LinkedIn. Recruiters know what self-review language looks like and discount it accordingly.
How recruiters actually read the section
How recruiters actually use the About section
Reading behaviourThe numbers above are roughly what recruiter eye-tracking and click-through studies report when they bother to measure. The plurality of recruiters read only the hook. About a quarter read past the fold. A meaningful minority read the whole thing, but they're almost always doing so right before they send you a message — they're checking what to say.
The implication is uncomfortable but useful: your About section is rarely read in full by someone who doesn't already want to read it. The job of the first two sentences is to earn the right to be read. The job of the bullets is to convert a reader who got there into a reply.
Where the About differs from the resume summary
LinkedIn About sections and resume summaries serve different functions even though candidates often paste one into the other.
The resume summary is read in the context of a specific application. The reader already knows what role they're hiring for. The summary's job is to confirm fit. See resume-summary-section for that structure.
The LinkedIn About is read in the context of "should I message this person at all." The reader doesn't have a specific role in mind yet. Your job is broader: be legible enough that a recruiter for a role you'd actually want can place you in 10 seconds.
Concretely, this means the LinkedIn About can be slightly more personality-forward and broader in scope. It can mention the kinds of roles you're open to, not just the role you held last. It can include the open-to signal that has no place on a resume.
For more on how the two surfaces differ, see linkedin-vs-resume.
A short editing pass
If you already have an About section, do this in 10 minutes:
- Cut the first sentence and rewrite it. If it contains "passionate," "results-driven," or "professional with X+ years," it needs to go.
- Find the most concrete sentence in the rest of the section. Move it to position two.
- Convert your prose paragraphs into 5-8 bullets. Lead each bullet with a verb.
- Add an open-to line at the bottom.
- Read the section aloud. If you hear yourself sigh, cut more.
What this isn't
A few clarifications:
- It's not a place for your life story. Save the origin narrative for the cover letter or the interview. The About section is professional positioning.
- It's not for keyword-stuffing. LinkedIn's search does pay attention to the About, but stuffing reads as desperate to human readers. Two or three relevant terms is enough.
- It's not static. Update it when your role shifts or you're actively searching. A profile last edited four years ago signals that nothing recent is worth showing.
The short version: hook above the fold, three-line story, bullets of recent work, open-to signal at the bottom. Five to eight minutes of editing turns a generic About into something a recruiter actually reads. Most of your competition won't bother.
More to read
5 min readLinkedIn connection requests: messages that don't get ignored
Most LinkedIn connection requests are sent without a note. The ones with notes are mostly bad. Here's what actually gets accepted and replied to.
linkedinnetworking
6 min readInformational interviews: a script that doesn't waste anyone's time
Most informational interviews accomplish nothing because both sides default to vague chat. Here's a script with a specific ask and a 25-minute structure.
networkinglinkedin
4 min readLinkedIn headlines: patterns that pull recruiter searches and don't sound cringy
Your LinkedIn headline does most of the search-surface work. Here are the patterns recruiters search for — and the ones they actively skip past.
linkedinheadlines
6 min readHow to message a recruiter on LinkedIn (with actual examples)
The cold message that recruiters actually respond to — what to write, what to skip, and the message sequence that converts when the first one doesn't.
job-searchapplications