How to Write LinkedIn Recommendations People Actually Believe | Resume Wiz

How to Write LinkedIn Recommendations People Actually Believe

August 28, 2026

The best LinkedIn recommendations follow one formula: a one-line hook, then who you are to this person, then one specific result, then a plain endorsement. I’d hire her again tomorrow." That’s the whole model. Everything below just shows you how to fill in your own version.

Key Takeaways:

  • Recommendations should include specific, measurable results and a clear example that demonstrates the person’s impact within a defined timeframe.
  • The relationship and context must be explicitly stated, with a focus on concrete actions rather than vague adjectives or traits.
  • Length is best kept to two to three short paragraphs, highlighting one standout achievement linked to a demonstrated trait.
  • Tailor recommendations to industry and role by referencing relevant metrics, projects, or situations that prove competence in that field.
  • Be honest and specific; avoid generic praise, overlong texts, or writing about someone with limited interaction, as authenticity and relevance matter most to hiring managers.

Table of Contents

What Makes A LinkedIn Recommendation Worth Reading

A recommendation is the only part of a LinkedIn profile the subject didn’t write. That’s exactly why hiring managers weight it so heavily. Anyone can claim “results driven” in their own summary. Only a former boss, client, or teammate can confirm it happened.

The problem is that most recommendations don’t work that way. They read like a thank-you card: warm, vague, and forgettable. “Jane is a pleasure to work with and always goes above and beyond.” That sentence could describe almost anyone, which means it tells a reader almost nothing. Hiring managers skim past dozens of these a week.

What actually lands is specificity. A recommendation that names the relationship, the timeframe, one concrete moment, and a measurable outcome reads as evidence rather than flattery. According to guidance from HubSpot, generic adjectives dilute credibility, while a single verifiable story with a specific action and outcome does the opposite. That’s the entire difference between a recommendation that gets read twice and one that gets skimmed once.

A handful of credibility cues separate the two:

  • A stated relationship and timeframe (“I managed Alex for two years”) instead of vague familiarity.
  • One concrete example, not a list of traits.
  • A measurable result where possible, even a rough one like “cut our reporting time roughly in half.”
  • A closing line that commits, such as “I’d bring her onto any team I lead.”

Pro Tip: If you can’t remember a specific project, ask the person you’re writing for to send you one bullet point from their resume. It jogs memory faster than staring at their profile photo trying to recall 2021.

On length and voice: two to three short paragraphs, written in first person, beats a long essay every time. Coursera’s guidance on writing LinkedIn recommendations makes the same point: a strong opening line, a clear statement of relationship, and specific contributions matter more than volume. Nobody has ever complained that a recommendation was too short.

LinkedIn Recommendation Examples By Relationship And Role

Below are working examples organized by the relationship you have with the person, plus a few grouped by professional function. Each one follows the hook → relationship → result → close structure, and each comes with a short note on why it works so you can adapt it rather than copy it word for word.

1. Manager writing for a direct report

“Priya turned our worst-performing region into our best in under a year. I managed Priya as a regional sales lead from 2023 to 2026, and she inherited a territory with a high attrition rate among key accounts. She rebuilt the account review process, personally re-engaged twelve at-risk clients, and closed the year with the highest retention of any region on my team. She’s direct, she’s fast, and she doesn’t wait for permission to fix something broken. I’d promote her again without hesitation.”

What makes this work: the retention numbers are specific and the closing line is a real commitment, not a compliment.

Template: “[Name] [achieved specific result] in [timeframe]. I managed [Name] as [your role/title] from [year] to [year], and [he/she/they] [specific challenge they solved]. [Concrete action taken] resulted in [measurable outcome]. [One sentence on working style or trait]. I’d [rehire/promote/recommend] [Name] without hesitation.”

2. Direct report writing for a manager

“The best career advice I ever got was from someone who never once told me what to do. David was my manager for three years at a mid-size agency, and instead of dictating solutions, he asked the one question that made me find my own. When I was stuck on a client escalation in 2024, he sat with me for twenty minutes, asked what outcome the client actually wanted, and let me run the fix myself. That client became our largest account. David makes the people around him better, not just his numbers. Any team would be lucky to have him.”

