Your First Hire, Step by Step

Your first hire is not like your fifth or your fifteenth. There is no team culture for them to join, no manager between you and them, and no existing process to show them how things work here. Everything you do – and everything you skip – becomes the template for every hire that follows.

Get the timing right

Hire too early and you're paying salary out of runway you can't spare, training someone on a product that's still changing shape weekly. Hire too late and you're the bottleneck: every decision, every customer conversation, every line of code routes through you, and growth stalls because there's only one of you.

• You're turning down or delaying work you'd otherwise take, because there's no time
• The same task eats hours every week and does not require your specific judgment to do it
• You have at least 6–9 months of runway left after the hire is paid, not before it
• You can describe the job in one sentence without hedging

Decide what you actually need before you write anything

The instinct is to hire a generalist who can do a bit of everything. That's a reasonable answer for a five-person team, but it's a bad starting point for a job description – it tells no one what to apply for. Before you post anything, write down the three or four things this person will actually spend their week doing in month one. Not the eventual job three years from now – the actual Monday morning.

Build a simple, repeatable process

• Post the role with a real description of month-one work, not an aspirational title
• Screen for the one or two things that predict success in this specific role, not a generic checklist
• Talk to at least one reference who worked with them directly, not just a character reference
• Give a small, paid, time-boxed work sample instead of a take-home that eats a weekend
• Make the decision within a week of the final conversation – good candidates don't wait

Resist the urge to hire the most impressive person who applies. The person who thrives in a five-person company doing under-defined work is not always the person with the strongest résumé – they're the person who is comfortable without a playbook, asks good questions instead of waiting for instructions, and can tell you what's wrong with your plan.

Set them up before day one

Have their tools, logins, and first two weeks of work ready before they start. A new hire's first impression of how the company operates is formed in the first 48 hours, and "nobody knew what I was supposed to do" is a bad one to give the person you spent weeks convincing to join you.

The goal of the first hire isn't to find someone who can do your job. It's to find someone who can own a piece of it completely, so you can stop being the answer to every question.