I have been writing about LinkedIn invisibility for two months. Last month I tested it on myself.
The setup: rotate seven headline patterns across thirty days, one week per pattern (with two patterns getting two weeks because I needed more data). Hold the rest of the profile completely static. Track inbound recruiter messages, profile views, and search appearances via the analytics tab. Use a private alt-account a friend ran to verify search position for the same target keywords across each headline.
Two patterns won. Five did not. Here is what shipped and what flopped.
The seven headlines I tested
I tried to hit the actual variance you see in the wild rather than only the ones I expected to win. Each is rendered exactly as it appeared on the profile.
- Senior Software Engineer at [Company] — the default
- Senior Software Engineer | Backend (Go, PostgreSQL, Kubernetes) | Remote
- Senior Software Engineer | I help fintech teams scale Go services to 10k req/sec without rewrites
- Building developer tools at [Company] | Backend / Distributed Systems | Open to remote
- Senior Software Engineer (Backend, Go, K8s) — building API platforms used by 200+ enterprise customers
- Backend Engineer focused on payment systems | Go, Postgres, Kubernetes | Open to senior roles
- Software Engineer | 8 years | Remote-first | Reach out about backend platform roles
The two that won
Pattern 2 and pattern 6 were the only ones that produced more than one recruiter message in their week. Pattern 2 produced 4 messages. Pattern 6 produced 5. The other five patterns produced zero, one, or — in one case — one ill-targeted message about a frontend role.
What those two had in common:
- Title or seniority word in the first 30 characters. Recruiter search seems to weight the first chunk of the headline heavily. "Senior Software Engineer" or "Backend Engineer" needs to be early.
- Stack tokens, not paragraphs. "Go, Postgres, Kubernetes" outperformed "Go, distributed systems, infrastructure." Concrete tools beat abstract domains.
- A "what I'm open to" signal. "Remote" or "Open to senior roles" — short, scannable. Recruiters filter by these.
The losers had three failure modes.
- Achievement headlines (3 and 5) flopped. "I help fintech teams scale Go services to 10k req/sec without rewrites" was clicked-through more (profile views went up) but recruiter outreach dropped. The headline read like a consultant pitch and recruiters skipped it.
- Brand-led headlines (4) flopped. Leading with the company name makes the title less searchable. The keyword that recruiters search ("backend engineer," "senior engineer") is buried.
- Short-sentence headlines (7) flopped. "8 years | Remote-first" sounds confident but it is too far from how recruiters search. They search by stack and seniority, not by years and preferences.
The week-by-week numbers
Profile views (LinkedIn analytics, weekly):
- Pattern 1 (default): 38
- Pattern 2 (stack-forward): 71
- Pattern 3 (achievement): 92
- Pattern 4 (brand-forward): 44
- Pattern 5 (achievement-numerical): 81
- Pattern 6 (focus-area + open-to): 76
- Pattern 7 (years-forward): 41
Recruiter messages:
- Pattern 1: 0
- Pattern 2: 4
- Pattern 3: 1 (unrelated role)
- Pattern 4: 0
- Pattern 5: 0
- Pattern 6: 5
- Pattern 7: 1 (recruiter-network spam)
The interesting wedge: pattern 3 had the most profile views and the worst outreach. Profile views and recruiter outreach are not the same metric. A headline that catches eyes from your network is not the same as a headline that surfaces in recruiter search.
Search-position check
The verification — a friend's alt-account searching "senior backend engineer Go Postgres remote" each week — added one more data point.
Pattern 2 surfaced on page 2 of search results. Pattern 6 surfaced on page 3. The other patterns either did not appear in the first 5 pages or appeared inconsistently. Default headline (pattern 1) did not appear at all.
If you take nothing else from this test: putting your stack tokens in the headline is the lowest-effort, highest-yield change you can make. The headline is not the place for personality. It is the place for keywords.
The headline I am running now
I wrote a synthesis of the two winners after the test ended:
Senior Backend Engineer | Go, PostgreSQL, Kubernetes | API platforms & distributed systems | Open to remote senior roles
It hits the four things that mattered: title in the first 30 chars, three concrete stack tokens, a focus-area phrase that scans, and an open-to signal. It is also still inside LinkedIn's 220-character limit with room to add or rotate.
What to do with this
If you have not changed your headline in six months, the cheap experiment is: write three variants on this template and rotate them weekly. Track recruiter messages and search appearances. Pick whichever wins. Repeat the test in six months because LinkedIn keeps tuning what its search ranks.
The pattern that has not changed in two years: keywords beat narrative. Stack beats story.
Free tools I built for the job search: resume-checker, job-keywords, resume-bullets. All free, all in the browser, no signup.
Earlier in this series:
