83. Recruiting

Recruiting is founder work until the company has a strong hiring machine.

Early candidates are not just filling jobs. They are choosing risk. They are betting on the founder, mission, market, team, and their own future. A founder who treats recruiting as an admin process will lose strong candidates to companies that make the opportunity feel clearer and more alive.

Good recruiting is a system: role clarity, sourcing, evaluation, closing, references, offer, and onboarding.

The core recruiting question is: can the founder create a repeatable hiring funnel that attracts the right people, evaluates real work, closes honestly, and protects the early team bar?

Recruiting Is Sales With Higher Stakes

Recruiting is similar to sales:

• You define the target customer: candidate profile.
• You build a pipeline.
• You personalize outreach.
• You qualify fit.
• You handle objections.
• You close.
• You deliver on the promise after the close.

But recruiting is higher stakes because a wrong hire affects the team every day. The best candidates also evaluate founders intensely. They ask: Is this company clear? Is the founder honest? Will I learn? Is the risk worth it? Will this team make me better?

A founder who cannot explain the role clearly will struggle to hire excellent people.

The hiring funnel

Role definition

A role begins with a problem, not a title.

Write:

• What bottleneck does this role remove?
• What outcomes should happen in 90 days?
• What decisions will this person own?
• What skills are non-negotiable?
• What behaviors are non-negotiable?
• What support will they have?
• What will they not own?

If the role definition is lazy, the interview process will be noisy.

Write a role scorecard before sourcing.

Section	Example
Mission	Own onboarding for the first 50 B2B customers
90-day outcomes	Reduce onboarding time by 30 percent; document top 10 workflows
Must-have skills	Customer communication, process writing, spreadsheet comfort
Must-have behaviors	Ownership, follow-through, calm under pressure
Non-goals	Does not own product roadmap or enterprise sales
Interview evidence	Work sample, past examples, references

The scorecard prevents “I liked them” hiring.

Sourcing

Sourcing is identifying people who might be good for the role.

Early startups should not depend only on inbound applicants. Build a target list. Ask for referrals. Search actively. Write personal messages.

Track:

• Source
• Candidate quality
• Response rate
• Interview conversion
• Offer conversion
• Joining conversion

Outreach

Strong candidates are usually not waiting for your job post. Founder outreach should be specific.

Weak:

“We are hiring. Interested?”

Stronger:

Hi Priya,

I saw your work on onboarding flows at [company/project]. We are building [one-line company] and need someone who can turn messy customer setup into a simple product experience.

The role is early, hands-on, and high-ownership. I thought your mix of product thinking and customer empathy could be relevant.

Open to a short conversation?

Good recruiting outreach explains why this person, why this role, and why now.

Screening

Screening should remove obvious mismatches quickly.

Check:

• Relevant experience
• Motivation
• Availability
• Compensation expectations
• Location or remote fit
• Notice period
• Communication
• Basic role fit

Keep screening respectful. A poor candidate experience damages reputation.

Use screening to answer:

• Do they understand the stage?
• Are they excited by the actual work?
• Are compensation and notice-period expectations plausible?
• Are they available in the required timeline?
• Is there a clear reason to continue?

Do not stretch a candidate through a long process if there is an obvious mismatch.

Work sample

Work samples reveal more than conversation.

Examples:

• Engineering: debug, architecture review, small build
• Sales: discovery role-play, account plan
• Marketing: messaging rewrite, campaign plan
• Product: product critique, prioritization exercise
• Operations: process design, escalation plan
• Design: onboarding flow critique

Use work samples that resemble real work. Avoid unpaid large assignments.

Design work samples carefully:

Role	Better work sample	Avoid
Engineer	Debug a small issue, discuss architecture tradeoffs	Building a full feature for free
Sales	Run discovery role-play, write account plan	Generic “sell me this pen” exercise
Product	Prioritize a small roadmap with customer context	Abstract brainteasers
Marketing	Rewrite positioning for one customer segment	Full unpaid campaign plan
Ops	Create a checklist from messy workflow	Long take-home project
Design	Critique onboarding and propose changes	Polished redesign without context

