Coworker to Coworker Recommendation Letter

The conventional reference structure in US hiring leans heavily on supervisor letters because supervisors are presumed to have the most evaluative authority and the broadest exposure to the candidate's work. A peer's view is structurally narrower (peers do not assess each other formally, peers do not have access to the candidate's full performance evidence, peers are not the people who decided to promote or compensate the candidate over time). Hiring managers reading peer letters in conventional contexts often discount them as evidence relative to supervisor letters.

The peer letter also carries an awkward signal in conventional hiring: if the candidate is offering a peer reference instead of a supervisor reference, the hiring manager will wonder why. Sometimes the reason is benign (confidentiality of the current job search, supervisor unavailability, recent supervisor change), but the wondering itself imposes a cost on the candidate. The candidate who submits a peer reference should usually accompany it with a brief explanation of why a supervisor reference is not in the pack, so the hiring manager does not have to guess.

The exception is 360-style hiring processes, increasingly common in technology, consulting, and senior-leadership recruiting, where the hiring loop explicitly invites references across the candidate's working relationships (supervisor, direct report, peer, cross-functional partner). In those contexts the peer letter is expected and is read on equal footing with the others.

The peer letter should not try to mirror what a supervisor letter would say; it should focus on the dimensions the peer is uniquely positioned to address. Three categories of evidence are stronger from a peer than from a supervisor. First, conduct in horizontal collaboration: how the candidate operates when there is no authority gradient, when they have to influence rather than direct, when they have to share credit on a shared deliverable. Supervisors see this only through the filter of the candidate's reports back; peers see it directly.

Second, technical or craft-level peer assessment. A peer who does the same kind of work as the candidate can speak to the quality of the candidate's work in a way the supervisor (who may not have the same depth of craft) cannot. A senior engineer writing about another senior engineer's code, a senior consultant writing about another senior consultant's case work, a senior designer writing about another senior designer's portfolio: these letters carry expert-witness weight that a supervisor letter often cannot match.

Third, cross-functional perception: how the candidate is perceived by the parts of the organisation outside the candidate's reporting line. A peer letter from a partner function (sales describing engineering, design describing product, legal describing operations) provides evidence about how the candidate's work lands outside their immediate team, which is often the more predictive evidence for senior roles.

When a current coworker is asked for a reference for a colleague's outside job search, two confidentiality issues attach. The first is the candidate's privacy: the writer should not discuss the candidate's job search within the company, should not mention it to mutual colleagues, and should treat the existence of the search as a confidential disclosure from the candidate. The second is the company's interest: the writer should not share information about the company's strategy, projects, or commercial position that the candidate or the prospective employer could exploit.

The first issue is mostly a matter of social discretion; there is no general legal duty for the writer to disclose a peer's job search to the employer. The second issue is potentially a contractual matter; some employment agreements include confidentiality, non-disparagement, or cooperation clauses that constrain what the writer can say in a reference for an outside job. The writer should review their own employment agreement before writing, particularly if the prospective employer is a direct competitor.

A clean practice for current-coworker references: write only about the candidate's individual capabilities and contributions, do not reference any confidential company information, and decline the request if writing honestly would require crossing one of those lines. The dedicated how to decline guide covers the language for graceful declines.

Senior-leadership recruiting, particularly in consulting and technology, has moved toward 360-style hiring loops that explicitly request a peer reference alongside the supervisor and direct-report references. The pattern is most visible in partner-track promotions at the major management-consulting firms, in senior-engineering-leader hiring at large technology companies, and in some senior-leadership searches run by executive-recruiting firms.

When the loop explicitly asks for a peer reference, the candidate should choose a peer who has seen them in cross-functional collaboration and who can speak credibly to the dimensions the loop is selecting on. A peer chosen primarily because they like the candidate, without a substantive collaboration history to draw on, produces a thin letter that adds little. A peer chosen primarily because they will be candid (even if the candour includes growth areas) often produces the letter that lands strongest with the hiring committee, because the committee reads it as honest rather than performative.

The candidate's brief to the peer reference matters. The candidate should provide the peer with the role description, a brief on the dimensions the hiring committee is selecting on, and a list of two or three specific collaborations the candidate hopes the peer will draw on. Without that brief, the peer letter often defaults to generic peer praise that is consistent with the role but does not specifically advance the candidacy.

The strongest peer letters acknowledge the boundaries of the peer vantage point and stay inside them. The writer does not pretend to be able to assess the candidate's overall performance against the company's expectations (that is the supervisor's role); the writer does not pretend to be able to assess the candidate's people-management capability if the writer has not been managed by them (that is the direct-report's role); the writer does not pretend to be able to assess the candidate's strategic judgement at the senior level if the writer has not been in the strategic rooms with them.

What the peer can do credibly is speak to the slice of the candidate's behaviour the peer has directly seen, with specific evidence, and let the hiring manager combine that evidence with the rest of the reference pack. A peer letter that says \"I worked with [Candidate] on these three specific projects over the past two years; here is what I saw; here is what I think it means for your role\" is much stronger than a peer letter that tries to make the same evaluative claims a supervisor letter would make from a thinner evidence base.

The honest, bounded peer letter is also harder to fake, which is part of what makes it credible. Hiring managers who have read many peer references recognise the difference between a peer letter that stays inside its evidence base and a peer letter that strains to imitate the supervisor letter; the former is taken seriously, the latter is discounted.