How to Hire Your First Employee: A Founder's Playbook

Hiring your first employee is the moment a company stops being only an extension of its founder.

That does not mean the first hire should happen as soon as you are overwhelmed. Founders are almost always overwhelmed. The decision becomes rational when a persistent business constraint is costing more than the fully loaded cost and management effort required to remove it.

The practical sequence is:

1. Identify the bottleneck.
2. Prove it is recurring work, not a temporary spike.
3. Define the outcomes the role must own.
4. Model the effect on cash and runway.
5. Decide whether the work belongs with an employee or a contractor.
6. Recruit and evaluate against a written scorecard.
7. Complete the employer setup before day one.
8. Use the first 90 days to transfer ownership—not merely assign tasks.

This guide covers the complete process for a US startup. It is operational guidance, not legal, tax, payroll, immigration, or employment advice. State and local requirements vary, remote hiring can create obligations where the employee works, and the rules change. Use current government guidance and qualified advisers for your facts.

The four gates: are you actually ready to hire?

A hire should pass four gates before you write a job description.

Gate	The question	Evidence you are ready	Evidence you should wait
Bottleneck	What important result is being constrained?	The same work repeatedly delays revenue, product, customers, or critical decisions	You are generally busy but cannot name the constrained outcome
Role	Is there a coherent job here?	Three to five recurring outcomes fit one reasonable role	The job is a miscellaneous pile of founder dislikes
Economics	Can the company support the full cost?	The base and downside cases preserve an acceptable runway and milestone plan	The plan works only if every revenue assumption lands on time
Management	Can you make this person effective?	Someone can provide priorities, context, feedback, and decisions	The founder wants to hand off chaos and disappear

Fail any gate and fix the underlying problem first. Hiring into an undefined role does not create clarity. It converts unclear founder work into unclear employee work, then adds payroll.

Gate 1: name the bottleneck, not your stress

Start with the operating system of the company. For two weeks, log work that consumes meaningful founder time and classify it:

• Create demand: sales, partnerships, content, outbound, community.
• Convert demand: demos, proposals, onboarding, implementation.
• Build and deliver: product, engineering, design, fulfillment.
• Retain customers: support, customer success, reliability, renewals.
• Run the company: finance, recruiting, compliance, administration.

Then ask four questions about each category:

1. Does this work recur every week?
2. Does delaying it harm a company priority?
3. Could another capable person own the result with reasonable context?
4. Is the work likely to remain important for at least the next year?

A founder spending ten hours once on a financing data room has a project. A founder spending ten hours every week onboarding customers while product decisions wait has a hiring signal.

Hire to remove a constraint, not to reward yourself for surviving one.

Gate 2: turn the need into outcomes

Before choosing a title, write the outcomes you need someone to own. Good outcomes describe a changed state in the business:

• New customers move from signed contract to first value within 14 days.
• Production incidents are triaged, communicated, and followed by corrective work.
• Qualified sales opportunities receive a useful follow-up within one business day.
• The monthly close is accurate enough to update cash and runway by the tenth business day.

Weak statements describe activity:

• Help with operations.
• Wear many hats.
• Support the founder.
• Manage projects as needed.

If you cannot define three to five durable outcomes, you probably have several projects or a process problem—not one job.

Gate 3: model the downside, not only the salary

Your first employee creates a recurring obligation. Model the full cash commitment before recruiting.

Use this structure:

Annual fully loaded cash cost =
  base salary or wages
  + employer payroll taxes
  + required insurance and statutory costs
  + benefits
  + equipment and software
  + recruiting and background-check costs
  + travel, workspace, or stipends
  + equity administration and professional fees

Do not apply a universal “salary plus X percent” shortcut. Employer costs vary by compensation, state, benefits, insurance, and company setup. Get actual quotes from payroll, benefits, insurance, and equipment providers.

Then convert the annual number into monthly cash impact and update the model:

Post-hire monthly net burn = current monthly net burn + monthly hire cost - near-term cash contribution
Post-hire runway = cash balance ÷ post-hire monthly net burn

Treat “near-term cash contribution” conservatively. An engineer may not create billable revenue in month one. A salesperson may need time to learn the product and build pipeline. An operations hire may create value by returning founder capacity, but that only matters if the founder actually reinvests the time in the company’s constraint.