Pay for substantial work trials when they require meaningful time or produce usable output.

Interviews

Each interview should have a purpose.

Possible rounds:

• Founder screen: motivation and startup fit
• Skill interview: role depth
• Work sample review: judgment
• Culture interview: values and behavior
• Team conversation: collaboration
• Closing conversation: mutual expectations

Do not ask every interviewer to judge everything. That creates vague feedback.

Create an interview plan:

Round	Evaluates	Evidence
Founder screen	Motivation, stage fit, communication	Candidate story and questions
Skill round	Ability to do the job	Past work and role-specific questions
Work sample	Judgment and execution	Realistic task
Values/operating style	Ownership, feedback, ambiguity, integrity	Behavioral examples
Closing	Mutual expectations and concerns	Direct conversation

After each round, write feedback against the scorecard. Avoid vague feedback like “good vibes” or “not startup enough” without evidence.

References

References matter especially for early hires.

Ask:

• What was the person’s strongest contribution?
• Where did they need support?
• How did they handle pressure?
• Would you hire them again?
• What role would you not put them in?
• How do they handle feedback?

Listen for specifics. Generic praise is weak.

Reference calls are especially important for senior hires, finance/admin roles, early sales leaders, and anyone with broad access or authority.

Ask one uncomfortable but fair question:

If we hire this person, what should we manage carefully in the first six months?

Useful references answer with nuance. Perfect references with no detail may be incomplete.

Offer

An offer is not only compensation. It is a story about the role.

Explain:

• Mission
• Current stage
• Why this role matters
• Expectations
• Salary
• Equity or ESOPs
• Risk
• Learning opportunity
• Growth path
• Decision timeline

Do not hide risk. Strong candidates appreciate honesty.

An offer should include:

Topic	What to explain
Role mission	Why the role exists
First 90 days	What success looks like
Compensation	Salary, ESOP, commission/bonus, benefits
Risk	Runway, stage, uncertainty
Growth	What the role could become
Manager	Who supports and evaluates them
Decision timeline	When you need an answer
Documentation	Offer letter and relevant policy documents

Never close with vague promises. Early trust is built through clarity.

Closing

Closing means helping the candidate decide.

Ask:

• What are you optimizing for?
• What concerns do you have?
• Who else is involved in the decision?
• What would make this a clear yes or no?
• What other options are you comparing?

In India, family, stability, commute, salary, brand, and notice period can affect closing. Discuss them respectfully.

Common closing objections:

Concern	Founder response
Salary lower than big company	Explain cash/equity tradeoff honestly; do not guilt them
Family worried about risk	Offer a clear stage/runway explanation the candidate can share
Notice period long	Plan joining date, buyout only if worth it
ESOP unclear	Explain basics and uncertainty in plain language
Role feels broad	Clarify 90-day outcomes and support
Startup seems chaotic	Show operating rhythm and priorities

Closing is not manipulation. It is helping the candidate make a high-quality decision.

Onboarding

Recruiting does not end when the offer is accepted.

Onboarding should cover:

• Company context
• Customer context
• Product walkthrough
• Current goals
• Role expectations
• Working norms
• Tools
• First week tasks
• First 30-day outcomes

The first week should create clarity, not confusion.

Candidate Experience Basics

Candidate experience is part of employer brand from day one.

Good experience:

• Clear process.
• Respectful scheduling.
• Fast feedback.
• Honest compensation range.
• Work sample expectations upfront.
• Interviewers prepared.
• No ghosting.
• Professional rejection.

A candidate you reject today may become a customer, referral, investor intro, or future hire. Treat people accordingly.

Sourcing channels

Referrals

Referrals are often strongest for early hiring.

Ask specific people for specific profiles. Do not say “know anyone good?” Say “I am looking for a backend engineer who has built production systems in Node or Python and likes early-stage ambiguity.”

Make referrals easy:

We are hiring a founding backend engineer.

Must have:
- Built production APIs.
- Comfortable with ambiguous product specs.
- Can talk to customers/support when needed.
- Wants early-stage ownership.

