You’ve Never Interviewed Anyone. How Do You Run the One That Decides Your First Hire?
You have written the job post, the applications are in, and now you have to sit across from a stranger and decide whether to bet your small company on them. You have never done this before, so you default to a friendly chat. That chat feels like the easy part of hiring. It is quietly the part where founders lose the hire.
When you have no HR team, no recruiter, and no template to copy, the interview is the one part of hiring that looks like it needs no preparation. You are good with people. You built the company by reading people. So you book an hour, you make the candidate comfortable, you talk about the role, and you leave with a feeling. The problem is that the feeling is measuring the wrong things, and you will not find that out until months after the person has started.
This is not an argument for turning yourself into a corporate interviewer with a five-round panel. It is the opposite. A founder can run a first interview that actually predicts the job with almost no machinery: a few questions decided in advance, real examples instead of opinions, and a habit of writing down what you saw before you decide. Here is why the friendly chat fails, and what to do instead.
Why the First Interview Feels Easy and Goes Sideways
A free-flowing conversation rewards the wrong candidate. Left to instinct, you warm to the person who is most like you: same references, same energy, same way of telling a story. That is rapport, and rapport is a real thing. It is just a weak predictor of whether someone can do the work you are hiring for. The candidate who interviews smoothly and the candidate who performs are two different populations that only sometimes overlap.
The cost of getting this wrong is not abstract. In a Leadership IQ study that tracked more than 20,000 new hires, 46% failed within 18 months. The striking part is why: 89% of the time the failure came down to attitude, things like not being able to accept feedback or the wrong temperament for the job, and only 11% to a gap in technical skill. In other words, almost nobody flames out because they could not do the task. They flame out over things a relaxed chat about their CV never tests, and a founder hiring on gut feel is exactly the setup that misses them. It is worth knowing what a bad hire actually costs a small team before you decide the interview is the part you can wing.
What You Are Actually Trying to Find Out
Before you write a single question, get clear on what an interview is for. You are not there to confirm that you like the person, and you are not there to have them recite the CV you already read. You are there to reduce your uncertainty on three things, in this order.
- Can they do the actual work? Not the work in general, the specific thing you need done in the next six months. A claim on a CV is cheap. A concrete, worked example of them doing something close to it is not.
- How do they behave under your conditions? Your first hire has no manual, no process, and no team to hide behind. They will hit ambiguity daily and get blunt feedback from you weekly. How someone handles both is the single best signal you can get, and it maps straight onto why hires fail.
- Do they want this job? Not a job, this one: a small company, wide scope, no ladder yet. A strong candidate who takes it for the wrong reasons is gone in six months, and at your size that is a full restart.
Everything in the interview should serve one of those three. If a question does not, it is small talk, and small talk is where the likeability trap lives.
A Light Structure You Can Run in an Afternoon
Structure sounds heavy. It is not. It means four things, none of which take more than an afternoon to set up, and together they do most of the work.
Ask every candidate the same core questions
Write down five or six questions before the first interview and ask all of them to everyone. This is the whole game. When each candidate answers a different set of questions, you are not comparing people, you are comparing your mood across conversations. Same questions, same order, and suddenly the differences you see are about the candidates, not about how the chat happened to flow.
Ask for real examples, not opinions
“How do you handle pressure?” invites a rehearsed answer everyone has ready. “Tell me about the last time a launch went wrong. What did you actually do?” makes them walk you through something that really happened. Past behaviour on a concrete case tells you far more than a candidate’s theory of themselves. Keep pulling for detail: what did you do, not what did the team do.
| What to probe | Why it predicts the job | A question that gets at it |
|---|---|---|
| The actual work | Skill claims are free; a worked example is not | “Walk me through the last thing you shipped that you were proud of. What was your part?” |
| Ownership under ambiguity | Your first hire has no manual and no team to hide behind | “Tell me about something you fixed that nobody asked you to fix.” |
| Response to feedback | The top reason new hires fail is they cannot take it | “Describe feedback you got that you disagreed with. What did you do next?” |
| Motivation for this role | Right person, wrong reasons, leaves in six months | “Why this job, at a company this size, right now?” |
Score against the role, not against each other
Before you meet anyone, decide what a strong answer to each question looks like, then rate each candidate against that bar, not against the last person you saw. Ranking candidates head to head feels natural and it drifts fast: a mediocre field makes an average candidate look brilliant. A fixed bar keeps you honest, and it is the same logic behind scoring every candidate against criteria you set instead of by comparison.
Separate taking notes from making the call
During the interview, your only job is to ask, listen, and write down what you actually heard. Do not decide in the room. The candidate should be talking far more than you, and you cannot both perform the interview and judge it at the same time. The verdict comes after, from your notes, when the charm of the conversation has worn off.
The Four Mistakes That Lose You the Hire
Most first interviews fail in the same handful of ways. None of them are about being a bad judge of people. They are about the format doing the judging for you.
- You talk too much. Excited founders sell the company for forty minutes and call it an interview. Aim for the candidate talking around 80% of the time. You cannot learn anything while you are the one speaking.
- You lead the witness. “We move really fast here, you are okay with that?” has one honest answer. Ask neutral questions and let the candidate reveal the fit or the mismatch on their own.
- You decide in the first five minutes. A strong handshake and an easy opener, and the rest of the hour becomes a search for reasons to confirm the yes. Hold the verdict until you have heard every answer.
- You keep it all in your head. Interview three people in a week with no notes and you will decide from whoever was most memorable, not most capable. That gap between memory and evidence is exactly how a hiring decision quietly gets distorted.
If this list feels familiar from other parts of building a company, it should. Most of it overlaps with the first-hire mistakes founders repeat, and the interview is where they all come to a head.
Key Takeaways
- A free-flowing chat rewards likeability and similarity to you, which are weak predictors of the job. Nearly half of new hires fail within 18 months, and almost always over attitude rather than skill, the exact things a casual chat never tests.
- An interview exists to reduce uncertainty on three things: can they do the specific work, how they handle ambiguity and feedback, and whether they want this exact role.
- Light structure does most of the work: same questions for everyone, real examples instead of opinions, a fixed bar instead of head-to-head ranking, and notes written before you decide.
FAQ
How many interviews do I actually need for a first hire?
Fewer than you fear. Two well-run conversations plus one small piece of real work beats five unstructured chats. Each round should test something the last one did not, so you are adding signal, not repeating yourself. Adding rounds for comfort just gives your best candidate time to accept another offer.
I am not a trained interviewer. Will a candidate see through my questions?
The opposite happens. Candidates trust a clear, consistent process more than a smooth talker. Asking for concrete examples and taking notes reads as seriousness about the hire, not inexperience. A vague, all-vibes chat is what makes strong people quietly downgrade their interest.
Should I trust my gut at all?
Yes, but late and on the record. Your instinct is a real signal, especially about motivation and fit. It just should not be the only signal, and it should not fire before you have written down what you actually saw. Gut feeling that survives contact with your notes is worth trusting. Gut feeling that decides in minute five is usually bias wearing a confident face.
You do not need to become a recruiter to run a first interview that holds up. You need a short list of questions, the discipline to ask for real examples, and notes you write before you decide. That is a habit, not a headcount. Kynto is built for founders doing this without an HR team: it scores every candidate against the criteria you set and hands you the structure around the conversation, so the judgment in the room stays yours. You can see how that works for founders hiring without an HR team.
A good first interview is a habit, not a headcount: a few fixed questions, real examples, and notes before you decide. Kynto handles the structure around the conversation so the judgment stays yours.
See how Kynto works for founders