How a small startup screens 300 applicants without a recruiting team

A small startup can screen 300 applicants without a recruiting team by taking the founder off the first-round calls and keeping the founder on the decisions. Write the role down, seal a rubric from it, send every applicant a link to an 8–10 minute voice interview in their own language, and read the evidence-backed scorecards in a fixed half hour each day. The live conversations go to the shortlist, and a person on your team still decides who moves forward. This guide walks through the setup, what to read in a scorecard, the compliance basics for a US startup and the daily cadence that keeps it to 30 minutes.

Who does the hiring at a small startup

At a company of ten or twenty people, hiring belongs to whoever owns the role, which is often a founder or the first engineering or sales lead. They screen candidates between building the product, selling it and raising money for it.

Ashby, which makes an applicant tracking system, published data on this in its State of Startup Hiring report (February 23, 2026). The report covers over 1,200 venture-backed startups globally that use Ashby, with 32,000 hires and 11 million applications, mostly from 2025. Three findings describe the small-startup reality:

• The volume is real. Its chart shows 298 inbound applications per hire at startups with fewer than 25 employees, the smallest of its size bands.
• Most jobs have no recruiter. At fewer than 25 employees, a recruiter is involved in 38% of jobs. The report notes that “smaller startups may not have a designated TA team.”
• That costs time. For startups under 25 employees, the report says “time to hire drops by almost 30% when a recruiter is involved.” Its chart shows an average of 42 days with a recruiter against 62 days without.

The data describes Ashby’s own customers rather than every startup, so treat it as a benchmark. It also describes the problem this guide is about: a lot of applicants, nobody whose job is to screen them, and a role that stays open while the founder catches up.

Why the first live screen is the bottleneck

The arithmetic for one role is short. At 30 minutes a call, 300 applicants × 30 minutes = 150 hours of screening calls. At 40 hours a week, that is 150 ÷ 40 = 3.75 working weeks of one person’s time, before scheduling, reschedules and no-shows. We worked through where those hours go in the math of high-volume screening.

No founder has 150 spare hours, so the queue gets cut. A common cut is to call the first 50 applicants: 50 × 30 minutes = 25 hours, and the other 250 never get a conversation. Ashby’s report shows how narrow the funnel already is: across the startups it studied, “for every hire made, 15 applicants receive an interview.” Set that figure (across all size bands) against the 298 applications per hire at startups under 25 employees, and it comes to about one applicant in twenty.

Who makes the cut is the problem. When a founder skims 300 résumés in an evening, the ones who get a call tend to be the ones who applied first or whose last employer sounds familiar. Neither tells you much about the work. We covered how these shortcuts creep into round one in what biases a first-round interview.

Step by step: screening 300 applicants with an AI interviewer

Six steps take a role from the job posting to a decision:

1. Write the role down. A job posting that describes the work: what the person will own in the first six months, the decisions they will make and the tools they will use. A vague posting produces a vague rubric.
2. Seal a rubric from it. Pick the few competencies that matter for the role and write each as observable levels, such as “named the tradeoff and what it cost” instead of “strong judgment.” Approve the follow-up techniques allowed for each competency, such as a specific example, the candidate’s own part in the work or a time something went wrong. Then seal it, so every applicant is measured against the same version.
3. Send the invitations. Every applicant gets a link. Tell them up front that an AI conducts the first interview, what it covers and how long it takes. Let them start right away or pick a time, and send reminders to anyone who has not started.
4. Let candidates interview in their own language. The interview runs 8–10 minutes, voice to voice, from a phone or a laptop, with no app and no account. Candidates who think in Spanish or Portuguese can answer in it, and the rubric stays the same.
5. Review the evidence. Each candidate comes back as a scorecard: a score for each competency, with the transcript moment that earned it.
6. Decide like a person. Book live conversations with the candidates whose evidence earned one. Nobody is rejected by software. A person on your team reads the evidence and makes the call.

Steps 1, 2 and 6 are where your judgment goes in. Steps 3 to 5 run the same way for applicant 1 and applicant 300, which is the point: the candidate who applied on day nine gets the same interview as the one who applied in the first hour.

What to look for in the scorecard

A scorecard is only as useful as the way you read it. Five habits help.