Not a fit:
- Needs large-team process.
- Wants only management.
- Uncomfortable with startup risk.

Specific asks produce better referrals.

LinkedIn

LinkedIn works when search criteria are clear.

Use filters by role, company, skill, geography, and past startup experience. Send personal messages that explain why the candidate is relevant.

Communities

Communities can work for developers, designers, marketers, founders, operators, and domain roles.

Contribute before hiring. Communities dislike extraction.

Colleges

Colleges can be useful for interns, freshers, campus ambassadors, and early talent.

Assess learning speed and ownership carefully. Many freshers need strong onboarding.

Twitter/X

Twitter/X can work for founder brand, design, engineering, product, AI, content, and startup talent. It is noisy but useful when the founder communicates clearly.

GitHub and Dribbble

Portfolio platforms help evaluate visible work.

For GitHub, look beyond stars. Look at code quality, consistency, collaboration, documentation, and projects that resemble your needs.

For Dribbble, look beyond visual polish. Ask whether the designer can solve product workflows.

AngelList/Wellfound, Naukri, Instahyre, CutShort

Job platforms can work, but quality depends on role clarity and screening discipline.

Use them as one channel, not the whole hiring strategy.

Recruiting Metrics

Track a few numbers:

Metric	Why it matters
Qualified sourced candidates	Shows top-of-funnel effort
Response rate	Shows outreach quality
Screen-to-interview conversion	Shows targeting quality
Work sample pass rate	Shows role clarity and sourcing
Offer acceptance rate	Shows closing and offer quality
Time to hire	Shows process speed
90-day success rate	Shows hiring quality

Do not optimize only time to hire. Fast wrong hires are expensive.

Founder network

Founder networks can produce high-trust candidates and references.

Ask other founders:

• Who was excellent but underused?
• Who left for reasons unrelated to performance?
• Who is looking for early-stage ownership?
• Who should I avoid for this type of role?

Candidate evaluation

Skills

Can they do the work at the required level?

Use evidence: past work, work sample, references, and specific examples.

Ask for concrete examples:

• “Show me something you shipped.”
• “What broke after launch?”
• “What tradeoff did you regret?”
• “What did customers/users say?”

Specific work beats abstract confidence.

Judgment

Judgment matters in startups because instructions are incomplete.

Ask:

• Tell me about a tradeoff you made.
• When did you choose speed over quality?
• When did you push back?
• What did you do with limited information?

Ownership

Ownership means the person closes loops.

Look for examples where they noticed a problem, acted without being asked, and followed through.

Speed

Startups need pace. Speed is not recklessness; it is the ability to move through ambiguity without waiting for perfect conditions.

Communication

Early teams need clear communication.

Evaluate:

• Written clarity
• Directness
• Listening
• Ability to explain tradeoffs
• Ability to say “I do not know”

Learning

The company will change. Hire people who learn.

Ask what they learned recently and how it changed their work.

Culture fit

Culture fit should not mean sameness. It should mean fit with operating values: ownership, honesty, customer focus, speed, quality, and respect.

Use “culture add” too. A candidate may strengthen the company by bringing a different background, working style, customer insight, or discipline. Do not confuse comfort with fit.

Integrity

Integrity is non-negotiable.

Watch for exaggeration, blame, disrespect, confidentiality issues, and inconsistency.

Motivation

Understand why they want this role.

Good motivation:

• Ownership
• Learning
• Mission
• Team
• Stage fit
• Craft

Weak motivation:

• Title only
• Startup glamour
• Escape from current job without interest in your work

Hiring Bar

The early hiring bar should be explicit.

Ask:

• Would we be excited to work with this person every week?
• Would this person raise the standard in at least one important area?
• Can they operate with the context and support we can actually provide?
• Do they make the team more capable, not just larger?
• Would we hire them again after seeing the interview evidence?

If the answer is “maybe, but we are desperate,” slow down. Desperation hires often create a larger problem.

India Angle

Recruiting in India often includes:

