Hiring your first engineer
Ten things to settle before you post the job. Tick them off with your co-founder; most take less than an hour.
Decide what the first hire must own
Write the three outcomes they are responsible for in their first six months.
Choose generalist or specialist
A first engineer usually needs to work across the whole product, not one layer.
Write the role around outcomes, not tools
Describe the problems they will solve before listing frameworks.
Set the budget, including equity
Agree the salary range and equity before the first interview, not after.
Plan a short interview loop
Two or three stages. Long processes lose the best candidates.
Use a paid, realistic test task
A few hours on a problem like yours tells you more than puzzles.
Ask someone technical to review
If you are non-technical, borrow an engineer you trust for the final stage.
Make sure you own every account
Code repository, hosting, domains and app stores should be in the company’s name.
Document what exists today
Set-up steps, open work and known problems, so they are not starting from zero.
Prepare a first-week plan
Access on day one, a small first task, and a clear person to ask.
Hiring will take a while? Pontra puts an engineer on your backlog within five working days and hands over cleanly when your hire starts.
pontrahq.com