Run three cases:

Case	Revenue assumption	Hiring assumption	Decision use
Base	The current plan, with realistic timing	Starts on the expected date	Normal operating plan
Downside	Revenue arrives later or lower	The cost still starts on time	Can we survive being wrong?
Delay	The hire starts one quarter later	Founder covers or cuts the work temporarily	What milestone would make the hire safer?

Our startup financial model guide shows how to connect headcount, cash, scenarios, and milestones. If the downside case puts the company into an emergency raise or a near-term layoff, the role is early, too senior, or too expensive.

Gate 4: budget for management

The first employee usually reports to a founder. That founder now owns:

• weekly priorities;
• decisions and escalation;
• feedback and coaching;
• access to customers, systems, and context;
• performance standards;
• difficult conversations;
• the employee’s understanding of how the company wins.

If you are hiring because you have “no time to manage,” pause. A good hire can create leverage after the transfer of context and ownership. During recruiting and onboarding, the hire consumes founder time before returning it.

Employee or contractor: classify the relationship, not the label

A contractor can be the right answer for a defined project, specialist expertise, uncertain demand, or work that can be delivered independently. An employee is usually the right answer for ongoing work that is central to the business and performed under company direction.

But you cannot choose classification only from preference. The signed agreement does not override the real relationship.

For federal tax purposes, the IRS groups evidence into three categories:

1. Behavioral control: who directs what is done and how the work is performed?
2. Financial control: who controls the economic aspects, tools, expenses, and opportunity for profit or loss?
3. Type of relationship: is the relationship ongoing, does it include employee-style benefits, and is the work a key part of the business?

The IRS says no single factor or magic count decides status; the whole relationship matters (IRS). Employment-law and state tests may differ from the federal tax analysis.

Use this table as an operating prompt, not a legal test:

The work looks like…	A contractor may fit	An employee may fit
Duration	Defined project or limited engagement	Ongoing role with no natural project end
Control	Worker controls methods and schedule within the deliverable	Company directs priorities, process, schedule, and collaboration
Integration	Specialist output can be delivered at arm’s length	Work is embedded in daily operations and the core product or service
Economics	Worker serves a market and bears business risk	Company provides the job, tools, systems, and continuing pay
Management	Vendor relationship around scope and acceptance	Performance management, development, and organizational responsibilities

Do not call someone a contractor because payroll feels inconvenient, because you want a “trial,” or because they work remotely. When classification is unclear, use an employment lawyer or tax professional; the IRS also provides Form SS-8 for a federal tax-status determination.

Who should your first employee be?

The first role should follow the company’s constraint.

Current constraint	Evidence	Common first-role direction	Watch out for
Product cannot ship or stay reliable	Validated demand exists; founder lacks build capacity	Product engineer, designer-engineer, or technical operator	Hiring a narrow specialist before the product architecture needs one
Founder cannot keep up with qualified demand	Leads wait, follow-up breaks, deals stall	Sales or revenue operator	Hiring sales before the founder has found a repeatable pitch
Customers buy but fail to reach value	Onboarding, implementation, or support is the bottleneck	Customer success or implementation operator	Treating service quality as junior administrative work
Work is delivered manually and inconsistently	Fulfillment quality or cycle time limits growth	Operations or delivery lead	Automating a process nobody has stabilized
Founder is buried in necessary company operations	Finance, recruiting, or administration repeatedly blocks core work	Operations generalist or finance/people operator	Creating a “do everything” role with no decision rights

Do not hire from an imaginary organization chart. A startup with five customers does not need the management layer of a company with five hundred.

Generalist does not mean undefined

Early employees need range. They also need a center of gravity.

A useful first-role design is T-shaped:

• one primary outcome they clearly own;
• adjacent tasks they can cover while the company is small;
• explicit work that remains with the founder;
• explicit work that is not part of the role.

“Generalist” should describe adaptability around a clear mission. It should not excuse a founder from making priorities.

If the role is your first technical employee, use our guide to the first engineering hire to evaluate judgment, communication, and shipped work without pretending every founder can review code.

Build the role scorecard before the job description

A job description markets the opportunity. A scorecard defines how you will decide.