What makes this work: it avoids the trap of praising a manager only for being “supportive” by pointing to one specific coaching moment with a business outcome attached.

3. Peer writing for a peer

“Jordan is the person you want on a project when the deadline moves up by two weeks. We worked together on the same product team for about eighteen months, and when our launch date got pulled forward suddenly last spring, Jordan reorganized the QA schedule overnight and caught three critical bugs before they hit production. She communicates under pressure better than almost anyone I’ve worked with, and she never makes it about her. I’d want her on my next team in a heartbeat.”

What makes this work: peer recommendations carry more weight when they describe a crunch moment, since peers see the pressure moments a manager often misses.

Template: “[Name] is the person you want when [difficult situation]. We worked together [context/team/duration], and when [specific challenge], [Name] [specific action]. [Result or outcome]. [One trait shown through the story]. I’d want [him/her/them] on my next team.”

4. Client writing for a vendor or freelancer

Marcus worked with our company for four months as an independent UX consultant, and what stood out wasn’t just the design work, it was how clearly he explained tradeoffs to a non-technical founder. He flagged risks before they became problems and hit every deadline without a single scope creep conversation. We’ve since brought him back for two more projects."

What makes this work: “we’ve since brought him back” is a stronger endorsement than any adjective could be, because it’s a repeat-business signal.

5. Freelancer or contractor writing for a client

“Not every client makes freelance work easy, but Elena did, and it showed in the final product. I contracted with Elena’s team for a six-week content project in 2025, and she gave feedback within 24 hours on every single draft, which kept the whole timeline from slipping. She also pushed back when a request didn’t serve the audience, which most clients never do. Projects with her move faster because she respects everyone’s time, including her own.”

What makes this work: flipping the usual direction (a contractor recommending a client) is memorable on its own, and the specific 24-hour turnaround detail proves the point instead of just asserting it.

6. Mentor writing for a mentee

“Two years ago, Sam asked me a question in an elevator that turned into a standing monthly coffee, and I’ve watched them go from analyst to team lead in that time. I’ve mentored Sam informally since 2024, mostly on negotiation and how to speak up in rooms where they were the youngest person present. Sam took every piece of pushback I gave them and came back with a sharper version of the plan every time. That kind of coachability is rare, and it’s exactly why they’ve moved so fast.”

What makes this work: mentor recommendations are more convincing when they describe growth over time rather than a single project, since that’s the mentor’s actual vantage point.

7. Intern or student writing for a professor or supervisor

“Professor Alvarez didn’t just teach the material, she made me defend my reasoning until it actually held up. I was a research assistant in her lab for one academic year, and when my initial data analysis had a flawed assumption baked in, she caught it in a five-minute conversation that saved me weeks of wasted work. She holds students to a standard that feels tough in the moment and turns out to be the best training I’ve had. I’d take another course with her without a second thought.”

What makes this work: naming a specific caught mistake is far more credible than “she’s a great teacher,” and it signals rigor rather than just kindness.

8. Leadership and executive contributions

As her peer on the executive team for two years, I watched her prioritize retention of critical engineers over blanket cuts, a call that paid off within a year when our attrition stayed flat while competitors lost senior staff. She makes hard calls look less dramatic than they are, which is its own kind of leadership skill."

9. Technical contributions

I worked alongside Wei on backend infrastructure for over a year, and what impressed me most wasn’t the fix itself, it was how clearly he documented it so the rest of the team could maintain it without him. That’s the difference between a good engineer and one you can build a team around."

10. Client services and account management

“Losing our biggest account looked inevitable until Tasha took over the relationship. As the account’s internal stakeholder for three years, I watched her rebuild trust with a client who’d already started evaluating competitors, largely by being the first person on our side to actually admit where we’d dropped the ball. She turns damage control into growth, which is a rarer skill than most people realize.”

11. Project leadership across teams

“Coordinating five departments for a product launch usually means something breaks. Under Devon’s leadership, nothing did. I served as a stakeholder on this cross-functional launch for four months, and Devon ran a weekly quarter-hour sync that somehow kept legal, engineering, and marketing all moving on the same timeline. The product launched on the original date, which almost never happens with a team that size.”

12. Remote and distributed team collaboration

