How to hire your first engineer
What to decide before the first interview, where to look, and how to make an offer a strong candidate says yes to.
Your first engineering hire shapes the product and the team that comes after. Founders often rush it because the backlog is on fire, and then spend months undoing the choice. This guide walks through the steps in the order you will meet them.
Decide what the role is
Write down what this person owns in the first six months. A list of outcomes beats a list of technologies: "ships the mobile app to the first hundred customers" tells a candidate more than "React Native, 3+ years".
- What has to ship in the first 90 days
- Which decisions they make alone
- Who they work with every day
- What you can teach them and what they must already know
Look where engineers already are
Post the role where people who like startups look for work, and write to people directly. A short, personal message that names something specific they built gets answers. Your job post should say what stage you are at, how much runway you have and what the salary range is. Leaving these out does not hide them, it only moves the question to the first call.
Run a short, honest process
Good candidates leave slow processes first.
- Intro call, 30 minutes
- A practical task close to the real work, paid if it takes more than two hours
- A conversation with the people they will work with
- An offer within a few days of the last step
Make an offer they can say yes to
Be clear about salary, equity and how the equity works. Explain vesting in plain words and say what happens if the company is sold. Then stay close: answer questions the same day and keep the paperwork short.
When they sign, the first month matters as much as the search did.