Write the scorecard first with five parts.

1. Mission

One sentence explaining why the role exists:

Own customer implementation from signed contract to first value so the founder can keep selling without new customers stalling after the deal.

2. Outcomes

Define three to five results across a realistic time horizon:

Horizon	Example outcome
30 days	Shadow every active implementation and document the current workflow and failure points
60 days	Own new implementations with founder review at defined checkpoints
90 days	Run the workflow independently and report time-to-value, blockers, and product feedback weekly
12 months	Build a repeatable implementation system that supports the target customer volume without founder involvement in every account

3. Competencies

Choose four to six capabilities required to produce the outcomes. Examples:

• written communication;
• problem decomposition;
• customer judgment;
• learning speed;
• technical fluency;
• commercial judgment;
• follow-through;
• comfort with ambiguity.

Define what each looks like in behavior. “Ownership” is vague. “Surfaces a blocked customer before the deadline, proposes options, and drives the decision to closure” is observable.

4. Evidence

For each competency, decide what evidence can reveal it:

Competency	Strong evidence source
Written communication	Candidate email, work sample, past customer document
Problem decomposition	Structured case based on a realistic role problem
Follow-through	Specific past example, reference check, communication during the process
Technical fluency	Explanation of a shipped system or job-related working session
Customer judgment	Scenario with competing customer, product, and commercial constraints

5. Rating scale

Use a simple anchored scale:

• 1 — No evidence / concerning evidence
• 2 — Partial evidence; would require substantial support
• 3 — Solid evidence for the role and stage
• 4 — Repeated, specific evidence above the requirement

Write what a 1, 2, 3, and 4 mean for each critical competency before interviews begin. Otherwise every interviewer silently invents a different standard.

Write a job description that tells the truth

The first employee is not joining a polished machine. The right candidate needs enough truth to choose the work deliberately.

Include:

1. What the company does and for whom. One clear paragraph.
2. Why this role exists now. Name the bottleneck and business context.
3. What the person will own. Use outcomes, not a copied responsibility list.
4. What the first 90 days look like. Make the transfer of ownership tangible.
5. The stage and constraints. Team size, funding or profitability context where appropriate, pace, and missing infrastructure.
6. The must-have evidence. Keep the list short and job-related.
7. Compensation and location. Include the salary or wage range where required—and preferably even where it is not.
8. How the process works. Explain the interviews, work sample, decision timing, and accommodation contact.

Avoid “rockstar,” “ninja,” “must thrive under pressure,” and a list of every tool your company has touched. Those phrases often hide a role that has not been designed.

Separate requirements from preferences

Every “must have” shrinks the pool. Keep it only if removing it creates a credible risk to the outcome.

Ask:

• Could a strong person learn this in 30 days?
• Are we using pedigree as a shortcut for evidence?
• Is this requirement actually relevant to the job?
• Would someone who has already solved the underlying problem in a different industry still succeed?

The best first employee may not have held the exact title before. They should have evidence of handling similar complexity, stakes, and ownership.

Source candidates where evidence travels

Your first hire is unusually sensitive to trust and context. Start close to the work:

1. Former colleagues and collaborators you would work with again.
2. Referrals from customers, founders, investors, and domain experts.
3. Communities where practitioners show their work.
4. Targeted outreach to people with relevant shipped outcomes.
5. A focused job board for the function or geography.
6. Broad job boards after the role and screening system are ready for volume.

A referral is a sourcing channel, not a hiring decision. Every candidate should still go through the same job-related process.

For outreach, lead with the problem and ownership:

We are hiring our first customer implementation lead. The role exists because demand is working, but I am still carrying every account from contract to first value. The first 90 days are about taking over that workflow, fixing what is brittle, and turning customer feedback into a tighter product loop.

That is more useful than “exciting opportunity at a fast-growing startup.”

Use a small, structured hiring funnel

A first-hire process does not need six interviews. It needs distinct evidence at each stage.

Stage	Purpose	Output
Application or referral review	Check minimum job-related evidence	Advance / decline with reason
20–30 minute screen	Confirm motivation, constraints, communication, and basic evidence	Updated scorecard
Structured interview	Test competencies with the same core questions	Independent ratings and notes
Work sample or working session	Observe performance on a representative problem	Rated artifact or behavior
Reference checks	Verify the pattern across real working relationships	Confirmed strengths, risks, and management needs
Final founder conversation	Resolve mutual fit, role truth, and open questions	Decision and offer readiness

