Every founder I have worked with asks me the same question in roughly the same week. We are about to grow from three engineers to ten — what do we hire, and in what order. They want a function, a seniority, a title. I never give them one. I give them a sequence, because the right answer is not who, it is when.

The first ten hires set the architecture of every decision the company will make for the next three years. More than the stack, more than the customers, more than the pitch deck. By the tenth hire, the culture is decided, the code style is decided, the way you ship is decided. Hire in the wrong order and you spend year two unwinding it.

Here is the order I recommend, and the trade-off each one is buying you.

1 — The second senior

Your first engineer was probably you, or a co-founder. The second engineer should be someone with twelve to fifteen years of experience and zero appetite for theatre. Not a manager. A builder. Their job for the next six months is to disagree with you in writing and ship anyway.

2 — The full-stack generalist

The third hire should be the fastest generalist you can find. Mid-level. Hungry. Comfortable in three layers of the stack and unbothered about which one they touch this week.

Hire for the invisible things first.

If you are about to make hire three or hire four and the order does not match this, that is a conversation worth having before you write the offer.