• Read the quote before the number. Each score should point to what the candidate said. If the quote does not support the level, trust the quote.
• Look for specifics. A concrete decision and the constraint behind it, a tradeoff the candidate named on their own, a failure case and how they handled it.
• Check who did the work. “I set up the billing migration” is evidence about the candidate. “We migrated billing” is evidence about a team.
• Treat thin evidence as a question. A short answer on one competency is a reason to ask about it in a live call, especially when the rest of the scorecard is strong.
• Ignore what never belonged in the score. Polish, accent and a familiar logo on the résumé say little about the competency in front of you.

Our guide to evidence-based scorecards goes deeper on what to cite and what to leave out.

Compliance basics for a US startup

A small team still has to think about this. US rules on AI in hiring are a patchwork that depends on where your candidates are and how the tool is used. New York City’s Local Law 144, for example, prohibits employers and employment agencies from using an automated employment decision tool unless it has had a bias audit within one year of use, information about the audit is public and candidates get certain notices. Our state-by-state guide to US AI hiring laws maps what is in force and when. None of this is legal advice, and when the stakes are real, talk to counsel.

Drawing on that guide, here is a reasonable starting checklist for a founder:

1. Know where your candidates are. A remote role posted nationally can draw applicants from every state with a rule on the books.
2. Tell candidates before the AI interview, in plain words: that an AI conducts it, what it evaluates and who makes the decision.
3. Keep a human decision, made by someone with the authority to change the outcome.
4. Keep the records. Transcripts and scorecards are what let you explain an outcome later. How long you must keep them depends on where you hire.
5. Keep another route open for any candidate who cannot do a spoken interview.
6. Look at your outcomes across groups of candidates, even where no audit is required.

A 30-minute-a-day cadence

Applications do not arrive all at once, so the review should not happen all at once either. Here is the arithmetic, with our assumptions stated: 300 applicants arrive over four working weeks, every one of them completes the interview (an upper bound), and a first pass on a scorecard takes about 80 seconds: the competency scores and the quote under each, enough to sort it, with deeper reads saved for later.

• 300 applicants ÷ 20 working days = 15 new scorecards a day.
• 15 scorecards × 80 seconds = 1,200 seconds, or 20 minutes of first pass a day.
• Add 5 minutes to check who finished and 5 to send invitations and decisions: 30 minutes a day.
• 20 days × 30 minutes = 10 hours in total, against 150 hours of phone screens.

A daily half hour can run like this:

• First 5 minutes: see who finished since yesterday and who has not started.
• Next 20 minutes: a first pass on each new scorecard. Sort each one into “talk to,” “read again” or “not now,” based on the evidence.
• Last 5 minutes: invite the “talk to” pile to a live conversation, and send a decision to anyone you have finished reviewing.

Once a week, set aside an hour for the “read again” pile with a second person, so no candidate’s outcome rests on one tired reading. The live conversations with the shortlist come on top of the half hour, and those are the hours worth spending.

Where Hure lands

Hure is the AI interviewer this setup describes. It drafts the rubric from your job posting, you edit and seal it, and every applicant for the role is measured against that version. Hure prepares each candidate’s single-use link and tracks who has started; email invitations and reminders are enabled per team during early access. Each candidate gets a natural 8–10 minute voice-to-voice interview from one browser link, in 100+ languages, with follow-ups drawn only from the techniques you approved. Every score is tied to the moment in the transcript that earned it. Hure judges what candidates say, never how they look or sound, and a person on your team makes every hiring decision; Workflows, which automates routing around the interview, has no reject action. You do not need an ATS: candidates can be added by hand, or imported from Greenhouse, Lever or Ashby, with integrations enabled per team during early access. Hure is billed per completed interview on a monthly plan sized to your volume, invitations are free and an abandoned interview is not billed.

The limits are worth knowing before you start. There is no independent bias audit of Hure to hand you today, which matters if you hire in New York City. Hure does not try to detect AI use, and no interview format can guarantee against a well-coached candidate. It does not run coding exercises or take-homes, so technical roles still need your own technical round. And a spoken interview is not right for every candidate, so keep another route open.

If you are weighing a larger platform, we compared the two row by row in Hure vs HireVue, with every HireVue claim linked to HireVue’s own site. The details for founders are on Hure for startups.