Decide what would make a candidate advance before each stage. Do not add interviews because the team feels nervous.

Screen for evidence, not keyword density

During the initial screen, ask for specific examples:

• What did you own?
• What changed because of your work?
• What constraints made it difficult?
• What did you personally decide?
• What would the people who worked with you say you should improve?
• Why does this stage and role make sense now?

Listen for clear ownership without inflated credit. Strong candidates can distinguish their work from the team’s work and explain tradeoffs without turning every answer into a victory story.

Run structured interviews instead of founder improvisation

Structure does not make an interview cold. It makes the evidence comparable.

The US Office of Personnel Management’s structured-interview guide notes that structured interviews have demonstrated stronger reliability, validity, and legal defensibility than improvised interviews (OPM). The basic mechanics are useful for startups too:

1. Base questions on the job analysis and scorecard.
2. Ask every candidate the same core questions.
3. Use planned follow-up prompts to get specific evidence.
4. Rate answers against anchored criteria.
5. Have interviewers score independently before discussing the candidate.

Build questions from real situations

For a customer implementation role:

• “Tell me about an implementation that was at risk. What was the first signal, what did you do, and what happened?”
• “A customer requests a custom workflow that would delay two other launches. Walk me through how you would decide.”
• “Describe a process you inherited that depended on one person. How did you understand and improve it?”

For each question, define what strong evidence contains. A polished story is not enough. Look for diagnosis, choices, tradeoffs, communication, and measurable consequences.

Keep every question job-related

The Equal Employment Opportunity Commission advises employers to limit pre-employment inquiries to information essential for deciding whether someone is qualified and warns against questions that reveal protected characteristics (EEOC). Before an offer, questions likely to reveal disability are restricted; employers may ask whether an applicant can perform job functions and should provide reasonable accommodation in the hiring process where required.

State and local laws can add protections and restrictions. Train every interviewer—even if the “team” is only two founders—to stay with the scorecard.

Use a representative work sample, not free labor

A good work sample resembles an important part of the role while remaining small enough to respect the candidate.

Examples:

• Prioritize a short list of customer issues and draft the response to one.
• Review a simplified product flow and identify the highest-risk assumption.
• Build a 30-day plan from a realistic set of sales or implementation facts.
• Debug or extend a small, self-contained technical exercise.
• Conduct a working session using a synthetic company scenario.

The EEOC notes that tests and selection procedures should be job-related and appropriate for their purpose, and that neutral tools can still create unlawful disparate impact when they disproportionately exclude protected groups without business necessity (EEOC). Use the same instructions, time expectation, evaluation criteria, and accommodation process for every candidate.

If the exercise creates real company value or requires more than a short, reasonable commitment, pay for it. If you use a paid project, define ownership, confidentiality, compensation, timing, and classification with counsel. Do not turn a “trial” into weeks of productive work without employment protections.

Check references for patterns

References should test the scorecard, not ask whether the candidate was “good.”

With the candidate’s permission, ask former managers or close collaborators:

1. What did the person own, and at what stage?
2. What were they unusually good at?
3. Where did they need more structure or support?
4. How did they respond when priorities changed or work went wrong?
5. What kind of manager and environment helped them do their best work?
6. If you were hiring for this exact outcome, what would you want us to understand?
7. Would you work with them again, and in what kind of role?

Compare patterns across references and interviews. One vague negative comment is not a verdict. Repeated, specific evidence about the same risk deserves attention.

Make the decision from the evidence

After the final stage, each interviewer should submit ratings and notes before the group discussion.

Use a decision sheet:

Dimension	Weight	Evidence	Rating	Risk / mitigation
Owns the role’s primary outcome	High	Interview, work sample, references	1–4	What support would be required?
Critical competencies	High	Structured questions and work sample	1–4	Which gap is trainable?
Stage fit	High	Past environment and candidate motivation	1–4	Does the person want the actual job?
Compensation and practical fit	Pass/fail	Candidate conversation	—	Are expectations aligned?
Values and working relationship	Medium	Behavior across the process	1–4	Is the concern job-related and specific?