• Long notice periods.
• Counteroffers.
• Family and stability concerns.
• Salary variance by city, company type, and remote opportunity.
• Candidates with strong execution experience but limited startup exposure.
• ESOP skepticism or misunderstanding.
• Title sensitivity.
• Relocation and commute concerns.

Discuss these early. A candidate who cannot join for 90 days may still be worth it for a senior role. A candidate with a big-company background may still be excellent if they want builder work. A candidate who needs family confidence may simply need a clearer explanation of runway, role, and risk.

Work Sample Design

The work sample should resemble the job, not a puzzle.

Good work samples:

Role	Useful work sample
Engineer	Debug a small realistic issue, review code, design a feature tradeoff.
Designer	Improve a specific flow and explain tradeoffs.
Sales	Write outreach for a defined ICP and run a mock discovery call.
Customer success	Diagnose a failed onboarding and write a recovery plan.
Operations	Map a messy workflow and identify failure points.
Marketing	Rewrite positioning for a segment and propose a distribution test.
Founder associate	Take an ambiguous problem and produce a crisp operating memo.

Avoid unpaid projects that take many hours. Respect candidates. A short, realistic sample plus a discussion usually tells more than a long assignment.

Reference Calls

References are not a formality. They are pattern detection.

Ask:

• What kind of environment helped this person do their best work?
• Where did they need management support?
• How did they handle ambiguity?
• What happened when they disagreed?
• Would you hire them again for an early-stage startup?
• What should I watch for in the first 90 days?

Listen for hesitation. Also listen for context. A candidate can fail in a large company and thrive in a startup, or thrive in a structured company and struggle in ambiguity.

Closing Strong Candidates

Strong candidates are not closed by pressure. They are closed by clarity.

Your closing conversation should cover:

• Why this role matters now.
• What the candidate will own.
• What support they will and will not get.
• Runway and company risk at the right level.
• Compensation and ESOP in plain language.
• How success will be judged.
• Why the founder believes this candidate fits.
• What concerns the candidate still has.

Do not hide risk. The best early employees choose risk knowingly. That trust compounds after joining.

Recruiting Scoreboard

Recruiting improves when it is measured. Use a lightweight scoreboard for every role.

Metric	Why it matters
Qualified sourced candidates	Shows whether the role definition and channel are working.
Response rate	Shows whether outreach and employer story are credible.
Screen pass rate	Shows whether sourcing quality is high.
Work sample pass rate	Shows whether candidates can do the job.
Offer acceptance rate	Shows whether compensation, role, and story are competitive.
Time to close	Shows whether process is too slow.
First 30-day confidence	Shows whether evaluation predicted reality.
Source quality	Shows where strong candidates come from.

Do not overcomplicate this. A simple sheet is enough. The key is to notice where the funnel is broken.

Funnel Diagnosis

Symptom	Likely issue	Fix
Few candidates enter funnel	Role too vague or sourcing too narrow.	Rewrite role and add channels.
Many candidates, few qualified	Screening criteria too loose.	Tighten must-have skills and relevance.
Good screens fail work samples	Interviews are not testing the job.	Add realistic work sample earlier.
Good candidates drop out	Process slow, story weak, compensation unclear.	Improve closing and speed.
Offers rejected late	Risk, salary, title, family, or notice concerns surfaced too late.	Discuss constraints earlier.
Hires struggle after joining	Evaluation missed ownership, ambiguity, or onboarding needs.	Improve work sample and 30-day plan.

Recruiting is not only candidate judgment. It is process judgment.

Candidate Scorecard

Use the same scorecard for every candidate in a role.

Dimension	Evidence
Role skill	Work sample, past work, examples.
Judgment	Tradeoff discussion, decision reasoning.
Ownership	Stories of taking responsibility without being asked.
Speed	How quickly and cleanly they move through the process.
Communication	Clarity in writing and conversation.
Learning	Ability to absorb feedback and improve.
Startup fit	Comfort with ambiguity, constraints, and changing priorities.
Motivation	Why this company and role, not just any job.
Integrity	References, consistency, ownership of mistakes.

Score after each stage while memory is fresh. Do not let one charming conversation override weak evidence.

Founder Recruiting Blocks

