Ask a Headhunter: Should I Ever Hire My Friend?

The email sat in drafts for three days. Not because the manager - call her Priya - didn't know what she wanted to say, but because she knew exactly what she wanted to say and wasn't sure she should say it. Her friend of eight years, Dom, had just been made redundant. He had the background. He had the instincts. The mid-level operations role she was trying to fill had been open for two months. She sent the email on a Tuesday afternoon: "Hey - I know this isn't ideal timing but I think you'd be great for the ops role. Want to grab coffee and talk about it?"

This scenario scores 3 out of 10. Here is where the seven points went.

The Specimen

This is a composite based on patterns we see. No real person or company is named.

Priya is a head of operations at a mid-size logistics firm. She has managed teams before, but this is her first time filling a role at this level. Dom is her friend from university - they've been close through moves, breakups, career changes, the works. He was just let go from a senior coordinator role at a company that folded. The position Priya is filling is Operations Manager, mid-level, reporting directly to her.

Dom applies informally, through Priya's message. They meet for coffee. The conversation is warm and wide-ranging: his redundancy, her team's struggles, whether the role could work.

They don't talk about salary. They don't talk about what happens if it doesn't work out. They don't talk about how Priya will handle a performance conversation if she needs to. Three weeks later, Dom starts.

The Teardown, Line by Line

The Coffee That Replaced the Interview

What happened: Priya invited Dom to talk through the role over coffee. The conversation covered his experience in broad strokes and moved quickly into shared history - mutual contacts, the company that folded, what the team was like.

What Dom heard: "This is already a yes. We're just working out the details." The casual setting signalled that the formal process was a formality at best. He didn't prepare. He didn't bring questions about the role's harder edges. He felt the job was his because of trust built over years, not because of anything he said at that table.

The fix: meet for coffee if you want, but follow it with a structured conversation - either a panel interview or, at minimum, a direct conversation that includes a brief and specific questions about how Dom would handle the parts of the role that will actually be hard. The warmth of the friendship is not a substitute for knowing whether he can do the job under pressure.

The Salary They Didn't Discuss

What happened: Priya assumed Dom would be flexible given his circumstances. Dom assumed Priya would offer something fair given the relationship. Neither said any of this out loud. The offer came via email, the number lower than Dom expected.

What Dom heard: "She thinks I'm desperate. She doesn't see me as a peer." The number felt like a signal about status, not market rate. He accepted, but with a quiet resentment that sat just below the surface of their first few weeks working together.

The fix: name the budget early - ideally in the first real conversation about the role. Something like: "The band for this role is X to Y. I want to be upfront because I don't want money to be the thing that gets weird between us." This is not an awkward conversation. It is the conversation that prevents six months of low-grade friction. First-time hirers navigating this kind of tension will recognise many of these dynamics in how poor candidate communication quietly costs you the people you most want to hire.

The Feedback Conversation That Never Quite Happened

What happened: six weeks in, Dom's reporting was consistently late. Priya mentioned it once, lightly, in a one-on-one - something between a joke and a nudge. Dom laughed it off. The reporting stayed late.

What Dom heard: "She's not really going to push me on this. We're friends." Priya's softened delivery landed as optional feedback, not a performance standard. He didn't change because the signal wasn't clear enough to require change.

What Priya felt: trapped. She didn't want to damage the friendship. She didn't want to be the manager who comes down hard on someone who'd just gone through a difficult year.

So she said less than she meant, and the problem compounded. The fix: separate the voices in the room. Before Dom started, Priya needed one direct conversation: "When I give you feedback as your manager, I need you to receive it as your manager giving it - not as your friend being critical. Can we agree on that?" Naming the dual role before it creates a problem is the only way to defuse it. The same dynamic - where the signals managers send are read very differently by the people receiving them - is at the heart of why your best employee can quit without warning.

The Scorecard

Five criteria, scored 0-2. Zero means the approach actively causes harm. One means it's barely adequate. Two means it's handled well.

1. Clarity on role expectations - 1. The role was described, but its harder requirements (deadlines, reporting, team dynamics) were never made explicit. Adequate at best.

2. Separation of friendship and management - 0. This conversation never happened. Priya moved Dom from friend to direct report without naming the shift. Harmful, because it left Dom reading friendship signals in a management relationship.

3. Transparency on compensation - 1. A number was shared, eventually, but the budget was never discussed openly before the offer. The silence created a resentment that didn't need to exist.

4. Peer team dynamics - 1. The rest of the team was not briefed on how Dom was hired. A few people noticed the friendship and drew their own conclusions. A brief, honest explanation would have taken ten minutes.

5. Exit plan if it fails - 0. Not mentioned. Not considered. If this role ends badly, neither Priya nor Dom has any frame for what happens next - to the work, or to the friendship. The same absence of planning that causes hiring processes to stall is explored in what the benchmarks reveal about where time-to-hire days actually disappear.

Total: 3 out of 10. Band: repair now.

The Rewrite

This is what Priya should have said, either at the start of the coffee conversation or in a follow-up note before Dom accepted.

Hey Dom,

I want to be straight with you about something before we go further, because I value our friendship enough not to be vague about this.

The Operations Manager role is a real job with real accountability attached to it. The band is £42,000-£47,000 depending on what you bring. Reporting lines are direct - you'd report to me, and I'd be the one managing your performance reviews. That means if something isn't working, I have to tell you. Not as your friend. As your manager.

I've thought about whether this is a good idea. I think it can be, but only if we're both honest about what it requires. The role needs someone who can own the weekly reporting cycle without reminders, coordinate between three teams who don't always agree, and flag problems early instead of hoping they resolve. Those aren't optional parts of it.

If you're interested, I'd like us to have one proper conversation about the role - not just a catch-up. I'll ask you some direct questions about how you'd handle the hard parts. You should ask me the same.

And one more thing: if it doesn't work out, I want us to agree now that we'll handle it like adults who care about each other. That means an honest conversation, not a slow fade. The friendship matters more to me than keeping things comfortable in the short term.

If that all sounds reasonable, let's talk properly. If any