u/Expensive-Swan-5009

Changed how I handle initial screening for high-volume roles — went from 6+ hours to under 30 minutes

Changed how I handle initial screening for high-volume roles — went from 6+ hours to under 30 minutes

Wanted to share something that's been working for me in case anyone else is dealing with the same volume problem.

I run a small recruiting operation — mostly mid-level tech and ops roles. Nothing crazy, but the application volume has been brutal lately. I had a senior frontend developer role last quarter that pulled in 310 applications in the first week. Another operations manager role got 240+.

My old process was: download all resumes → open in tabs → scan each one for 30-60 seconds → tag yes/no/maybe in a spreadsheet → do a deeper read on the maybes → build the shortlist. For 300 resumes, that's easily 6-8 hours of screening before I've even picked up the phone. And honestly, by resume 150 or so, I'm not really reading anymore. I'm pattern-matching on formatting and keywords, which means I'm probably missing solid candidates who just describe their experience differently.

I know some of you use ATS platforms with built-in screening, but I've found that most of them just do keyword matching. If my client's JD says "React experience" and the candidate wrote "built production web apps with component-based JavaScript frameworks" — that's the same skillset, but keyword matching doesn't catch it. And the bigger ATS platforms are overkill for a small operation — I don't need a $500/month enterprise tool to screen resumes.

What I switched to:

I started using a tool called HireSort (hiresort.ai) a few days ago. The workflow is basically:

  1. Upload the resumes in batches of up to 100 at a time (PDFs, DOCX, zip files)
  2. Set up a scoring rubric for the specific role. Each criterion gets an importance percentage and they all sum to 100. So for that frontend dev role it was something like: React/frontend framework experience = 25%, years of relevant work = 20%, system design / architecture = 15%, communication signals = 10%, etc.
  3. Hit run. The AI reads every resume and scores each candidate against the rubric.
  4. I get a ranked list with an explanation for each score — not just a number, but actual reasoning like "Scored 8/10 on React because resume shows 3 years of production React at two companies, including state management with Redux and performance optimization work."

The whole thing takes about 15-20 minutes of setup and a few minutes of processing. Then I spend maybe 10-15 minutes reviewing the top 25-30 candidates, spot-checking a few scores to make sure the reasoning tracks.

What I've noticed after using it for ~4 months:

  • The shortlist quality is genuinely better than what I was producing manually. Not because the AI is smarter than me, but because it doesn't get fatigued. It gives resume #280 the same attention as resume #3.
  • I catch candidates I would have missed. People who describe their skills in non-standard ways or have unconventional career paths that don't scream "match" on a quick scan but actually have the right experience.
  • My clients have noticed. My time-to-shortlist has dropped significantly, which means I'm presenting candidates faster. Two clients specifically mentioned it.
  • The rubric setup forces me to actually think about what matters before I start screening, instead of having vague criteria in my head that shift as I get tired.

What it doesn't do:

It's not a replacement for the actual evaluation. I still read the shortlisted resumes in detail, I still do phone screens, I still assess culture fit. It's a first-pass filter that handles the volume so I can focus on the part of the job that actually requires human judgment.

It also doesn't handle reference checks, interview scheduling, or any of the other ATS stuff. It does one thing — screens and ranks resumes. If you need a full ATS, this isn't that.

The rubric thing was the biggest change for me honestly. Having to put numbers on what matters for each role — and having those numbers be transparent and auditable — has made my conversations with hiring managers much more productive. Instead of "find me someone good," we now agree upfront that React experience is 25% of what matters and leadership signals are 15%. When I present the shortlist, I can point to exactly why each candidate is there.

Curious if anyone else has changed their screening workflow recently. What's working for you on high-volume roles?

u/Expensive-Swan-5009 — 6 days ago