When to Hire
Hiring too early burns runway. Hiring too late burns founders. The timing of your first engineering hire is one of the most consequential decisions a technical startup makes, and most founders get it wrong in one direction or the other.
Too early: you are paying a salary before you have product-market fit. You are managing someone when you should be talking to customers. You are burning cash to build features that might get thrown away next month.
Too late: you are drowning. Every feature takes twice as long because you are also doing support, sales, infrastructure, and hiring. Technical debt has compounded to the point where simple changes take days. You have not taken a day off in months and your decision quality is declining.
The right time is somewhere in between. Here is how to find it.
The Signals That It Is Too Early
Most first-time founders hire too early. They have funding, they have a product vision, and they want to build a team. The instinct is understandable but often wrong.
Signs it is too early to hire:
- You do not have product-market fit yet
- You are still pivoting or exploring different ideas
- Your product roadmap changes every two weeks
- You could build the next three months of features yourself
- You have not talked to 50+ potential users
- Your runway would drop below 12 months with the hire
- You do not know what you would have them work on
Hiring before PMF is expensive in more ways than salary. You now have to onboard someone into a codebase that might get rewritten. You have to explain a vision that is still forming. You have to manage someone during the most chaotic phase of the company.
Basecamp ran with a tiny team for years before hiring aggressively. They wanted to be sure they knew what they were building before they brought in people to help build it.
Cost of hiring too early:
- Salary: $100K-$200K per year (loaded cost)
- Onboarding: 2-4 weeks of founder time
- Management overhead: 5-10 hours per week
- Context switching: constant interruptions
- Direction changes: explaining pivots, re-assigning work
- Potential layoff: if you run out of runway
The Signals That It Is Time
There are concrete, observable signals that tell you it is time to hire. Not feelings. Not aspirations. Signals.
Strong signals it is time to hire:
1. You are turning down customer requests because you cannot build fast enough
2. Technical debt is blocking features (not hypothetically, actually blocking)
3. You have not taken a meaningful day off in 3+ months
4. Response time to customer issues is measured in days, not hours
5. You have a clear 6-month roadmap that requires more hands
6. You have revenue or funding that supports 18+ months of runway with the hire
7. You are spending more than 50% of your time on non-product work
The strongest signal is number one: you are losing revenue or growth because you cannot build fast enough. This means you have product-market fit, you have demand, and the constraint is engineering capacity. That is the ideal time to hire.
The hiring trigger framework:
Demand exceeds capacity -> hire
Capacity exceeds demand -> do not hire
Uncertain about demand -> do not hire (wait for clarity)
The Founder Burnout Trap
There is a dangerous gray area where founders feel they need to hire because they are burning out, but the business fundamentals do not support it.
Burnout is real and serious. But hiring is not always the solution. Sometimes the answer is:
Alternatives to hiring when burned out:
- Cut scope ruthlessly (stop building features nobody asked for)
- Automate repetitive tasks (deploys, customer onboarding)
- Say no to custom requests (focus on core product)
- Take a weekend off (the company will survive)
- Use contractors for one-off projects
- Use freelancers for non-core work (design, content, admin)
If you cut scope, automate, and focus, and you are still drowning, then it is time to hire. But make sure you have tried the simpler solutions first.
WhatsApp had 35 engineers serving 450 million users. They did not hire more engineers because they were burned out. They hired when the product needed it. Their discipline about hiring is a significant reason they maintained high quality.
The Contractor Bridge
Between "do everything yourself" and "hire a full-time engineer" is the contractor option. Contractors can bridge the gap when you need help but are not ready for a full-time commitment.
When contractors make sense:
- One-off projects (redesign, mobile app, integrations)
- Specialized work (iOS development, DevOps, security audit)
- Temporary capacity boost (pre-launch crunch)
- Validating that you need a full-time hire
- Testing a role before committing to headcount
When contractors do not make sense:
- Core product development (they leave, knowledge leaves)
- Work that requires deep context (months of domain knowledge)
- Ongoing maintenance (cheaper to hire full-time)
- When you need someone who cares about the company
Contractors cost more per hour but less per commitment. A contractor at 12,000/month. That is expensive, but there is no equity, no benefits, no commitment, and no awkward layoff if things change.
Use contractors to test the hypothesis that another engineer would help. If a contractor working 20 hours per week meaningfully accelerates your product development, a full-time hire will too.
The Financial Reality
Before you hire, do the math.
Full-time engineer cost (US market, 2024):
- Salary: $120K-$180K (early startup, below market)
- Benefits: $15K-$30K (health insurance, 401k)
- Equipment: $3K-$5K (one-time)
- Payroll taxes: 8-10% of salary
- Total loaded cost: $150K-$230K per year
- Monthly burn increase: $12K-$19K
With equity:
- Typical early employee: 0.5%-2% equity
- 4-year vesting, 1-year cliff
- Below-market salary offset by equity upside
Runway impact:
- Current runway: 18 months
- Monthly burn increase: $15K
- New runway: 13-14 months (significant reduction)
If hiring one engineer drops your runway below 12 months, you either need to raise more money or wait. Running out of money is the most common way startups die. Do not accelerate that timeline for a hire you might not need yet.
The Decision Framework
A structured approach to the hiring decision.
Step 1: Do you have product-market fit?
No -> Do not hire. Find PMF first.
Yes -> Continue.
Step 2: Is demand exceeding your capacity to build?
No -> Do not hire. Focus on growth.
Yes -> Continue.
Step 3: Can you afford 18+ months of runway after the hire?
No -> Consider contractors, or raise first.
Yes -> Continue.
Step 4: Do you know what the person would work on for 6 months?
No -> You are not ready. Clarify the role first.
Yes -> Hire.
This framework biases toward not hiring, which is intentional. The cost of hiring too early is higher than the cost of hiring too late by a few months. An engineer with nothing impactful to work on is demoralizing for them and expensive for you. An overworked founder can push through for another quarter.
Timing Relative to Fundraising
If you are planning to raise funding, the timing of your first hire matters relative to your raise.
Before raising:
- Smaller team shows capital efficiency
- Investors see founders doing the work
- Lower burn rate makes runway look better
- BUT: slower product development
After raising:
- More runway to support the hire
- Can offer more competitive compensation
- Investor expectations include team growth
- Can hire from a position of strength
Best practice:
- Include the hire in your fundraising plan
- Raise enough to cover the hire for 18+ months
- Start recruiting during the raise (closing takes time)
- Make the offer after the money is in the bank
What Happens After You Decide
Once you decide to hire, move quickly. The hiring process for startups takes 4-8 weeks from first conversation to start date. That means you should start recruiting 2-3 months before you need someone.
Hiring timeline:
Week 1-2: Write the job description, activate your network
Week 3-4: Screen candidates, technical conversations
Week 5-6: Final interviews, reference checks
Week 7-8: Offer, negotiation, acceptance
Week 9-12: Notice period (if employed)
Week 13-14: Onboarding
Total: 3-4 months from "we should hire" to "productive engineer"
The gap between deciding to hire and having a productive team member is longer than most founders expect. Factor this into your planning.
Common Pitfalls
Hiring because you raised money. Investors give you money to grow the business, not to grow the team. Hire when the business needs it, not when the bank account allows it.
Hiring to solve a management problem. If you are struggling with prioritization, scope, or direction, another engineer will not help. They will amplify the chaos. Fix the management problem first.
Waiting for the perfect candidate. Your first hire will not be perfect. They will be good enough and willing to take a risk on your startup. Perfect candidates go to companies that can offer more certainty.
Not considering the onboarding cost. Your first hire will make you slower for the first 2-4 weeks. You will spend time explaining the codebase, the product vision, and the customer context. Plan for this. Do not hire the week before a big deadline.
Hiring a friend without evaluating them. Working with friends is great when it works and devastating when it does not. Evaluate friends as rigorously as strangers. A bad hire that is also a friend is the worst outcome.
Key Takeaways
- Hire when demand exceeds capacity, not when you have funding or feel burned out.
- The strongest hiring signal is turning down revenue because you cannot build fast enough.
- Before hiring, try cutting scope, automating, and using contractors. If you are still bottlenecked, hire.
- Do the financial math. If the hire drops runway below 12 months, wait or raise first.
- The hiring process takes 3-4 months from decision to productive team member. Start early.
- Hiring too early is more expensive than hiring too late. When in doubt, wait.