“Working across four time zones with Lena never felt like working across four time zones. I collaborated with her on a fully remote team for over a year, and she built a habit of recording short video updates instead of relying on long email threads, which cut our miscommunication almost to zero. Distributed teams live or die on communication discipline, and she has more of it than most people who sit in the same office.”

Quick fill-in template for any role: “[Name] [one-sentence result]. I [worked with/managed/reported to] [Name] as [relationship] for [timeframe], and when [specific challenge or context], [he/she/they] [specific action]. The result: [measurable or observable outcome]. [Trait demonstrated]. [Clear closing endorsement].”

Grouping by role isn’t just for readers who want examples fast. Neal Schaffer’s collection of LinkedIn recommendation examples makes the same case: role-organized examples that include at least one quantifiable result and a clear endorsement are easier to adapt without sounding like a template, precisely because the reader can match their own situation to a close analog instead of starting from a blank page.

The 5-Part Formula For Writing A Recommendation

Every strong recommendation, regardless of relationship or industry, follows roughly the same five moves. Skip a step and the whole thing gets softer.

  1. Craft a knockout opener. Skip “I had the pleasure of working with” entirely. Try instead: “Ana solved a problem that had cost us three clients before she arrived,” or “I’ve managed a lot of engineers, and only one of them rewrote our entire deployment pipeline in her first quarter.” The first sentence decides whether the reader keeps going.

  2. State your relationship and timeframe. One clause is enough: “I managed Sam for two years” or “We worked together on the same account team from 2024 to 2026.” This tells the reader how much weight to give what follows.

  3. Name one concrete action or result, and quantify it if you can. Not “she was great with clients,” but “she saved a $2 million account after the client had already started a competitor RFP.” A rough number (“cut turnaround time nearly in half”) beats no number at all.

  4. Connect the action to the trait it demonstrates. Don’t just say someone is “a great communicator.” Show it: “That kind of transparency under pressure is why clients trust her.” The trait should feel earned by the story, not bolted onto it.

  5. Close with a plain endorsement and an explicit action. “I’d hire her again” or “Any team would be lucky to have him” carries more weight than “highly recommend.” Say what you’d actually do, not just how you feel.

This sequence mirrors what The Muse recommends as a five-step process: hook, relationship, standout trait, example, close. It’s built specifically so you can write a solid recommendation in the time it takes to drink a coffee, not draft a college essay.

Pro Tip: Write the closing line first. Once you know what you’d actually say if a friend asked “should I hire this person,” the rest of the recommendation writes itself backward from there.

Before you post it, run this quick edit pass:

  • Cut every adjective that isn’t attached to a specific example.
  • Replace “responsible for” with an actual verb: built, closed, fixed, launched, cut, doubled.
  • If it’s longer than three paragraphs, something can go.
  • Read the closing line out loud. If it sounds like a form letter, rewrite it as a decision you’d actually make.

Copy-Paste Openers And Short Templates

Sometimes you don’t need a full example, just a sentence to get unstuck. Here are openers sorted by relationship, plus two complete short templates you can fill in during a coffee break.

Openers by relationship:

  • Manager to report: “[Name] turned [specific problem] into [specific win] in [timeframe].”
  • Peer to peer: “[Name] is who you want on a team when [specific pressure situation].”
  • Client to vendor: “We hired [Name] to [task], and [measurable result] followed within [timeframe].”
  • Direct report to manager: “The best [career lesson type] advice I ever got came from [Name], who [specific coaching moment].”
  • Mentor to mentee: “I’ve watched [Name] go from [starting point] to [current point] over [timeframe].”

Short template 1 (single paragraph, fast version):

“[Name] [one-line result]. I worked with [him/her/them] as [relationship] for [timeframe], and [he/she/they] consistently [specific behavior or skill]. I’d [hire/recommend/work with] [Name] again without hesitation.”

Short template 2 (two paragraphs, slightly fuller):

"[Name] [result-driven hook sentence]. As [relationship] for [timeframe], I saw [him/her/them] handle [specific challenge] by [specific action], which led to [measurable outcome].

Beyond the numbers, [Name] [trait shown through behavior, not adjective]. [Closing endorsement with explicit action, e.g., ‘I’d bring them onto any team I build in the future.’]"

