How to Hire Your First Employees as a Startup Founder
The short answer
To hire your first employees, start with the bottleneck: the one thing slowing you most on the way to your next milestone. Write a one-page role scorecard with a mission, three measurable outcomes and four competencies. Set pay bands and equity rules you apply to everyone. Source through people who trust you, run a short structured interview loop with a work sample, make an honest offer quickly, put the terms in writing and onboard with a 30-60-90 plan.
- Hire to remove a named bottleneck, and check every hire against your runway.
- Write the role scorecard before the job post; it drives every later step.
- Use the same pay bands and equity rules for everyone, and show candidates the zero outcome.
- A short structured loop with a work sample beats long unstructured conversations.
- Move from final interview to offer within about two days.
- Contractor, employee or employer of record is a decision about the real relationship, not a label: check local law.
Who should a startup hire first?
The first hire should remove the biggest bottleneck between you and your next milestone. That sounds abstract, so make it concrete: write down where each founder's hours went last week, what is waiting on one person right now, and what the next milestone is. The overlap usually points to the hire.
For many software startups the first hire is a builder, because nothing else matters if the product does not improve. But it is not a rule. If customers sign and then struggle for months to get value, onboarding may come first. If a founder has closed the first customers and the pipeline now stalls whenever she travels, the first seller may be right. The one pattern that holds almost everywhere is that founders sell first: do not hire a salesperson to discover whether the product sells.
Generalists usually serve a company of fewer than about eight people better than specialists. Hire a specialist when you can name the depth the product needs and cannot judge it yourself, such as security or data engineering, and borrow an adviser to help assess candidates.
| Bottleneck you see | Likely next hire | Consider first |
|---|---|---|
| Features wait weeks because one person writes the code | Engineer | Can a contractor take a defined piece? |
| Customers get lost in the product | Product designer | A contract for a defined redesign |
| A founder runs every sales call and is the limit | First account executive | Has a founder sold enough to have a pattern? |
| Founders onboard every new customer by hand | Onboarding or customer success | Write the onboarding steps down first |
| Founders spend days on invoices, payroll and contracts | Operations generalist | Better tools or an outsourced bookkeeper |
| A founder has more than six to eight direct reports | First manager | Promote and train someone from within |
How do I check if we can afford the hire?
Every early hire is also a runway decision. CB Insights' March 2026 analysis of venture-backed startups that shut down since 2023 found that 70% of those with an identifiable reason had run out of capital, so the cost of each person deserves a hard look.
Work out the fully loaded cost, not just salary: employer taxes and statutory contributions, benefits, equipment, software and recruiting costs. Divide your cash by your monthly net burn before and after the hire to see how many months of runway it uses. If the hire takes runway below the minimum you and your investors are comfortable with, change the order, use a contractor for a defined piece, or wait.
What is a role scorecard and why write one first?
A role scorecard is a one-page definition of what the role must achieve. It owes a lot to the scorecard idea in Geoff Smart and Randy Street's book Who: The A Method for Hiring, which starts from the mission and measurable outcomes rather than a list of duties.
For a startup, keep it to six parts: a one-sentence mission, three outcomes for the first year that you could count or see, four competencies with what good and poor look like in behaviour, one 90-day goal, a single must-have that you would genuinely reject someone without, and the pay and equity range. Everything else is trainable.
Writing it first stops interviews drifting into whatever each interviewer finds interesting, removes proxies such as degrees and years of experience, and gives the new hire a clear 90-day goal on day one.
How much should I pay, and how much equity should I give?
Decide a compensation philosophy before you negotiate with anyone: where you pay against the market for cash, how you give equity, whether bands are per location or global, and how open you are about ranges. Then build simple bands for each role family, level and location from at least three real benchmarks. Never use AI-generated salary figures as benchmarks.
Most startups offer stock options: the right to buy shares later at a fixed strike price, vesting over time. Four-year vesting with a one-year cliff is a common pattern, but plans differ. As one reference point, Carta reported in December 2025 that the median equity grant to a startup's first engineer on its platform was 1.54%. Your pool, cash offer, stage and country matter more than any median.
Offer a number of options subject to board approval and your plan, not a vague percentage. Explain dilution, the exercise price and what happens if someone leaves. Show the outcome where the options are worth nothing, because for many startups that is what happens. Option rules and tax differ by country, so check your lawyer and accountant before you promise anything.
Where do you find early hires without a recruiter?
Mostly through people who already trust you. Writing on the Y Combinator blog in 2018, Harj Taggar called personal networks the most important source by far when hiring a first engineer. Ask advisers, investors and former colleagues for the best person they have worked with in the role. Ask for two names, not a forward of your post.
Then widen the circle: your own team's networks once you have one, communities where you already contribute, short personal outreach to people whose work you have seen, and content about the problem you solve. Job boards bring volume; screen against the single must-have. If you use recruiters or marketplaces, agree fees and terms in writing first.
Write the job post honestly: pay range and equity near the top, the mission in one sentence, three outcomes, the must-have, how you work and what happens next with timings. Add one honest line about startup risk. It helps the right people say yes and the wrong people say no. Several places now require pay ranges in job adverts, and the EU Pay Transparency Directive, due to be transposed by 7 June 2026, requires applicants to get pay information before interview; check the rules where you hire.
Reading helps; measuring tells you what to work on. These AI-graded assessments on AssessAll pair with this topic:
What should the interview process look like?
Keep it short, structured and the same for every candidate for a role. A loop of about five hours of the candidate's time works for most early roles.
- A 30-minute intro call: two-way, checking the must-have, range and timing.
- A short work sample with fictional data that looks like the real job, scored on criteria the candidate can see. Pay for longer tasks where you can.
- Two structured interviews, each covering two competencies from the scorecard, with the same questions in the same order.
- Scores entered independently before any discussion, then a debrief where the founder speaks last and every reason ties to the scorecard.
- A founder conversation for the candidate's questions, and two reference calls with the candidate's consent asking for examples.
| Step | Time | What it tests |
|---|---|---|
| Intro call | 30 minutes | Must-have, motivation, range, timing |
| Work sample | 90 minutes to 3 hours | Two competencies in realistic work |
| Structured interview 1 | 45 to 60 minutes | Two competencies |
| Structured interview 2 | 45 to 60 minutes | Two other competencies |
| Founder conversation | 45 minutes | Their questions; not scored |
| References | Two calls | Examples against the top two competencies |
How do you make an offer a strong candidate accepts?
Speed and clarity matter a great deal to candidates. Aim for a debrief within a day of the last interview and an offer within about two days of the decision. Design the offer before the call: base, variable pay, options, what can move and how far, and a fair response date. Never invent deadlines or competing interest.
Sell by answering the candidate's real questions: what they will own, who they will learn from, how long the runway is and what happens if things go wrong. When a larger company offers more cash, do not pretend to match it; show the trade-offs inside your band using the same rules you use for everyone. When an employer makes a counter-offer, go back to the reasons the candidate gave for wanting to move.
Employee, contractor or employer of record?
Choose by the reality of the work. Ongoing core work that you direct day to day usually points to employment, either through your own entity or through an employer of record, a provider that legally employs the person in their country and runs payroll and statutory benefits for a fee. A defined project with an end can suit a contractor. Most countries judge status by the real relationship, not the label, and misclassification can bring back taxes and penalties.
Whatever the route, put the essentials in writing before day one, and do right-to-work checks before the person starts, the same way for everyone. In the UK, for example, the Home Office's employer's guide sets out how and when checks must be done. Have a lawyer formalise your templates once for each country you hire in.
What happens after they say yes?
Onboarding in a small company needs a plan precisely because nobody else will do it. Before day one, have equipment, accounts, paperwork and a buddy ready. On day one, a founder spends real time on the company story, customers and numbers. In week one, agree a 30-60-90 plan from the scorecard: learn by day 30, own by day 60, deliver the 90-day goal by day 90, with short written check-ins at each point.
Hold a weekly one-to-one with every person who reports to you. Somewhere around six to eight direct reports, plan the first manager: promote and train someone, or hire a lead with people outcomes on their scorecard. If you are about to become a manager of managers yourself, the AssessAll First-Time Manager Readiness Assessment is one way to see where you are starting from, and a Jobulary development plan can turn the gaps into dated actions.
The First Ten Hires Kit from Bodhih Training puts all of this into working files: a hiring plan with budget checks, scorecards, an offer and equity calculator, loop sheets, offer templates, an onboarding plan and a culture tracker.

