You Should Want 1,000 Resumes for Your Next Hire

One thousand resumes sounds like a disaster only because we assume somebody must read them one by one, in the order they arrived.

That assumption shaped the old hiring advice: make the job description narrower, ask for an exact title, add more years of experience and discourage anyone who does not look like the person you pictured. Fewer applications meant less work.

But fewer applications also mean fewer chances to find somebody you did not picture.

If software can organize a large batch against the work you actually need done, the better question is no longer “How do I stop so many people applying?” It is “How do I review a wider group without losing judgment, consistency or good candidates?”

That is the case for wanting 1,000 resumes. Not because volume guarantees quality. Not because an algorithm can identify the perfect employee. Because a broad search gives you more possible answers before you narrow the field.

The lesson from broad advertising

Small-business advertisers have lived through a similar change.

The old habit was to build a tiny audience by hand: the right age, interests, location and assumptions about who would buy. Newer advertising systems often work better with room to explore. Meta describes its Advantage tools as using automation to reach more potential customers and find new audiences, rather than relying only on a marketer's manual targeting. That does not mean “target nobody.” It means give the system a clear result and enough room to discover patterns you would not have chosen yourself. Meta explains the approach here.

Hiring can borrow the broad-search instinct, but not the whole advertising model.

An advertising platform gets frequent feedback: someone clicked, bought or did not. Hiring feedback is slower and much less tidy. A person can interview well and struggle in the role. A strong employee may take months to prove it. Different managers may disagree about what “good” means. Resume software therefore should not be trusted to learn your ideal employee from a few past hires.

Use the advertising analogy for discovery, not for the final decision:

• let more plausible people enter the pool;
• define the work clearly;
• use software to organize the evidence;
• keep the shortlist and hiring decision with people.

Narrow targeting often hides assumptions

Imagine a small company hiring somebody to manage customer support.

The owner might ask for five years with the title “Customer Support Manager,” experience in the same industry and a bachelor's degree. Those filters feel safe because they describe a familiar candidate. They may also remove:

• a restaurant manager who handled difficult customers, scheduling and staff training;
• an office manager who built the company's complaint process;
• a support specialist already doing team-lead work without the title;
• somebody returning after caring for a family member;
• a candidate from another industry who has used the same systems at a larger scale.

The exact previous title is only a shortcut for the evidence the owner really wants: judgment, writing, ownership, calm problem-solving and the ability to improve a service process.

This is not just theoretical. Harvard Business School's research on “hidden workers” found that employer screening processes often discard people who could perform the job but do not fit exact criteria in the job description. Read the report. LinkedIn's skills-first research similarly found that expanding searches beyond conventional titles and credentials can multiply the eligible talent pool. Treat those figures as platform research rather than a promise for any one vacancy, but the direction is useful: proxies shrink a pool much faster than job-related skills do. See LinkedIn's analysis.

The practical rule is simple:

Be strict about the work. Be flexible about where credible evidence of that work may come from.

One thousand resumes are not automatically better

A broad pool is useful only when the job is real, the requirements are clear and applicants receive a reasonable process.

More volume will not rescue:

• a vague job description;
• pay or location that is hidden until late in the process;
• an employer collecting resumes for a role it is not ready to fill;
• a ranking rule that rewards repeated keywords;
• an automatic rejection system nobody checks;
• a company that cannot communicate with the people who applied.

Application volume is already high. Ashby's recruiter-productivity analysis reported an average of 291 applications per hire, compared with roughly 100 in early 2021, across the employers in its dataset. See Ashby's recruiting trends report. A Greenhouse survey also found that some recruiters were spending a large part of their week filtering junk and spam. Read the survey.

Those numbers do not prove that every employer should chase a bigger pile. They show that large pools are already part of hiring. The useful response is to build a better review process, not to add arbitrary barriers and hope the pile becomes smaller.

The 1,000-resume plan

Here is a workable version for a business without a large HR department.

1. Write four job outcomes

Before publishing the vacancy, write the four most important things the person needs to accomplish.

For a customer-support lead, that might be:

1. Own difficult customer cases without making the situation worse.
2. Help a small team produce clear, consistent replies.
3. Find recurring problems and explain them to the product or operations team.
4. Keep response times and unresolved cases under control.

