A founding engineer title should lead to a conversation about responsibility, authority and ownership. It does not tell you enough about any of them on its own. Compare the decisions you would make, the support around you and the equity terms, whether the advert says founding, early or senior engineer.
The first engineer hired into a company may establish much of its technical foundation. A founding engineer in a new specialist function may join a business that already has several engineers. Those are different jobs, even when the title sounds similar.
Use the founding engineer brief to see how a founder should describe the work. Then turn that brief around: what would you need to know before taking it on?
Ask what is being founded
Start by asking what already exists. Is there a working product, a customer base, a codebase, a deployment process and someone with technical responsibility? Which of those would you inherit, and which would you establish?
A role may be founding because you are the first engineer outside the founding team, the first specialist in a discipline or the first engineer in a new location. Ask which meaning the company intends.
Find out what would be different if the title simply said engineer. If the answer is broader decisions, customer access and responsibility for future hiring, explore those commitments. If the answer is mainly a sense of belonging, assess the work and package independently of the label.
The most useful description names the company’s current problem and what you will own in solving it. It should remain clear even after the title is removed from the page.
Compare responsibility with authority
Broad responsibility needs a route to decisions. Ask who decides the technical direction, what you can change independently and how a disagreement with a founder is resolved.
Use a concrete example. If a customer commitment requires a risky shortcut, can you change the scope, delay the release or require additional testing? Who joins that decision, and who communicates the outcome?
| Area | Questions to resolve |
|---|---|
| Product | Do you help choose the problem, or implement a defined plan? |
| Architecture | Which decisions are yours, and who reviews them? |
| Delivery | Who agrees the scope and changes a commitment? |
| Reliability | Who owns incidents, access and recovery? |
| Hiring | Will you assess candidates or help define the team? |
| Customers | Can you speak directly with the people using the product? |
You can prefer either a broad or a focused role. The problem is accepting one while the company expects the other.
Find the support behind the ownership
Ask who can help when the work moves beyond your current experience. A first engineer may need specialist support in security, design, infrastructure or a regulated domain. Find out whether that support is available and who can approve it.
Discuss the working relationship with the founders. Are they looking for someone to challenge the brief, or someone to deliver a direction they have already chosen? How often will you review priorities together?
An early engineer joining an established technical lead may receive more review and narrower ownership. That can be a strong choice if you want to develop a particular skill. The right role depends on what you want to practise, not how early your employee number is.
The technical leadership mandate guide helps distinguish technical influence, people management and wider organisational responsibility. Ask which of those the company expects from you now.
Treat equity as a set of terms
Ask for the proposed instrument, number of shares or options, fully diluted percentage and calculation date. Then ask about vesting, exercise price, exercise windows, approvals and what happens when you leave.
A percentage alone cannot tell you the eventual value. New share issuance and option-pool changes can dilute ownership. [Source 1] Your rights and costs also depend on the plan and grant documentation.
For US options, the distinction between statutory and nonstatutory options matters to tax treatment. [Source 2] For a UK EMI proposal, confirm the qualifying conditions and the terms of the actual grant. [Source 3] Do not assume a founding title creates a particular scheme or tax result.
Ask how the company explains the balance between cash and equity for this role. If you are taking on broad responsibility with limited support, that should be part of the discussion rather than an expectation left behind the title.
Use advert evidence without turning it into an entitlement
Corellia’s October founding-engineer research contains individual equity disclosures, but it does not establish a typical percentage by employee number or funding stage. The examples below show why the terms need to stay attached to the work.
| Anonymous advertised role | Advertised salary | Advertised equity |
|---|---|---|
| London founding full-stack engineer | £80,000 to £100,000 | 0.5% to 1% |
| New York founding software engineer | $160,000 to $250,000 | 0.5% to 2% |
| SF seed-stage Staff/ex-founder engineering scope | $180,000 to $250,000 | 1% to 3% |
These disclosures were checked on 31 October 2026, with salary collection dates retained in the underlying research. [Sources 4 to 6] The collection does not provide a reliable mapping from hire number to grant size, and stage coverage remains thin.
Use the examples to formulate questions: what scope is being compensated, what experience is expected and what cash trade-off is involved? Use the salary guide for broader city and role context, keeping its labelled estimates separate from observed adverts.
Understand how the role could change
Ask what happens after the next few hires. Will you continue as a technical individual contributor, become a manager or help appoint a specialist leader? Those routes need different expectations and support.
Do not assume that being the first engineer means becoming the future CTO. Discuss the decisions you want to own and the work you want to keep doing. A clear technical path can be more useful than an uncertain promise of a larger title.
The first five engineering hires guide offers a founder’s perspective on complementary roles. Ask where your responsibilities would expand and where another hire would take over.
Agree when to revisit the scope and package. The review should examine the work and contribution at that point, with a named owner, rather than rely on an informal promise that everything will be reconsidered after funding.
Get the practical agreement clear
Before accepting, write a short account of the role in your own words. Include the initial outcome, decisions you own, support available, reporting line and the main uncertainties. Ask the founder to correct anything that does not match their understanding.
Read the employment and equity documents alongside that account. Separate what is agreed now from a future intention or a grant still awaiting approval. A useful title should summarise the agreement, not substitute for it.
Finally, choose the role for the experience it gives you and the commitments you can make. You may thrive with broad early ownership, or prefer to join a little later with stronger support. Either can be a serious engineering decision when the scope is clear.
If you are considering your next technical role, Start a conversation.
Examples are individual adverts, not benchmarks. Legal and tax points are summaries; take professional advice.
Sources
- Carta: option pools and equity ownership, primary equity-management explanation, checked 31 October 2026.
- IRS Topic 427: stock options, official guidance, checked 31 October 2026.
- GOV.UK: Enterprise Management Incentives, official guidance, checked 31 October 2026.
- Founding full-stack engineer advert, London startup, £80,000 to £100,000 with 0.5% to 1% equity, checked 31 October 2026.
- Founding software engineer advert, New York startup, $160,000 to $250,000 with 0.5% to 2% equity. Salary collected 24 October and equity checked 31 October 2026.
- Staff/ex-founder engineering advert, seed-stage SF startup, $180,000 to $250,000 with 1% to 3% equity. Salary collected 24 October and level/equity checked 31 October 2026.
The questions, decision framework and suggested wording are Corellia Talent’s editorial recommendations.