Alternative closing lines to swap in:

  • “Any team would be lucky to have [him/her/them].”
  • “I’d work with [Name] again on any project, no question.”
  • “[Name] is the rare hire who makes everyone around them better.”

Swap in role, project, and metric wherever brackets appear, and the template holds up across almost any industry.

Requesting And Publishing A LinkedIn Recommendation

Getting a recommendation written is often the harder half of this process, mostly because people are busy and forget. LinkedIn only lets you request recommendations from first-degree connections, so confirm the connection before you ask, according to Coursera’s guide on the topic.

  1. Send a short, specific request message. For a former manager: “Would you be open to writing a short LinkedIn recommendation about our work on [project]? Happy to send a draft if that’s easier.” For a client: “I’d love a brief recommendation about the [project] results if you have five minutes this week.” For a peer: “Could you write a quick recommendation touching on the [specific project] we worked on together?”

  2. Use LinkedIn’s request flow. Go to the recommender’s profile, click “More,” select “Request a recommendation,” choose your relationship and their position at the time, and add a short personal note.

  3. To write and publish one for someone else, visit their profile, click “More,” select “Recommend,” pick your relationship and their title, write the recommendation, and submit. It posts immediately unless the recipient has “Recommendations” set to require approval before showing publicly.

Offering a short draft dramatically increases both the speed and accuracy of the final version, a point echoed by usability research on the LinkedIn recommendation flow, which also flags that the relationship and position fields are required steps in the request form, not optional extras.

Pro Tip: Ask for a recommendation within two weeks of finishing a project, while the specifics are still fresh. Six months later, even a willing recommender will default to vague praise because the details have faded.

On etiquette: never request from someone you haven’t actually worked with, and always give the recommender an easy out if they’re too busy. On privacy, recipients can hide a recommendation from public view without deleting it, which is useful if the wording needs a revision before it goes live.

What Hiring Managers Actually Notice

Recruiters read hundreds of LinkedIn profiles, and a Resumewiz’s founder, Kim Taynor, spent over ten years inside that process before founding the company. Her take: hiring managers skim past “hardworking” and “team player” without registering them at all. What stops the scroll is a number attached to a name, or a sentence that could only have been written by someone who actually watched the work happen.

The other is filler that a recommender could paste onto anyone’s profile without changing a word.

That distinction matters most for executives and career changers, where a recommendation often has to do the work a reference call used to do. A vague recommendation on a senior profile can actually read as a red flag, since it suggests nobody who worked closely with that person could point to something specific they did.

Common Mistakes That Undercut A Recommendation

The most common mistake is leading with adjectives instead of evidence. “Talented, dedicated, and a joy to work with” tells a reader nothing that a hundred other profiles don’t already say. Every one of those words should get replaced with a sentence describing what the person actually did.

The second mistake is length. A five-paragraph recommendation doesn’t read as thorough, it reads as unedited. Readers skim past anything longer than three short paragraphs, which defeats the purpose of writing one at all.

Third, writing about someone you barely worked with produces a recommendation that sounds hollow no matter how well-intentioned it is. If your only interaction was two meetings, say so honestly, or decline and suggest a better-positioned colleague instead.

Fourth, copying a template word for word without swapping in a real detail is easy to spot. Readers notice generic phrasing like “went above and beyond” attached to no actual example, and it costs the recommendation its credibility instantly.

Finally, writing in third person (“Jane is an excellent worker who always delivers”) instead of first person weakens the whole thing. A recommendation is inherently a personal account. Write it that way: “I watched Jane deliver,” not “Jane is known for delivering.”

Tailoring Recommendations To Different Industries And Roles

A recommendation for a software engineer and one for a sales executive should not read the same way, because the proof of good work looks different in each field.

In technical roles, specificity means naming the system, the bug, or the metric: uptime percentage, load time, lines of legacy code untangled. Vague praise like “a strong engineer” means far less than “rebuilt our CI pipeline so deploys went from 45 minutes to under 10.”

In sales and client-facing roles, the strongest recommendations quantify revenue, retention, or deal size. “Closed our largest enterprise deal in company history” does more work than “excellent relationship builder.”

