For founders
Founding engineer job description template
A job description the best founding engineers will actually read, with a template you can copy and the parts most posts get wrong
A good founding engineer job description is short, specific and honest about the stage. It says what the company is building and why now, what the engineer will own in the first year, the base and equity range, how the team works, and how the hiring process runs. Strong candidates read it to judge whether the founders know what they need.
The strongest founding engineers are rarely looking, so most of them will see your job description because someone sent it to them. They read it for signal about the founders. A list of fifteen technologies and a paragraph about passion suggests the company hasn’t decided what it needs. A clear first-year mandate and a real number suggest it has.
The template
Title. Founding Engineer. Add a focus only if it’s real, as in Founding Engineer, Infrastructure.
What we’re building. Two or three sentences a stranger could repeat: the product, who uses it, and what has changed that makes it possible now.
Where we are. Team size, how much you’ve raised and from whom, whether there are paying customers, and what each founder does. Name the founders and link to their profiles, because a founding engineer is choosing who to work with as much as what to work on.
What you’ll own in the first year. Three to five outcomes, written as results. For example: ship the first version of the pipeline our three design partners run in production, choose and set up the deploy and monitoring stack, and help hire the next three engineers.
What we need from you. The few things that actually matter, such as experience shipping a product end to end with nobody to hand work to, comfort talking to customers, and depth in the one area that is hardest for this product. Leave out years of experience and any tool you could teach in a month.
Compensation. The base range, and the equity range as a percentage of fully diluted shares. California, New York, Washington, Colorado and several other states already require a pay range in job posts for roles there.
How we work. Where the team sits, how many days a week in person, the hours people actually keep, and how decisions get made.
The process. Each step, who it’s with, and how long the whole thing takes. A short loop with a founder in every conversation is a selling point in itself.
What to leave out
Cut the phrases every post shares, like fast-paced environment, rockstar and wear many hats. Drop degree requirements, which screen out some of the people this role attracts most. Keep the list of nice-to-haves off the page, since strong candidates tend to read it as a list of reasons they don’t qualify.
Where it should go
Post it, but don’t count on the post. The founding engineers you want are mostly employed and not browsing. Send the description to the people who know them, including other founders, your investors and engineers you’ve worked with, and ask each of them for a name. How to hire a founding engineer covers the rest of the search, and founding engineer salary in 2026 has the numbers for the compensation line.
Common questions
- What should a founding engineer job description include?
- What the company is building and why now, the stage and the team, what the engineer will own in the first year, the few requirements that matter, the base and equity range, how the team works, and the steps of the hiring process.
- Should a founding engineer job post include salary?
- Yes. California, New York, Washington, Colorado and several other states require a pay range for roles there, and the range with the equity as a percentage is one of the first things a strong candidate checks.
- How long should a founding engineer job description be?
- Short enough to read in two minutes. A clear first-year mandate and a real number carry more weight than a long list of technologies.