A first-timer's checklist for hiring a role you've never hired before

Search “hiring your first employee” and you’ll get the same ten steps everywhere: get an EIN, set up payroll, post the labor law notices, write a handbook. That’s real advice. It’s also solving a different problem than the one you actually have.

You’re not hiring your first employee. Your business already runs. What’s new is the role: your first content person, your first coordinator, your first salesperson who isn’t you. And the part no checklist covers is what happens the moment you’re hiring for a role you’ve never hired before and a candidate starts answering a question you can’t actually judge.

Get that part wrong and every other step in the process is just paperwork, done well, for the wrong hire.

Most first-time hiring advice solves a problem you don’t have

Search around long enough and you’ll find two genres of advice for this exact moment. The first is generic: forms, an EIN, a handbook, the mechanics of becoming an employer. Useful if this is genuinely your first hire. Beside the point if it’s your tenth hire and your first marketer.

The second genre is role-specific, and it’s better. Guides on hiring your first SDR or your first marketing person tell you to get clear on your bottleneck before you post the role, and to hire for scrappiness over a polished resume. That’s real guidance, and it’s worth following.

It also stops exactly where your problem starts. Nobody tells you what to do with an actual answer, from an actual person, in an actual interview, when you have no reference point for what a strong one sounds like. That’s a candidate screening problem, not a paperwork problem, and you can define the bottleneck perfectly and still freeze the moment a candidate starts talking about a discipline you’ve never practiced.

Not knowing the craft is what makes you hire on the wrong signal

Without a reference point, you default to signals that have nothing to do with the job. The candidate who talks fastest and sounds surest reads as competent. The candidate who answers carefully, with honest uncertainty about tradeoffs, reads as weak, even when careful is exactly what the role needs.

Say you’re hiring your first SDR. The confident candidate tells you they’ll “just start dialing” and book fifty meetings a month. The candidate who asks what a qualified lead actually looks like for your business, before promising anything, sounds less impressive in the room. On paper, the second candidate is doing the job better already, and no amount of training yourself to be a sharper interviewer fixes that if the underlying scorecard is still your gut.

The cost lands different on a ten-person team

A big company absorbs a bad hire in a role nobody notices. A ten to forty-person founder-led business doesn’t have a role like that. If the person you brought in for a job nobody else on the team understands turns out wrong, nobody can quietly cover for them while you figure it out.

The commonly cited industry estimate puts the cost of a bad hire around $17,000 once you count the salary paid for work that didn’t happen, the team time spent managing it, and the search that has to start over. That figure moves depending on the role and the source, but on a small team it’s real money and a real hole in the calendar, not an HR abstraction.

Build the criteria before you read a single resume

You don’t need to become a marketer to hire one. You need to write down what winning in the role actually looks like before a single application lands in your inbox, so you’re grading candidates against a standard instead of against how they made you feel.

Start from outcomes, not tasks

Skip “what will this person do all day” and start with “what does this role need to be true in six months.” For a first content hire, that might be a content calendar that runs itself and a measurable lift in organic traffic. For a first SDR, it’s qualified meetings booked against a number you can actually defend, not just activity.

Outcomes translate across roles you don’t understand in a way that task lists don’t. You don’t need to know the tactics of SEO or cold outreach to know whether traffic moved or meetings got booked. That’s a standard you can hold someone to without having done the job yourself, and it’s the same thinking that goes into a job description your screening process can actually score instead of one that just lists responsibilities.

Write down your yes, your maybe, and your no

Turn the outcome into three short lists before you post the role: the must-haves that disqualify someone if they’re missing, the nice-to-haves that break ties, and the red flags that would make you pass regardless of how the rest of the interview went. Write these down. Don’t keep them in your head, where they quietly change shape after you meet someone likable.

This is the same discipline behind a good-fit read that holds up without a hiring team backing you up in the room. You’re building a standard once, on a day when you’re calm and not yet attached to a specific person, so you’re not inventing one on the fly while a candidate is mid-answer.

What if you genuinely have no idea what good looks like

Sometimes you can’t write the criteria alone because you’ve genuinely never seen the job done well. That’s fair, and it’s more common than it feels when you’re buried in a pile of resumes with no one to hand them to. Rather than going and learning the craft yourself, borrow judgment you don’t have and add evidence you can actually read yourself.