Founders often become the bottleneck:

• Slow feedback after interviews.
• Unclear role requirements.
• Changing compensation mid-process.
• Selling the dream but not the real work.
• Avoiding rejection conversations.
• Delegating recruiting before the hiring bar is clear.

If hiring matters, the founder must own the bar. Recruiting can be supported by others, but early hiring quality is a founder responsibility.

Reader action

For your next role, create a recruiting tracker with columns:

• Candidate
• Source
• Why qualified
• Screen result
• Work sample result
• Interview feedback
• Reference result
• Offer status
• Concern
• Next action

Then write one clear reason why a strong candidate should join your startup despite the risk.

Also write one clear reason why the wrong candidate should not join. Recruiting is not about convincing everyone. It is about finding people who understand the risk and still choose the mission, role, and team.

Interview Calibration Loop

Founders often interview by instinct. Instinct is useful, but hiring improves faster when the team calibrates.

For each role, run a calibration loop:

Step	Practice
Define evidence	Agree what must be proven before offer.
Ask consistent questions	Use the same core questions for comparable candidates.
Score immediately	Write feedback before discussing with others.
Compare evidence	Discuss examples, not vibes.
Update process	If the process misses signal, improve it before the next batch.

A useful feedback note sounds like:

Evidence for hire:
- In the work sample, she identified the onboarding bottleneck and proposed a simpler flow.
- In the interview, she gave a specific example of handling ambiguity without waiting for a manager.

Concern:
- Has not worked in a company with less than 50 people.

How to test:
- Reference call should ask how she handled unstructured work and changing priorities.

A weak note sounds like:

Smart, good energy, seems like a fit.

Hire decisions should be made from evidence, not mood.

Candidate Experience

Candidate experience is part of employer brand, especially in small ecosystems where people talk.

Set these standards:

• Explain the process and timeline upfront.
• Do not create long unpaid assignments.
• Give candidates enough company context to make an informed decision.
• Move quickly when interested.
• Reject respectfully and clearly.
• Do not oversell stability, runway, or role scope.
• Keep compensation and location constraints visible early.

This matters in India because founder networks, operator groups, alumni communities, and city startup circles are dense. A sloppy process becomes reputation damage faster than founders expect.

Reference Pattern Sheet

After reference calls, summarize patterns:

Signal	Notes
Ownership
Speed
Ambiguity
Collaboration
Conflict
Integrity
Management needs
Would rehire?

Do not hunt only for praise. Ask, “What conditions help this person succeed?” A good hire with the wrong support system can become an avoidable failure.

Recruiting Operating SLA

Recruiting breaks when nobody owns the clock. Set a simple service level agreement for hiring.

Step	Target timing	Owner
New referral acknowledged	24 hours	Hiring owner
Resume/profile screen	48 hours	Hiring owner
First interview scheduled	Within 5 working days	Recruiting owner/founder
Work sample reviewed	48 hours after submission	Functional owner
Interview feedback written	Same day	Interviewer
Candidate update sent	Within 48 hours of decision	Hiring owner
Offer decision	Within 24 hours after final round	Founder/decision owner
Rejection note	As soon as decision is clear	Hiring owner

These numbers can change by stage, but the principle should not: candidates should not disappear into founder chaos. Slow process loses good people and damages trust.

Interview Panel Design

Even a tiny startup needs interview roles. Do not let every interviewer ask the same vague questions.

Interviewer	Evaluates	Should not evaluate alone
Founder/CEO	Mission, stage fit, ownership, values, closing	Deep technical skill unless qualified
Functional lead/founder	Core skill, work quality, tradeoffs	Culture alone
Future peer	Collaboration, communication, practical working style	Compensation or role scope
Customer-facing founder	Customer judgment and communication	Technical depth
Advisor/expert, if used	Specific seniority or domain bar	Final hiring decision

Before interviews, assign evidence:

• Who checks skill?
• Who checks ownership?
• Who checks ambiguity tolerance?
• Who checks communication?
• Who checks values and trust?