Make your first ten hires with a method
The First Ten Hires Kit gives you the hiring plan, scorecards, offer and equity calculator, interview loop, offer templates and onboarding plan in ready-to-use files.
Sources
- Y Combinator: How to Hire Your First Engineer (Harj Taggar, 2018)
- Carta: The Median First Engineer Equity Grant Is 1.54 Percent (December 2025)
- CB Insights: The top reasons startups fail (March 2026)
- GOV.UK: Right to work checks: an employer's guide
- Remote Work Europe: EU Pay Transparency Directive transposition tracker
More from the Bodhih family
Questions people ask next
When should a startup make its first hire?
When a named bottleneck is slowing you down on the way to your next milestone, a hire is the fastest fix, and you can afford the fully loaded cost without taking runway below your safe minimum.
Should the first hire be a co-founder or an employee?
A co-founder shares the founding risk and usually receives founder-level equity; an early employee joins with a salary, options on a standard plan and a defined role. If you are offering co-founder equity, treat it as a co-founder decision, not a hire, and take legal advice.
What is a typical vesting schedule?
A common pattern is four years with a one-year cliff, then monthly vesting. Plans differ, and the rules and tax treatment depend on your company and country, so check your plan documents and lawyer.
Should I pay candidates for take-home work samples?
Keep work samples short and realistic. Paying for anything longer than about two hours is a fair practice that respects candidates' time, and you should never use a candidate's work in your product.
How long should a startup hiring process take?
A few weeks from first conversation to offer is common for early roles. What matters most is the time between steps: debrief within a day of the last interview and offer within about two days of the decision.
Can I hire someone in another country without a company there?
Often yes, through an employer of record or, for genuinely project-based work, a contractor arrangement. Each has trade-offs on cost, protections, intellectual property and equity. Take local advice before you offer.
Can AI help with startup hiring?
Yes for drafting scorecards and job posts, checking wording, building question sets and summarising anonymised scores. A person should make every hiring decision, personal data should stay out of unapproved tools, and AI-generated pay figures are not benchmarks.