Every company has a founding DNA. It is not in the mission statement or the values deck. It is in the first five people who sat in the room and decided how things would work. Those five people set the bar for quality, the tolerance for ambiguity, and the speed of execution. Every hire after them is evaluated against the standard they set.
Why do the first five matter more than the next fifty?
Because culture compounds. Hire someone who cuts corners and the next hire learns that cutting corners is acceptable. Hire someone who documents everything and the next hire learns that documentation is the norm. The first five people create the gravitational field that every subsequent hire enters.
This is not abstract. We have watched companies where the first engineer set a standard of shipping tested, documented code, and every engineer after them matched it. We have also watched companies where the first engineer shipped fast and broke things, and three years later the team is still paying the interest on that technical debt. The first hire's habits become the team's habits.
The same applies to every function. Your first salesperson sets the tone for how you treat customers. Your first operations hire sets the standard for how you run processes. Your first marketer sets the voice for how you communicate. Choose carefully.
What does slope over intercept mean?
Intercept is what someone knows today. Slope is how fast they are learning. In a startup, slope wins every time.
The candidate with ten years of experience at a big company has a high intercept. They know a lot. But their slope is often flat. They have been doing the same thing the same way for years. The candidate with three years of experience who has built three different things has a lower intercept but a steep slope. They learn fast. In eighteen months, the steep-slope candidate will know more than the high-intercept candidate and will be better adapted to your specific context.
The test for slope: ask them to explain something they learned in the last ninety days. Not something from a book or a course, but something they figured out by doing. The specificity and recency of the answer tells you their slope. If they cannot name anything, their slope is flat, regardless of what their resume says.
What should you look for in each of the first five roles?
The specifics vary by company, but the patterns are consistent.
| Role | What to look for | What to avoid | The key question |
|---|---|---|---|
| First engineer | Has shipped a full product end-to-end | Specialists who need infrastructure | "Show me something you built alone" |
| First salesperson | Entrepreneurial AE, 3-7 years closing | VP of Sales who wants to manage | "Walk me through a deal you closed from cold to signed" |
| First marketer | Can write, analyze, and run experiments | Brand strategists who need a budget | "What would you write about us this week?" |
| First operations person | Has built processes from scratch | Big-company ops who maintain systems | "What process would you fix here first?" |
| First designer | Can do research, UX, and visual design | Pure visual designers who need a brief | "Redesign our onboarding flow right now" |
The common thread: every first hire should be able to do the work themselves, not manage someone else doing it. Managers become relevant when there is a team to manage. At hire one through five, there is no team. There is the work.
How do you run reference checks that actually work?
The references the candidate gives you are curated. They will say good things. The references that matter are the ones you find yourself: former managers, former colleagues, people who worked with the candidate but were not prepped.
The process: after the final interview, ask the candidate for three references. Then find two more on your own through LinkedIn or your network. Call all five. Ask one question: would you hire them again, and why?
The curated references will say yes immediately. The uncurated ones will pause. That pause is the signal. A long pause followed by "yes, but..." tells you more than any interview. A quick, enthusiastic "absolutely" from someone who was not prepped is the strongest signal you can get.
Skip reference checks and you are hiring based on the candidate's ability to interview. Some people are great at interviews and terrible at the job. Reference checks are the only way to find out before you make the offer.
What does a bad early hire actually cost?
The salary is the smallest cost. A bad hire at one hundred twenty thousand per year costs sixty thousand in salary before you let them go at the six-month mark. But the real costs are larger.
The opportunity cost: six months of output you did not get. The management cost: the hours you spent trying to make it work instead of doing your own job. The team cost: the morale hit when the team watches someone underperform while they carry the weight. The cultural cost: the lowered bar that the next hire is measured against.
Add it up and a bad early hire costs two hundred to three hundred thousand dollars and six months of lost time. At an early-stage company, that can be the difference between making it and not. Take the extra two weeks to check references. Take the extra interview to be sure. The cost of slowness is trivial compared to the cost of wrongness.
Frequently asked questions
What should you look for in a first hire?
Slope over intercept: how fast they learn, not what they already know. Curiosity about your specific business. Evidence they have built something, even a side project. And the ability to operate without structure, because you do not have any yet.
How much should you pay early hires?
Market rate base salary plus meaningful equity, typically point-five to two percent for the first ten employees depending on role and seniority. Do not lowball. A great hire at market rate produces ten times the return of an average hire at a discount.
Should early hires be generalists or specialists?
Generalists. Your first engineer should ship product, not manage infrastructure. Your first marketer should write, analyze, and run experiments. Specialists become valuable later when there is enough work to fill a narrow role.
How do you interview for a role you have never done?
Use the working session format: give the candidate a real problem from your business, thirty minutes of context, and sixty minutes to work through it with you. You learn how they think. They learn what the job involves. Both sides make a better decision.
What is the biggest mistake in early hiring?
Hiring for the company you want to be instead of the company you are. A big-company executive will struggle in a five-person startup. You need people who thrive in ambiguity and build structure, not people who need structure to thrive.