Should You Hire a Friend as Your First Employee? The Trust Is Real. The Evaluation Usually Isn’t.

Why Your First Hire Is So Often Someone You Know

For a small company, the network is not a lazy shortcut. It is often the best channel you have. Apec’s yearly survey of executive hiring practices in France keeps listing the contact network, professional and personal, alongside the job ad as one of the channels that most often produces the person actually hired, and smaller companies lean on it more than large ones do.

The reasons are sound. A company nobody has heard of struggles to attract strangers, a problem we look at in what to do when barely anyone qualified applies. A person you know arrives with context no CV can carry. And someone who already believes in you says yes faster, often for less than the market would ask.

So the real question is rarely whether to look in your network. It is what happens once the person you know becomes the obvious candidate. That is usually the moment the hiring process stops being a process.

What Trust Tells You, and What It Can’t

Trust answers real questions. Will this person be honest with me? Will they stay when things get hard? Do we work well together under pressure? In a team of three, those matter a great deal. But they are not the questions the job asks. The job asks whether this person can do this specific work, at this level, in this company, and friendship has almost never shown you that.

Think about what you have actually seen. Perhaps you worked together years ago, in a different role, at a different company, under a manager who was not you. Perhaps you have never seen them work at all and only heard them talk about it over dinner. You know the person well. You know their work in this role barely, if at all.

Research from a neighbouring field points the same way. Studying venture capital firms, Harvard economist Paul Gompers and his co-authors found in The Cost of Friendship that investors who share a background are more likely to team up, and that this affinity lowers the odds of the investment succeeding, an effect the authors trace mainly to weaker decisions made together after the deal is done. Hiring is not venture capital, but the mechanism carries over: closeness makes the hard conversation less likely to happen, both before the decision and after it.

The Steps a Warm Hire Quietly Skips

None of this comes from carelessness. It happens because every step of a normal hiring process feels awkward, even slightly insulting, when the candidate is a friend. So each step slips away on its own, and nobody decides to drop it.

• No written role. You “both know what the job is,” so nobody writes down what success looks like after ninety days. Months later, you each remember a different job. Our guide to writing your first job description starts from exactly this mandate.
• No comparison. There is one candidate, so “good enough” is measured against nothing.
• A catch-up instead of an interview. Asking a friend to walk you through how they solved a hard problem feels strange, so you talk about old times instead. We cover what a real conversation should test in how to run your first interview as a founder.
• Vague terms. Salary, title, equity and start date get settled over coffee, generously or awkwardly, and rarely in writing.
• No agreed way out. Nobody discusses what happens if it does not work, because saying it out loud feels like predicting failure.

The last row is the one founders underestimate. When a stranger hire fails, you lose time and money. When a friend hire fails, you lose the same, plus a relationship, and the fear of that second loss makes you wait longer before acting. The probation period exists for this moment, but as we explain in why the probation period is not a safety net, it only protects you if you are willing to use it, and that is much harder with someone you will see at a birthday next month.

How to Hire Someone You Know Without Skipping the Evaluation

The fix is not suspicion. It is putting back the steps the friendship removed, and telling the candidate up front that you are doing it for both of your sakes. Most good people respect that. Someone who is offended by a fair process is telling you something useful too.

Write the role before you think about the person

Define the outcomes you need in the first ninety days, the level of autonomy the role requires, and the two or three skills it genuinely runs on. If you cannot write it without picturing your friend in the seat, write it as if they had already said no. The role should exist on its own before anyone is measured against it.

Put at least two other people in the pipeline

Comparison is the only way to know whether the person you know is the best you can get or simply the first one you thought of. Two or three outside candidates are enough. This also protects your friend: if they get the job, they got it on merit, and everyone, including them and your future team, knows it.

Ask everyone the same questions, and test the real work

Use the same questions for every candidate, your friend included, and add a short, paid piece of real work that looks like the job. It feels formal with someone you know, which is precisely why it helps: it gives you evidence where you would otherwise have only affection. If the role sits outside your own skills, borrow someone who knows the field to evaluate alongside you, as we describe in hiring for a role you could never judge yourself.

Have the hard conversation before the offer

Agree in writing on the role, the pay, the title and what happens at the end of the probation period if either of you feels it is not working. Then say the sentence out loud: “Our friendship matters more to me than this job, so let’s agree now on how we handle it if it doesn’t work.” It is a two-minute conversation at the start. At month three, it is the conversation nobody manages to have.

Underneath all four steps is one idea: decide the criteria before you meet anyone, then score every candidate against them at every step, so a familiar face cannot outweigh the evidence. That is why we built Kynto to score candidates against the criteria you define across the whole process, with a person reading the reasoning behind every score. It keeps the comparison honest even when one of the candidates is someone you have known for ten years.

Key Takeaways

• Looking in your own network for a first hire is normal and often sensible. The risk is not the channel; it is that a warm candidate quietly removes the evaluation.
• Trust tells you about loyalty and honesty, not about whether this person can do this job at this level. Closeness also makes the hard conversations less likely, before and after the hire.
• Put the steps back: a written role, outside candidates to compare against, the same questions and a real work sample for everyone, and written terms, including how you part ways if it does not work.

FAQ

Is it a bad idea to hire a friend as my first employee?

Not in itself. Many strong first hires come from a founder’s circle. It becomes a bad idea when the friendship replaces the evaluation: no written role, no other candidates, no real test of the work. Hire a friend the way you would hire a stranger, and the friendship becomes an advantage rather than a blind spot.

How do I tell a friend they didn’t get the job?

Early, directly, and with the reason tied to the role rather than to them: another candidate matched what the job needs right now more closely. It is far easier if you said at the start that you were running a fair process with other candidates. A clear no at the offer stage costs much less than an unclear yes that ends badly six months later.

What should I put in writing before a friend starts?

The same things you would write for anyone: the role and its expected outcomes, salary, title, any equity, start date and the probation period. Add one more, informally: how you will both handle it if the job is not working, and that the friendship comes first.