TL;DR
A technical co-founder is a partner: they share the vision and the risk, take founder-level equity (often 10% to 50%), work for little or no salary early on, and help set product and company direction. A founding engineer is an early employee: they take a market-rate salary plus a smaller equity slice (typically 0.5% to 2%), and their job is to build the product fast, not to co-own the company. Same technical work, very different role, risk, and stake.
Which you need comes down to one question: do you need a partner, or an execution hire? If the company is fundamentally a long-term engineering company and you want someone who shares the risk and the upside, that's a co-founder. If you mostly need someone to build the product and you can pay a salary (usually after some funding or revenue), that's a founding engineer. This guide covers the exact differences, the equity, when to hire which, and the honest catch for pre-funding founders.
Key Takeaways
- A technical co-founder is a partner: they share the vision and risk, take founder-level equity (often 10% to 50%), and help set direction.
- A founding engineer is an early employee: market-rate salary plus a smaller equity slice (typically 0.5% to 2%), focused on building fast.
- Same technical work, very different role, risk, and stake.
- The deciding question: do you need a partner, or an execution hire?
- Choose a co-founder for shared long-term risk and upside; choose a founding engineer when you mainly need someone to build and can pay a salary.
What is a founding engineer?
A founding engineer is usually the first technical hire at a startup: a senior individual contributor who joins very early (often at pre-seed or seed, sometimes before you close funding) to build the product hands-on. They write most of the initial code, choose the stack, set up the infrastructure, and iterate fast on user feedback.
The defining traits:
- They code, most of the time. Building the product is the primary job, not managing people or setting three-year strategy.
- They wear many hats. Frontend, backend, DevOps, and sometimes talking to customers. They thrive in ambiguity.
- They help hire the next engineers and shape the early engineering culture, without being a formal manager.
- They're an employee, not an owner. "Founding" refers to being early and foundational to the product, not to founder status. They take a salary and a modest equity grant, not a co-founder's stake.
In short: a founding engineer is the person who ships the thing, hired for velocity, at the earliest stage.
Founding engineer vs technical co-founder: the real differences
Both are senior technical people at an early startup.
The difference is role, risk, and stake, not coding ability.
| Founding engineer | Technical co-founder | |
|---|---|---|
| Role | Early employee who builds the product | Partner who co-owns the company |
| Equity | ~0.5% to 2% (an option grant) | ~10% to 50% (founder equity, often near-equal) |
| Salary | Market-rate (or close), from day one | Little or none early on ("sweat equity") |
| Decision power | Executes the vision, owns technical architecture | Sets product, engineering, and company direction |
| Commitment | Full-time employee; can leave like any hire | All-in owner, tied to the company for years |
| Financial risk | Low (paid a salary) | High (bets years on uncertain equity) |
| How it evolves | Can grow into a CTO or Principal Engineer role | Stays an owner; leads or hands off as it scales |
The single clearest signal, if you strip away titles: equity and salary. Someone taking founder-level equity and forgoing salary is a co-founder. Someone taking a near-market salary and a 1%-ish option grant is a founding engineer, no matter what the title on the offer says. As founders on Hacker News and r/ycombinator repeatedly point out, the label is mostly noise; the cap table tells the truth.
When to hire a founding engineer (vs look for a co-founder)
Reach for a founding engineer when:
- You can pay a salary. Usually this means you have some funding or revenue. A founding engineer is a hire, and hires expect to be paid.
- You need velocity, not a partner. You already own the product vision and direction; what you need is someone to build it well and fast.
- You want to keep your equity. A founding engineer costs a few percent, not tens of percent. If you don't need a co-owner, you shouldn't pay co-owner prices.
- You can lead the technical direction (or have someone who can). A founding engineer executes; they don't usually set the whole strategy alone.
Look for a technical co-founder instead when:
- It's a deeply technical, long-term company where you want owner-level technical leadership committed for years (see do you need a technical co-founder?).
- You can't pay salaries yet and need someone to take the risk with you for equity.
- You need a genuine partner to share the load, the decisions, and the emotional weight of building, not just an executor.
The honest rule: if you can pay and you mostly need building done, a founding engineer is cheaper and keeps your equity. If you need a committed partner and can only offer equity, that's a co-founder.
Founding engineer equity: what's fair
For a founding engineer joining at seed or pre-seed, 0.5% to 2% equity is the common range, usually as stock options that vest over four years with a one-year cliff. It's higher than a normal early-employee grant because they're taking more risk and doing foundational work, but it is nowhere near a co-founder's stake.
The number moves with stage and cash: earlier and lower-salary leans toward the top of that range (or higher); later and fully-paid leans lower. What is not a founding-engineer grant is a co-founder's slice. If you're offering someone 15% to 50%, you're offering a co-founder deal, and you should expect co-founder commitment in return. Conversely, offering 0.5% to someone you're asking to build the entire product as a "co-founder" is the classic mistake that makes serious engineers walk. For the co-founder side of this, see how much equity a technical co-founder should get.
What about a CTO? (the quick distinction)
People often lump in a third title. A CTO is a technical executive: they mostly manage engineers, own technology strategy, and rarely write production code day to day. That role fits later (typically Series A and beyond, once you have five or more engineers), not at the idea or MVP stage. Hiring a CTO too early means paying executive money to manage a team that does not exist yet.
So at the earliest stage your realistic technical hires are a founding engineer (full-time builder) or a co-founder (owner-builder), not a CTO. If you specifically want senior technical judgment part-time without a full hire, that is a fractional CTO, which is a different tool again.
The honest catch for pre-funding founders
Here's what the "just hire a founding engineer" advice skips: a founding engineer wants a salary and a real equity grant, and the good ones are scarce. Pre-funding, with no salary to offer, you're competing for the same rare senior engineers that everyone wants, and you often can't afford or attract one yet.
That's the same wall as the co-founder search, just with cash instead of equity.
So for many founders the practical sequence is: get the product built and validated first, then hire a founding engineer once you have traction or funding to pay and attract one. Building first is what gives you the two things that make a founding engineer hire realistic, money to pay them, and a real product they'd be excited to join.
That is the gap we fill. Rather than spend months trying to attract, and afford, a founding engineer before you have funding, you hand the build to a small senior team: we scope the core flow, agree a fixed price up front, and ship it in 3 to 4 weeks as production-grade code you own, with auth, payments, and deployment included. You come out with a live product and real usage, which is exactly what makes a founding-engineer hire realistic later: you are recruiting on traction and able to pay, not pitching an idea. If you are stuck between 'find someone' and 'get it built,' bring us the version where it just gets built.
Common mistakes founders make
- Calling an employee a co-founder (or vice versa). The title should match the equity and commitment. Mismatches cause disputes and confuse investors.
- Offering co-founder work for founding-engineer equity. Asking someone to build the whole product for 0.5% "as a co-founder" won't attract anyone good.
- Trying to hire a founding engineer with no salary. Without cash, you're really looking for a co-founder, so pitch it honestly as one.
- Hiring a CTO at the idea stage. Paying executive salary to manage a team that doesn't exist yet is expensive overhead.
- Waiting to hire before there's a product or funding. Build and validate first; that's what makes the hire both affordable and attractive.
Related guides
- Do you need a technical co-founder?: the bigger decision this sits inside
- How much equity should a technical co-founder get?: the co-founder side of the equity question
- What is a fractional CTO?: the part-time senior-leadership alternative
- How to find a technical co-founder: if a partner is what you decide you need
- MVP development team: who you actually need to build an MVP
Frequently asked questions
What is the difference between a founding engineer and a technical co-founder?
A technical co-founder is a partner who co-owns the company: they share the vision and risk, take founder-level equity (often 10% to 50%), usually work for little or no salary early, and help set company direction. A founding engineer is an early employee hired to build the product fast: they take a market-rate salary plus a smaller equity grant (typically 0.5% to 2%) and execute the vision rather than own it. The clearest tell is equity and salary, not the job title.
Is a founding engineer a co-founder?
No. A founding engineer is an early, senior employee, not an owner. "Founding" means they are foundational to building the product and join very early, but they take a salary and a modest equity grant rather than a co-founder's stake, and they don't carry founder-level ownership or risk. Occasionally a founding engineer is brought on with near-co-founder equity and effectively functions as one, but in the standard case they are the first technical hire, not a founder.
How much equity should a founding engineer get?
At seed or pre-seed, a founding engineer typically gets 0.5% to 2% in stock options, vesting over four years with a one-year cliff. It's higher than a normal early-employee grant because of the risk and foundational work, but far below a co-founder's 10% to 50%. Lower salary and earlier stage push it toward (or above) the top of that range; a fuller salary and later stage push it lower.
Should I hire a founding engineer or find a technical co-founder?
Hire a founding engineer if you can pay a salary, you own the product vision, and you mainly need someone to build fast while you keep your equity. Look for a technical co-founder if it's a deeply technical, long-term company, you can only offer equity rather than salary, and you need a committed partner who shares ownership and direction. In short: pay-and-build points to a founding engineer; equity-and-partner points to a co-founder.
When should a startup hire a founding engineer?
Usually once you can pay a salary, which typically means you have some funding or revenue, and you have a product vision that needs building fast. Pre-funding with no salary to offer, attracting a strong founding engineer is very hard, so many founders get the MVP built and validated first, then hire a founding engineer on the back of traction and cash. Hiring one too early, before you can pay or attract them, tends to stall rather than help.
Founding engineer vs CTO: what's the difference?
A founding engineer is a senior individual contributor who codes most of the time and joins at seed to build the product. A CTO is a technical executive who mostly manages engineers and owns technology strategy, and fits later (typically Series A and beyond, with five or more engineers). At the idea or MVP stage you want a builder (founding engineer or co-founder), not an executive; a CTO at seed stage is usually expensive overhead. For part-time senior judgment without a full hire, a fractional CTO is a separate option.
Sources & references
This guide synthesizes established startup hiring practice and the wider founder-community discussion (including Hacker News and r/ycombinator) on the founding-engineer versus co-founder distinction.
- Y Combinator, Startup Library: first technical hires, co-founders, and equity for early-stage startups
- Paul Graham, How to Start a Startup: founders, early hires, and why the technical team matters
This article is general educational information, not legal or financial advice. Equity and compensation vary widely, so have a startup lawyer paper any co-founder or employee equity agreement.
