How to write a founding role job description
An effective founding role job description is not a corporate template. It should lead with mission and scope, be transparent about stage and compensation, and clearly describe the team, culture, and next steps so the right candidates can self-select.
A founding role job description should read more like a high-signal pitch than a corporate checklist. The best candidates care about the mission, the people, and the upside—not years-of-experience requirements or buzzwords.
Start With the Mission, Not the Requirements
Open with what you are building, who they will build it with, and what is at stake. Describe the problem in concrete terms, including the users, geography, and a clear metric. For example:
"We are building payroll infrastructure for contractors in Latin America. Today, 40% of cross-border contractor payments take more than five business days to settle. We cut that to under 24 hours."
Immediately follow with what this founding hire will own. Be explicit about scope: are they building the initial API, designing the data model, setting up infra from scratch, defining the brand identity, building the design system, or running user research? Vague scope signals you have not thought through the role.
Be Honest About Stage and Funding
Founding candidates are evaluating risk. State your stage and funding directly: pre-seed with $500K, seed with $3M, Series A with product-market fit signals, etc. If you are comfortable, include runway (e.g., "18 months of runway").
Add concise credibility markers: funding history, notable investors, or traction. If you lack brand-name backers, highlight real usage and revenue instead (e.g., "50 design teams using our beta, $10K MRR"). Evasion around stage or funding is a red flag for strong candidates.
Define Equity and Compensation Up Front
Transparency on compensation filters for serious candidates and builds trust. Publish a realistic equity and salary range based on your stage and the role. For example:
- Pre-seed founding engineer: ~1.0%–2.5% fully diluted
- Seed founding engineer: ~0.5%–1.5%
- Series A founding engineer: ~0.1%–0.5%
Pair this with a cash range, even if below market. Briefly explain vesting terms (e.g., "4-year vesting with a 1-year cliff, monthly thereafter") and mention any acceleration on acquisition—or explicitly state if you do not offer it.
Describe the Team and Culture
Founding hires are joining people, not just a product. Give them a clear picture of who they will work with and how you operate.
Provide short, contextual bios for the founding team: prior companies, exits, or relevant experience (e.g., "CEO previously built and sold a B2B SaaS company. CTO was a staff engineer at [Company], where they scaled infra from 10K to 1M users.").
Explain your working style: pair programming or solo ownership, RFCs before building or fast prototyping, weekly demo days, async vs. synchronous collaboration. Be explicit about expectations around ambiguity: call out that there will not be a spec for every feature, they will talk to customers, prototype quickly, and iterate based on feedback. This attracts candidates who thrive in early-stage chaos and repels those who do not.
Include a Clear Call to Action
End with a specific, low-friction next step instead of a generic "apply below." For example:
"Send us a short note about a project you built from scratch and why it mattered to you. Include your GitHub or portfolio if relevant."
Avoid mandatory cover letters; they add friction without adding much signal. Short, targeted prompts and portfolio links reveal more about how someone thinks and ships.
What to Avoid
- Years-of-experience requirements: They filter out non-traditional but exceptional candidates and add little signal.
- Degree requirements: CS degrees are optional; the ability to ship and learn fast matters more.
- Buzzwords: Terms like "rockstar," "ninja," or "hungry self-starter" are vague and signal laziness.
- Hiding equity details: If you cannot share exact ranges, at least explain your equity philosophy. Silence is a red flag.
- Copy-pasting Big Tech templates: Your startup is specific; your description should reflect your unique problem, team, and stage.
Key Takeaways
- Open with the mission and the specific problem you are solving.
- Clearly define what the founding hire will own.
- Be transparent about stage, funding, and runway.
- Publish equity and salary ranges and explain vesting.
- Describe the team, culture, and working style so candidates can self-select.
- Close with a concrete, low-friction call to action.
Related
Frequently Asked Questions
Should I list salary on a founding role job description?
Yes. Listing a salary range, even if it is below market, builds trust and respects candidates' time. People considering founding roles understand the tradeoff between cash and equity; hiding the number suggests you may be underpaying or are not being straightforward about the offer.
How much equity should I offer a founding hire?
Typical equity ranges for founding engineers are:
- Pre-seed: ~1.0%–2.5% fully diluted
- Seed: ~0.5%–1.5%
- Series A: ~0.1%–0.5%
The exact number depends on seniority, risk taken, and how much cash discount they accept. Use these as starting points and adjust based on the candidate's impact and the role's criticality.
Should I require a take-home project for founding roles?
Only if it is tightly scoped and respects the candidate's time—around two hours is reasonable, a full day is not. Strong alternatives include pairing on a real problem during the interview, reviewing open-source work, or having the candidate walk through a past project in depth.
What is the most common mistake founders make in founding role job descriptions?
The most common mistake is copying Big Tech job templates. Those emphasize years of experience, degrees, and long tech stacks instead of impact, autonomy, and equity upside. For founding roles, you should focus on mission, scope, stage, and ownership so the best candidates can self-select.
How long should a founding role job description be?
Aim for 400–800 words. That is enough space to explain the mission, scope, team, stage, and compensation without overwhelming candidates. Treat it like a pitch deck for the role—every sentence should earn its place and increase signal.
Last updated: May 23, 2026