After interviews, discuss evidence in this order: must-have skill, stage fit, ownership, values, compensation/closing risk. This prevents charismatic candidates from winning before the evidence is reviewed.

Hiring Decision Memo

For important hires, write a short decision memo before making the offer.

Section	Prompt
Role	What bottleneck does this hire reduce?
Candidate	Why this candidate?
Evidence	What proof supports the decision?
Risks	What could make this hire fail?
Support plan	What must the company provide?
90-day outcome	What should be true after 90 days?
Compensation logic	Why this offer is fair and affordable
Decision	Hire, no hire, hold, or redesign role

This memo is most useful when the founder feels rushed. If you cannot explain the hire clearly in writing, do not compensate with enthusiasm.

Hiring Bar Calibration Board

Hiring quality drops when every interviewer privately uses a different bar. Before a role goes live, calibrate the bar.

Create a board with four columns:

Column	What to write
Must have	Skills, behaviours, and constraints without which the person cannot succeed.
Strong signal	Evidence that predicts success in this company, not just in a mature company.
Tradeable	Things you can compromise on if ownership, learning, and core skill are strong.
Disqualifier	Behaviours or gaps that would damage speed, trust, quality, or customers.

For each role, define examples:

Role:
90-day outcome:
Must-have evidence:
Work sample:
Interview evidence:
Reference question:
Disqualifier:
Tradeable weakness:
Final decision owner:

Review the board after the first five candidates. If everyone fails, the role may be unrealistic, the sourcing channel may be wrong, or the company may not be attractive enough for the bar it wants.

The hiring bar should be high, but not imaginary. A startup needs people who can succeed in its actual mess, not only people who look excellent in a polished interview process.

Recruiting Weekly Operating Review

Recruiting fails when founders treat it as occasional messaging instead of an operating rhythm. A startup does not need an HR department to run a disciplined hiring funnel. It needs one weekly review with honest numbers and decisions.

Run this review for every open role:

Metric	Question
Sourced candidates	How many relevant people did we identify this week?
Replies	Which messages produced real conversations?
Screen pass rate	Are we attracting the right people or filtering too late?
Work sample pass rate	Is the role clear and the bar realistic?
Interview feedback time	Are we moving fast enough for good candidates?
Offer stage	Are we losing candidates on cash, role, risk, timing, or trust?
Pipeline risk	Do we have enough qualified candidates for next week?

Use the review to make decisions:

Signal	Likely issue	Action
Many candidates, few screens pass	Sourcing is too broad	Tighten ICP and channels.
Good screens, weak work samples	Resume screen is overvaluing pedigree	Add practical evidence earlier.
Good candidates drop out	Process is slow or unclear	Shorten loop and improve communication.
Offers rejected on salary	Compensation is mismatched	Adjust scope, level, or cash/equity mix.
Offers rejected on risk	Story is weak	Explain runway, traction, role impact, and founder commitment.
No candidates from referrals	Team/network does not understand role	Rewrite role brief for referrals.

Candidate communication standard

Good candidates remember how the process felt. Set a simple standard:

After every conversation:
- Tell the candidate the next step.
- Give a realistic timeline.
- Do not disappear.
- Close the loop even on rejections.
- Do not oversell the company.

Fast, respectful rejection is better than polite silence. Many candidates you reject today may become customers, employees, investors, or referrers later.

Founder sourcing block

For important early roles, founders should personally source.

Use two weekly blocks:

• One block for identifying 30-50 relevant people.
• One block for writing thoughtful outreach and follow-ups.

Founder outreach works because early candidates want to understand the mission, risk, and seriousness from the source. Do not outsource all early hiring communication to generic job posts.

Recruiting retro after every hire

After a hire joins, answer:

• Which source produced the hire?
• Which interview step predicted success best?
• Which step added little signal?
• What did the candidate almost reject us over?
• What did we learn about our compensation, role clarity, and company story?
• What will we change before the next search?

Recruiting is a learning system. If every hiring process starts from zero, the company is wasting its own evidence.

Candidate Scorecard Calibration

A scorecard is useful only if interviewers interpret it consistently. Before interviewing, calibrate the bar with examples.

