A third of your applicants can't take the job. You're finding out one resume at a time.

You posted a role in Ohio. By the end of the week you had applications from Lagos, Manila, Cape Town, Karachi, and Dhaka. Some of them were excellent — better, on paper, than the local candidates. And almost none of them could take the job.

This is the part of modern recruiting nobody puts in the webinar. When you post on the open web, you're not advertising to your city or even your country. You're advertising to the planet. Across the applications we've watched come through, candidates originated in more than 60 countries. For a typical US-based role, a real chunk of your inbound is international — talented people who found your post, recognized the work, and applied in good faith, without the work authorization that would let you actually hire them.

Nobody's the villain here. The candidates are doing exactly what the system invites them to do. The job boards are doing what job boards do — maximizing reach, because reach is the product. The recruiter is the one left holding the cost, and the cost is brutal in a way that never shows up on a report: you discover the eligibility problem one resume at a time, by hand, after you've already invested the attention.

Reach was never the same thing as fit

The open-web model sells you a number: impressions, views, applicants. Big numbers feel like progress. But an applicant who can't legally work the role isn't a lead with a small problem — they're not a lead at all, for this job. And when a meaningful share of your pile falls into that bucket, your "47 applicants" is really 30-something you can consider, minus the ones who aren't qualified for unrelated reasons. The headline number lied to you, and you paid for the lie in screening hours.

The honest reframe: the size of your applicant pool tells you almost nothing about your odds of a hire. What matters is how fast you can isolate the candidates who are both qualified and eligible. Every minute spent manually confirming someone can't take the job is a minute stolen from the someone who can.

The manual screen is the most expensive screen

Think about what actually happens. A resume comes in. A recruiter opens it, reads the experience, gets a little excited, scrolls to the location, sees a city eight time zones away, checks for a work-authorization note, finds none, and closes the tab. Ninety seconds, gone, with nothing to show for it. Now multiply that across an entire req load and a global applicant flood. That's not screening. That's a tax you pay in your most focused hours of the day.

The fix isn't to read faster. It's to stop reading the ones you were always going to close. When you build triage rules in Cortex, eligibility becomes the first gate, not the last discovery. A rule that checks location and work authorization runs on every applicant the instant they apply — the ineligible ones get routed and answered, the eligible ones surface to the top, and your ninety seconds go to people you can actually hire.

Stop waiting for the right applicant. Go get them.

Here's the deeper shift, and it's the one that separates recruiters who are buried from recruiters who are ahead: the best candidate for your role probably isn't in your applicant pile at all. They're employed, they're not looking, and they live exactly where you can hire them. Inbound will never surface that person, because that person will never apply.

Sourcing solves the eligibility problem and the quality problem in one move. HiredGPT lets you search 850 million candidates in plain language — paste the job description or just describe who you want, including where they need to be based — and pull a list of people who match. You set the location and eligibility constraints up front, so the flood never happens. You're not sorting the world's applicants anymore; you're selecting from the right ones.

And the outreach doesn't have to be a second job. Cortex can run automated sourcing and candidate outreach in the same flow, so the eligible, qualified people you surface actually hear from you while the role is open. If you'd rather skip the setup entirely, the Ask feature takes a plain-language instruction — "find me eligible warehouse supervisors near Columbus and draft outreach" — and runs it for you.

What about genuinely global roles?

None of this is an argument against international talent. If the role is truly remote and you can hire across borders, the same tools work in your favor — you target the regions you can actually employ from instead of treating every applicant identically. The problem was never that international candidates applied. The problem is that the open-web model gives you no way to match people to the roles they're eligible for, so everyone lands in the same undifferentiated pile and you sort it by hand. Triage and sourcing give you that matching layer. You can manage your live reqs, outreach, and candidate status from the campaigns dashboard once it's running.

A cleaner pipeline, by design

The recruiters who feel calm in this market aren't getting fewer applicants. They've just stopped letting the raw pile dictate their day. Eligibility and fit are decided before a human gets involved, the qualified-and-eligible candidates rise to the top automatically, and the genuinely strong people who'd never have applied get found and contacted directly.

You can keep treating every application as a thing you personally have to open, read, and rule out. Or you can post the role, let the rules handle the first pass, and spend your attention only on people who can say yes.

Where to start

The straightforward sequence: post your job so inbound has somewhere to land, set up eligibility and fit rules in Cortex so the pile pre-sorts itself, then use HiredGPT to source eligible candidates directly instead of waiting. If you want the full picture first, the platform capabilities overview shows how the pieces fit, and the getting-started guide walks the first week. When you're ready to post your next role, the flood will be someone else's problem.

FAQ

Questions recruiters actually ask

How many job applicants are international?

For a typical US-based role posted on the open web, a meaningful share of applicants apply from outside the country — across the applications we've seen, candidates came from more than 60 countries. Many are genuinely qualified but unable to work where the role is located, which means raw applicant counts overstate how many people you can actually hire.

How do recruiters check work authorization without reading every resume?

Instead of discovering work-authorization issues one resume at a time, you can set it as an up-front triage rule. With Cortex, a rule can flag or route candidates based on location and authorization the moment they apply, so ineligible applicants are handled automatically before a recruiter ever opens them.

Is it legal to filter job applicants by work authorization?

Employers can screen for whether a candidate is legally authorized to work for the employer in the job's location, and many roles require it. This is general information rather than legal advice, and authorization and sponsorship rules vary by country and role, so confirm specifics with an employment attorney. The practical point is that screening on a clearly job-related requirement up front saves hours of manual review.

Why am I getting so many unqualified or ineligible applicants?

Open job boards optimize for reach, so a single post can attract applicants worldwide regardless of fit or eligibility. The result is a large pile where the hireable candidates are a thin slice. Automated triage rules and direct sourcing let you cut to the eligible, qualified candidates instead of manually sorting everyone who applied.

How can I find qualified candidates instead of waiting for applicants?

Sourcing flips the model: instead of waiting for applicants, you search for the people you want. HiredGPT lets you search a database of around 850 million candidates in plain language, so you can filter for location and eligibility up front and reach qualified people directly, whether or not they ever applied.

Does HiredAI support international and remote hiring?

Yes. The point of triage and sourcing isn't to reject international candidates, it's to match candidates to the right roles. For genuinely remote or global positions, the same tools let you target candidates in the regions you can actually hire from, instead of treating every applicant the same regardless of where the job allows them to work.