LinkedIn profile score FAQ

Your LinkedIn profile score out of 100 is the weighted sum of 8 dimensions. Each dimension is scored 0 to its max, and the 8 subscores add up to your overall profile score:

Headline 20 · About 25 · Experience 20 · Skills 15 · Education 8 · Activity 8 · Recommendations 5 · Media 4 = 100 points total.

The rubric is fully deterministic — identical inputs always produce identical scores. There is no hidden randomness and no per-profile variability. The full weight breakdown with strong-vs-weak examples lives on the rubric page.

Read the full breakdown on the rubric page →.

There isn't a single universal "good" score — it depends on who is reading the profile. Recruiters and ATS systems scan for specific keywords and quantified outcomes, so a 70+ usually reads as strong, while anything below 50 reads as generic. Profile viewers who are not recruiters tend to anchor on the headline and photo first, then the About, then top Experience.

That said, the same profile almost always scores higher for a recruiter-relevant reader than for a casual one — the rubric weights specificity, quantification, and ATS keywords heavily because those are what recruiters and applicant-tracking systems actually scan for.

For the per-cohort benchmark table (recruiter-read score vs. self-read score, percentile band, and what to fix first), see the score benchmarks guide: What is a good LinkedIn profile score? →

The LinkedIn profile scoring rubric is deterministic — there is no hidden randomness, no model drift, and no per-profile variability. Your score only changes when the underlying profile content changes: a new headline, an updated About, a fresh Experience entry, a new Skill added in an order that matches your headline, a new post, or a new Recommendation.

Re-scoring the same profile content always returns the same number, every time. If your score moved between two runs, the input changed — or the scorer caught a new public profile state (LinkedIn sometimes reorders Skills, or adds a Featured item without you realizing it).

For the long-form walkthrough of the deterministic scoring model, see: How LinkedIn scoring actually works →

The Headline dimension is worth 20 points — the second-largest single dimension after About. It measures:

Specificity of role. "Senior Engineer" beats "Engineer", and "Staff ML Engineer" beats "Senior Engineer". Specificity tells the reader what you actually do.

Keyword breadth. Recruiters and ATS systems scan the headline for stack words and seniority markers. Three to five specific keywords is the sweet spot.

Value-proposition framing. A strong headline opens with a quantified impact — "Senior Engineer at Acme | Scaled platform to 10M daily users". A weak one is just the role and company.

For the full definition with strong vs. weak examples, see the Headline section on the rubric page →.

The About dimension is worth 25 points — the single largest dimension in the rubric. It measures:

Hook strength in the first two lines. "I built the platform that 10M people use every month" lands a recruiter. "Experienced full-stack engineer with 8+ years…" does not.

Quantified outcomes. Numbers separate senior ICs from mid-level. The best About sections name at least two quantified outcomes (users served, latency cut, ARR influenced).

Narrative coherence. The hook, the past, the next step — they should thread into one arc, not three chronological paragraphs.

Call-to-action. Strong About sections end with an invitation — "Open to: staff IC roles, founding-engineer opportunities." — so a recruiter knows what the writer is looking for.

Full definition and strong vs. weak examples are on the rubric page →.

The Experience dimension is worth 20 points. It is scored per-role and aggregated across the profile. It measures:

Quantified impact per role. "Reduced p99 latency 40%" beats "Improved performance". A strong Experience description names team size, the architecture decision, and the measured outcome.

Seniority indicators. Scope (single feature vs. platform), scale (team of 3 vs. team of 50), and budget (cost of the system owned) — these together signal seniority.

Progression across positions. Steady growth in title, scope, and impact across the timeline. A flat trajectory scores lower than an upward one.

See the Experience entry on the rubric page → for the strong-vs-weak side-by-side.

The Skills dimension is worth 15 points. It measures:

Coverage of the modern stack for the role. A senior backend engineer is expected to name a cloud platform, a container layer, an orchestration layer, a database, and a language. Three keywords is too thin.

ATS-friendly keyword breadth. Exact-match keywords ranked by LinkedIn's search filter. Recruiters filter by stack, so missing common keywords drops the search rank.

Reorder alignment with headline and About. The first three Skills should match the stack named in the headline and About in roughly the same order. This signals intent to a recruiter scanning top-down.

Full strong vs. weak comparison is on the Skills entry on the rubric page →.

The Education dimension is worth 8 points. This is the dimension that surprises most people — and the one the request originally called "Connections". It measures:

Institutional credibility. Named institution plus named program. "Stanford MS Computer Science" beats "State University, MS CS".

Degree relevance. Whether the degree maps to the role — a CS MS for a backend role, a Statistics MS for an ML role, an MBA for a GM role.

Complementary credentials. For senior candidates, certifications carry weight: "AWS Solutions Architect Professional · ongoing" signals current technical breadth beyond the degree.

Definition and examples live on the Education entry on the rubric page →.

The Activity dimension is worth 8 points. LinkedIn weights signals of a living, breathing profile rather than a dormant one. It measures:

Recent posting cadence. A monthly post (or better, a monthly cadence plus a recurring Newsletter) reads as actively engaged.

Enablers present. Newsletters, long-form Articles, and consistent Comments all count — they broaden the surface area a recruiter can sample.

Engagement signals. Comments and reactions on other people's posts — quality reactions that show domain reading, not drive-by likes.

Full definition and examples are on the Activity entry on the rubric page →.

The Recommendations dimension is worth 5 points. Small but high-signal. It measures:

Number of recommendations. Four to six is the sweet spot. Zero is the worst state; ten is more than a recruiter will read.

Credibility of recommenders. A skip-level manager, a peer PM during a launch, a startup founder you advised — these are different voices that signal how you work across contexts.

Specificity. Recommendations that name a project, an outcome, and a personal characteristic beat recommendations that read as "great to work with".

Examples live on the Recommendations entry on the rubric page →.

The Media dimension is worth 4 points — the smallest single dimension, but the easiest to lift. It measures:

Featured section content. Conference talks, GitHub repos, podcasts, and long-form blog posts all count. Three to five items is the sweet spot.

Visual artifacts of work. A screenshot of a dashboard, a diagram of a system, a slide deck — anything a recruiter can click on and see what you actually built.

Recency. Recent items count for more — a 2018 conference talk is okay, but a current repo is better.

Definition and strong vs. weak examples are on the Media entry on the rubric page →.