How to Write a Founding Role Job Description: A Guide for Startups
Writing a job description for your first major hire is different from writing one for an established role.
Founding candidates are not just looking at the job title and list of requirements. They want to understand what you are building, what they will own, who they will work with and why they should join at this stage.
This is particularly important when hiring founding engineers, AI engineers or other early-stage technology talent. A generic job description can make an exciting opportunity sound like any other job.
So, how do you write a founding role job description that attracts the right candidates?
Start With the Mission
Don't begin with a long list of requirements.
Start by explaining what your company is building and the problem you are trying to solve.
A strong opening should quickly answer:
What does your company do?
Who is the product for?
What problem are you solving?
Why does it matter?
Why is now an exciting time to join?
For an early-stage SaaS or AI company, this context can be particularly important. Candidates need to understand the product and the opportunity before they can decide whether the role is right for them.
Clearly Define What the Founding Hire Will Own
One of the biggest mistakes in a founding job description is being vague about the role.
"Help build our product" doesn't tell an experienced candidate enough.
Instead, explain what they will actually be responsible for.
For a founding engineer, this could include:
Building the first version of the product
Making key technical decisions
Developing the architecture
Working across frontend and backend
Building APIs and integrations
Developing AI or data capabilities
Setting up cloud infrastructure
Speaking directly with customers
Helping shape future engineering hires
The exact responsibilities will depend on your product and stage, but candidates should be able to picture themselves doing the job.
Be Honest About Your Startup Stage
Founding candidates are taking on more uncertainty than someone joining an established company.
Tell them where the business is today.
Are you:
Pre-seed?
Seed stage?
Series A?
Pre-product?
Already generating revenue?
Growing an existing customer base?
You should also explain relevant traction, funding or runway where appropriate.
You don't need to oversell the company. In fact, being honest about the challenges can help you attract people who genuinely enjoy early-stage environments.
Explain the Team and Working Culture
A founding hire is likely to work closely with the founders, so who they are matters.
Briefly explain the founding team's background and how you work together.
You should also be clear about what day-to-day life looks like.
Will the engineer have complete ownership? Will they speak directly with customers? Will they work remotely? How much structure is there? Are priorities likely to change?
This is particularly important for founding roles because not every great engineer is suited to an early-stage startup.
Being upfront helps candidates self-select.
Don't Turn the Requirements Into a Shopping List
It can be tempting to list every technology you use.
JavaScript. TypeScript. Python. AWS. Kubernetes. PostgreSQL. React. Five years' experience. Computer Science degree.
Before you know it, you've created a list that filters out potentially excellent candidates.
Instead, separate your requirements into:
Essential: What does someone genuinely need to do the job?
Useful: What would make them stronger, but can be learned?
Nice to have: What would be beneficial, but shouldn't prevent a great candidate from applying?
For a founding engineer, evidence of ownership, adaptability and the ability to build and learn quickly may be more valuable than ticking every technology box.
Make the Opportunity Clear
A founding role should explain why someone would choose this opportunity over a more established company.
Talk about:
The level of ownership
Product and technical influence
Access to the founders
The problems they will solve
The opportunity to shape the engineering team
Career progression
Salary and equity, where appropriate
You don't need to make unrealistic promises. Simply explain what the candidate will genuinely have the opportunity to influence.
Include a Clear Call to Action
Don't finish with a vague "Apply Now".
Give candidates an easy next step.
For example, you might ask them to apply with their CV and LinkedIn profile, or invite them to share a project they have built that demonstrates their approach.
The easier it is to understand what happens next, the less friction there is in the application process.
What Should You Avoid in a Founding Role Job Description?
There are a few common mistakes worth avoiding.
Copying a corporate job description: A founding role is fundamentally different from a role in a large organisation.
Using vague buzzwords: Words like "rockstar", "ninja" and "self-starter" don't tell candidates anything useful.
Overloading the job description with requirements: Focus on what someone genuinely needs to succeed.
Hiding the reality of the role: If the position involves ambiguity, changing priorities and significant ownership, say so.
Being unclear about the opportunity: Candidates need to understand why joining your company now is worth the risk.
Need Help Defining Your Founding Role?
Sometimes the hardest part isn't writing the job description. It's working out what the role should actually look like.
Do you need a founding engineer or a more specialised software engineer? Should your first technical hire be focused on AI, product engineering, data or infrastructure? What experience does the business genuinely need at its current stage?
At Peritus Partners, we work with early-stage and scaling technology companies across AI, SaaS and software engineering. We can support founders in defining the profile they need, understanding the market and reaching the candidates who are right for the opportunity.
That means looking beyond the job description and understanding what you are building, where the business is going and what your first hire needs to achieve.
Once those things are clear, writing the job description becomes much easier.
Frequently Asked Questions
What should a founding engineer job description include?
A strong founding engineer job description should explain the company mission, product, stage, responsibilities, technical environment, team, culture, compensation and what the candidate will own.
How long should a founding role job description be?
Keep it focused. You need enough detail for candidates to understand the opportunity, but not so much that the important information gets lost. Every section should help someone decide whether the role is right for them.
What should I look for in a founding engineer?
Look beyond technical skills. Ownership, adaptability, problem-solving, technical breadth and comfort with ambiguity are particularly important when hiring an early-stage engineer.
Should a startup include salary and equity in a founding job description?
Being transparent about compensation can help build trust and allow candidates to make an informed decision. The right package will depend on your stage, location, responsibilities and the candidate's experience.
How do I attract candidates to a founding role?
Explain the problem you are solving, what the candidate will own and why joining at this stage is exciting. Strong founding candidates are often motivated by impact, autonomy and the opportunity to shape something from an early stage.
Final Thoughts
A good founding role job description should do more than explain a vacancy.
It should give candidates a clear picture of your mission, the problem you are solving and the role they will play in building the company.
Get the role clear first, then write the job description around it.
And if you need support defining or hiring your first technical team, Peritus Partners can help you turn your hiring plans into a clear, targeted search for the right talent.
Comments