Cap Table Decoded
Cap Table DecodedFounding Engineer Equity Expectations vs. Early Hires at Series A
Equity NormsLong read

Founding Engineer Equity Expectations vs. Early Hires at Series A

Earlier-stage engineers accept more risk and uncertainty, justifying steeper equity grants.

· 8 min read

Founding engineer equity expectations versus early hires at Series A turn on timing and risk. The same engineer should expect more ownership when joining before there is a product than after Series A funding. For an ML engineer evaluating an AI startup job, stage, decision-making authority, cash, and equity terms provide a more useful comparison than the prestige of being called “founding.

Why the same engineer commands fundamentally different equity at different stages

An engineer can be offered a “founding engineer” role at a four-person pre-seed company and another at a twenty-person Series A company, with very different ownership attached. The first offer asks the engineer to help make the company viable, while the second comes from a business that has already cleared some of its hardest hurdles.

Before there is a product, an engineer is betting on technical choices, whether customers will want it, and a team that has yet to prove it can work together. At Series A, some of those questions have answers. The engineer’s skill has not become less valuable, but the company no longer needs to offer the same ownership to compensate for the same unknowns.

A prestigious title does not turn an established engineering seat into the first technical hire at a pre-product business. The relevant questions concern when the engineer joins, what remains unresolved, and what responsibility the role actually includes. Without that frame, a candidate can mistake a smaller grant for an insult, or a flattering title for compensation.

How cap-table logic translates risk into a percentage — and why the gradient is steep

A cap table shows who owns the company. At the earliest stage, the ownership offered to a hire also reflects how much uncertainty that person agrees to absorb. There may be no product, no evidence of product-market fit, and no proven team. Equity compensates for taking that bet when the company has little else with which to make it attractive.

As the company grows, later hires get to build on work that earlier hires had to do from scratch. Each addition can reduce the unresolved risk facing the next person through a stronger team, a working product, or evidence that customers want it. The starting point changes. A company that has raised Series A funding has survived the period when most startups die, so its next engineer enters a narrower risk profile.

Dilution adds another layer to the calculation. Each later funding round cuts the founding engineer’s ownership percentage, so the engineer should expect to keep a smaller stake than the grant they start with. A meaningful pre-seed grant can become materially smaller after Series B. The early percentage therefore compensates for uncertainty while also facing more rounds of dilution before a possible exit.

What the equity gradient actually looks like across the first five hires

In Carta’s H1 2026 grant-level data, hire #1 has the highest median equity grant on a fully diluted basis. That is the clearest starting benchmark in the supplied data. It ties ownership to entry order rather than to a job title that companies use inconsistently. The first hire enters with the least established foundation beneath the role.

Across the first five hires, the useful comparison is how far the company has progressed when each person joins. The available figures do not establish a complete five-hire ladder, so they do not support a precise percentage for every seat. Precision would be misleading here. What they do establish is that the first-hire benchmark belongs to a different negotiating context from an early role at a company already shipping a product.

Pave’s founding-engineer percentile bands cover seed-to-Series A roles, so they compare a different group from one made up of first employees. The populations are not interchangeable. A lower benchmark for a role called “founding engineer” does not contradict Carta’s first-hire pattern when the company has already reduced its risk. For offer evaluation, the source’s population must match the job’s actual stage before its median becomes a useful anchor.

What cash looks like at each stage — and why it moves in the opposite direction from equity

Cash rises as the company’s risk falls. Earlier hires usually take a lower salary and more equity, while later hires get cash closer to market rates and a smaller ownership stake.

In the 2026 stage bands, base compensation for a seed founding-engineer is in the low-to-mid hundreds of thousands. Series A founding and early engineering roles sit in the mid-to-upper hundreds of thousands. These broad bands leave room for offers to vary. Companies using the same title can have very different funding, runway, and room to pay.

Bonuses do not reliably close the gap. Cash bonuses are uncommon at pre-seed and seed, and those that exist tend to depend more on milestones than on annual targets. Signing bonuses appear in a minority of Series A offers, primarily to offset unvested equity at a previous employer.

Compare total compensation over a realistic period, including both salary and equity. Cash has a different economic role from illiquid equity. Comparing equity with salary takes assumptions about how much dilution it will face and what it could be worth.

The AI talent market and what it has done to the equity floor in 2026

Carta’s data shows AI/ML-specific equity grants growing faster than generalist engineering grants over the past two years. That changes the benchmark for a specialist role. A 2024 reference point for an ML/AI founding engineer is now too low, even if it once described a reasonable offer. General engineering data can therefore underprice the same job in 2026.

