Back to The Edit

The Edit · Founding Teams

Who should your first five hires really be?

The first people you hire won't just help build your company. They'll influence what kind of company it becomes. So perhaps it's time we stopped treating early recruitment like a shopping list.

By The Edit · 13 October 2026 · 3 min read

You've raised your first round. The business plan is looking good. You've got a product to build, customers to find and approximately 47 things that needed to happen yesterday.

Naturally, you start hiring.

A CTO. A Head of Marketing. A Product Manager. Someone in Operations. Maybe a CFO, because that sounds like something a serious company should have.

Congratulations. You've just created an organisational chart.

But have you actually worked out what your company needs?

Your first five aren't necessarily five job titles.

At the beginning, every hire has an outsized influence.

Your first engineer could shape the technical foundations of your product. Your first commercial hire could influence how you sell for years. Your first marketing hire could determine whether customers understand what you're trying to build.

And your first leadership appointments? They begin defining how decisions are made when you're no longer in every room.

In a Y Combinator interview, Pave founder Matt Schulman explained how he personally recruited his earliest employees. He prioritised adaptable people who believed in the mission and could work across different problems—not simply experienced specialists with impressive job titles.

There's something worth taking from that.

An early-stage business often needs people who are comfortable building the machine while operating it.

Start with the biggest problem. Not the biggest title.

Before recruiting, ask yourself:

What's the one thing preventing us from making meaningful progress?

Is it that nobody can build the product?

That you've built something great but haven't found customers?

That sales are coming in, but everything depends on the founder?

Or that you've raised funding and simply don't know how to structure the team?

The answer should shape your hiring priorities.

Consider two hypothetical startups.

Startup A: A B2B software company with a commercial founder.

Its first major need may be technical leadership, followed by product engineering and someone who can translate early customer feedback into a better product.

Startup B: A consumer business with an existing product and early traction.

Its priorities might instead be distribution, customer acquisition, commercial partnerships and operational delivery.

Both are startups. Both need talented people.

They absolutely do not need identical first teams.

Do you need a CTO—or do you need somebody to build the product?

This distinction matters more than many founders realise.

A CTO, technical co-founder, founding engineer and fractional technology leader aren't interchangeable.

A CTO may need to define long-term architecture, manage technical strategy and eventually build an engineering organisation.

A founding engineer may be precisely the person you need to turn an idea into a working product.

A fractional CTO could provide experienced technical direction before the company has the resources or need for a full-time executive.

And a technical co-founder? That's an entirely different relationship, involving shared ownership, responsibility and long-term commitment.

Don't recruit an expensive title when you haven't defined the problem.

The qualities worth looking for

Early employees need different abilities from people joining mature organisations.

We would prioritise evidence of:

  • Ownership: Can they take responsibility without waiting for instructions?
  • Adaptability: Can they operate when the plan changes?
  • Relevant capability: Can they actually solve the problem in front of the company?
  • Communication: Can they work effectively with people outside their own specialism?
  • Learning ability: Can their responsibilities grow alongside the business?
  • Commitment: Do they understand the realities and risks of joining at this stage?

Being comfortable with ambiguity doesn't mean accepting disorganisation. Founders still owe employees clear expectations, fair conditions and the support needed to succeed.

And while your personal network is a useful starting point, don't let it become the entire recruitment strategy. A deliberately broader search can bring expertise and perspectives your immediate circle doesn't contain.

The question we'd ask before hiring anyone

Forget the job title for a moment.

Complete this sentence:

If we hire this person, our business will finally be able to \_\_\_\_\_\_\_\_.

Build its first product?

Win its first ten customers?

Enter a new market?

Deliver without the founder managing everything?

If you can't finish that sentence, you may not be ready to recruit.

And that's fine.

Sometimes the smartest first step isn't finding someone. It's working out exactly who you need.

Building your first team?

We help founders define their first critical hires and find the people who can make them happen.

Sources & further reading

Y Combinator's interviews and early-stage recruitment guidance support the emphasis on founder involvement, adaptable early employees and clear hiring criteria. The hypothetical startup teams and practical hiring framework are our proposed editorial advice, not findings presented as statistical research.