Short version: your first engineer's compensation has two levers, salary and equity, and founders almost always over-think the salary and under-explain the equity. A first engineer at a funded early-stage startup typically takes a base somewhat below big-company rates in exchange for an equity grant that is meaningful, often in the range of half a percent to two percent depending on stage and seniority. The number that matters most is not either figure in isolation. It is whether you can explain the whole package honestly, including what the equity is really worth and what it is not.
I sit in on a lot of these offer conversations, and the pattern is consistent. The founder has spent two weeks negotiating ten thousand dollars of base salary and about ninety seconds thinking about an equity grant that could end up being the single largest line in the person's compensation or worth nothing at all. That ratio of attention is backwards, and it produces offers that either scare off good people or quietly resent the company later.
The two numbers, and why founders get the mix wrong
Early-stage compensation is a trade. You are usually asking a strong engineer to take a base below what a large, stable company would pay, and you are compensating for that gap with equity and with the upside, autonomy, and impact of being early. Common shape in 2026: an early-stage startup might offer a base in the low six figures plus a real equity grant, where the base runs perhaps twenty to fifty percent under big-company rates and the equity is meant to bridge the difference. Exact figures swing hard with your location, your stage, and the candidate's seniority, so treat any single number as a starting point rather than a rule.
The mistake is treating these as two separate negotiations instead of one trade-off. A founder will fight hard on salary to protect runway and then hand over an equity grant they have not modeled, or protect equity obsessively and lose a great hire over a salary gap that a slightly larger grant would have closed. The right move is to think in total package and to be deliberate about the mix, because a candidate's situation, savings, family, risk tolerance, changes which lever is worth more to them. Your first engineer is not an employee in the ordinary sense, a point I make in your first engineer doesn't have to be an employee, and the compensation should reflect that they are taking a real bet on you.
Equity: what the first engineer should actually get
Equity is where founders most need to slow down. A useful anchor that has been around for years: a company ought to give roughly ten percent in total to its first ten employees. That is a guideline, not a formula, and real grants vary a lot, but it sets the order of magnitude. For a genuine first engineer, especially one joining at pre-seed or seed and taking real risk, grants commonly land somewhere from about half a percent to two percent, with the higher end reserved for very senior people joining very early when the risk is highest.
Several things move the number. Earlier stage and higher personal risk push the grant up. More seniority and more scope push it up. A higher base salary pushes it down, because it is a trade. And the funding climate matters: boards and investors in a tighter market scrutinize dilution closely, so equity-for-all is common but grant sizes are under more pressure than they were a few years ago. Whatever you land on, explain the vesting, typically four years with a one-year cliff, and be honest that the grant is a bet that may be worth a great deal or nothing. Engineers who have been around know the difference between a founder who levels with them about this and one who waves a big percentage around as if it were cash. This is the same honesty I argue for in paying a fractional CTO in equity: equity is a real instrument with real terms, not a bargaining prop.
Salary: below market, but honest about it
The base salary should be below big-company rates, and you should say so plainly rather than pretending your offer competes with a large employer's on cash. What you are offering instead is equity, impact, and the chance to shape the company technically from the start. A strong engineer evaluating an early-stage offer already knows this trade exists. Trying to disguise it insults their intelligence.
That said, below market is not the same as too low to live on. An offer that forces a strong candidate to take a painful lifestyle cut on top of the equity risk is asking them to bet twice, and the best people will simply choose a different startup that asks them to bet once. Pay enough base that the person is not anxious about rent, then make the equity the reason the total is compelling. And resist the urge to win the negotiation. You want this person motivated and unresentful for years, not feeling they got squeezed in week one, because the cost of a demotivated first engineer dwarfs the salary you saved.
The offer conversation that builds trust
How you deliver the offer matters as much as the numbers, because it is the candidate's first real look at how you handle something high-stakes and personal. Walk them through the whole package, base and equity together, and explain your reasoning rather than just stating figures. Tell them why the base is where it is, what the equity represents, how vesting works, and what you honestly think the upside and the risk are.
Be ready for them to negotiate, and treat that as a good sign rather than an irritation, because an engineer who negotiates thoughtfully is showing you the judgment you are hiring them for. Decide in advance where you have room, on base, on equity, on a signing bonus, and where you do not, so you can respond cleanly instead of improvising. The whole interaction is a preview of working with you, and a founder who is transparent, prepared, and fair in the offer sets a tone that pays off long after the number is forgotten. If you are unsure what a fair package looks like for your stage, that is a reasonable thing to get a second opinion on before you send it, and a fine reason to book a call; you can also see how we think about pricing and scope for the leadership side of these decisions.
Frequently asked questions
How much equity should my first engineer get?
For a genuine first engineer taking real early-stage risk, grants commonly run from about half a percent to two percent, with the high end for very senior people joining very early. The old guideline that the first ten employees share roughly ten percent sets the right order of magnitude. Stage, seniority, base salary, and your dilution constraints all move the exact number.
What salary should I pay my first engineer?
Below big-company rates, usually by something like twenty to fifty percent, with equity bridging the gap. But not so low that the person is taking a painful lifestyle cut on top of equity risk, because that asks them to bet twice and the best candidates will pass. Pay enough that rent is not a worry, then let the equity make the total compelling.
Should I lead with salary or equity?
Think in total package and present both together. Founders tend to over-negotiate salary and under-explain equity, which is backwards. Decide your mix deliberately based on the candidate's risk tolerance and your runway, and explain the reasoning behind both numbers rather than defending each in isolation.
Is it bad if my first engineer negotiates the offer?
No, it is usually a good sign. An engineer who negotiates thoughtfully is demonstrating the judgment you are hiring them for. Decide in advance where you have room and where you do not so you can respond cleanly, and treat the conversation as the relationship-setting moment it is rather than a contest to win.