A friend of mine runs technical recruiting at a mid-size SaaS company. Last month I sat over her shoulder for an hour while she did a normal LinkedIn sourcing session for a senior backend role. Then I did the same with two other recruiters from different companies, on different searches.
What I watched was not what I expected. The recruiters did not behave the way every "optimize your LinkedIn" guide assumes they do. They scrolled fast, made decisions in 4-9 seconds per profile, and most of the things career-advice content tells you to put on your headline did not even register.
Here is the actual pattern across 30+ profile views per recruiter, three sessions, three different niches.
What they actually click on
Three signals decided whether the recruiter clicked the profile or kept scrolling. In order of how often they triggered the click:
1. The headline contains a specific technology stack, not a job title.
"Senior Backend Engineer | Go, Postgres, Kubernetes" got clicked. "Senior Software Engineer at [Company]" got skipped. Recruiters told me the same thing in different words: the job title alone tells them nothing because every other profile says the same thing. The stack tells them whether you are the right shape for the role.
2. The current company is one they recognize, OR the previous company is.
Recruiters scan the right rail of the search result for company names. A recognizable name (FAANG, well-known startup, well-known agency) anchors the click even when the current role is unknown. This is the "halo effect" people complain about and it is real. If you have ever worked at a recognizable name, get it into your tagline area.
3. The headline mentions a number.
"Scaled X to 50M requests/day" or "Shipped Y across 12 markets" — anything quantitative — outperformed adjective-heavy headlines like "Passionate, results-driven engineer." The recruiters told me numbers were a signal that the candidate would have answers in a phone screen.
What they ignored
These showed up in nearly every profile but did not influence the click decision once:
- Buzzword soft-skill claims in the headline. "Passionate", "results-driven", "growth mindset", "innovator". Every recruiter I watched specifically said some version of "I do not read those words anymore."
- Open-to-work green ring. This was supposed to help, but in the niche we sourced (senior eng), the recruiters explicitly de-prioritized it. One said "if you are senior and openly searching, that is sometimes a flag." Two of the three filtered it out manually. (For junior roles the signal goes the other way — green ring helps.)
- Profile photo aesthetic. Within the bounds of "professional and not distracting," none of the recruiters spent more than half a second on the photo. A great photo did not save a weak headline. A weak photo did not kill a strong headline.
- The "About" section. None of the recruiters opened it during the initial scan. The About only got read after a candidate was already in the shortlist, as a sanity check.
What they hated
Three things consistently triggered an explicit "next" click:
- A title that is one level above what the company supports. "Principal Engineer" at a 12-person seed-stage startup got rolled eyes from every recruiter. They all assumed it was inflated and dropped the profile.
- A long string of contractor stints with no detail on outcomes. Multiple 4-6 month engagements with no quantified result reads as "could not get re-upped".
- Headline written like a Twitter bio. "Builder. Coffee enthusiast. Dog dad. Ships software." The recruiters skipped these instantly. The cuteness signal works on Twitter; it actively hurts on LinkedIn search results.
A 30-minute headline rewrite that probably moves the needle
Based on what I watched, here is what an effective senior-eng headline structure looks like:
[Seniority + Function] | [Top 3 technologies] | [One concrete outcome with a number]
Examples of headlines I sketched on paper while watching the sessions:
- "Senior Backend Eng | Go, Postgres, K8s | Took $120K/mo infra spend down 38%"
- "Staff iOS Engineer | Swift, SwiftUI, RxSwift | Shipped 4 apps to 10M+ installs"
- "Engineering Manager | Distributed systems, on-call ownership | Cut PagerDuty volume 64% in 8 months"
The pattern is the same: function, stack, proof. Three pieces. Done in under 220 characters.
What this builds on
The original LinkedIn Profile Is Invisible to Recruiters post covered the LinkedIn search algorithm side of why your profile may not be surfacing. This post is the human side of the same problem — what happens once a recruiter actually does see you.
For the data side, I Scraped 50 LinkedIn Profiles That Got Recruited goes deeper on what the winning profiles had in common at the structural level (skills section, endorsements, recommendations).
The fast version of all of this: rewrite your headline to function + stack + one number. Most everything else is downstream noise.
Top comments (0)