---
title: "The nuances of hiring at each stage — what changes between the 5th employee and the 22nd to 25th"
description: "The nuances of hiring at each stage reveal a genuine shift in mechanics, stakes, and failure modes as you move from your fifth employee to your twenty-fifth."
author: "Marcus Telle"
category: "Hiring Playbooks"
date: 2026-07-25T09:13:38.705Z
canonical: "https://theartofpeople.io/blog/nuances-of-hiring-at-each-stage-5th-to-25th-employee"
---

# The nuances of hiring at each stage — what changes between the 5th employee and the 22nd to 25th

![Close-up of two interlocking geometric rings, one small and one large, with their overlapping zone in a warmer stone tone.](https://hsppuvezyxmkpzkgfkho.supabase.co/storage/v1/object/public/media/enrichment/9463a8df-8756-4bbf-9116-1c81813b66ee/38f97b23-1357-4ff5-a0ac-2d7e244b657a/7db214b1-70d8-4f91-b3b6-6e369a6a1b6b.png)

> The nuances of hiring at each stage reveal a genuine shift in mechanics, stakes, and failure modes as you move from your fifth employee to your twenty-fifth.

The fifth hire and the twenty-third hire are not the same kind of decision. They share a name - recruitment - but the mechanics, the stakes, and the failure modes are genuinely different. Most founders don't realise this until they've already made a [costly mistake somewhere in the middle of that range](/blog/why-ceos-call-me-after-a-bad-hire-never-before-87l3), usually around hire fifteen or sixteen, [when the old informal approach starts producing bad outcomes](/blog/how-to-read-hiring-market-signals-before-they-hit-the-headlines-7tnz) but the new structured approach hasn't been built yet.

This piece maps that transition. Not as a tidy checklist, but as a cause-and-effect chain - because understanding *why* the process changes helps you time the shift correctly, rather than clinging to [founder intuition two stages too long](/blog/why-the-best-talent-strategies-take-years-not-quarters-wvwt).

## How hiring changes as you grow from 5 to 25 employees

  ![](https://hsppuvezyxmkpzkgfkho.supabase.co/storage/v1/object/public/media/enrichment/9463a8df-8756-4bbf-9116-1c81813b66ee/38f97b23-1357-4ff5-a0ac-2d7e244b657a/a7acf069-2dc1-4993-a02b-06fb5d07e7c1.png)
  Two concentric radial grids side by side - the left one small with three warm nodes connected by direct lines to a central silhouette, the right one large with thirty nodes fanning outward through layered geometric rings, most nodes unconnected, a few highlighted, in Sacred Geometry Flat

At five employees, hiring is almost entirely founder-led and largely instinctive. You identify a need on Monday, have a long conversation over coffee by Wednesday, and make an offer by the weekend. The process is fast because the organisation is simple: you know everyone in the room, you know what needs doing, and you have a good enough read on the person in front of you to make a call.

By employee twenty-three, that same informal approach will get you burned. The hiring manager for that role might not be you. The person they hire will report to someone who didn't interview them. Their onboarding will be handled by a team that didn't exist a year ago. If the role wasn't written down clearly, if the values were never articulated, if the process had no structure, you'll feel it - in a slow ramp, in friction with their manager, in a resignation six months later that you saw coming but couldn't quite explain.

The pain point that forces change is usually a specific hire that went sideways. At five people, you might hire someone brilliant but quietly misaligned - they're sharp, they ship, but they don't collaborate the way you need. You absorb it. You work around it. At twenty-two people, the same mistake doesn't stay contained. A misaligned senior hire at that stage influences three or four other people, shapes decisions you aren't part of, and makes it harder to bring in the right people after them.

## Sourcing and candidate discovery at each stage

At five employees, sourcing is personal. A co-founder texts someone they worked with at their last company. A friend of a friend knows a designer who's looking. You post something brief on LinkedIn and three former colleagues send it to people they trust. You end up with three or four candidates, all of them warm, all arriving with some context about who you are and what you're building.

That approach works because three candidates is enough when you're vetting them as the founder with full knowledge of the role, the team, and the culture. But at twenty-two employees, you need thirty candidates to find the right three to interview seriously. That requires a written job spec - not because writing is inherently valuable, but because you can no longer relay the role verbally to every hiring manager, recruiter, or sourcing partner involved. The spec becomes the single source of truth that travels without you.

The causal link here is direct: as sourcing widens, vetting must tighten. When you sourced warm candidates through your network, the informal conversation was enough because you already trusted the signal. When you're sourcing from job boards or recruiter databases, you're working with strangers. The screening layer that your network used to provide invisibly now has to be built explicitly into your process.

## Vetting and interview rigour - what you can and can't skip

Early-stage vetting is loose by design. One long conversation with the founder, maybe a half-day working session, maybe a call with a future colleague. You're testing two things simultaneously - capability and fit - and you're doing it with the person who has the most context about both. That compression works when the organisation is small enough that you're the right person to be making that assessment.

At twenty-two to twenty-five employees, vetting is structured out of necessity. You now have multiple interviewers: a hiring manager, a peer from the relevant team, sometimes someone from a cross-functional area. You have a skills assessment or a work sample. You do reference checks. You have a debrief where people share scores, not just impressions. The process takes longer and feels heavier, and there's a temptation to shortcut it when you're under pressure to fill a role.

The mechanism that makes rigour necessary is simple: the cost of a hiring mistake compounds as you grow. At five people, a bad hire is visible and painful and expensive in time, but you can manage it relatively quickly. At twenty-five, a bad hire into a senior role takes longer to recognise, longer to address, and has already shaped team dynamics and decisions before you've fully understood the problem. The upfront investment in structured vetting is directly proportional to how hard it is to undo a mistake on the other side.

## Role clarity and job descriptions - why they matter more as you scale

At five employees, roles are beautifully fluid. You hire someone as head of operations and within a month they're handling customer support tickets, giving product feedback in every meeting, and doing the admin that nobody claimed. There's no job description because the role doesn't exist yet in a fixed form - it's being invented around the person who's doing it, and that's often the point.

By twenty-two employees, that same fluidity becomes a liability. You now have a manager who didn't hire the person and needs to know what the role is supposed to encompass. You have multiple teams whose work overlaps, and without written boundaries, things fall through the gaps or get duplicated in ways that create friction. A new hire who doesn't know where their role ends and the next person's begins will either overreach or undershoot, and either way they'll frustrate someone.

The causal chain runs in both directions. Vague roles lead to unclear expectations, which lead to a new hire who struggles, a manager who grows frustrated, and a retention risk that looks like a people problem but was actually a process problem from day one. The reverse is equally reliable: a clear role spec means the candidate understood what they were walking into, the manager has a shared reference point for evaluating performance, and the new hire has something concrete to orient around in the first ninety days.

## Onboarding and integration - from founder-led to systematic

Early onboarding is personal in a way that's genuinely hard to replicate. The founder pairs with the new hire for their first week. They walk them through the product, introduce them to everyone by name, explain the story behind decisions that might otherwise seem arbitrary. The new hire absorbs culture, context, and working norms simultaneously, and they do it through proximity to the person who built the thing.

Think of a new engineer joining at employee number four. The founder and CTO spend the first week with them - not in a structured way, but in the way you teach someone you're excited to have around. They learn the codebase, yes, but they also learn why certain decisions were made, which parts of the architecture are load-bearing and which are provisional, and what the team genuinely cares about getting right. That knowledge transfer is rich and fast, but it only works when the people doing it have both the time and the direct relationship.

At twenty-two to twenty-five employees, the founder doesn't have that week to give to every new hire - and increasingly, they shouldn't be the one providing it. Onboarding at this stage needs to be documented: a first-week schedule, a buddy system, clear milestones at thirty, sixty, and ninety days. Not because documentation is better than the founder's personal touch, but because the founder's personal touch is no longer available at scale, and the alternative to a good system isn't warmth - it's confusion.

## Who makes the hiring decision - and why it shifts

At five employees, the founder makes every hire. They ask for input - the team's read on a candidate matters - but the final call is always theirs. This works because they are the only person with full context on the culture, the strategy, and what the organisation genuinely needs next.

By twenty-five employees, hiring is distributed. A hiring manager leads the process for their team. The founder or leadership team has final sign-off on senior roles. You might have an HR coordinator managing the logistics. The decision involves more people, which creates alignment risk: if the hiring manager wants someone who can own a process end-to-end and the founder wants someone with the chaotic generalism of an early startup employee, you'll interview the same candidates and score them completely differently.

That misalignment doesn't stay in the hiring decision. It follows the new hire into their first week. The hiring manager thought they were getting one thing; the founder expected another. The new hire reads the friction and spends their early weeks trying to work out which direction is right. The fix is to have the alignment conversation before the process starts, not during the debrief - but that requires building the habit of writing down what success looks like before you start sourcing.

## Hiring timeline and speed - what you gain and lose as you grow

Early-stage hiring is fast in a way that feels almost reckless when you look back on it. You identify a need, source a candidate through your network, have one or two conversations, and make an offer - sometimes inside a fortnight. The speed is possible because the organisation is simple and because the founder holds all the context needed to make the call.

At twenty-two to twenty-five employees, a full hiring cycle - job spec, sourcing, phone screens, structured interviews, references, offer - takes six to eight weeks on a good run. Sometimes longer. That feels slow when you have a gap in the team and work piling up. The temptation is to shortcut the process, to hire the first credible candidate rather than the best-available one, to skip reference checks because you liked them in the interview.

The tension between speed and rigour is real, and it doesn't fully resolve - it just shifts. At five people, you can afford to move fast because a mistake is visible quickly and relatively containable. At twenty-five, you need the extra weeks because the cost of getting it wrong is higher, the problem is harder to see in time, and the fix is more disruptive to a team that's now large enough to have its own momentum and culture.

## First 90 days - what success looks like at each stage

At five employees, a successful ninety days looks like someone shipping, selling, or handling operations with increasing independence. The founder checks in informally - over lunch, in a Slack thread, on the walk to the coffee shop around the corner. Feedback is constant but unstructured. You know it's working because you can see it and feel it.

At twenty-two to twenty-five employees, success is defined earlier and measured more deliberately. There's a thirty-sixty-ninety plan written before the person starts. There are explicit milestones: systems access and setup in week one, team introductions and process orientation in week two, first independent deliverable by week six. A hiring manager runs regular check-ins. HR or a buddy tracks the broader integration.

The causal chain works in both directions here too. Clear onboarding leads to a faster ramp, which produces early wins, which builds the new hire's confidence, which makes retention dramatically more likely. The reverse - vague onboarding, slow ramp, persistent confusion - produces a person who spends their first two months feeling behind, wondering if they made the right call joining, and eventually deciding they didn't. The thirty-sixty-ninety plan isn't bureaucracy. It's the thing that turns a good hiring decision into a good outcome.

## Culture and values - how you communicate them as you scale

Culture at five people is lived rather than articulated. The founder embodies the values in every decision they make, every conversation they have, every hire they bring in. New people absorb norms by proximity - by watching how the team handles a problem, how the founder responds to a mistake, what gets celebrated and what gets quietly corrected. It works because everyone is in the same room often enough that the culture transmits continuously.

At twenty-two to twenty-five employees, that transmission path doesn't reach everyone anymore. You have people on different teams who don't interact with the founder daily. You might have remote workers who have never been in the same room as half the company. The culture that felt obvious and self-sustaining at five people is now at risk of drifting - not because anyone is acting in bad faith, but because it was never documented well enough to travel without the founder attached to it.

The mechanism that keeps culture intact through growth is deliberate. Written values, hiring criteria that reflect those values, interview questions designed to surface them, and onboarding that explains them explicitly rather than hoping new hires absorb them over time. Early on, everyone was scrappy and transparent because the founder was scrappy and transparent and you could see them being it every day. At twenty-five people, you need to say that out loud - what scrappy actually means here, what transparency looks like in practice, where the line is. The culture doesn't change because you write it down. It survives because you did.

## FAQ

### At what point should a founder stop making every hiring decision themselves?

There's no fixed number, but most founders start feeling the strain around hire twelve to fifteen. That's when the volume and complexity of hiring exceeds what one person can manage well alongside everything else. The practical signal is when a role requires someone to be hired by a manager rather than directly by the founder - at that point, the decision-making structure needs to shift, even if the founder retains final sign-off on senior roles.

### Why do job descriptions matter more as a company grows?

At five employees, the founder can explain the role verbally to the handful of people involved in hiring. By twenty-five employees, the role description needs to travel without the founder present - to hiring managers, recruiters, interview panels, and eventually the new hire's manager who didn't run the process. A written spec becomes the shared reference point that prevents misalignment between what was promised and what the person actually walks into.

### How long should onboarding take at a company of 20 to 25 people?

A structured onboarding period of ninety days is a reasonable standard at this size. The first two weeks should cover systems access, team introductions, and process orientation. The first month should include an independent deliverable of some kind. By the end of month three, the person should be operating without constant guidance and have a clear sense of what success looks like in their role. The specifics depend on the role, but the general shape - with explicit milestones at thirty, sixty, and ninety days - holds across most functions.

### What is the biggest hiring mistake companies make when scaling from 5 to 25 employees?

Keeping the informal founder-led process too long. The approach that worked beautifully at five people - gut instinct, fast decisions, loose vetting - starts producing bad outcomes somewhere in the middle of that range. The mistake is treating those bad outcomes as individual errors in judgement rather than as a signal that the process itself needs to change. By the time the problem is obvious, there are usually two or three prior hires who didn't work out for the same underlying reason.

### How do you maintain company culture when you're no longer small enough for it to transmit by proximity?

You have to make explicit what was previously implicit. That means writing down what the values actually look like in practice - not abstract words, but specific behaviours and decisions. It means building those values into your hiring criteria and your interview questions. And it means designing onboarding so that new hires understand the culture as a deliberate introduction, not something they're expected to absorb through osmosis. Culture doesn't change because you document it. It drifts because you don't.


---
Source: https://theartofpeople.io/blog/nuances-of-hiring-at-each-stage-5th-to-25th-employee