Borrowing judgment can be as simple as a 20-minute call with someone in your network who’s done the role, or hired for it before, walking you through what a strong answer to your actual interview questions sounds like. You’re not trying to become an expert. You’re trying to calibrate one reference point so you’re not grading in a vacuum.

Adding evidence means not betting the whole decision on one hour of conversation you can’t fully judge. A resume tells you baseline credentials, which you can read regardless of the role. A recorded answer to a specific question tells you how someone actually reasons, which you can compare across candidates side by side instead of trusting your memory of who sounded best last Tuesday. Stack two or three signals instead of one, and your inexperience in the craft matters less, because no single moment is carrying the whole call.

How this looks with an actual pile of candidates

Say you’re a fifteen-person, founder-led business hiring your first content person, and the role pulls forty applications in a week. You’ve never hired a marketer. You have your outcomes written down (traffic, a content calendar that runs without you) and your three lists (must-haves, nice-to-haves, red flags).

Screen the pile against your own criteria, not your own gut

This is the part where screening for a role you can’t personally evaluate stops being a gut exercise and starts being a repeatable one. Truffle is a candidate screening platform that combines resume screening, one-way video interviews, and talent assessments, and you run all three against the exact criteria you wrote down instead of your own read of who sounds sharpest.

Upload your must-haves and the resume review scores every candidate against them, so the twelve people missing a genuine must-have fall away before you spend a minute on them. For the rest, a one-way interview asks the specific questions you’d have asked in person, and candidates answer on their own time. Instead of forty full recordings, you watch a 30-second Candidate Shorts clip for each one, tied to the criteria you set instead of a generic quality label.

Stack three checks instead of trusting one conversation

If the role calls for judgment under ambiguity, a short assessment adds a signal a resume and an interview both miss. AI surfaces the evidence against your own criteria. You still decide, and you decide with three separate checks on a job you couldn’t have judged alone, instead of one conversation you weren’t equipped to read.

This is a hiring skill you’ll use again

The next role you’ve never hired before is coming. Maybe it’s ops, maybe it’s your first designer, maybe it’s someone senior enough to make you nervous in a different way. The specific checklist for this hire won’t transfer. The habit will.

Writing outcomes and a yes-maybe-no list before you meet anyone, and refusing to let one conversation carry a decision you’re not qualified to make alone, works on every unfamiliar role you’ll ever fill. You don’t have to have done the job to hire well for it. You have to know what winning looks like and build a process that checks for it consistently, on this hire and the one after it.

Frequently asked questions about hiring for a role you’ve never hired before

How do I write a job description for a role I don’t understand?

Start from the outcome, not the task list. Decide what needs to be true in three to six months (traffic up, a pipeline of qualified meetings, a process documented) and work backward into the skills that outcome requires. If you can’t state the outcome, a 20-minute call with someone who’s done the role or hired for it before will get you further than reading ten job descriptions from other companies.

What should I actually ask in an interview for a role I’ve never done?

Ask about a real decision, not a hypothetical. “Tell me about a time you had to choose between two approaches with an unclear right answer” reveals reasoning you can judge even without craft expertise, because you’re grading how they think through tradeoffs, not whether their vocabulary sounds impressive.

How do I avoid hiring the most confident candidate over the most qualified one?

Grade against the must-haves, nice-to-haves, and red flags you wrote down before the interview, not against how the conversation felt. Confidence and competence are different traits, and separating them is easiest when you have a written standard to check answers against instead of relying on how someone made you feel in the room.

Is it worth hiring a recruiter just for the first hire in a new role?

For a single role, a recruiter’s fee is hard to justify, especially since you’ll face this exact problem again on your next unfamiliar hire. A screening workflow built for hiring without a recruiter gets you most of the benefit (structured evaluation, evidence instead of gut feel) without the ongoing cost.

How many candidates should I expect to screen before I feel confident in a hire?

There’s no universal number, but an unfiltered pile of forty applications causes the same problem as one of four hundred. If you’re reading every application the same way you’d read the first, screening 100 or more applicants without a ranked shortlist first is how good candidates get lost in a pile you never finish.