The short answer
Recommendations carry weight because a named person attached their reputation to them. The problem is that an open-ended request produces three vague sentences about you being a pleasure to work with. Ask specific people for specific things, tell them what you would like covered and why, give them a deadline and an easy way to decline, and offer to write theirs first.
What matters most
- Five specific recommendations beat twenty generic ones. Nobody is counting them; readers sample two or three.
- An open-ended request produces generic praise. Name the project and the quality you want covered.
- Ask a former manager, a peer and, if the work allows, a client or stakeholder — three perspectives, not three copies.
- Offer to write theirs first, and give them an explicit and comfortable way to say no.
Why the request matters more than the ask
Put yourself on the other side. A former colleague messages you: "Would you mind writing me a LinkedIn recommendation?" You want to help, you have twenty minutes of goodwill and no particular structure, and you cannot remember which of the several things you worked on together they would want mentioned. So you write what anyone writes in that position — that they were reliable, easy to work with, and a real asset to the team.
That paragraph is not a failure of goodwill but a failure of brief. The person had everything except direction, and direction was the one thing only you could supply. Almost every technique below is a variation on the same insight: make the request small, specific and easy to answer.
- 1Pick the person for a reason
Not who likes you most, but who can speak to the thing you want to be known for. A manager who watched you turn something around is worth five contacts who remember you fondly.
- 2Ask outside the platform first if you can
A message, an email or a five-minute call, before the formal LinkedIn request arrives. The platform request is an admin task; the human ask is the part that gets a yes.
- 3Name the project and the quality
One or two specifics. "The warehouse re-slotting, particularly the training side" gives them a subject, a scene and permission to be concrete.
- 4Give them an exit
One sentence making it entirely comfortable to decline or delay. It costs you nothing, it protects the relationship, and it markedly increases the quality of the yes.
- 5Give a soft deadline
A date makes the task finite. Without one it sinks to the bottom of an inbox and stays there, and you are left wondering whether to chase.
- 6Send the formal request, then leave it alone
One reminder after a fortnight is fine. A second is not — you are asking a favour, not chasing a deliverable.
What to actually say
Two example messages, written for this guide. Both are short, both do the same three jobs — remind, specify, release — and neither takes more than a minute to read.
Hi Dan, hope you are well! I am updating my LinkedIn and wondered if you would be able to write me a recommendation? Anything you can say would be much appreciated. Thanks so much!
Hi Dan — I am putting my profile in order for an operations manager search, and I would value a few lines from you if you have the time. The part I would most like covered is the re-slotting project, especially the training side, since that is what I want to be known for and you saw it up close. Three or four sentences is plenty. If the next couple of weeks are difficult, or you would rather not, please just say so — no awkwardness at all.
Hi Priya, could you endorse me on LinkedIn? I will do the same for you.
Hi Priya — I am moving towards senior analyst roles and would love a short recommendation if you are willing. The forecasting model we built for the store rollout is the piece I want on the record, particularly how we handled the pushback from regional. Happy to write one for you first, and happy for the answer to be no.
Who to ask, and how many
The instinct is to ask everyone who might say yes. Better to assemble three or four perspectives that together describe the whole of you, because a reader samples rather than reads — two or three, usually the most recent, and rarely more.
- A former manager
- The most valuable single recommendation you can hold, because a manager is the person who could have said something critical and did not. One is worth several from peers.
- A peer or close collaborator
- Speaks to how you are to work alongside, which a manager sees only partially. Particularly useful for cross-functional roles.
- A client, customer or stakeholder
- Where the work allows it, external validation carries a different weight — it is the closest thing to a result the platform can display.
- Someone you managed
- For leadership roles this is the one people forget, and it is the most revealing. Ask a former report to describe how you handled something difficult.
- A tutor, supervisor or placement lead
- Early in a career, where a work history is short, an academic or placement referee is a legitimate and expected substitute.
Four or five good ones is a complete set. Beyond that you are accumulating rather than building, and a wall of twenty begins to read as an exercise in collection.
Freshness matters more than volume
A recommendation is timestamped and the reader sees the date. Six glowing paragraphs, all from years ago, tell a story you probably did not intend. If you are only going to make one request, make it to someone who worked with you recently.
What a good one contains
Useful when you are asking, and equally useful when you are writing one for somebody else — which, given the reciprocity, you will be.
- The relationship, stated plainly. How they know you, in what capacity, for how long. It sets the reader's expectations about how much the rest is worth.
- One specific situation. A named project, problem or period. Specificity is the entire difference between a recommendation and a compliment.
- Something that was hard. The detail that makes praise believable. "The rollout slipped twice before she took it over" does more work than three adjectives.
- An outcome. What changed. It need not be a number, but it should be something a reader can picture.
- A qualification or a limit. The best recommendations carry a note of realism — the person is exacting about detail, or works best with clear priorities. It reads as an assessment rather than a favour.
- A short close. Whether they would work with you again, and in what kind of role. Two hundred words is a strong recommendation; six hundred is an essay nobody finishes.
If you are writing one and stuck, the same rule applies as on a resume: describe what happened rather than what the person is like. The character assessment emerges from the story, and the reader trusts it more for having drawn the conclusion themselves. Our action verbs guide is written for a different document, but the discipline is identical.
The awkward cases
Three situations that come up constantly and have reasonable answers.
Do not ask that manager. Ask a peer from the same period instead — a colleague-level recommendation covering the same work does the job, and nobody is auditing which of your managers is absent.
One friendly reminder after a fortnight, framed as a check that the request did not get buried. If nothing follows, let it go. People go quiet for reasons unconnected to you, and a second chase turns a non-event into a real awkwardness.
You control whether a recommendation is displayed, so a thin one can simply be left unpublished. Do that quietly and do not explain — and next time, brief more specifically, because a vague recommendation is nearly always a vague request coming back to you.
One more worth naming: recommendations are public. If your current employer follows your profile, a burst of new ones is noticeable in a way that quietly updating your skills is not — a reason to space them out rather than to avoid them. The settings guide covers the visibility controls that keep profile activity discreet.
Recommendations are not references
They are related and conflating them causes real problems. A recommendation is public and voluntary. A reference is a private, often formal check requested by an employer at offer stage, sometimes limited by policy to dates and job titles. Someone who wrote you a warm recommendation may still be unable to act as a formal reference, and a company confirming nothing beyond your dates is following policy rather than expressing an opinion. Our references guide covers that side.
Putting it in the profile
Once they arrive, check that they agree with the rest of your profile — a recommendation calling you a project manager sits oddly beneath a headline claiming product manager. That quiet contradiction is what the profile audit looks for in pasted text, and the consistency guide covers it across both documents.
For plain, non-commercial guidance on references and on approaching people in a job search, the National Careers Service and Purdue OWL are both useful, and LinkedIn's own help page on requesting a recommendation covers the mechanics of the request button itself.
Questions people actually ask
How do I ask for a LinkedIn recommendation?
Ask the person directly before sending the formal request, name the specific project or quality you would like covered, suggest a length, give a soft deadline and make it explicitly comfortable to decline.
How many LinkedIn recommendations should I have?
Four or five specific ones is a complete set. Readers sample two or three, usually the most recent, so a long wall of them adds very little.
Should I write the recommendation myself for them to approve?
No. It removes the effort and the value at the same time, and readers can usually tell. Give a brief — the subject and the angle — and let the words be theirs.
Are LinkedIn recommendations the same as references?
No. A recommendation is public and voluntary; a reference is a private check an employer requests at offer stage, and company policy sometimes limits it to dates and job titles. Someone can happily do one and be unable to do the other.
What if someone writes me a weak recommendation?
You control whether it is displayed, so leave it unpublished and say nothing. Brief more specifically next time, because a vague recommendation is nearly always a vague request coming back to you.