For each must-have, define:

Score	Meaning
1	Clear miss. Candidate lacks evidence and would need too much support.
2	Weak. Some signal, but risk is high.
3	Hireable. Can do the job with normal startup support.
4	Strong. Has repeated evidence in similar conditions.
5	Exceptional. Raises the bar and can teach others.

Example for an early sales hire:

Skill	1	3	5
Prospecting	Waits for leads.	Can build and work a focused list.	Has created pipeline from scratch in an ambiguous market.
Discovery	Asks generic questions.	Understands pain, buyer, urgency, and next step.	Can teach the founder something about the market through calls.
Resilience	Needs structure and brand.	Can handle rejection and iterate messaging.	Has proven grit in a low-brand, early-stage environment.

After the first few candidates, compare interviewer scores. If one person sees a 5 where another sees a 2, the scorecard is unclear.

Role-Specific Work Samples

A work sample should resemble the job without becoming unpaid labor.

Role type	Useful work sample	Avoid
Sales	Write outreach to a real ICP and role-play discovery.	Asking for a full GTM strategy.
Product	Prioritize a small set of customer problems with tradeoffs.	Long speculative product roadmaps.
Engineering	Small scoped task or architecture discussion based on a realistic constraint.	Free feature development.
Marketing	Rewrite positioning or draft a campaign from a brief.	Asking for a complete campaign plan.
Operations	Diagnose a messy workflow and propose a simple operating system.	Generic case studies unrelated to your company.

Tell candidates:

This exercise should take about [time].
We are testing [skills].
We will not use your work commercially.
You do not need polished design; we care about reasoning.

Respectful work samples improve signal and candidate trust.

Reference Checks For Early Hires

Reference checks matter more in small teams because one wrong hire changes culture quickly.

Ask references:

What kind of environment helps this person do their best work?
What kind of ambiguity can they handle?
Where did they need management support?
What would you trust them to own completely?
What would you not put them in charge of yet?
How did they respond to pressure or feedback?
Would you hire them again for an early-stage startup? Why or why not?

Listen for hesitation. References rarely attack candidates directly. The signal is often in pauses, narrowing language, or “they are great when…” conditions.

Do not use references to outsource judgment. Use them to verify the risks you already see.

Closing Candidates In India

Early candidates in India often evaluate more than salary. They may consider family expectations, stability, brand, commute or remote flexibility, ESOP credibility, founder trust, and whether the startup can survive.

Address the real questions:

Candidate concern	Founder response
”Is this company stable enough?”	Share runway, traction, funding path, and honest risks.
”Will my family understand this move?”	Give a clear company story the candidate can explain.
”Are ESOPs real?”	Explain grant size, vesting, exercise basics, and what is uncertain.
”Will I learn faster here?”	Show scope, ownership, mentoring, and customer exposure.
”Will the founder be reasonable?”	Run a respectful process and be transparent.
”Is the role real or chaotic?”	Share 90-day outcomes and decision rights.

Do not close by exaggerating. Good people join early startups because the risk is meaningful, not because the founder pretends there is no risk.

Final Hiring Decision Memo

For every important hire, write a short decision memo:

Role:
Candidate:
Why we need this role now:
Evidence they can do the job:
Evidence they fit early-stage conditions:
Main risks:
Reference signals:
Compensation:
90-day outcomes:
Decision:

This prevents “we liked them” hiring. It also creates a learning archive if the hire succeeds or fails.

Candidate Evidence Packet

A hiring decision should not depend on who argued most confidently in the debrief. Build an evidence packet for serious candidates.

Evidence	What to capture
Role scorecard	Must-have outcomes, skills, and behaviors.
Work sample	Output quality, assumptions, questions, tradeoffs.
Interview notes	Specific examples, not vibes.
Reference patterns	Repeated strengths, risks, management needs.
Motivation	Why this role, company, stage, and compensation mix make sense.
Red flags	Concerns and how they were tested.
Closing risk	Notice period, competing offers, family constraints, compensation gap.

The founder should be able to explain the hire in one paragraph:

