How to Hire Your First Employee
A hundred applicants, one role, and no obvious way to tell who is worth a call. This guide covers the full sequence for hiring your first employee: defining the role, collecting every applicant in one place, screening on evidence rather than keywords, and making the offer.
·
Most people think the hard part of hiring your first employee is the interview. It is earlier than that. The hard part is the pile.
You post one role and a hundred people apply. Maybe more. Before you can interview anyone, before you can check anyone's story, you face one blunt question: out of all these people, who do you even reach out to? Answering that by reading every CV is the work that eats your week. This guide is written for a founder doing this alone. It is about doing that one thing well: turning a big pile of applicants into a short list of people worth your time, and then hiring one of them.
This is not about payroll, tax, or the legal setup of employing someone. That is a separate job. This is about picking the right person out of the crowd.
First, know what the role is
Before you post anything, write down what the job actually is. One job. One clear result you want in the first few months. Then list the three or four things the person must be able to do to get that result.
That short list is your ruler. You will judge every applicant against it. Skip this step and you are sorting a pile with nothing to measure people by, which means you will drift toward whoever you happen to like. If your job post itself is vague, that drift starts before the first applicant arrives, so it pays to check the wording of the role against that ruler before you publish it.
If you cannot write that one clear result down, you are not ready to hire yet. That is not a delay, it is the cheapest mistake you will ever avoid. A role you cannot describe is a role you cannot fill, and you will find that out three months and one salary later.
Where to find candidates when you have no network
If you have hired before, or you know people who do the work, you already have a shortlist in your head. A first-time hirer usually does not. So you are choosing between two kinds of places to post.
Broad job boards like LinkedIn and Indeed give you reach and very little filtering. You will get a hundred applicants and most of them will not fit. Niche boards, communities where the work actually gets discussed, and your own network give you far fewer applicants but a much higher hit rate, because something has already filtered them before they reached you.
The usual advice is to favour the second kind. For a first hire with no network, that advice is wrong. You do not have the relationships to make it work yet, and a thin pile of five is not safer than a thick pile of a hundred. It just hides the problem. Take the volume. The rest of this guide is about handling it.
Step 1: Post the role and collect every applicant in one place
Post wherever your people are. LinkedIn, Indeed, a niche job board, your own network, a message to your circle. Where you post does not matter much. One thing does matter: every applicant, from every source, should land in the same place.
Set up a single link that collects all of them, together with a couple of pre-screening questions you want everyone to answer. One link means one pile to work through, not five inboxes and a spreadsheet you keep losing. You can build this yourself with a simple online form and share it everywhere you post. The rule is the same either way: one door for every applicant.
Step 2: How to screen 100 resumes
Now you have a hundred-plus applicants and their pre-screening answers. The first pass is rough sorting. Who clearly fits, who clearly does not, who is a maybe. You do this by reading the CV and the pre-screening answers side by side.
Here is the trap most people fall into. They sort by keywords, checking whether the applicant used the right job title, named the right tools, used the same words as the job post. That rewards people who write a good CV, not people who do good work. Worse, it drops strong candidates who described the exact same skill in different words.
The better way is to match on context, not words. Look at what the person actually did and whether it maps to the result you want, rather than whether their vocabulary matched yours. Done by hand across a hundred CVs, this is slow, which is why most people fall back on keyword scanning and hire the better writer, and why AI resume screening is worth it only if it reads for context instead of counting keywords.
Step 3: Verify the claims
This is the step that actually decides your hire, and the one people skip because it is the most work.
A CV is a list of claims. Claims are not facts. Someone writes "led a team that grew revenue by 40 percent." Did they lead it, or sit near the people who did? You only find out by testing the claim: going back to the person, asking them to explain exactly how they did it, then asking a follow-up question they cannot dodge. Real claims survive the follow-up. Inflated ones fall apart under it.
Doing this by hand means calling every promising candidate and interviewing them one at a time, just to learn whose claims are real. For a pile of a hundred, one person running a business cannot do that. So most first-time hirers don't. They guess from the CV, and the guess is often wrong.
This is where BestHire comes in, and it runs the whole chain above rather than one piece of it: the single link from Step 1, the context-based sorting from Step 2, and then the part you cannot do alone.
It interviews every applicant who fits the role, not a few you picked out first, the whole fitting pool. Each interview is built from that person's own CV, and asks follow-up questions about the exact claims they wrote down. It reads only what the person says, never their face, their voice, or their accent. Then it ranks everyone by whose claims held up and hands you a short list with the evidence attached: the line from the CV, and the answer that either backed it up or broke it. It does not reject anyone for you. You make every call.
Step 4: What to ask your first hire
Now you have your short list, and you already know their claims are tested. Reach out to those people and get the conversations booked. You can do that from inside BestHire, since it already holds everyone's details and the evidence behind each name.
That evidence changes what the interview is for. You are not sitting down to work out whether they can do the job; you already have proof either way. So the human interview gets short. Spend the first five to ten minutes on a real introduction: who you are, what the role is, why it matters. Then ask a few questions to ask in an interview about them as a person, because you are going to work closely with this hire and how you two get on is real. Ask a couple of quick technical questions, just to confirm with your own eyes what the shortlist already showed you. If it fits, you make the offer.
That is the whole shift. Your limited time comes off the hundred-person pile and goes onto a five-person conversation, because the filtering already happened.
Making the offer
Once you have decided, move. The candidate you want is usually talking to someone else, and days matter here in a way they did not at any earlier step. Make the offer on a call first, then put it in writing the same day: role, salary, start date, working arrangement, and anything you promised out loud. Expect a negotiation. The rest of it, the contract, payroll, tax registration, and whether this person is an employee or a contractor, is a separate job with real legal consequences, and the rules depend on where you are, so get proper advice on it. Nothing here is legal advice.
Why a small business hire is different
Hiring employees for a small business is not a smaller version of hiring at a big company. It is a different job.
At a big company, a bad hire is absorbed. There is a team around them, a manager to correct course, and other people doing similar work. In a small business, your first employee might be a tenth of your headcount and a much larger share of your payroll. There is nobody to absorb the mistake, and there is nobody to train them but you.
Two things follow. First, breadth beats specialism. Your first hire will do things that were never in the job description, so someone who can figure out an unfamiliar problem is worth more than someone perfect at one narrow task. Second, verification matters more, not less. A big company can afford to find out in month three. You cannot. The specifics change by role. Hiring a developer tests for different things than a personal assistant or a first sales rep, but the filtering method underneath is the same.
The 5 steps of hiring your first employee, in short
Hiring your first employee is not really about the interview. It is about the pile. The person who hires well is the one who turns a hundred applicants into the handful worth talking to, by testing what people claim instead of trusting what they wrote, and then spends their interview time only on those few.
The whole process, in five steps:
- Define the role. One job, one clear result, three or four things they must be able to do.
- Post it and collect everyone in one place. One link, one pile, pre-screening questions attached.
- Sort on context, not keywords. Judge what they did against the result you want, not whether their words matched yours.
- Verify the claims. Test what is on the CV with follow-up questions. This is the step that decides the hire.
- Interview the short list. Short conversations, focused on fit, because the filtering already happened.
Do that, by hand or with a tool, and the actual hire becomes the easy part.