Every hire at a startup carries more weight than the same hire at a large one. There is no HR department to absorb a bad decision, no deep bench to cover a slow start and no budget to repeat the process quickly if it goes wrong. Getting it wrong is expensive in ways that go beyond the obvious.

This guide covers how to run a hiring process that finds the right person and holds up to scrutiny if it is ever challenged.

Start With the Job, Not the Person

The most common hiring mistake at early-stage companies is starting with a candidate in mind and building the role around them. It feels efficient. It rarely is.

Before you write a job description or speak to a recruiter, write down three things: what the person will actually do week to week, what they need to be able to do on day one, and what they could learn once in the role. That last distinction matters more than most founders realise. Requiring five years of experience for a skill that could be developed on the job narrows your candidate pool without improving your hire, and in some cases can create indirect discrimination risk if the requirement disproportionately excludes a protected group without genuine justification.

Be honest in the description about what the role is. If the company is early-stage and the work involves ambiguity, changing priorities, and wearing multiple hats, say so. Candidates who are not suited to that environment will self-select out. Candidates who are will know what they are walking into, which means fewer surprises for either side.

Brief Your Recruiter Like a Business Partner

If you use a recruiter, the quality of the brief you give them directly determines the quality of candidates they send you. A job description and a salary band is not a brief.

Tell them why the role exists, what the person before did well or poorly if it is a replacement, what the team dynamic is, and what kind of person has thrived in your business before. The more context they have, the better they can filter before a CV reaches you, which is the part of the process that saves the most time.

A recruiter who does not understand your business will optimise for candidates who look good on paper. That is not the same as candidates who will work well in your specific environment.

Run the Process Like a Project, Not a Conversation

Good candidates are rarely only speaking to you. The companies that consistently hire well treat the process as a time-sensitive project with defined stages and deadlines, not an ongoing conversation that progresses when everyone gets around to it.

Set a timeline before you start. Know when you want to have CVs reviewed, first interviews completed, second stages done, and an offer made. Communicate that timeline to candidates. A founder who runs a tight, well-organised hiring process signals something real about how the business operates. One who takes three weeks to respond to a CV signals something equally real.

Build a Process That Can Withstand Scrutiny

This is where the legal dimension becomes practical rather than theoretical.

Employment tribunal claims for discrimination in hiring are uncapped in terms of the award that can be made. They do not require the candidate to have been employed by you. A rejected candidate who believes they were discriminated against on the basis of a protected characteristic, which includes age, sex, race, disability, religion, sexual orientation, and several others, can bring a claim based on the hiring process alone.

The defence against such a claim is evidence: that every candidate was assessed against the same criteria, that those criteria were relevant to the job, and that the decision was made on that basis rather than on impression or instinct.

Building that evidence is not complicated, but it needs to happen during the process, not after a claim is made.

Before you interview, identify three to five criteria that are genuinely central to the role. These become the basis on which every candidate is assessed. In the interview, ask questions that invite candidates to evidence past behaviour rather than describe hypothetical responses. "Tell me about a time when..." produces more useful and more defensible information than "What would you do if...". Take notes in the candidate's own words rather than your interpretation of them. Score each candidate against your criteria after the interview, before discussing with anyone else involved in the process. Keep those scores and notes.

This is not bureaucracy for its own sake. It is a record that shows the decision was made on the right grounds, which protects the business and, as importantly, tends to produce better hiring decisions.

Involve the Team, But Control the Decision

Team involvement in hiring is useful. Candidates who meet potential colleagues get a more honest picture of the environment, and people who will work closely with a new hire have relevant perspective on whether they will work well together.

The risk is that "culture fit" becomes a proxy for personal preference, and personal preference in a hiring context can shade into discrimination without anyone intending it. Brief anyone who meets candidates to focus on specific, job-relevant observations. What did they notice about how the candidate approached a problem? What came up in conversation that was relevant to the role? Not: did they like them.

Be explicit internally about where the final decision sits. Team input is input, not a vote, and if the hire has strategic implications that not everyone will immediately understand, it is worth saying so.

The Period Between Offer and Start Date Is Part of the Hire

Resignation periods at senior levels can run to three months or more. That is a long time for enthusiasm to cool, for a counter-offer to land, or for doubt to set in.

The companies that lose new hires between offer and start date are usually the ones who treat the contract signing as the end of the process. It isn't. A welcome message from the founder, an invitation to a team event, a pack of useful reading about the company and its context, a coffee before day one: none of these take much time and all of them reinforce the decision the person has made. The goal is for a new hire to arrive on their first day feeling they have already started, not arriving as a stranger.

What a Good Process Actually Delivers

A structured hiring process is not about process for its own sake. It tends to produce better hires because it forces clarity about what you actually need before the pressure of a specific candidate clouds the picture. It protects the business legally because it creates a record of decisions made on the right grounds. And it signals to candidates, including the ones you want most, that the company is well run.

The cost of a bad hire at a small company, in time, money, team disruption, and sometimes legal exposure, is high enough that the investment in doing this properly is rarely the most expensive option.