What a founding engineer actually does

A founding engineer is one of the first two or three engineers at a startup, hired before there is a product team, a roadmap you did not write, or a process to follow. The job is to build the first real version of the product, own most of the stack alone, and make technical decisions the company will live with for years. You trade a market salary and a safety net for a large equity grant and unusual reach. That trade is the whole story, and most of this post is about reading it honestly.

The title is also used loosely. Some companies call the fifth or tenth hire a founding engineer because it helps close the offer. The test is not the title, it is the scope: are you building the first version, or maintaining someone else's? This post is about the first kind. If you want the broader case for joining early, read is a startup job worth the risk alongside it.

What does a founding engineer actually do day to day?

On a normal week you write most of the code, pick the stack, set up the infrastructure, talk to the first customers, and fix the thing that broke at 11pm because there is no one else on call. There is no specialization yet. You are the backend engineer, the frontend engineer, the person who configures the database, and the person who decides whether to use a managed service or run it yourself.

• Build the first product, not a feature of it. You ship the initial version that customers pay for, then rebuild the parts that were wrong.
• Own the stack end to end. Database, API, frontend, deploys, monitoring. Whatever exists, you set up or inherit from a founder's prototype.
• Make durable decisions alone. Language, framework, data model, hosting. These choices outlive you, so the cost of a careless one is high.
• Talk to users directly. You will sit in sales calls and support threads. The feedback loop is short because you are the loop.
• Set the engineering culture. The third and fourth hires copy what you do. Your test discipline becomes the team's test discipline.

The work is wide, not deep. You will rarely spend three weeks on one hard problem. You will spend three weeks touching nine different problems and shipping all of them at 80 percent. People who need a single, deep, well-scoped problem to feel productive often struggle here.

How is a founding engineer different from engineer #20?

By the twentieth hire the company has a product that works, a team with roles, and a roadmap that exists before you arrive. That is a good job. It is a different job. The founding engineer builds the thing that engineer #20 will later scale and maintain.

The equity gap is the part people underweight. A founding grant can be 5 to 20 times larger than a grant at the same company eighteen months later. You are paid in ownership for taking on the time when the company is most likely to fail. To understand why that grant is shaped the way it is, read how much equity a startup engineer gets by stage.

What are the equity and salary numbers really like?

A founding engineer at a seed-stage company in San Francisco or New York commonly sees a salary 10 to 30 percent below what the same person would earn at a later-stage startup, paired with an equity grant of roughly 0.5 to 2 percent. The exact split depends on how much the company has raised and how early you are. Someone joining a 4-person company the month after a seed close is in a different position than someone joining a 15-person company a year later.

Here is a worked example (illustrative, not advice). Say you join a seed company at 1.0 percent on a 4-year vest, the company has 8,000,000 shares outstanding, and you take $170,000 instead of the $200,000 a Series B startup offered. You are giving up $30,000 a year in cash, $120,000 over the vest, in exchange for 80,000 shares. If the company sells in five years at a price that values your stake at $600,000 after dilution, the trade paid. If it shuts down, which is the base-rate outcome, you earned $120,000 less than the safe path and the equity is worth zero. Both endings are normal. The math only resolves at an exit, and most exits are nothing.

Two numbers change everything and both are easy to ask for: how many shares are outstanding (so a percentage means something), and the strike price and last preferred price (so you can see whether your options are already underwater). If you do not know how grants, cliffs, and dilution work, read how stock options and vesting work before you sign anything.

Who thrives as a founding engineer, and who should not take it?

This role rewards a specific temperament more than a specific resume. The best founding engineers are not always the strongest pure coders. They are the ones who can hold ambiguity, ship fast without panicking about polish, and make a decision with half the information and own the consequences.

Signs you will thrive

• You are comfortable being wrong in public and correcting fast.
• You can finish things without a manager scoping them for you.
• You get energy from talking to users, not just from the codebase.
• You are fine being the most senior and the most junior person in the room on the same day.
• You can sit with the chance that the company does not exist in a year and still do good work.

Signs you should pick a different role

• You do your best work on one deep problem with clear edges.
• You need mentorship or code review to grow right now.
• Your finances cannot absorb a 20 percent pay cut or a worthless equity outcome.
• You want defined hours and a predictable scope.
• You are joining mainly for the title.

None of the second list is a flaw. They describe most good engineers. A senior role at a company that just raised a Series A or B can be a better job in every way that matters to you, with real scope and market pay. If that sounds closer, compare the paths in startup vs big tech for software engineers.

What should you ask before taking a founding-engineer offer?

The role is high variance, so the questions are about reducing the things you cannot see. You are trying to learn how long the money lasts, whether the founders can sell, and whether your equity is real or decorative.

1. 01How much runway is left, in months, at the current burn? A founding engineer wants 18 months or more so there is time to build before the next raise.
2. 02How many shares are outstanding, and what was the last price per share? This turns your percent into dollars.
3. 03What is the strike price? If it is close to the last preferred price, a chunk of your upside is already priced in.
4. 04Who has the founders sold to before? Distribution is harder than building. You want a team that can find customers.
5. 05What happens to my equity if I leave after two years? Ask about the exercise window. A 90-day window can force a large tax bill to keep what you earned.
6. 06What does the first year of the roadmap look like? If they cannot describe it, you are signing up to invent it, which is the job, but you should know that going in.

Watch the answers about runway and customers most closely. A company with 8 months of runway and no paying users is asking you to bet your year on a single coming raise. For the full interview script, see questions to ask in a startup interview and how to evaluate a startup job offer.

How do you find founding-engineer roles worth taking?

The best founding-engineer roles open in the weeks right after a company raises, when the bank account is full and the hiring plan was just approved. That window is exactly what the roles.cc board sorts for. Every role carries the company's latest round and how recently it closed, so you can see which teams just got the cash to make a founding hire. You can watch the closes land on the recent raises page.

Funding recency is the single most useful filter for this kind of role, because a founding hire is a budgeted decision made right after a close. If you want the reasoning behind that, read why funding recency is the best hiring signal.

One last honest note. The founding-engineer path is not better than a senior role at a funded startup. It is a different bet with a different payout and a different failure mode. Pick it because the wide scope and the ownership are what you want, with eyes open about the salary you give up and the base rate of startups that do not make it. Read how to evaluate a startup job offer and run your own numbers before you decide.