Hiring a founding engineer in San Francisco starts with a clear decision about what this person will own, what support they will have and why the opportunity is worth leaving their current role for. The title alone does not answer any of those questions.
For an SF startup, the useful distinction is between access to engineers and a reason for the right engineer to join. This guide sets out Corellia’s recommended approach to the brief, assessment and offer.
In this guide
- Define the first six months before the technology list
- Separate hands-on building from future leadership
- Make the SF working week explicit
- Explain what your opportunity offers alongside larger employers
- Assess the decisions behind delivered work
- Make salary and equity understandable separately
- Use one decision process and address the actual hesitation
- Questions founders ask
Define the first six months before the technology list
A founding engineer brief should describe the product and decisions that must move forward, rather than collect every technology the company might use.
Write down the customer problem, the current product state and the next meaningful milestone. A prototype that needs reliable deployment creates a different brief from a functioning product that needs customer integrations. Both might use the same programming language.
Then separate three kinds of ownership:
- Delivery: the features, systems or customer outcomes this engineer will be responsible for.
- Decisions: the choices they can make without waiting for a founder, including technical trade-offs and operational priorities.
- Support: who reviews difficult decisions, handles product questions and helps when something fails.
Be specific about the starting point. Explain what already exists, where it is fragile and what you are prepared to replace. A candidate should be able to picture their first meaningful piece of work before the final interview.
The founding engineer hiring brief provides a useful starting point. Use it to agree the job internally before writing outreach.
Separate hands-on building from future leadership
A founding engineer should know which responsibilities are immediate and which are possibilities as the company grows.
If most of the job is building the product, say that. If you also need someone to recruit colleagues, review their work and manage delivery, explain how much time those responsibilities will require. Do not offer a future CTO title as a substitute for agreeing authority today.
A useful interview question is: what would this person still need to do themselves after the next two engineers join? It exposes whether you want a senior individual contributor, a player-coach or a leader whose main job will become hiring and management.
Connect that answer to your first five engineering hires. Avoid promising a management path that the next hiring plan does not support.
Make the SF working week explicit
Office expectations need to appear in the brief, because a candidate cannot assess a role without understanding its location and routine.
There is no single SF working pattern. Two founding engineer adverts checked on 31 October 2026 described different arrangements: one was in person, the other hybrid. [Sources 1 and 2]
State the address or area where work happens, the required days, the reason for those days and any regular overlap with other time zones. Explain whether relocation support is available rather than leaving candidates to infer it.
Do not treat housing and commuting as minor objections. The US Bureau of Labor Statistics identifies housing as the largest expenditure category in its 2023 to 24 SF metropolitan household study. That is context for a practical conversation, not a salary calculator for an individual engineer. [Source 3]
Ask whether the arrangement is workable before investing in several interviews. A precise requirement is more useful than describing the team as flexible and revealing a different expectation later.
Explain what your opportunity offers alongside larger employers
A startup should explain its actual scope and working environment rather than claim it can match every alternative available to an engineer.
AI laboratories are one visible part of that alternative set. OpenAI’s published SF software engineering roles include product and infrastructure ownership, so autonomy is not a benefit only small companies can claim. [Source 4]
Make your own distinction concrete. Which customer will this engineer speak with? Which product decisions can they influence? What can they own from design through operation? How often will they work directly with the people deciding what to build?
Also explain the constraints. If there is no dedicated platform team, limited design support or a changing product direction, put that into the conversation. Someone who chooses those conditions knowingly is making a different decision from someone who discovers them after joining.
Assess the decisions behind delivered work
Relevant work is stronger evidence than a familiar employer name or a confident account of being comfortable with ambiguity.
Ask candidates to explain a system they were permitted to discuss, including what they personally built, what failed and how they changed their approach. Separate their contribution from the work of the wider team.
For the practical assessment, use a bounded problem resembling the role. For example, ask how they would make an unreliable integration observable, then work through a small part together.
Agree the assessment criteria first: problem framing, technical judgement, communication and response to new information. Tell candidates whether AI tools are allowed and assess their ability to explain and verify the result. Offer an alternative format where needed, and keep the task proportionate.
A non-technical founder should involve a credible technical assessor. That person should test the agreed mandate, rather than substitute their preferred stack for the company’s needs.
Make salary and equity understandable separately
The package should show cash, equity and benefits as separate components, with enough detail for a candidate to compare them.
Use the salary guide with the relevant city, specialism and level, checking whether the result is observed advert evidence or a labelled modelled estimate.
Corellia’s 24 October 2026 dataset contains 19 SF adverts in the reviewed founding-engineer cohort across engineering disciplines. Only four have a recorded funding stage: three Seed adverts and one Series B advert. No numerical equity ranges are recorded in that cohort. This is too thin to establish a typical package by stage, and missing equity data does not mean that an employer offers none. [Source 8]
Two further adverts checked on 31 October 2026 illustrate different packages: one listed $150,000 to $220,000 plus unspecified equity; another listed $90,000 to $140,000 and 2.5% to 5% equity. [Sources 1 and 5]
For equity, explain the instrument, grant amount, percentage basis and date, vesting, exercise cost, leaving provisions and approvals still required. Set out assumptions and confirmed terms clearly. US option taxation depends on the option type and events such as exercise or sale. [Source 6]
California also has pay-transparency requirements. Employers covered by the posting requirement, including employers with at least 15 employees under the state’s guidance, must include a pay scale for covered vacancies. Check the official guidance and obtain advice on your circumstances. [Source 7]
Use one decision process and address the actual hesitation
A clear process assigns each interviewer a question to answer and gives candidates a reliable next step.
Before making an offer, ask what remains unresolved about the work, package, working pattern or company risk. Treat each answer differently. More cash does not resolve an unwanted commute; a larger option grant does not establish who owns architecture.
Do not describe a candidate’s decline as a lack of ambition. They may prefer a different stage, a particular technical problem or a working arrangement you cannot offer. Record the reason they actually give, including when they choose not to share one.
Agree an offer conversation, provide written terms and let the candidate ask questions of the relevant decision-maker. An artificial deadline cannot repair an unclear role. The aim is an informed decision on both sides.
Questions founders ask
Do we need a founding engineer or a CTO?
Choose by the work and decision authority needed now. Hands-on delivery and responsibility for the entire technical organisation are different mandates, even when one person may eventually do both.
Must they have worked at an SF startup before?
No. Test the relevant work, judgement and motivation directly. Previous experience can supply evidence, but a location or title should not replace assessment.
What is the right founding engineer equity percentage?
There is no universal percentage established by the examples in this guide. Compare the scope and grant terms, and check current, relevant evidence before setting a package.
Should we require five days in the office?
Require the arrangement the work genuinely needs, explain why and communicate it early. Do not imply that every SF startup uses the same policy.
Can a recruiter help before the role is finalised?
Yes. Founding engineer recruitment can begin with clarifying ownership and trade-offs before approaching candidates.
Examples are individual adverts, not benchmarks. Legal and tax points are summaries; take professional advice.
Sources
Sources checked 31 October 2026.
- Founding engineer advert, in-person SF role: duties, location and advertised package. Checked 31 October 2026.
- Founding engineer advert, hybrid SF role: hybrid arrangement. Checked 31 October 2026.
- US Bureau of Labor Statistics, SF metropolitan consumer expenditure study, 2023 to 2024: household expenditure context, released 16 January 2026.
- OpenAI, software engineer, cloud infrastructure: example of an alternative engineering mandate.
- Founding engineer advert with cash and equity on YC: advertised cash and equity. Checked 31 October 2026.
- IRS, Topic 427: Stock options: high-level US tax distinction.
- California Department of Industrial Relations, pay transparency FAQs: posting requirements.
- Corellia, employer-advert dataset collected 24 October 2026, founding-engineer cohort audit: 19 SF records. See the salary source collection.
If you are defining your next founding engineer hire, Start a conversation.
Start a conversation