Founding Engineer Salary in 2026: Cash vs. Equity Data

A founding engineer in 2026 commands roughly a $185K to $220K base salary and, as the literal first engineering hire at a seed-stage startup, a median equity grant near 1.5% of the company (fully diluted). Those are the defensible anchors. The catch: the public sources you would Google to confirm them disagree with each other by as much as $80K on base pay alone, and “1.5%” is really the middle of a range that runs from 0.5% to 4%. This guide triangulates the real numbers, shows you why every source contradicts the next, and helps both sides price the cash-versus-equity trade honestly.

How much does a founding engineer make in 2026?

The short answer: a base salary in the $185K to $220K range, plus equity that depends far more on when you join than on your résumé. For the first engineer at a pre-product seed company, the median equity grant is about 1.5%; for a senior engineer joining an already-staffed startup, it can be a fifth of that.

Here is what the four most-cited public sources actually report for a founding engineer’s base salary:

The equity side is cleaner because one source dominates it. Per Carta’s data on tens of thousands of startups, the median equity grant to a startup’s first five hires falls off a cliff:

Keep both anchors in mind as you read: a base near $195K and a first-hire equity grant near 1.5%. Everything below is about how much to trust each number and how to price the two against each other.

Why every “founding engineer salary” number disagrees

Public founding-engineer salary data is folklore dressed up as data. The clearest proof is that two “average” figures for the exact same job title, pulled the same month, differ by roughly $80K: Glassdoor reports an average of $217,555 while Comparably reports $136,698. A founder opening three browser tabs to sanity-check an offer gets a different answer on each one.

There are three reasons the numbers scatter this badly.

Self-report bias. Glassdoor and Comparably rely on people volunteering their pay. Who self-reports skews the pool, and self-reporters often blend base, bonus, and the paper value of equity into one “salary” number. That is how Glassdoor’s 75th percentile balloons to $289K while its methodology says nothing about how those 76 data points were verified.

Tiny samples hiding behind big headlines. The most quoted 2026 figure, a $195K median, comes from a recruiting firm that headlines its analysis with “1.9 million job postings.” That 1.9 million is the size of the firm’s total scraped database, not the founding-engineer sample. The actual founding-engineer sample is small, and here is the tell: the firm published two near-identical articles that contradict each other on how many postings they analyzed, one saying 55 and the other 197, with slightly different percentiles ($175K/$215K versus $170K/$218K). When a source cannot agree with itself on its own sample size, treat the round headline number as an anchor, not a fact.

No normalization. “Founding Engineer,” “First Engineer,” and “Founding Software Engineer” are the same role with three titles, posted across cities with different costs of living and, sometimes, different currencies. Nobody reconciles them before averaging. Un-normalized, apples-to-oranges data is exactly how you get an $80K spread on one title.

The honest takeaway is not “the data is useless.” It is: no single public number is a benchmark. You have to triangulate across independent methods and present a range, which is what the rest of this guide does.

The base salary, triangulated

Cross the sources that use different methods and they converge. Recruiting from Scratch’s scrape of posted ranges lands at a $195K median. Pave’s payroll-integration data for a senior software engineer at a Tier-1 startup lands at a $187K median. Two methods that share no data source, landing within $8K of each other, is the strongest signal in this whole picture. That convergence is why $185K to $220K is the base range worth quoting.

How to read those percentiles matters as much as the median:

• 25th percentile (~$170K): an early-stage company with tight runway, a strong equity story, or a more junior “founding” hire.
• Median (~$187K–$195K): the honest default for a senior engineer taking the first-engineer seat at a funded seed startup.
• 75th percentile (~$215K–$218K): a competitive offer for a proven operator, or a company that has decided to lead on cash because it cannot lead on equity.

Does location still move the number?

Weakly, and the data won’t let you pin it down. The scraped-postings source claims San Francisco pays only about 3% more than remote ($200K versus $195K). Glassdoor’s self-report says SF runs about 25% above the national average ($271K versus $217K), with New York roughly 5% higher. Both cannot be right.

The most likely reconciliation: remote-first hiring has compressed the old SF premium on posted base salary, while self-reported total comp still shows a large Bay Area gap that is probably equity- and bonus-driven. Present location as a band, not a multiplier, and do not let one source’s “3%” or “25%” masquerade as settled fact.

The equity ladder: 1.5% for hire #1, and the 43% cliff

For the first engineering hire at a seed-stage company, the median equity grant is 1.50% fully diluted, per Carta. But the median hides the real story, which is the spread: the 25th-to-75th percentile range on hire #1 runs from 0.50% to 4.00%, an eightfold difference. “Founding engineer equity” is not a number. It is a negotiation range, and where you land inside it depends on how early, how essential, and how underpaid-in-cash you are.

The second story in the ladder is how fast it collapses:

The single steepest step is #1 to #2, a 43% drop. For a candidate, this is the whole case for being first: the premium for employee #1 over employee #2 is larger than any raise you will negotiate later. For a founder, it is a reminder that the first grant sets the reference point every subsequent hire will anchor to.

Why the same engineer is worth 1.5% or 0.33%

