LinkedIn Recommendations

LinkedIn recommendations are a secondary signal in most hiring contexts. Hiring managers reviewing a candidate's profile may glance at the recommendations section to check for pattern signal (does the candidate have recommendations, who wrote them, what dimensions do they consistently address). They do not typically read the recommendations carefully or rely on them as a primary reference source. The formal reference call with candidate-nominated references remains the dominant mechanism for the substantive evaluation step.

The pattern signals hiring managers look for: who wrote the recommendations (recognised peers and supervisors carry more weight than acquaintances or junior colleagues), what they say specifically (concrete details about the candidate's work carry more weight than general praise), and how recent they are (recommendations from the past two to three years carry more weight than older recommendations). A profile with three to five substantive recommendations from credible writers reads as well-supported; a profile with no recommendations or with a single generic recommendation reads as a neutral signal.

The negative-signal risk: a profile with many recommendations that read as low-quality (generic praise, mutual-back-scratching patterns where the candidate has written reciprocal recommendations for the same writers, recommendations from people whose own LinkedIn profiles look low-credibility) can read worse than no recommendations at all. The signal-quality dimension matters more than the count. Candidates who think strategically about which recommendations to display do better than candidates who accept every recommendation that comes in.

Three structural properties make LinkedIn recommendations a different document type from formal references. Public: the recommendation is visible to anyone viewing the candidate's profile, including future employers, customers, partners, competitors, and (in some cases) members of the candidate's current employer who may not know the candidate is open to opportunities. Persistent: the recommendation stays on the profile indefinitely unless removed by the writer or hidden by the candidate, accruing as part of the candidate's broader professional reputation. Unsolicited from the hiring side: the recommendation was not requested by a specific hiring manager, did not address dimensions the hiring manager wanted covered, and was not verified through the formal reference process.

The public property is the most consequential constraint on what writers will honestly say. A writer producing a LinkedIn recommendation knows that the candidate, the candidate's current and future employers, and the writer's own current and future employers will all see it. The writer self-censors significantly more than they would in a private reference letter or in a confidential reference call. The implication: LinkedIn recommendations skew positive even by reference-letter standards, and hiring managers calibrate accordingly.

The persistent property means writers are sometimes uncomfortable writing LinkedIn recommendations they would happily provide privately. A recommendation written today may be read by a different audience years later, in a context the writer cannot predict. Writers thinking about the long-run reputation implications often write more conservatively than they would for a single-moment reference letter, which further compresses the dynamic range of what is said.

For most professional hiring contexts, LinkedIn recommendations function as supplementary signal rather than as primary references. Three contexts make them more consequential. First, freelance and consulting engagements, where the client is often a single decision-maker who reviews the candidate's LinkedIn profile as the primary research source before engagement. A profile with strong LinkedIn recommendations from past clients can be the deciding factor for a small engagement decision.

Second, recruiter-mediated hiring for senior individual-contributor or mid-level roles, where the recruiter uses LinkedIn as the primary research tool and may rely more heavily on the recommendations section than the eventual hiring manager will. Candidates working with active recruiters often see meaningful uplift in interest from a stronger recommendations section. Third, business development and partnership contexts where the candidate's LinkedIn profile is the customer-or-partner-facing artefact; the recommendations function as customer testimonials in the absence of a formal testimonials page.

For these contexts specifically, candidates have a real incentive to cultivate a thoughtful set of LinkedIn recommendations. For more conventional hiring contexts, the marginal return on building out the LinkedIn recommendations section is lower, and candidates' time is better spent on the formal reference relationships that will be invoked through the structured hiring process.

The mechanical ask through LinkedIn's request-a-recommendation feature is straightforward: the candidate sends a request, the writer receives a notification, and the writer composes a recommendation that the candidate can accept or decline before it appears on the profile. The substantive ask, by contrast, requires the candidate to be thoughtful about what to request and from whom.

Specificity in the ask produces specificity in the recommendation. A request that references a specific shared project, a specific moment in the candidate's work, or a specific capability the writer has direct knowledge of will produce a recommendation built around that material. A generic request (\"would you write me a recommendation?\") produces a generic recommendation. The candidate should usually accompany the LinkedIn-platform request with a brief direct message that names the specific thing they hope the writer will mention.

Timing matters. Recommendations are most easily written when the shared work is fresh in both parties' memory. Candidates wrapping up a major project, leaving a role with strong references to maintain, or completing a notable consulting engagement should request LinkedIn recommendations in the weeks following the completion, while the specific details are still retrievable. Recommendations requested years after the shared work often produce generic content because the writer cannot reconstruct the specific moments to draw on.

The most useful LinkedIn recommendations run 100 to 250 words and address two specific elements: the working context (when, where, and on what the writer worked with the candidate) and one or two specific things the candidate did well. The format mirrors the formal-reference structure in miniature, with the constraint that everything must compress to a paragraph or two.

A workable structure: one sentence on the working context (\"I worked with [Candidate] for two years at [Company] when [Candidate] led the [function] organisation that supported my [team / function]\"), two to three sentences on the specific thing the writer most clearly recalls (\"the work I most remember [Candidate] for is [the specific project / capability / moment], where [the specific thing they did and the outcome]\"), and one closing sentence with a forward-looking framing (\"for any team thinking about working with [Candidate], the capability they will get most directly is [the specific capability]\").

The format that does not work: pure adjective accumulation (\"[Candidate] is a hardworking, talented, dedicated professional with strong leadership skills\"). The format is recognised by readers as filler and is discounted entirely. The format that also does not work: humblebrag indirection where the writer is mostly talking about themselves rather than about the candidate. Both patterns are common; both produce recommendations the candidate would be better off not having.

For academic, postdoctoral, and senior research-and-development job markets where Interfolio dossiers are the standard reference-collection mechanism, LinkedIn recommendations do not substitute for the formal letter. Interfolio dossiers contain confidential, longer-form recommendation letters submitted directly to applications, with the candidate's FERPA waiver and the recommender's structural assumption of confidentiality. The format is structurally different and the content runs much longer (one to three pages versus 150 to 250 words on LinkedIn).

For most professional hiring, the structural parallel is not Interfolio but the formal reference call. The hiring manager's reference call with the candidate's nominated references produces the substantive evaluation that drives the hiring decision; the LinkedIn recommendations are an upstream-research signal that contributes to whether the candidate gets to the reference call stage but does not determine the call's outcome. Candidates should invest in both layers but should weight the formal reference layer more heavily for the decisions that materially affect career outcomes.

For candidates whose work has a public-portfolio dimension (consulting, design, writing, software development, public speaking), LinkedIn recommendations can complement a portfolio that already does most of the credibility work. The portfolio shows what the candidate did; the LinkedIn recommendations corroborate it from the relationship side. The two layers together produce a stronger public profile than either alone. See the coworker to coworker and professor to student pages for adjacent reference patterns.