SkillMatcher
Start free
NewHiring Copilot drafts the job and runs the match

Read every resume.Interview only six.

SkillMatcher parses every applicant you receive, scores them against the role on six weighted dimensions, and hands your team a ranked shortlist — with the evidence behind every number, not just the number.

Start matching freeSee a run
512
resumes scored per run
38s
median run time
6
weighted dimensions

Match run

Senior Backend Engineer

Remote · Europe

Completed
Resumes scored0 / 512
  • 1
    0

    Priya Raghavan

    Senior Backend Engineer · 8y

  • 2
    0

    Tomas Lindqvist

    Platform Engineer · 6y

  • 3
    0

    Adaeze Okonkwo

    Staff Software Engineer · 9y

  • 4
    0

    Mateo Herrera

    Backend Engineer · 5y

508 candidates below the 80 threshold were filtered out.

  • PDF
  • DOCX
  • Plain text
  • Scanned pages · OCR
  • Greenhouse export
  • Lever export
  • LinkedIn PDF
  • Bulk ZIP upload
  • Email forward
  • REST API
  • Career-site webhook

The pipeline

A PDF goes in. A ranked, defensible shortlist comes out.

Nothing here is a black box — every score traces back to a line the parser actually read on the page.

  1. Ingest

    PDF, DOCX, or a link

  2. Parse

    Structured candidate record

  3. Score

    Six weighted dimensions

  4. Rank

    Ordered shortlist

PRIYA RAGHAVAN
Senior Backend Engineer
priya@example.dev · +44 20 7946 · London, UK

Experience

Staff Engineer, Monzo · 2021–now
Senior Backend Engineer, Bolt · 2018–2021

Skills

Go · Kubernetes · PostgreSQL · gRPC · Kafka · Terraform

Education

BSc Computer Science — Imperial College London
Priya RaghavanSenior Backend EngineerLondon, UK8.5 yearsGo · Kubernetes · PostgresBSc CS, Imperial

Candidate record

resume_8f31c2
NamePriya Raghavan
TitleSenior Backend Engineer
LocationLondon, UK
Experience8.5 years
SkillsGo · Kubernetes · Postgres
EducationBSc CS, Imperial

0

Match

  • Technical0
  • Skills0
  • Experience0
  • Soft skills0
  • Quality0
  • Education0

Shortlist · 512 scanned

Ready for review
  • 1

    Priya Raghavan

    Staff Engineer · Monzo

    94
  • 2

    Tomas Lindqvist

    Platform Engineer · Klarna

    91
  • 3

    Adaeze Okonkwo

    Staff SWE · Paystack

    88

Scoring

One number, six arguments, all of them visible.

A match score is only useful if you can take it apart. Every candidate carries the six sub-scores that produced their total, the weights that were in force when the run happened, and the reason for every rejection.

Change a weight and the whole shortlist re-ranks — no re-parsing, no waiting for another batch job.

Deterministic re-runsPer-job weightsWritten rejection reasons

Weights

Senior Backend Engineer

v3 · saved
  • Technical0%

    Depth in the stack the role runs on, weighted by recency.

  • Skills0%

    Named tools and skills the requirements ask for.

  • Experience0%

    Years, seniority, and the shape of past teams.

  • Education0%

    Degrees and certifications, when the role needs them.

  • Soft skills0%

    Ownership, communication, and mentoring signals.

  • Quality0%

    How much the document actually evidences its claims.

The platform

Everything around the match, not just the match.

Scoring is the easy part to demo and the hard part to trust. The rest of the product exists so the number holds up when someone asks you to explain it.

Hiring Copilot

Describe the role in a sentence. The copilot drafts the requirements, proposes the weights, runs the match, and tells you which candidates it rejected and why.

Backend role, Go and Kubernetes, at least 5 years, EU remote.
Drafted “Senior Backend Engineer” and weighted technical skill at 35%. Matched 512 resumes — 4 clear the bar.

Talent pool

Every resume you have ever received stays parsed and searchable. Open a new role and it is scored against the whole pool, not just this week’s applicants.

18,402
candidates already scored

Bulk ingest

Drag in a folder of 500 PDFs or point us at your ATS export. Parsing runs in the background and failures come back with the reason, not a silent skip.

Weights you set

A staff role and a first engineering hire should not be scored the same way. Move the weights per job and re-run — the shortlist reorders in seconds.

Evidence trail

Every score links to the lines that produced it, and every rejection carries a written reason you can put in front of a candidate or a regulator.

Team controls and an API behind all of it

Scoped API keys, per-seat roles, usage metering, and invoices — so the recruiting team and the platform team can both live in the same account without stepping on each other.

  • Roles & seats
  • Scoped API keys
  • Usage metering
  • Invoices

Developers

The dashboard is one client. Yours can be another.

Everything the interface does runs on the same public API — upload a resume, create a job, trigger a run, read the sub-scores. Issue a scoped key, meter it per environment, and revoke it without touching anyone’s session.

Create an API key
POST /v1/matches200 OK
curl -X POST https://api.skillmatcherai.com/v1/matches \
  -H "Authorization: Bearer $SKILLMATCHER_KEY" \
  -d '{ "jobId": "job_2b91", "minScore": 80 }'
{
  "matchRunId": "run_7c40a2",
  "totalResumes": 512,
  "totalMatches": 4,
  "matches": [
    {
      "resumeId": "resume_8f31c2",
      "score": 94,
      "detailedScores": {
        "technicalScore": 96,
        "skillScore": 93,
        "experienceScore": 89,
        "softSkillScore": 88,
        "qualityScore": 91,
        "educationScore": 84
      },
      "locationMatched": true,
      "failureReasons": []
    }
  ]
}

Your next shortlist is already in the pile.

Upload the resumes you have been meaning to get to, point them at one open role, and see the ranking before this tab loses your attention.

Start freeWatch a run again

No card required · 50 free resume scans