Here is the nuance almost no salary page explains. Carta’s “1.5% for hire #1” describes the literal first employee at a pre-product seed company. Pave’s cut for a “senior software engineer (P4–P5)” across all startup stages puts median equity at just 0.33% (75th percentile 0.62%, 90th 1.24%). That is roughly 4.5x less equity for the same caliber of human.

The difference is not skill. It is dilution position. Equity prices the risk you absorb, not the title on your offer letter. The identical engineer is worth ~1.5% as employee #1 at a four-person company with no product, and ~0.33% as a senior IC at a twenty-person Series A where the risky years are behind everyone. If you are a candidate weighing two “founding-ish” offers, this is the lever: you are paid in equity for earliness, not for seniority. If you are a founder, it means you cannot copy a Series A company’s grant table for your first hire, because your hire is buying much more risk.

The 2026 shift: AI pressure is lifting early-hire equity

The old folklore, “take less cash, more equity,” has a real tailwind in 2026, but only for specific profiles and only at the smallest companies. The direction is more equity, and the driver is the AI talent crunch colliding with shrinking teams.

Per Carta:

• At startups valued $1M to $10M, the median initial equity grant to AI/ML engineers rose about 64% over two years, the sharpest jump among early-stage companies.
• Across AI/ML engineers broadly, the median initial grant grew roughly 31% between January 2024 and February 2026, nearly triple the growth rate of the overall employee population.

The mechanism is arithmetic. The median seed-stage team is now about four people. Smaller teams mean fewer heads to split the option pool with, so more equity is available per hire. And a sub-$10M company that cannot match Big Tech cash has exactly one competitive card to play, which is ownership. AI has simultaneously made small teams viable (fewer engineers get more done) and made the engineers who can build with it scarce enough to bid up.

So the equity tailwind is real, but narrow. It applies most to scarce AI/ML profiles at the smallest companies, which is also, not coincidentally, the exact hire this guide is about. If you want the longer argument for why founders keep hiring engineers at all in an AI world, we made it in why founders still hire engineers.

Pricing the trade: cash vs. equity, honestly

“Less cash, more equity” is a slogan until you put numbers on it. The honest way to price the trade is to convert the equity grant into a paper dollar value at the current valuation, then treat that number with appropriate suspicion.

Pave’s worked example is a clean template. A fair, roughly 75th-percentile offer might be $200K cash plus 0.85% equity, which is about $85K in gross equity value at a $10M valuation. So the “total” reads like $285K. But the $85K is not $85K in your bank account. It comes with four heavy caveats every candidate should say out loud:

1. It vests over ~4 years. You earn it by staying, not by signing.
2. It is illiquid. You cannot spend it until a sale or IPO that may never come.
3. It dilutes. Every future round issues new shares, and your percentage shrinks unless you are topped up.
4. The valuation is a guess. At $10M pre-revenue, the price is a negotiation, not a market.

That is why you should never publish or accept a single “year-one cash-out” number for a founding-engineer offer. Equity is not year-one cash. The right move is to price the two components separately: benchmark the base against the $185K to $220K range, then treat equity as a probability-weighted bet you are choosing to make, sized by how much you believe in the company.

Questions the founder should answer in the offer: What is our fully diluted share count? What percentage, not just how many options? What is the current preferred price the equity is valued against? What is the vesting and cliff? Is there acceleration on acquisition?

Questions the candidate should ask: How much runway is left? What does the cap table look like after the next round’s expected dilution? What did the last common-stock (409A) valuation say? Am I being paid a genuine first-hire premium, or a senior-IC grant with a “founding” title on it?

A clear, well-structured offer answers these before the candidate has to ask. For the full picture on structuring the role itself, from the job description to the interview loop, see our guide on how to hire a founding engineer, and for how this hire fits the broader sequence, the first five hires at a seed-stage startup.

Turn the benchmark into a real offer with Kit

A defensible number is worthless if the hire itself is a mess. The value of getting to “$195K base, ~1.5% equity, priced honestly” is that you can now run a clean, fast, fair process around it, and that is where Kit comes in.

Kit is an AI-native applicant tracking system built for startups making exactly this hire. Once you have your range, Kit carries it into the actual work:

• A founding engineer template gives you a pre-configured pipeline, so you are not designing a hiring process from scratch while also running a company.
• GitHub-integrated code assignments let you screen for the ownership and build-from-zero instinct a founding engineer actually needs, instead of a whiteboard proxy for it.
• Structured scorecards and team voting keep the evaluation anchored and comparable across a tiny team where every hire is existential and one bad gut call is expensive.
• The offer stage is where your benchmarked base and your first-hire equity grant become a concrete, well-documented offer, the kind that answers a candidate’s cap-table questions before they have to ask.

And because equity is a sequence, not a single decision, the 1.5% you give hire #1 sets the reference for hires #2 through #5. Planning that ladder deliberately, rather than reacting to each candidate’s ask, is the difference between a cap table you designed and one that happened to you. Kit is built to keep that whole sequence, from benchmark to offer to your fifth hire, in one place.

You cannot control that public salary data is messy. You can control whether your first engineering offer is defensible, honest, and fast. Start free and run your founding-engineer hire on numbers you can stand behind.

Salary figures reflect published 2025–2026 data from Recruiting from Scratch, Pave, Glassdoor, and Comparably; equity figures reflect Carta’s compensation data. Public sources disagree, so treat every number here as a triangulated range, not a guarantee.