Sample Reference Letter For Coworker

How to Actually Write Something Useful

Most people wing reference letters. They fire off a quick email from memory, slap on some generic adjectives, and hit send. The result is usually forgettable, and sometimes actively harmful to both the writer and the person being referenced. I learned this the hard way a few years back when I wrote a positive letter for a direct report who later turned out to have been quietly undermining our team for months. HR came to me asking clarifying questions because the letter was so glowing it looked performative. That was my introduction to the idea that a reference letter carries legal and professional weight you don't want to ignore. Writing a solid one doesn't take hours. It takes a few minutes of honest note-taking followed by a clean structure. Here's the approach that actually works.

Sample Reference Letter For Coworker

Start by pulling specifics before you write anything. Look at project timelines, performance reviews, Slack threads, or whatever documentation exists. Generic praise like "hardworking" and "great team player" means almost nothing to anyone reading these letters. Hiring managers see them constantly. They scan for verifiable details — dates, project names, quantified outcomes, specific competencies. A letter that mentions "led migration of our legacy CRM to Salesforce over a six-month period, reducing support ticket resolution time by 35%" tells you something real about what that person actually did.

The structure is straightforward. Opening paragraph establishes your relationship and duration of working together. Body paragraphs cover specific contributions, work style, and areas of impact. Closing paragraph gives an unambiguous recommendation. Keep it to one page. Anything longer suggests either the person is padding or the writer doesn't know how to prioritize. Here's a template you can adapt. It's deliberately sparse because the specifics in the bracketed sections are what matter: I worked closely with [Name] at [Company] from [Start Date] to [End Date], primarily on [specific project or functional area]. During that time, they held the role of [Title] and reported to [Manager Name or Team Structure].

[Name]'s most notable contribution was [specific achievement with measurable outcome]. They approached this by [brief description of method or process], which resulted in [quantified result]. Beyond that project, they consistently demonstrated strength in [2-3 specific skills], which was evident when [concrete example].

In terms of day-to-day work style, [Name] is [professional characterization supported by a specific behavior]. They communicate clearly under pressure and handle feedback constructively. One thing worth noting is their ability to [unique or valuable trait with brief example].

I recommend [Name] without reservation for [type of role or opportunity]. They would be an asset to any team that values [specific quality]. Please feel free to contact me at [email] or [phone] if you need additional context.

This format works across industries because it forces specificity. Anyone who reads it gets a picture of what the person actually does, not a list of compliments. There's an edge case that comes up more often than you'd think — and it's worth addressing directly. You are asked to write a reference for a coworker you had a genuinely difficult relationship with. This happens. Maybe they were competent but toxic. Maybe they were friendly but delivered subpar work. Maybe both. A bad relationship doesn't mean you write a negative letter. It means you write an honest one that stays within professional bounds. If the person was reliable but interpersonal skills were a problem, state that. "Jane consistently met her deadlines and produced technically sound work. Her communication style with cross-functional partners could be improved, and I would recommend roles with clear documentation standards and structured collaboration processes." That's truthful, protective for everyone involved, and still useful. What you should never do is write a glowing letter you don't mean. It reflects poorly on your judgment when the next employer finds out. Another nuance most people miss: the letter's credibility depends heavily on the writer's own positioning. A reference from a peer carries different weight than one from a direct manager or someone who supervised the person's work. If you're writing as a peer rather than a supervisor, make that explicit. "As a senior developer who collaborated with Alex across three major projects over two years" sets expectations about what perspective you're bringing. Hiring teams understand the difference between a manager's assessment of performance and a peer's assessment of collaboration. Don't pretend otherwise.

You also need to think about what kind of reference this is. A letter for a government position, a private-sector role, and a graduate program all have different expectations. Government applications often require specific language about eligibility and scope of responsibility. Academic programs want evidence of research capability and intellectual curiosity. Private sector roles typically care most about deliverables and teamwork. Adjust the emphasis accordingly. The facts don't change but how you frame them does. There's a practical bottleneck worth mentioning. Some people struggle to write these because they genuinely don't have strong things to say. That's fine. In those cases, you can write a shorter, more restrained letter that focuses on what you can credibly endorse. "I worked with Mark for eight months on the Q3 infrastructure project. He was punctual, followed through on assigned tasks, and maintained good relationships with the QA team. I recommend him for roles requiring dependable execution." That's a legitimate reference. It's just honest about the depth and scope of your observation. Inflating it to fill space helps nobody. Send the draft to the person before you send it to anyone else. This isn't just politeness — it's verification. They might catch a factual error, or they might ask you to emphasize a particular project you overlooked. It also gives them the chance to request changes if they feel something is mischaracterized. A reference letter that goes out with incorrect dates or wrong project names loses credibility immediately, and you don't want to be the person who provided inaccurate information about a coworker.

The whole process from gathering facts to sending the final version usually takes 20 to 40 minutes for someone who knows the person well. If it's taking longer than an hour, you're probably overthinking or gathering too much detail. Cut it down. Recipients don't read every word. They scan for names, dates, outcomes, and a clear recommendation. Make sure those elements are easy to find.