Do not average away a critical failure. A candidate who cannot perform the core outcome is not rescued by charisma. A candidate who is quiet but demonstrates repeated evidence should not lose to the best storyteller.

Build an offer a strong candidate can evaluate

A written offer commonly covers:

• title and reporting line;
• start date;
• salary or wage and pay schedule;
• exempt or nonexempt classification where applicable;
• benefits and time-off terms;
• equity terms or a clear statement that the grant requires board approval;
• work location and any travel expectation;
• contingencies such as authorization or a lawful background check;
• at-will language where applicable;
• confidentiality, invention-assignment, and other agreements prepared for the jurisdiction;
• acceptance deadline.

Do not promise equity casually. If equity is part of the package, explain the number of shares, fully diluted percentage or denominator, vesting, cliff, strike price when available, exercise terms, and the fact that ownership will dilute. Our guide to equity for first employees covers the grant and option-pool mechanics.

Give the candidate space to evaluate risk. The first employee is making a concentrated bet on the founder, the business, and the job. Honest answers about cash, stage, customers, and what is broken build more trust than overselling certainty.

The first-employee compliance checklist (US)

The recruiting process and employer setup should run in parallel. Do not wait until the offer is accepted to discover that payroll, insurance, or state registration takes time.

Before the start date

• Confirm the employing entity and EIN. The IRS uses the Employer Identification Number for employer tax accounts and says not to use a Social Security number in its place. If the entity does not have one, apply through the IRS (IRS Publication 15).
• Register where the employee works. Review state and local withholding, unemployment insurance, paid-leave, disability, and other employer accounts. Remote employment can create obligations in the employee’s location.
• Set up payroll and tax deposits. Configure wages, pay periods, federal and state withholding, employer payroll taxes, and required filings. The 2026 IRS Employer’s Tax Guide is the federal starting point (IRS Publication 15).
• Obtain required insurance. Workers’ compensation rules are state-specific; also review disability, unemployment, and any industry requirements.
• Determine wage-and-hour treatment. Confirm employee classification, pay frequency, minimum wage, overtime, timekeeping, meal/rest rules, and required notices for the role and location.
• Prepare policies and records. At minimum, define working hours, timekeeping, expenses, security, acceptable use, leave, conduct, reporting channels, and how personnel, medical, and I-9 records will be separated and protected.
• Use the Department of Labor Poster Advisor and state tools. Required notices depend on the laws that cover the employer and the work location (DOL Poster Advisor).
• Prepare secure access. Email, identity management, password manager, device, least-privilege permissions, backup, and offboarding controls should exist before credentials are issued.

At hire and during the first days

• Form W-4: The IRS says to obtain a signed W-4 from each new employee when they start and use it for the first wage payment (IRS). Collect any required state withholding form too.
• Form I-9: The employee completes Section 1 no later than the first day of employment. The employer or authorized representative generally completes Section 2 within three business days after employment begins by examining acceptable documentation. The employee chooses which acceptable documents to present; do not demand a specific document (USCIS).
• New-hire reporting: Federal law requires reporting basic information on new and rehired employees within 20 days to the state where they work, and some states require it sooner (Administration for Children and Families). Payroll providers may support the filing, but confirm who is responsible.
• Benefits and required notices: Deliver enrollment information and any federal, state, or local notices on the applicable schedule.
• Records: Maintain payroll, tax, time, personnel, benefits, safety, leave, and employment-eligibility records for the required periods and with appropriate access controls.

This is a baseline, not a complete legal checklist. The correct list depends on the employee’s state and city, company size, industry, work arrangement, compensation, benefits, and immigration facts.

Onboard for ownership: the first 30, 60, and 90 days

A first employee cannot learn the company by osmosis. There is nobody else to copy.

Before day one

Prepare:

• a written role scorecard and 90-day plan;
• a one-page company strategy and current priorities;
• customer, product, and financial context appropriate to the role;
• a glossary of company language and systems;
• access to tools and documentation;
• a stakeholder map;
• a calendar for the first two weeks;
• one useful early deliverable;
• a list of decisions the employee can make without founder approval.

Days 1–30: context and an early win

Goals:

