Writing A Recommendation That Actually Helps Someone
I spent years doing performance reviews and recommendation letters at a mid-size SaaS company. Most of them were fine, but a few made real difference in someone's career. The ones that worked had one thing in common: they were specific without being gushing. The ones that didn't work were either too vague or tried too hard. A coworker recommendation is different from a manager letter. You're not evaluating someone's report; you're testifying about what it's like to work alongside them. Hiring managers know this, which is why they often read these more carefully than they admit. They're looking for evidence of collaboration, not just individual brilliance. The biggest mistake I saw was people writing about what the coworker did rather than how they worked. Anyone can list achievements. What matters is describing the pattern of behavior behind those achievements. Did they stay calm when the API broke at 2am? Did they volunteer to fix the documentation even though it wasn't their bug? These details show character better than any adjective.
How To Structure It Without Sounding Generic
Start with context. Tell the reader how long you worked together and in what capacity. One sentence is enough. "I worked with Sarah for three years on the payments team, primarily as her peer on the checkout integration project." That's it. Then get into the meat. The body should have two or three concrete examples. I recommend picking situations where your coworker's behavior was visible to others, not just you. If they made your life easier, that matters. But if other teams noticed too, that's stronger evidence. A good example from my experience: I once recommended a developer who kept detailed handoff docs when leaving projects. That wasn't in his job description, but three different teams wrote to us saying it saved them days of confusion. End with a clear statement of endorsement. Not "I think she would be good" but "I recommend her without reservation for any role requiring X and Y." Be specific about what kind of team or role you think fits. This helps the hiring manager place the person.
Specific Phrases That Work And Ones That Don't
Avoid "hard worker," "team player," and "go-getter." These appear in roughly 90 percent of recommendations and tell the reader nothing. Replace them with observed behavior. Instead of "she's a great communicator," write "she rewrote our onboarding doc and then ran a 30-minute session for the next three cohorts who joined." The second version proves the claim. Don't overstate things. I once saw a recommendation claim a coworker was "the best engineer we've ever had." The hiring manager assumed either the writer didn't know better engineers, or they were exaggerating. Both interpretations hurt the candidate. Stick to honest superlatives: "one of the top three," "better than most seniors I've worked with," "the person I'd want in a crisis." These are defensible and memorable.
Get the Full Details
When You Shouldn't Write One
Sometimes the answer is no. If you barely knew the person, if you had conflicts, if you can't think of a specific example, don't write it. A weak letter is worse than no letter. I learned this the hard way when I recommended someone I barely worked with and the hiring manager called me to ask follow-up questions I couldn't answer. The candidate ended up looking suspicious by association. If you must decline, be direct. "I haven't worked closely enough with [name] to write a meaningful recommendation. You might ask [colleague] instead, who collaborated with them on the migration project." This actually helps more than a generic positive letter would.
The Email vs PDF Question
Send it as email text when possible. Attachments get filtered, lost, or ignored. A well-formatted email body is easier to read on mobile, searchable, and harder to misplace. If the company requires a formal letter on letterhead, that's fine, but the email version should contain the same content. Use a subject line that helps the recipient. "Recommendation for Alex Chen - Senior Backend Engineer" is better than just "Reference." This small detail saves time for both the candidate and the hiring team.
Timing And Follow-Up
Write it within a week of asking. If you wait longer, the details fade and you'll either write something generic or ask the person to remind you about their accomplishments. That puts the burden back on them, which is unpleasant for everyone. If you forget and realize days later, apologize briefly and send it. "Apologies for the delay. Here's the recommendation for Marcus." No need to over-explain. People understand life gets busy.
Legal And Policy Considerations
Check your company's policy on references. Some organizations only allow HR to provide dates of employment and title. Others permit peer recommendations as long as they're factual and non-defamatory. When in doubt, stick to what you personally observed and avoid speculation about salary, promotions, or internal disputes. Never write something you wouldn't say in person. If you're hesitant to tell the hiring manager directly, don't put it in writing. Documentation persists longer than memory, and candidates sometimes share letters with colleagues or even post them publicly.
A Real Edge Case I Encountered
Once I recommended a coworker who had been fired from a previous role for cause. The hiring manager asked me directly about it. I said: "I don't know the circumstances of their departure from their last company, but in my team they consistently met deadlines, helped juniors debug issues, and never blamed others for mistakes." This was true and relevant. I didn't endorse their entire career history; I endorsed what I could verify. The candidate got the job. They told me later that my honesty about what I didn't know actually helped more than blind praise would have. Transparency builds trust with hiring managers, even when the information isn't entirely positive. If you encounter this situation and can't in good faith recommend the person, decline. "I worked with them for six months but didn't see enough of their work to write a substantive letter. I'd suggest asking someone from their earlier tenure instead." This protects everyone involved.
What Happens After You Send It
You usually won't hear back. That's normal. If the candidate asks for an update, you can share whether the hiring manager contacted you, but details are often confidential. A simple "They reached out and asked a few questions. Everything went well on my end" is sufficient. Keep a copy for your records. Not because you expect trouble, but because three years later you might need to recall exactly what you wrote when someone asks. I once had to verify a date I mentioned in a letter and realized I'd written it incorrectly. Having the original helped me correct the record quickly. The process usually takes 20 to 40 minutes for someone you know well. Longer if you're struggling to find examples or if the person has changed jobs frequently and you need to reconstruct timelines. Budget accordingly and ask early so you're not rushed.
Alternative When You Can't Write One
If you genuinely can't write a recommendation but still want to help, offer a different kind of support. Introduce the person to someone in your network who might be a better fit. Review their LinkedIn profile and leave a detailed endorsement there. These alternatives are often more useful than a weak letter. Networking introductions have a higher success rate than I initially expected. A warm email from you to a hiring manager saying "I've worked with this person and think they'd fit your team" carries more weight than any structured letter. Use this when appropriate.
Final Thoughts On The Process
Writing a coworker recommendation is a small act with outsized impact. Most people remember who advocated for them years later. A few remember the ones who didn't. Neither outcome is complicated; it's just a matter of showing up when asked and being honest about what you observed. The method isn't difficult. Context, examples, endorsement. The execution matters more than the structure. Write what you actually saw, skip the filler, and send it promptly. Everything else is noise.
