What a Strong Letter Actually Looks Like
A letter of recommendation for an employee is supposed to answer one simple question: will this person do the job you're hiring them for, and will they be decent to work with? Everything else is decoration. I used to write these all the time when I managed a team, and honestly, most of them were garbage. Generic, padded with praise that meant nothing, signed without anyone actually reading it. It's only when you spend years doing it that you start understanding what the reader actually needs. The core structure is straightforward but most people get it wrong because they focus on the wrong section. Here's how it breaks down in practice.
Letter Of Recommendation For An Employee Example
The format you'll see work best is shorter than people expect. Three to four paragraphs, roughly 400 to 600 words. Anything longer and the reader's attention fragments. Anything shorter and you haven't said enough to be useful. Paragraph one: relationship and context. State who you are, who the employee is, how long you've worked together, and in what capacity. Be specific. "I managed Sarah for three years as her direct supervisor on the product operations team at Meridian Software" carries weight. "I worked with Sarah and she's great" does not. The reader needs to calibrate your credibility before they invest attention in your opinions. Paragraph two: the actual evidence. This is where most letters fall apart. People list responsibilities instead of achievements. "John was responsible for managing client accounts" tells you nothing about how well John did it. Instead: "John took over a portfolio of 40 accounts with a 23% churn rate and brought it down to 7% within fourteen months by restructuring the onboarding process and introducing quarterly business reviews." That's a sentence that actually informs a hiring decision. Specific metrics, specific actions, specific outcomes. If the employee doesn't have hard numbers, describe behavioral evidence. "She was the person other team members came to when a deadline was impossible, and she consistently found a path through by redistributing work and negotiating scope." Concrete examples beat superlatives every time.
Paragraph three: growth and trajectory. Anyone can be good at their current job. What matters more is whether they're getting better. Mention a skill they developed, a project where they took on more responsibility than expected, or a mistake they owned and corrected. I once recommended someone who had missed a critical compliance deadline early in our engagement. Instead of omitting it, I wrote about how he caught his own error, implemented a dual-check system that prevented it from recurring, and ended up training the rest of the team on it. That kind of honesty makes the rest of the letter more credible, not less. Paragraph four: the close. One clear sentence. "I recommend Marcus without reservation" or "I recommend Elena with confidence for roles requiring independent project ownership." Don't hedge. Don't add caveats like "I think she'd be good somewhere, maybe." The person reading this needs a straight answer from someone who should know.
Get the Full Details
Common Mistakes That Undermine the Letter
Here are the patterns I see repeatedly, and they all do the same damage: they make the letter feel templated, which makes the reader discount everything in it. Using superlative language without anchoring it in evidence. "Outstanding," "exceptional," "incredible" — these are empty unless the paragraph before them proves why. A hiring manager has read ten thousand of those words. They mean almost nothing in isolation. Recommending someone for a role they're clearly not suited for just because the person asked nicely. I had a colleague ask me to write a letter recommending him for a senior leadership position after eighteen months as an individual contributor. He'd done his job well. Leadership wasn't part of it. I told him I could write an honest letter about his technical contributions but wouldn't endorse him for management because I genuinely didn't have enough data. He was frustrated, but two years later when he was ready, I wrote the other letter.
Mentioning personality traits without demonstrating them. "She's a team player" is the single most overused sentence in recommendation letters. Show the team-playing through a specific situation if you're going to claim it. Did she cover a sick colleague's sprint? Did she mentor a junior hire who then got promoted? That's the evidence. Writing from a distant perspective. If you supervised someone indirectly through multiple layers of management, say so. A letter from a VP who hasn't interacted with the employee in six months carries less weight than one from a direct manager. Transparency about the relationship strengthens rather than weakens the endorsement.
A Practical Scenario I Faced
One edge case that comes up more often than you'd think involves employees who left under complicated circumstances. A developer on my team had a serious disagreement with our CTO about technical direction. The meeting was tense. He resigned shortly after. Two years later he applied to a company I'd referenced as a contact, and they asked if I'd write a recommendation. The honest answer was that the working relationship had soured before he left, and I couldn't in good faith write a glowing letter. But declining entirely would hurt him professionally. What I did was write a letter focused exclusively on his technical output during the period we worked well together — the first eighteen months out of twenty-four. I noted the positive work and the later disagreement factually, without assigning blame. The hiring team understood the nuance. He got the job. It was the right compromise between honesty and usefulness. This isn't something you want to practice on your first try. Knowing when to write selectively versus declining altogether is a judgment call that takes experience.
What Most People Miss About Tone
The best letters read like they were written by a real person who actually knew the employee. That means occasional informal language, specific details that no template would include, and the occasional admission of a limitation. It also means not writing like a press release. I've noticed that letters with slightly dry, matter-of-fact language tend to land better than ones trying to sound inspiring. You're not selling a product. You're providing a professional assessment. The reader is a peer who understands their own job. Treat them like one. Another thing worth noting: the format you deliver matters more than people realize. A typed letter on company letterhead signed by hand carries different weight than an email body pasted into an application portal. If the employee needs something formal, print it. If it's going into an ATS system, a well-formatted document attached as a PDF works fine. Don't waste time on fancy designs. Clean, readable, professional is sufficient.
When Not to Write One
This gets overlooked. You are not obligated to write a recommendation for everyone who asks. If you didn't work closely with the person, if your interactions were purely transactional, if you genuinely don't have enough positive material to write an honest letter, it is perfectly acceptable to decline. A neutral or lukewarm letter can be worse than no letter at all because it raises questions without providing answers. A polite refusal that offers to stay in touch or help in a different way preserves the relationship without compromising your credibility. Sometimes the best response is: "I don't feel I worked closely enough with them to write a meaningful recommendation. I'm happy to connect you with someone who can speak more directly to their work." That's professional and it's honest.
Quick Reference Template
If you need to write one and want something to adapt rather than starting from scratch, here's the skeleton I fall back on: I have known [Name] for [duration] in my capacity as [title] at [company], where they served as [role]. During that time, I directly oversaw their work on [specific projects or responsibilities], and I am writing to provide my assessment of their professional capabilities. [Name]'s most notable contribution was [specific achievement with measurable outcome]. They approached this by [what they actually did], which resulted in [the impact]. Beyond this example, they consistently demonstrated [second area of strength with brief example].
One area where [Name] has grown noticeably is [skill or responsibility area], particularly through [situation or project]. This kind of development is what distinguishes someone who is merely competent from someone who is building lasting capability. I recommend [Name] for [type of role or opportunity]. They would be a strong addition to any team that values [key quality relevant to the role]. Please feel free to reach out if you need additional detail. The bracketed sections are where the actual work happens. Fill those with specifics and the letter works. Leave them vague and you've produced noise.