These are more useful than “dynamic self-starter” or “five years of experience.” They tell applicants what matters and give reviewers something concrete to look for.

2. Keep only genuine hard requirements

A hard requirement should prevent the person from doing the job as offered. Examples may include a legally required licence, an unavoidable location, a language genuinely needed for the work or another practical constraint.

Move preferences out of the rejection pile. A degree, exact title, uninterrupted work history or experience at a famous company should not become mandatory merely because it makes screening faster.

Current employer surveys show skills-based hiring is increasingly used during screening and interviews. NACE's Job Outlook 2026 summary is one useful benchmark. The phrase matters less than the behaviour: decide what somebody needs to do, then look for evidence they have done something comparable.

3. Let the job ad invite adjacent evidence

Say this plainly:

You do not need to have held this exact title. If you have done comparable work in another setting, show us the clearest example.

That sentence does more than “we welcome diverse applicants.” It tells somebody with an unusual background how to make the connection.

Also tell people the salary range, location, schedule and important constraints. Broad does not mean vague. Honest details help applicants decide for themselves whether the role is workable.

4. Organize the pool by evidence

Do not ask software, “Who is the best person?” Ask smaller questions:

• Which resume shows evidence for each job outcome?
• What exact sentence or project supports that finding?
• What important requirement is not demonstrated?
• What remains unclear and needs a question?

The result should be a review queue with evidence, not an oracle with a mysterious score.

If you use Resume Ranker, upload the PDF resumes with the job description and add the four outcomes as custom criteria. It works best with batches of up to 500 resumes, so a pool of 1,000 can be reviewed in two batches using the same instructions. Use the rankings as a starting point for human review, not as an automatic rejection list.

5. Audit the top, middle and bottom

Before trusting the order, inspect a mixed sample:

• the 20 or 30 strongest-looking matches;
• at least 10 from the middle;
• at least 10 selected randomly from the lower end;
• unusual career paths that the system may have interpreted poorly.

For every surprising result, ask why it happened. Did the resume use different language? Did the criteria reward an exact title? Did missing information get treated as failure? Rewrite the instructions and review affected candidates again.

This is the step that turns “AI reviewed 1,000 resumes” from a sales claim into a process you can examine.

6. Make a small human shortlist

The broad search ends here. The next stage should be deliberately narrow.

Select a manageable group for the same short first conversation. Ask the same core questions and score the same job-related evidence. Advance only the strongest few to a job-shaped exercise or structured final interview.

You are not trying to interview 1,000 people. You are making sure the small group you interview was not chosen from an unnecessarily small corner of the market.

Run a broad-versus-narrow test

You can test the argument on one real vacancy without changing the entire company.

After the application period closes, create two shortlists from the same pool.

Narrow shortlist: use the traditional requirements—exact titles, conventional industry experience, degree and years of experience.

Broad shortlist: use the four job outcomes, genuine hard requirements and transferable evidence.

Then compare:

• Who appears only on the broad shortlist?
• What evidence would the narrow rules have missed?
• Which broad candidates survive a human review?
• Do any narrow requirements fail to distinguish the stronger applicants?
• Does a random lower-ranked audit reveal somebody the broad criteria still missed?

Do not hire from a spreadsheet just to prove the idea. The experiment is successful if it shows you where your original picture of the candidate was too narrow—or confirms that a requirement really is necessary.

Where the argument stops

“Get 1,000 resumes” is a provocation, not a quota.

A highly licensed role in a small location may have only a handful of plausible candidates. A business should not buy broad exposure if it cannot provide a real vacancy, secure application handling and basic communication. Nor should it encourage people to spend hours on an application merely to feed a database.

Hiring laws also vary by location. In the United States, the EEOC advises small employers to screen applications consistently, apply the same standards to people seeking the same position and ensure selection practices are job-related where required. Read the EEOC's small-business guidance. Treat this article as workflow guidance, not legal advice for every jurisdiction.

The principle is narrower than the headline:

Do not make the applicant pool small merely because your review process is weak.

Cast widely enough to be surprised. Write down what the job needs. Let software help you examine more evidence than you could alone. Audit what it misses. Then make a small, human decision you can explain.