What the 220 characters are actually for
If you have never edited it, your headline is whatever LinkedIn generated from your current job title and employer — something like “Software Engineer at Infosys”. That is 28 characters doing the work of 220, and it is word for word identical to the headline of several thousand other people the recruiter is scrolling past that morning.
The full 220 characters only appear on your profile page. In search results, comments, notifications and invitation requests you get a truncated version, often the first 40 to 60 characters on a phone. The terms that decide whether anyone clicks through have to sit at the front, not at the end after two separators.
So one field has two jobs. The opening fragment has to stand on its own as a complete claim, and the remainder has to carry the specifics — stack, sector, numbers — that make the profile worth opening. Written as one long flowing sentence, a headline fails at both.
What LinkedIn search reads
Recruiters search with ordinary job titles: “Java Developer”, “Performance Marketing Manager”, “Chartered Accountant”. Your headline is one of the fields matched against those words, alongside your experience entries and your skills list. A headline that says “Code Alchemist” or “Growth Ninja” matches nothing anyone has ever typed.
Keep the literal title in the line even if it feels plain, and put the specialism beside it rather than in place of it. “Data Analyst | SQL, Power BI, Python” covers both the title someone searches and the three tools they filter on. Personality can go later in the line, once the matching terms are safe.
Repetition earns nothing. Writing “Digital Marketing” four times does not rank you higher, it just spends characters you needed for evidence. One clear instance of each term you want to be found for is enough, and the space left over is worth more as a measured result than as another keyword.
Structures worth borrowing
Role-first suits people whose title already sells them: “Senior Backend Engineer | Go, Kafka, Kubernetes | Cut order-service p99 latency from 1.2s to 340ms”. Title first for search, stack second for filtering, one checkable number third. It reads as fact rather than opinion, which is the whole reason a figure beats an adjective.
Outcome-first suits consultants, freelancers and anyone with a vague title: “I help Indian D2C brands cut acquisition cost — Performance Marketer | ₹4 crore in Meta and Google spend managed”. The benefit opens the visible fragment, the searchable title still appears, and the spend figure signals scale without asking anyone to take your word for it.
Job seekers need a third shape, because screeners in Indian hiring check availability before anything else. “Final-year B.Tech CSE, NIT Trichy | Java, Spring Boot, MySQL | 2 internships, 1 app with 5,000 users | Open to SDE roles from June 2026” answers what, how good and when in 140 characters. If you are serving notice, give the date.