The useful idea
Your first hire should fill a gap you can name, through a process short enough to run while you keep doing your own work.
Decide what the role owns before you write an advert
The hardest part of a first hire isn’t the interview. It’s being honest about what the person is actually for. Before writing anything public, finish one sentence: in six months, this person will own ______. If you can’t name two or three concrete outcomes, the role isn’t ready to advertise yet.
Outcomes are more useful than tasks. “Own our customer onboarding so new accounts reach their first success without me” tells a candidate, and your future self, what good looks like. A list of tools or a job title on its own doesn’t. Write the outcomes down and keep them beside the process; they are what every later decision refers back to.
Agree a budget and a salary range first
Decide what you can pay before you meet anyone you like. It is much harder to set a fair number after a good conversation, when enthusiasm quietly becomes negotiation. A written range also keeps the role honest: if the outcomes you want are worth more than you can pay, it is better to learn that now.
Publishing the range in the advert is increasingly expected in the EU, and it tends to attract people who actually fit the level. It saves everyone the awkward late discovery that expectations were never close. Decide the range, the working arrangement and the employment type together, since they all shape who will consider the role.
Keep the process short enough to run
You are hiring on top of your existing job, so design a process you can actually sustain. A first hire rarely needs five rounds. It needs a clear path, one or two focused conversations, and a quick decision. The example below is a starting point to adapt, not a fixed template.
Decide who makes the final call before you begin. For a first hire that is usually you, but naming it still helps you avoid drifting while you wait to “feel sure”.
| Step | What it answers | Keep it short by |
|---|---|---|
| Application | Is this person roughly the right level and interested? | Asking two or three questions, not a long form. |
| First conversation | Could they own the outcomes we wrote down? | Exploring one real example of relevant work. |
| Focused interview | What is the evidence for and against? | Covering the few capabilities that matter, not everything. |
| Decision and offer | Are we ready to commit? | Making the offer within a few days, in writing. |
Try not to hire a copy of yourself
A first hire often feels easiest when the conversation flows, and conversation flows most easily with people who think the way you do. That comfort is worth noticing rather than trusting. The point of a first hire is usually to cover something you are not already good at, or do not have time for.
Keep bringing the discussion back to the outcomes and the evidence. “I liked them” is a feeling; “they showed how they’d reduce our onboarding drop-off, with an example” is a reason. If you can’t point to evidence against the role’s requirements, you have a pleasant conversation, not yet a decision.
Keep the whole thing in one place
A first hire is where scattered tools start to hurt: the advert in one place, replies in an inbox, notes in your head. Rolefern keeps the job, the application form, candidate profiles and your notes together, so the process is understandable even on a busy week.
Set up one role, add the few stages you need, and write down the next action for each candidate. The tool keeps the context; the judgement stays with you. When the role closes, you’ll have a tidy record of how you decided — useful the second time you hire, which usually comes sooner than you expect.
Make it part of your day-to-day hiring.
Keep applications, candidate profiles and hiring progress connected in one workspace your team can actually follow.
Explore applicant tracking