The upper end has moved differently, however. The very large grants common in 2021 have largely disappeared, narrowing the realistic top end for pre-seed founding hires. Both developments can be true at once.

Strong founding-engineer candidates commonly have multiple active offers when deciding, so speed-to-offer can rival an incremental equity increase in determining which company closes the hire. The negotiation is not just about the percentage. For candidates, this makes data on what the role pays now more useful than an old benchmark or an unusually large grant someone got years ago.

The founding engineer role versus an early Series A hire — what the equity difference actually buys

The first founding hire absorbs career risk that the twentieth hire at a Series A company does not face. The work itself is also different. With no product, playbook, or platform team, the founding engineer sets technical constraints and makes choices that later engineers inherit. A larger grant pays for making those decisions before the company knows which ones will work.

That responsibility extends beyond one technical specialty. Founding work can span backend, frontend, infrastructure, and product decisions, while the scope narrows as a company scales. Early judgment also sets engineering standards. The next hires inherit not only the code but the expectations about quality and how technical work gets done.

For an engineer evaluating an offer, the test is concrete. Does the role include genuine technical direction-setting and product influence, or is it a senior individual-contributor seat with a flattering label? The former may justify the higher end of the Series A range. The latter should be compared with other early-employee roles rather than with the first hire at a pre-product company.

Management duties sharpen that distinction further. A founding engineer who will manage others, set technical direction, and represent engineering to investors should be at the top of the range for that stage. A founding role with only individual-contributor duties should be nearer the middle. Both roles have value, but their grants should reflect what each person does, even if they share a title.

The strongest objection to prevailing equity norms — and what it reveals about the negotiation

The strongest objection is that a stage-based benchmark can hide a mismatch between responsibility and reward. A company may ask for founding-level ownership of decisions while offering early-employee equity and unclear authority. Competitive cash may explain the mix of cash and equity, while the grant’s fit with the work requires a separate assessment.

“Founding engineer” can describe a role with fuzzy decision rights and limited strategic influence, despite suggesting the opposite. When the company pivots, the title supplies no chain of command to rely on. An engineer who negotiated the label but not the authority can discover that the supposed founding role offers little control over the decisions it must implement.

There is a legitimate counterargument to much larger grants. Dramatically above-market equity can raise the question of why the company needs to offer so much. A generous percentage is not automatically reassuring. The same risk premium that attracts a candidate can signal uncertainty the candidate needs to understand, making unusually large grants harder to sell than they first appear.

Negotiating on the basis of a title or benchmark requires understanding the role’s underlying scope. A founding label with small equity backed only by the promise of competitive salary makes for a weak package. Engineers should price that as an early-employee offer unless the authority and ownership terms back up the founding label.

How do you evaluate and negotiate a founding engineer equity offer?

The headline percentage is the least useful number on its own. To evaluate the economics, ask for the number of shares granted, total shares outstanding, current preferred price, vesting schedule, expected dilution from future rounds, refresh policy, and acceleration mechanics. Those inputs explain what the percentage represents. They also expose differences between offers that look similar at first glance.

Start with the post-money valuation and calculate the grant’s value today as the baseline for analysis. That calculation is not a promise of realizable cash. Next, work out what the grant could be worth in realistic exit outcomes, with honest estimates of dilution from future rounds. Compare those scenarios with the unvested RSUs or deferred compensation that would be left behind at a current employer, because the startup’s equity pitch competes with that amount.

Standard four-year vesting with a one-year cliff is the baseline. Double-trigger acceleration on change of control and extended post-departure exercise windows are negotiable at the founding level. Ask whether refresh grants are standard at the 24-month mark and whether the offer documents them or leaves them to future discretion.

Use Carta’s first-hire data for pre-seed roles and Pave’s percentile bands for seed-to-Series A offers. An offer below Pave’s 50th-percentile figure deserves an explicit explanation when the job claims founding-engineer responsibilities. For AI/ML roles, name the specialist premium directly rather than allowing a generalist or outdated benchmark to set the anchor.

Leverage also extends beyond the headline grant. Candidates with multiple offers are especially well placed to negotiate vesting mechanics and refresh policy, which are less visible and more flexible than the percentage. Warm introductions and direct referrals are also common routes into the best founding-engineer jobs. A candidate already invited into that process may have more negotiating leverage than someone applying cold.

The timing of this work is important. Learning the right benchmark after anchoring on the wrong one can damage the relationship even if the negotiation closes. Understand the stage, scope, and terms before the first compensation conversation. Companies know these numbers, and engineers who do not are negotiating blind.

Filed underEquity Norms

More in Equity Norms