The Short Answer
A founding engineer is your first real engineering hire. They take a salary and around 1%, they build most of the product, and they make hundreds of decisions a week without asking. They think like an owner and commit like an employee, which is exactly the combination you want and a genuinely rare one.
The role only works if you hire for the right shape of person. You need a generalist who will do frontend, backend, deployment, the database and the thing nobody wants to touch, without a specification and often without praise.
The risk here is subtler than in the other two routes. Hiring a specialist when you needed a generalist, or paying co-founder equity for employee commitment. Both are expensive, and neither is obvious until several months in.
How Much Equity Is Normal
The usual range at pre-seed is 0.5% to 2%, with a median near 1%. The benchmarks agree closely:
| Hire | Typical equity | Source |
|---|---|---|
| First technical hire | 1.5% average | Carta, 2026 State of Seed |
| First non-founder engineer | 1% | Pave, mid-2026 |
| Hire #2 | 0.85% | Carta |
| Hire #3 | 0.5% | Carta |
| Hire #5 | 0.33% | Carta |
| Founding engineer at Series A | 0.2% to 0.6% | 2026 benchmarks |
These figures have drifted upward through 2026 under pressure from AI hiring. If you are competing for someone strong, treat them as a floor rather than a ceiling.
Vesting applies here too: four years, one-year cliff, same as anywhere else. It is standard, expected, and nobody will be surprised by it.
This Is Not a Co-Founder
The difference is not skill. The same person could take either job. It is ownership, risk and what they want from their life.
| Founding engineer | Technical co-founder | |
|---|---|---|
| Equity | Around 1% | 25 to 50% |
| Pay | Real salary, possibly below market | Little or none |
| Decides | How it gets built | What gets built, and whether the company should exist |
| Wants | Autonomy, interesting problems, no management | To run a company with you |
| If they leave | Painful, survivable, you backfill | Existential, and messy on the cap table |
Be clear which one you are offering, and use the right words in the conversation. Most failed first hires are a mismatch of expectation rather than of ability: someone took a job they thought was a partnership, or a founder gave away a quarter of the company to someone who wanted a job.
What You Are Looking For
- Breadth over depth. They will write the frontend, the backend, the deployment pipeline and the email templates. A deep specialist in one layer will be idle or blocked most weeks.
- They have been early somewhere before. Someone whose entire career is large companies with product managers and design systems is in for a shock, and you will absorb the cost of it.
- They ship rough things on purpose. Early products need speed and iteration. Perfectionism at this stage is a liability wearing a respectable coat.
- They are comfortable with no spec. You will say something vague and need them to come back with a working version and good questions.
- They will talk to customers. The best first engineers want to hear the complaints directly rather than through you.
- They do not want your job. Owner instincts, employee commitment. Someone who wants to be a founder should be offered a co-foundership or will eventually leave to go and be one.
Red Flags
- They ask what the role is exactly. Wanting a defined remit is reasonable in a real company and fatal in a five-person one. The job is everything nobody else is doing.
- They want to specialise. A frontend specialist at hire number one leaves you paying someone to wait for a backend that nobody is building.
- They expect co-founder equity. Not unreasonable as a wish, but it means you are having different conversations. Resolve it before an offer, not after.
- They only want to work on new things. Most of the job is fixing, maintaining and reworking what already exists. Greenfield enthusiasm alone burns out fast.
- They will not do a paid trial. A short paid project tells you more than four interviews, and any strong candidate is evaluating you too.
- They cannot explain their work to you. You are going to be their main collaborator. If you cannot follow their reasoning now, you will not be able to steer later.
- They are dismissive about your not being technical. It signals what the next two years of every disagreement will feel like, and it will not improve once they have equity.
What to Ask
“Tell me about a time you shipped something you weren't proud of.”
Good answer: A story about a deliberate trade-off, why speed mattered, and what they went back and fixed later.
Walk away: Never. Either they have not worked somewhere early, or they cannot tell the difference between standards and perfectionism.
“What's the first thing you'd want to change about how we build?”
Good answer: A specific observation, usually about process or feedback loops, offered without contempt.
Walk away: Nothing, or a wholesale rewrite of everything. One is incurious, the other is a warning.
“How do you feel about talking to customers directly?”
Good answer: Enthusiasm. The best first engineers want the complaints unfiltered.
Walk away: A preference to receive requirements from you. That is a bigger-company instinct, and it will slow everything down.
“What do you want to be doing in three years?”
Good answer: Building, with more scope, ideally here. Honest about wanting a bigger technical remit.
Walk away: Running their own company. Perfectly respectable, but you are a stop on the way and should price that in.
Making the Offer
Be explicit about all three components: salary, equity percentage, and vesting terms. State the equity as a percentage rather than a share count, since a number of shares means nothing without a denominator and hiding behind that is a well-worn trick you should not adopt.
If you are paying below market, say so plainly and say what they get instead: equity, autonomy, scope, the chance to shape the whole system. Sophisticated candidates respect the honesty and can price the trade. Pretending a below-market offer is competitive simply means the good ones decline and you never learn why.
Buy the technical assessment you cannot do yourself. Pay an independent senior engineer for a few hours to run the technical portion of the interview. This is normal, it costs a fraction of a bad first hire, and a good candidate will think more of you for treating the decision seriously.
And if a salary is out of reach right now, say that out loud rather than dressing up an unpaid role in employee language. The honest alternatives are paying for a defined build or finding a technical co-founder who is taking the risk with you.
What This Looked Like For Us
Theanna is the arrangement this page describes. A non-technical founder, and a founding engineer rather than a technical co-founder. Kyle Cupples is Theanna's founding engineer and technical lead, and the platform is built by a non-technical founder using the same AI tools we teach founders to use.
Two things from that experience are worth passing on. The first is that the generalist point above is not a preference, it is the whole job: the useful early engineer is the one who will do the deployment and the email templates and the unglamorous fix, and who does not need a specification to start. The second is that a non-technical founder can genuinely run this relationship, but only by being honest about which parts of it you cannot assess, and buying help for those rather than bluffing.
Most founders reading this cannot afford a founding engineer yet, which is the awkward part. Until you can, Theanna is built to cover the gap. Build Mode™ is an agent that knows your business and keeps context between sessions, in plain language, and connects through MCP to Claude Code or Cursor so your build tool works from real context. On the Connector tier at $99 a month you get two technical office hours a month with Kyle, which is a founding engineer's judgment on your actual problem without a founding engineer's salary and equity.
The Theanna Accelerator concentrates that into four weeks at $1,497 and 0% equity, with four build sessions with Kyle, one a week, taking a product that demos to one a customer can use.
Connector also includes the community of 300+ women founders through a peer feed and founder circles, and for this decision it does something the benchmarks above cannot. Carta and Pave tell you the national median. The founder two stages ahead of you tells you what she offered, what the candidate pushed back on, and whether the person is still there a year later. When you are making a hire you have never made before, in a role you cannot fully assess, that difference is most of what you need.
This is why Theanna is built for non-technical women founders specifically. Every question on this page has an answer that circulates informally among people who have hired before: is that equity ask reasonable, is this candidate senior or just confident, is it normal to pay someone to run your technical interview. Those conversations happen in networks women founders have historically been outside of, and the absence is not a gap in ability. It is a gap in access, and it shows up as founders paying more, waiting longer, and finding out in month six. Closing that gap is the product.
To be clear about what that is: office hours are judgment, not labour. When the product becomes the business and needs continuous work, hire the engineer. Use this page to do it well, and use the trial project, because the first one matters more than any hire that follows.
Frequently Asked Questions
How much equity should a founding engineer get?
The common range at pre-seed is 0.5% to 2%, with a median around 1%. Carta's 2026 State of Seed data puts the first technical hire at about 1.5% on average, falling to 0.85% for the second hire, 0.5% for the third and 0.33% by the fifth. Pave's mid-2026 benchmark sits at 1% for the first non-founder engineer at a US seed-stage startup. Engineers joining at Series A with a founding engineer title typically receive 0.2% to 0.6%. These numbers have been drifting upward through 2026 under pressure from AI hiring, so treat them as a floor rather than a ceiling if you are competing for someone strong.
What is the difference between a founding engineer and a technical co-founder?
Ownership and mentality, not skill. A technical co-founder takes 25% to 50%, usually little or no salary, and owns technical direction as a partner who is expected to disagree with you. A founding engineer takes around 1% plus a real salary, has enormous influence over how things get built, and does not want to run the company. The distinction matters because the two roles attract different people. Offering co-founder responsibility at founding-engineer equity will lose you good candidates, and offering co-founder equity to someone who wants an employee's commitment gives away a quarter of your company for nothing.
Should a founding engineer take a salary?
Yes. That is much of what separates the role from a co-foundership. A founding engineer may accept below-market pay in exchange for meaningful equity and unusual autonomy, but they are an employee and should be paid like one. If you cannot pay a salary at all, you are not hiring a founding engineer, you are looking for a co-founder or for contract work, and it is better to say so plainly than to describe an unpaid role in employee language.
When should I hire a founding engineer instead of an agency?
When the product has become the business rather than a project with an end. An agency is right for a defined scope with a finish line. A founding engineer is right when you need someone who holds the whole system in their head, makes hundreds of small judgment calls a week without asking, and is still there in eighteen months when something breaks at 2am. The signal is usually that you have customers, the product needs continuous change, and the cost of explaining context to a rotating cast of contractors has started to exceed the cost of a salary.
How do I hire a founding engineer if I'm not technical?
Judge what you can observe and buy help for what you cannot. You can assess whether someone explains trade-offs clearly, whether they ask about customers, whether they have worked somewhere early before, and how they behave when you disagree with them. What you cannot assess is code quality, so pay an independent senior engineer for a few hours to run the technical portion of the interview. That is a normal thing to do, costs very little relative to a bad first hire, and a good candidate will think better of you for taking the decision seriously.