• understand the customer and business model;
• shadow the current workflow end to end;
• meet the people required to do the job;
• learn security, compliance, and operating expectations;
• complete one bounded piece of useful work;
• identify contradictions between the documented process and reality.

The founder should explain not only what the company does, but why current choices were made. Context turns a task-taker into a decision-maker.

Days 31–60: transfer a workflow

Goals:

• own a recurring workflow with defined escalation points;
• make decisions inside a clear boundary;
• establish a weekly metric or operating review;
• improve one part of the inherited process;
• build relationships with customers or partners relevant to the role;
• surface risks before they become deadlines.

This is where leverage begins. The employee should no longer wait for a list of tasks each morning.

Days 61–90: own the outcome

Goals:

• run the role’s core workflow independently;
• report outcomes and tradeoffs, not only activity;
• propose the next quarter’s plan;
• document the operating system another future hire could learn;
• identify capabilities the company should build, buy, automate, or continue doing manually;
• complete a direct 90-day review against the original scorecard.

The review should answer:

1. Which promised outcomes are on track?
2. Where was the role definition wrong?
3. What context or authority is still missing?
4. What is the employee unusually good at?
5. What behavior must change for the role to work?
6. What will they own next quarter?

Create the management cadence your second hire will inherit

Your first employee teaches the company how employment works. Build a minimum viable management system:

• Weekly one-on-one: priorities, decisions, feedback, development, and friction.
• Weekly operating update: outcomes, metrics, risks, and next actions.
• Monthly role review: progress against the scorecard and whether the role still matches the constraint.
• Quarterly performance conversation: results, behaviors, scope, compensation questions, and the next quarter’s expectations.
• Decision log: important choices, owner, date, reasoning, and revisit trigger.

Do not postpone feedback until a formal review. Specific, close-to-the-event feedback is easier to use and less likely to feel like a hidden verdict.

Ten first-hire mistakes to avoid

1. Hiring because the founder is tired. Fatigue is real, but the role still needs a business case.
2. Combining three jobs. “Marketing, customer success, and operations” usually means no priority will survive.
3. Choosing the title first. Start with the constraint and outcomes.
4. Ignoring runway. Salary is not the full cost, and revenue contribution rarely begins on day one.
5. Calling an employee a contractor. Classification follows the relationship, not the invoice.
6. Writing the scorecard after interviews. That lets the most charismatic candidate redefine the job.
7. Interviewing from chemistry. Ask the same job-related questions and record evidence.
8. Using free productive work as a test. Keep work samples small and representative; pay when value or burden becomes meaningful.
9. Treating the signed offer as the finish line. Compliance, access, management, and onboarding are part of hiring.
10. Refusing to correct a bad role design. Sometimes the person is capable and the job is incoherent. Fix the system before blaming the hire.

The founder’s first-hire decision sheet

Do not open the role until you can complete this page:

Business constraint:
What important outcome is currently limited?

Evidence:
What recurring work or missed result proves the constraint?

Role mission:
Why does this job exist?

12-month outcomes:
1.
2.
3.

First 90-day outcomes:
30 days:
60 days:
90 days:

Employment model:
Why employee rather than contractor, agency, software, or founder process change?

Fully loaded monthly cash cost:

Post-hire runway:
Base case:
Downside case:

Manager:
Who sets priorities, gives feedback, and removes blockers?

Selection evidence:
Which interview questions, work sample, and references test the scorecard?

Compliance owner:
Who owns payroll, registrations, insurance, I-9, W-4, reporting, notices, and records?

Start-date readiness:
What must exist before day one?

If the page is hard to complete, recruiting will not make it easier. The uncertainty will simply move into candidate conversations and employee performance.

The bottom line

Your first employee should not be a human patch for founder chaos. They should own a clearly defined outcome that matters enough to justify the cash, management, and legal obligations of becoming an employer.

Name the constraint. Design the role. Model the downside. Classify the relationship correctly. Use structured evidence. Build the employer infrastructure. Then spend the first 90 days transferring context, authority, and ownership.

Do that well and employee number one does more than increase capacity. They establish the hiring and management system every later employee will inherit.

Continue with How Much Equity to Give Your First Employees, the first engineering hire guide, or browse the full Team & Hiring archive.