CandidatesFor recruiters3 min read

Bulk-uploading candidates

Drop in up to 100 resumes at once. Each is parsed, scored against a job, and ranked — so you only invite the top of the pile.

Key takeaways

  • Candidates → *Add Candidates* → *Bulk upload*. Drop up to 100 resumes.
  • Each scan costs 0.05 credits (5 credits per 100). The AI scores them against a job you pick.
  • You get a ranked list and choose who to invite — bulk-invite the top N in one click.
  • Bulk upload is the highest-leverage flow on the platform. Use it whenever you have more than ~20 resumes to triage.

Bulk upload is where RecruitMe earns its keep. If you have 80 resumes for an open role, the difference between triaging them one by one (4 hours) and bulk-scoring (5 minutes) is the value of the platform.

The five-minute path

[@portabletext/react] Unknown block type "undefined", specify a component for it in the `components.types` prop

Cost

Each resume scan costs 0.05 credits. A 100-resume batch is 5 credits — well under one interview's worth, and saves you hours of manual review.

TIP

If you are recruiting at high volume (1000+ candidates/month), Enterprise contracts can often negotiate Resume Scan to zero. Worth asking your account manager.

How to read the ranked list

Each row shows:

  • Name + email parsed from the resume
  • Profile Score (0–100) against the job
  • Top matched skills — the skills the resume has that match the JD's Required Skills
  • Years of experience parsed from work history
  • Last job title and company

Sort by Profile Score descending to see the top of the pile. Most teams invite the top 20–30% and ignore the rest at this stage.

What the score is NOT

WARNING

The Profile Score is a *resume-fit* signal, not a hire/no-hire judgement. A score of 65 doesn't mean the candidate is bad — it might mean their resume undersold them, or they wrote it for a different role. Use the score to *prioritise interviewing*, not to filter people out completely.

Common bulk-upload mistakes

  • Uploading without picking a job first. The candidates land in your pool unscored, defeating the point.
  • Inviting all 100 just because credits are cheap. Each interview is 0.5–1 credit; 100 interviews = 50–100 credits. Be deliberate — invite the top 20% who you actually want to see in interview.
  • Skipping resumes that scored low. Read the top 5 low-scorers as a calibration step. If you'd interview them but the AI scored them low, your JD or skill list may be tuned wrong.

Next: how to filter and search across your full candidate list.

Frequently asked questions

What file formats are supported?

PDF, DOCX, and TXT. Image-only PDFs (scanned) work but OCR is best-effort. Avoid them when you can.

How long does parsing take?

About 5–15 seconds per resume, but they run in parallel. A 100-resume batch usually completes in 2–4 minutes total. You can leave the page during processing — the platform finishes in the background.

How is the score calculated?

Multi-parameter AI scoring across skills (40%), experience (30%), education (15%), and location (10%) relative to the job you picked. Higher is better; the score is comparable across candidates in the same job.

Can I re-score the same candidates against a different job?

Yes — add the candidate to the new job via *Add to job* on their profile, and a fresh score is generated for that role.

Next steps

Related articles