We are hiring this person because they have evidence of [specific capability], they fit [stage need], their main risk is [risk], and we will manage that risk by [support or constraint].

Hiring Pipeline Health Review

Review the recruiting funnel weekly for important roles:

Funnel area	Founder question
Sourcing	Are we seeing enough candidates from the right channels?
Screening	Are we rejecting quickly and consistently?
Interviews	Are interviewers calibrated on the role scorecard?
Work samples	Are trials testing real work without wasting candidate time?
References	Are we learning patterns or only collecting compliments?
Offers	Are strong candidates accepting, hesitating, or dropping?
Onboarding	Are recent hires becoming productive fast enough?

Recruiting is not only filling seats. It is a system for increasing the quality of people trusted with the company’s scarce time and cash.

Offer Acceptance Risk Map

Before making an offer, map the risk:

Risk	How to handle
Compensation gap	Explain cash/equity tradeoff clearly; do not oversell ESOPs.
Family or location concerns	Discuss working model, stability, and expectations honestly.
Notice period	Keep engagement warm with useful context and founder time.
Big-company comfort	Explain startup ambiguity, pace, and role compression.
Competing offers	Know what the candidate optimizes for: learning, salary, title, mission, manager, flexibility.
Trust gap	Share customer proof, runway context, founder story, and role success plan.

Closing is not manipulation. It is helping a strong candidate make a clear-eyed decision.

Candidate Market Positioning

Strong candidates evaluate the company the way customers evaluate a product. They ask: why this company, why this role, why now, and why should I trust these founders?

Write a candidate positioning note for important roles:

Question	Founder answer
Why this role matters	The bottleneck this person will remove.
Why now	The company stage and trigger that makes the role urgent.
Why this founder/team	What the candidate will learn and who they will work with.
Why this market	Why the customer problem is worth years of work.
What is hard	Ambiguity, pace, pay tradeoff, lack of process, customer pressure.
What success looks like	First 90-day outcomes and long-term role path.
What the company will not promise	Inflated title, guaranteed wealth, fake stability, or vague ownership.

This note improves sourcing, interviews, referrals, and closing. It also keeps the founder honest. If the role cannot be positioned clearly, the role may not be ready.

Interview Debrief Discipline

Most hiring mistakes happen after the interview, when everyone relies on vibes.

Run a debrief within 24 hours:

Debrief question	Why it matters
What evidence did we observe?	Separates signal from personality preference.
Which scorecard criteria are strong?	Keeps evaluation tied to the role.
Which criteria are weak or untested?	Prevents confidence from filling gaps.
What did the work sample show?	Anchors judgment in output.
What concerns would make us reject?	Names risk before offer excitement.
What would onboarding need to cover?	Turns concerns into management plan if hired.
Would we hire this person if they had no brand-name background?	Checks pedigree bias.
Would we trust this person with scarce founder time?	Focuses on early-stage reality.

End with one decision: reject, hold, test further, reference check, offer, or redesign role.

Hiring should feel human, but the decision should be evidence-based.

Offer Debrief

After every accepted or rejected offer, run a short offer debrief. The hiring process should learn from the market.

Question	Why it matters
Why did the candidate accept, reject, or hesitate?	Reveals whether the role, compensation, risk, or story is working.
Which part of the process built trust?	Shows what to repeat.
Which part created doubt?	Shows what to fix before the next candidate.
Was compensation the real issue or the visible issue?	Candidates may cite salary when trust, role clarity, or family risk was deeper.
Did the candidate understand ESOPs and risk?	Prevents future resentment.
Did we oversell anything?	Protects culture and onboarding.
What should change in sourcing, interviewing, or closing?	Turns recruiting into an operating loop.

Capture:

Role:
Candidate outcome:
Main accept/reject reason:
Trust builder:
Trust breaker:
Compensation learning:
Role clarity learning:
Next process change:

A rejected offer is not wasted if it teaches the company how serious candidates see the opportunity.

Related links

• 82. Early Hiring
• 84. Culture
• 85. Compensation and ESOPs
• 100. Scaling Teams
• 150. Hiring Templates