What is a founding engineer? Role, equity, salary, and how to hire one
The term “founding engineer” gets thrown around loosely, which makes it one of the hardest roles to hire for, because half the people involved are not picturing the same job. A founder hears “first engineer.” A candidate hears “almost a co-founder.” A recruiter who has not done these searches hears “senior engineer who joined early.” Those are three different deals, and getting them confused is how offers fall apart at the equity conversation.
I have run founding-engineer searches for early-stage companies, and the pattern is consistent: the search goes well when the founder can clearly articulate what the role is, what it owns, and what it is worth, and it stalls when any of those three is fuzzy. This guide is meant to make all three clear, so you can decide whether you need a founding engineer, and if so, hire one without the avoidable mistakes.
What a founding engineer actually is
A founding engineer is typically the first engineering hire, or among the first few, and often the first non-founder employee. The defining feature is not the title. It is the scope. A founding engineer builds the first version of the product, sets the technical foundations that every later hire inherits, and does it under real ambiguity, before there is a roadmap, a process, or product-market fit.
The cleanest way to understand the role is by contrast.
Founding engineer versus senior engineer. A senior engineer joins a system that already exists and makes it better. A founding engineer creates the system. They pick the stack, set the deployment approach, establish the code-quality bar, and shape the engineering culture that the next ten hires absorb. As one industry guide puts it, the senior engineer joins a moving system while the founding engineer creates the initial one. That difference shows up in the day-to-day: a founding engineer spends as much time deciding what to build and what to skip as actually building.
Founding engineer versus co-founder. A co-founder is a partner, not a hire. They take inception risk, share the earliest uncertainty, and typically hold equity in the double digits. A founding engineer joins after the company concept exists and takes execution risk instead. They get meaningfully more equity than a normal early employee, but an order of magnitude less than a co-founder. If someone is genuinely sharing the founding risk from day zero, they are a co-founder, and you should structure it that way.
Founding engineer versus CTO. A CTO is, eventually, an executive: they own long-term technical strategy, build and manage the engineering organization, and translate technology into business outcomes. A founding engineer is a builder-first individual contributor who ships code daily. Many strong founding engineers grow into the CTO seat as the company scales, but on day one the jobs are different. If what you need is someone to manage a team and set multi-year strategy, you are looking for a leader. If what you need is someone to build the product and set its technical bar, you are looking for a founding engineer.
The Pragmatic Engineer’s breakdown of the role captures the breadth well: a founding engineer turns the founder’s vision into shipped product, works across the full stack and into DevOps, makes build-versus-buy calls constantly, talks to users directly, and does a pile of non-coding work, from interviewing later hires to weighing in on the pitch. An engineer who resists the product, support, and customer-facing parts of the job is usually a poor fit, no matter how strong they are technically.
How much equity a founding engineer should get
This is the question that decides most founding-engineer offers, and it is where founders most often either lowball and lose the candidate or overshoot and regret it later. The good news is that there is solid benchmark data.
Carta, which holds the largest dataset of US startup cap tables, shows the first engineering hire receiving a median grant around 1.5 percent, declining with each subsequent hire to roughly 0.33 percent by the fifth hire and down toward 0.18 percent by the tenth. Index Ventures, drawing on more than twenty thousand option grants, benchmarks a senior engineer at the seed stage at roughly 1.0 percent of fully diluted equity, with mid-level around 0.45 percent and junior around 0.15 percent. Pave puts the first-engineer range at roughly 0.33 percent at the median to 1.24 percent at the 90th percentile.
So the realistic range for a true founding engineer is roughly 0.5 to 2 percent, depending heavily on stage and on how early they are. The earlier the company and the higher the risk the person is taking, the closer to the top of that range. By the time you are at Series A, the same role lands lower, because the risk is lower and the equity is worth more.
xychart-beta title "Median equity grant by hire number" x-axis ["Hire 1", "Hire 2", "Hire 3", "Hire 5", "Hire 10"] y-axis "Equity %" 0 --> 1.6 bar [1.5, 0.85, 0.5, 0.33, 0.18]
It is worth knowing that many founders and investors argue the benchmarks are too stingy. Sam Altman has written that companies should give at least 10 percent in total to their first ten employees, and that while founders deserve a large premium for starting earliest, it should not be 100 or 200 times what employee number five receives. Y Combinator’s guidance points the same direction: be generous with the earliest hires, because they are taking real risk and their upside is what makes the offer competitive against a safe big-company job.
My practical advice: anchor on the Carta and Index numbers so you are not wildly off market, then lean generous for the genuine first engineer, because that person is choosing you over a much safer paycheck and you want them fully bought in. The difference between 1 percent and 1.5 percent is rounding error to your cap table and everything to how the candidate feels about the bet.
Salary, and the cash-versus-equity trade
Equity is only half the offer. Founding engineers still need a real salary, and underpaying on cash to “save it for equity” tends to filter out exactly the experienced people you want, who have mortgages and options elsewhere.
Pave’s data puts base salary for a senior software engineer in the top US markets, the profile most founding engineers fit, in roughly the 187,000 to 235,000 dollar range, with the median near 187,000. Founding-engineer base offers commonly land somewhere between 150,000 and 210,000 depending on stage and location, with the understanding that the candidate is often accepting somewhere around half to four-fifths of big-tech total comp in exchange for the equity upside.
The way to frame the trade-off, which Sam Altman also argues, is to target a total expected value that is competitive with a strong big-company offer, then shift the mix toward equity. A candidate who could earn 400,000 in total comp at a large tech company is not going to take 150,000 with a tiny equity grant. But they may well take 190,000 with a meaningful grant, because now the expected value is in the same neighborhood and the upside is theirs. If your cash is tight, your equity has to do more work, and you have to be honest about that math with the candidate rather than hoping they do not run it.
When to hire a founding engineer, and when not to
Timing matters as much as the offer. Hire a founding engineer when you have validated the problem enough to give real direction, you can articulate what success looks like in the first ninety days, and you can offer meaningful equity. The role pays off when there is genuine product to build and own.
Hold off, or use a different model, in two situations. If you are still exploring the idea and have not validated anything, a senior contractor working part time can give you execution capacity at lower risk than a full-time founding hire, and you preserve equity for when the picture is clearer. And if you are a solo non-technical founder who needs to get to a first version, a fractional or contract senior engineer can sometimes get you there faster than a months-long founding-engineer search, though you should plan to bring the foundational work in-house before it calcifies.
The two failure modes are mirror images. Outsourcing too long means the early work does not hold up and a future founding engineer inherits a mess. Hiring too early means you burn equity and runway building the wrong thing before you know what the right thing is. The window to hire a founding engineer opens when you can answer, concretely, what this person will build in their first quarter.
If you do go the nearshore route for cost or talent reasons, the same seniority bar applies, and our guide to nearshore hiring in Latin America walks through how to do that without diluting the bar.
What a great founding engineer looks like
Once you know you need the role, the evaluation is different from a normal senior screen. The technical bar is necessary but not sufficient. The traits that actually predict success are about judgment and ownership.
High ownership. The best founding engineers behave like partners. They see a gap and close it without being asked, they set standards that others inherit, and they treat the product’s success as their own. This is the trait that most separates a great founding engineer from a merely strong senior one.
Comfort with ambiguity. The job is acting on half-defined ideas. As one hiring guide bluntly notes, execution breaks when the first engineer lacks judgment, product sense, or the stomach for ambiguity. You are not hiring someone to be handed tickets. You are hiring someone to decide what the tickets should be.
Generalist instincts over deep specialization. Early on, breadth beats depth. A strong generalist who can learn a new part of the stack in a week is more useful than a specialist who has mastered one framework. The founding engineer who can move across frontend, backend, infrastructure, and a bit of everything else is the one who keeps the product moving.
Pragmatism. Great founding engineers reach for boring, proven technology they know well rather than the newest shiny tool, because the goal is to ship and iterate, not to build a resume. Technical taste at this stage means choosing the option that lets the company move fast and change direction, not the one that is most impressive.
The way you screen for these is the same way you should be writing the role in the first place: specifically. Vague job descriptions filter out exactly the candidates you want, which is a problem I have written about in how to write a job description engineers actually read. For a founding role, that means describing the actual problem, the actual stage, and the actual ownership on offer, not a generic list of requirements.
The role is in demand, and the bar is high
If it feels harder to hire founding engineers than it used to, that is because it is. The phrase has real momentum: search volume for “founding engineer” has been climbing, and recruiters who specialize in early-stage leadership searches have reported running substantially more of these engagements year over year. Startup hiring overall surged alongside the AI wave, with generative-AI and LLM skills driving a large share of new postings, and “AI engineer” topping LinkedIn’s fastest-growing roles. The best builders have more options than ever, which means the offer, the clarity, and the speed of your process all matter more.
That demand is also why the founding-engineer search overlaps so heavily with hiring AI and ML engineers. A large share of the founding-engineer roles I see today are at AI-first companies, where the first engineer needs to be both a strong generalist builder and comfortable shipping on top of foundation models.
If you are about to make your first engineering hire and want a second opinion on the scope, the offer, or where to find the right person, book a free strategy call. Getting the first engineer right is the highest-leverage hire most founders ever make, and it is worth getting a clear-eyed read before you start.