In creative fields, the proof point often isn’t a number at all. It’s naming the specific campaign, the constraint they worked within, or the client reaction. “Redesigned our brand identity under a two-week deadline after our original agency fell through” tells a much sharper story than “creative visionary.”

For executives and leadership roles, the recommendation should focus on decisions made under ambiguity or pressure. Reviewers at that level expect to see judgment demonstrated, not just output delivered.

For early-career professionals and interns, a lack of big metrics is fine. Lean instead on growth, coachability, and specific moments of initiative, since that’s what a hiring manager at that level is actually screening for.

Keeping It Professional And Genuinely Authentic

A recommendation only works if it sounds like it came from a real person who actually worked with the subject, not a corporate form letter. That means writing the way you’d talk about a colleague at lunch, minus the slang, not the way you’d write a press release.

Authenticity mostly comes down to specificity you couldn’t fake. Anyone can write “detail-oriented.” Almost nobody can invent “caught a $40,000 billing error the week before the invoice went out” unless they were actually there to see it. The more specific the memory, the more trustworthy the recommendation reads, and readers can tell the difference almost instinctively.

Professionalism still matters alongside that honesty. Avoid inside jokes, avoid oversharing personal details unrelated to the work, and keep any criticism embedded gently, if at all. A recommendation isn’t the place to air a mixed opinion. If your honest assessment isn’t strongly positive, the professional move is to decline the request rather than write something lukewarm that damages more than it helps.

When To Write A Recommendation And When To Say No

Not every request deserves a yes, and pretending otherwise does nobody any favors. Before writing, run through a simple check: Do you know their work well enough to be specific? Did you see it firsthand, not secondhand through a manager’s summary? And can you be honest without it turning into faint praise?

If any of those fail, it’s fine to decline. Say something like, “I don’t think I’d write the strongest version of this since we only overlapped briefly, but I’m glad to make an introduction instead,” or offer a skill endorsement in place of a full recommendation. Both are graceful exits that don’t leave the relationship worse off.

If you do write it, resist the urge to inflate. A recommendation that stretches the truth eventually gets tested, often in a reference call where the gap between the written praise and the real memory becomes obvious fast. Kindness and candor aren’t opposites here. The kindest thing you can do for someone is write a recommendation specific enough that it actually helps them get hired.

Kim

Getting Professional Help With Your LinkedIn Profile

Writing a great recommendation for someone else is one thing. Making sure your own profile, resume, and outreach are strong enough to earn those recommendations in the first place is a different project, and it’s the one Resumewiz was built around.

Resume Wiz homepage

Resumewiz offers LinkedIn profile optimization alongside executive resume writing, so the recommendations you collect land on a profile built to convert a hiring manager’s attention into an interview, not just sit there looking polished. The team is led by Kim Taynor, who spent over ten years recruiting before founding the company, which is exactly the vantage point behind the phrasing advice above: what stops a recruiter’s scroll and what gets skimmed past. For professionals who want a second set of eyes on their profile, including whether the recommendations they’ve collected are actually pulling their weight, a profile audit through Resumewiz is the direct next step, and it starts with a look at what’s already on your page today.

Want a recruiter in your corner for your next senior role? Book a free call with Resume Wiz and we will map out your next move together.

Sources

A few outside guides are worth bookmarking alongside this one. HubSpot’s guide to writing LinkedIn recommendations covers the case against generic adjectives in more depth. Coursera’s breakdown is strong on the platform’s connection requirements and UI mechanics. The Muse’s five-minute guide is the fastest read if you need a template right now. Neal Schaffer’s example collection is the deepest well of role-specific samples if the ones above don’t quite match your situation. For readers also polishing a resume alongside their LinkedIn presence, Easy CV’s guide to professional resume templates pairs well with this process, and Prosp-Her’s networking guide offers useful etiquette notes for requesting recommendations without feeling pushy.

linkedin recommendations exampleslinkedin recommendation tipsbest practices for recommendationshow to write linkedin recommendationslinkedin recommendation templatesexamples of professional recommendationslinkedin testimonial exampleswriting effective recommendationslinkedin reference examplescrafting recommendations on linkedin
Back to Blog