Hiring at 10x speed without breaking culture

We grew the team from 5 people to more than 40 in 18 months. On paper that is a hiring achievement. In practice, for a good chunk of it, it felt like trying to change the tyres on a car doing 100 on the motorway.

Fast hiring is not the hard part. The hard part is keeping the thing that made the small team good while you dilute it with people who were not there for any of it.

Culture at 5 people is just how those 5 people happen to behave. Culture at 40 has to be something you can transmit on purpose, because you no longer have a small enough room for it to spread by osmosis.

Here is what I learned holding those two things together.

Onboarding is an operational system, not a welcome email

At 5 people, onboarding was osmosis. You sat next to someone good and absorbed how things were done. That does not survive contact with scale. When you are hiring two or three people a month, osmosis produces two or three slightly different versions of how things are done, and within a year you have no shared standard at all.

So I stopped treating onboarding as a welcome and started treating it as a system with a definition of done. What should someone know by end of week one, end of month one, end of month three. What are the handful of things they must be able to do unsupervised before we call them onboarded. Who owns walking them through it.

The point was not to make it corporate. The point was to make the standard transmissible. A new project manager should absorb how we actually work, not just whatever the nearest desk happened to model that week.

Onboarding is where culture either replicates or degrades. At 10x speed it degrades by default unless you build it deliberately.

Hire for judgement, and be slow on the hires that set the tone

When you are under pressure to fill roles, the temptation is to lower the bar to keep pace. I did it a couple of times and regretted it both times. A wrong hire at 5 people is a problem. A wrong hire who then helps onboard the next five is a multiplier of the problem.

The people I got most right were hired for judgement, not just competence. Could they reason through a situation the playbook did not cover. Could they hold the standard when it was inconvenient. Those people become the ones who carry the culture into the parts of the team you can no longer personally see.

I learned to go faster on the roles where a mistake is cheap and reversible, and deliberately slower on the roles that set the tone for everyone around them. Speed everywhere is how you break the thing. Speed where it is safe, patience where it matters.

Protect the standard, out loud

The thing that nearly broke was the standard slipping without anyone deciding to lower it. No single moment. Just a hundred small compromises made under time pressure, each defensible on its own, adding up to a team that was quietly operating below the bar the original five held.

You cannot catch that in a metric. You catch it by naming the standard out loud, repeatedly, and being willing to be the person who says "this is not good enough yet" when everyone would rather ship and move on. That is uncomfortable and it is the job.

The five people at the start held a standard because they cared and they could see everything. At 40, most of them cannot see everything anymore. So the standard has to be stated, modelled, and defended, or it erodes to whatever the busiest, most rushed version of the team can get away with.

What I would do differently

I would build the onboarding system before I needed it, not scramble it together at hire number fifteen when the pain was already obvious. I would hold the hiring bar harder in the middle stretch, where the pressure to just fill seats is highest and the cost of a wrong hire compounds fastest.

Growing 8x in 18 months is a good problem. It is still a problem. Culture does not scale on its own. It scales only as fast as you can make it transmissible, and never faster than that, no matter what the hiring plan says.