You’ve been asked to write a LinkedIn recommendation for a former manager, and you’re staring at a blank text box that feels weirdly high-stakes for a few paragraphs. Or maybe it’s the reverse — you’re job hunting, your profile has zero recommendations, and you’re not sure how to ask without it feeling like you’re fishing for compliments.
Both situations come down to the same problem: most people have read a hundred generic LinkedIn recommendations (“great to work with, always a team player”) and have no idea what actually makes one land differently.
Why Most LinkedIn Recommendations Say Nothing At All
Here’s the pattern almost every generic recommendation falls into: it lists adjectives instead of evidence. “Hardworking,” “collaborative,” “a pleasure to work with” — these words could describe literally anyone, which means they tell a reader literally nothing. A recruiter or hiring manager skimming your profile has seen thousands of these. They’ve learned, correctly, to skim right past them.
The actual value of a recommendation isn’t the compliment — it’s the specificity. A recommendation that says “she’s a great problem solver” is forgettable. A recommendation that says “when our biggest client threatened to walk over a missed deadline, she rebuilt the delivery timeline overnight and got them back on board within 48 hours” is not — because it’s a fact, not an opinion, and facts are much harder to write generically. Recent recruiter-behavior research found that the large majority of recruiters actively use LinkedIn as part of their hiring process — which means recommendations aren’t decoration on a profile, they’re one of the few pieces of third-party evidence a recruiter sees before ever picking up the phone.
There’s a second reason generic recommendations fail: they’re clearly written for the person being recommended, not for the person reading it later. A good recommendation should read like it was written for a stranger evaluating whether to hire, promote, or work with this person — which means it needs enough context (what the situation was, what this person actually did, what happened as a result) for someone with zero background to understand why it matters.
Length matters less than most people assume, too. A common misconception is that a longer recommendation signals a stronger relationship or more enthusiasm. In practice, a tight two-paragraph recommendation built around one real example almost always reads as more credible than a sprawling one that tries to cover someone’s entire skill set — the sprawling version starts to sound like it’s straining to fill space, which undercuts the sincerity it’s trying to convey.
This cuts both ways. If you’re writing a recommendation, the fix is simple: pick one specific moment, not a general character sketch. If you’re requesting one, the fix is just as simple, and this is the part almost nobody does — tell the person writing it exactly what specific project or moment to reference, instead of leaving it fully open-ended. Most people, asked to write a recommendation cold, default to vague praise because they haven’t been prompted to think of a specific example. Giving them one removes that entire problem.
The Practical Tool: Examples by Relationship, Plus How to Ask
Here’s what a specific, evidence-based recommendation looks like across common relationships — use these as a starting structure, not a copy-paste template.
From a manager, about a direct report:
“I managed [Name] for two years on the [team/project]. When we lost our lead analyst mid-quarter, [Name] stepped in with two days’ notice and rebuilt our reporting process from scratch — we didn’t miss a single deadline that quarter. Beyond the technical skill, what stood out was how calmly they handled the pressure and kept the rest of the team focused. Any team would be lucky to have them.”
From a peer or colleague:
“I worked alongside [Name] on [specific project] for over a year. What I remember most is [specific moment — e.g., a hard deadline, a difficult client, a process they fixed]. [Name] has a rare combination of being genuinely easy to work with and relentlessly reliable — the kind of colleague who makes the whole team’s work better, not just their own.”
From a direct report, about a manager:
“[Name] managed me for [timeframe], and one thing that shaped how I think about leadership is [specific example — e.g., how they handled a mistake, gave feedback, or advocated for the team]. They gave me real ownership over [specific responsibility] and backed me publicly even when things didn’t go perfectly. I’m a better [role] because of how they managed me.”
From a client or vendor:
“We worked with [Name] on [specific project or engagement]. What set them apart was [specific example — responsiveness, problem-solving under a tight deadline, a specific result they delivered]. We’d work with them again without hesitation.”
From a mentor or professor:
“I mentored [Name] through [program/course/timeframe]. What made them stand out wasn’t just [technical skill] — it was [specific example, e.g., how they handled a setback, sought feedback, or applied a concept in a real project]. They’ve grown more in [timeframe] than almost anyone I’ve worked with, and I expect that trajectory to continue.”
How to ask for one, without it feeling awkward:
“Hi [Name] — I’m updating my LinkedIn and would really appreciate a recommendation if you have a few minutes. If it’s helpful, I was thinking you might mention [specific project or moment] — but totally your call on what to focus on. Happy to return the favor if you’d like one too.”
Notice the ask does the same work as the good examples above: it hands the writer a specific starting point instead of leaving them to invent one from scratch.
A quick reflection on this: Early on, I asked a former manager for a recommendation with no context at all — just “would you mind writing me one?” What I got back was three warm but completely generic sentences that could’ve described any employee she’d ever had. A year later, I asked a different manager the same question, but reminded her of a specific project where I’d caught a costly error before it shipped. The recommendation she wrote was three times more useful — not because she liked me more, but because I’d given her something concrete to write about instead of asking her to invent praise from memory.
Common Mistakes That Undercut a Recommendation
Writing (or asking for) a recommendation with no specific example. Adjectives without evidence are forgettable and interchangeable — the reader has no way to distinguish a genuine recommendation from a favor.
Making it entirely about the writer’s relationship, not the subject’s work. “I’ve known [Name] for 10 years and they’re a wonderful person” says nothing about their professional capability.
Writing something so long it reads as a résumé rewrite. Two to four tight paragraphs beat ten generic sentences — length doesn’t substitute for specificity.
Asking for a recommendation with zero direction. It puts the entire creative burden on the writer, which is exactly why most unprompted recommendations default to vague praise.
Never reciprocating. If someone writes you a strong recommendation, offer one back (when genuine) — it’s a small gesture that keeps the relationship balanced and often results in a stronger recommendation on both sides.
Requesting a recommendation right after a conflict or a rocky project. Timing matters — ask when the working relationship is on solid footing, not immediately after a tense stretch, even if the underlying relationship is fine. The recommendation will read more naturally if it’s not written under lingering awkwardness.
FAQs
How many LinkedIn recommendations should I have on my profile? There’s no hard number, but two or three specific, well-written ones outperform ten generic ones — quality and relevance to your current field matter far more than the total count.
Is it okay to write a draft and ask the person to edit or approve it? Yes, and it’s common practice, especially for busy executives — offer a draft based on a specific project you both remember, and let them adjust the wording so it still sounds like their voice.
Should I request a recommendation from someone I only worked with briefly? It depends on whether they can speak to something specific — a strong recommendation from a three-month project with a clear outcome beats a vague one from a two-year role with nothing concrete to point to.
What if my manager says yes but never actually writes it? Send one polite follow-up after a couple of weeks with a specific example attached — most delays come from not knowing what to write, not reluctance, so removing that barrier often gets it done.
Can I ask someone to remove or edit a recommendation they wrote for me? You can ask, but you can’t edit someone else’s recommendation yourself — if it’s outdated or off-brand for your current career direction, a polite request explaining why is reasonable.
Do LinkedIn recommendations actually matter as much as endorsements or skills badges? Yes, more so — endorsements are a single click with no context behind them, while a written recommendation carries a named person’s specific, attributable account of your work, which is much harder to fake and generally weighed more heavily by anyone actually reading your profile.
The Takeaway
A LinkedIn recommendation is only as strong as the specific moment it references — vague praise is forgettable, a concrete example isn’t. Whether you’re writing one or requesting one, do the other person the favor of narrowing it down to a single real example instead of leaving it open-ended. The same principle scales down to just a few sentences or up to a full paragraph — specificity is what does the work either way, not length.
If you’re building out the rest of your profile alongside this, our guide on what actually makes a cover letter get noticed covers the same specificity principle in more detail.
