I spent a long time treating LinkedIn like a shinier resume. Same content, better font, occasional post about a certificate.
Then a recruiter friend showed me her screen. She was not reading profiles. She was running a search — and my profile either matched the query or it did not exist.
That reframing changed everything about how I write it.
LinkedIn is a search product, not a document
The tool most recruiters use is LinkedIn Recruiter, and it works the way any search interface works. You type constraints. It returns a ranked list. A typical query looks something like this:
("frontend engineer" OR "front-end developer" OR "UI engineer")
AND (React OR Next.js)
AND (Bengaluru OR Remote)
NOT (intern OR fresher)
Look at what that query touches. Job titles. Skills. Location. Seniority words.
It does not touch your summary paragraph. It does not touch the phrase you agonised over. If the literal strings are not in the searchable fields, you are not in the result set — and you cannot be rejected by someone who never saw you.
The fields that actually carry weight
Not all of your profile is equal. Roughly, in order of how much search weight it carries:
| Field | Why it matters |
|---|---|
| Headline | Indexed heavily, shown in every result row. Your one line of ad copy. |
| Job titles | The primary filter. Recruiters search titles before anything else. |
| Skills | A controlled vocabulary — you pick from LinkedIn's list, so it maps cleanly to filters. |
| Location | A hard filter. Wrong or blank location removes you entirely. |
| Current company | Used for sourcing from competitors. |
| About / summary | Read by humans after you surface. Nearly useless for surfacing. |
The pattern: anything structured gets searched, anything prose gets read later. Most people invest their effort in exactly the wrong half.
The headline mistake I made for two years
By default, LinkedIn sets your headline to your current job title at your current company. Mine said Software Engineer at [Company].
That is a description of where I was. Recruiters were searching for where I wanted to go.
The fix is not to lie. It is to include the vocabulary of the role you are targeting alongside the one you hold:
Before: Software Engineer at Acme After: Software Engineer at Acme · React, TypeScript, Node · Building design systems
Same person, same job. But now four more queries can find me, and a human skimming a list of forty results has a reason to stop.
Skills are a checklist, not a trophy shelf
The skills section feels like the least serious part of the profile. It is one of the most functional.
- It maps to a fixed taxonomy, so it filters cleanly.
- Recruiters filter on presence, not on endorsement count. Twelve endorsements for "Microsoft Word" help nobody.
- Order matters — your top skills are the ones displayed. Audit it once a quarter. Delete the skills from the career you are leaving. Add the ones from the job description you keep applying to.
Match the vocabulary, not the vibe
Here is the part people resist. If every posting you want says "data analyst" and your title internally is "Insights Associate," the internal title is costing you.
You are allowed to write Insights Associate (Data Analyst). You are allowed to describe the same work in the market's words rather than your company's. This is not embellishment — it is translation, and refusing to translate only punishes you.
The same logic drives what happens to your actual resume file once you apply, which runs through a parser with even less patience for creativity. I wrote about that in why my resume kept disappearing.
The quiet signals
A few switches that do more than they look like they do:
- Open to Work — the recruiter-only version is visible in Recruiter search filters and does not put a green frame on your photo.
- Location set to a metro you can actually work in. Blank location is invisible to location filters, and most searches use one.
- A photo. Profiles without one get skipped in list view, fairly or not.
- Activity. A profile that has posted or commented in the last month reads as active rather than abandoned.
What I do now, in ten minutes a quarter
- Rewrite the headline to match the job I want next.
- Reorder skills to put the target role's stack first.
- Confirm location and Open to Work are set.
- Add one line of recent work to the current role. That is the whole ritual. It is not glamorous. But it moves you from "not in the result set" to "in the result set," and everything else in a job search — the resume, the phone screen, the questions you prepare — only matters after that.
Once you are surfacing, the next problem is being ready when the call comes. That is a different checklist, and I keep mine here.