Resume vs Job Description Match Score — explainable, skills-only

Stop your AI from guessing. AI resume screening is a black box and gets accused of bias. This tool returns a sourced, structured answer in seconds.

Use when: a recruiting agent or ATS needs to score a resume against a job description: 0-100 fit, matched and missing must-have skills, experience fit and interview questions for gaps. Explainable, skills-only, bias-safe; resume never stored.

For recruiting AI agents, ATS integrations and hiring teams: send a resume and a job description as text, get back:

• Score 0–100 and verdict: STRONG_MATCH (75+), POSSIBLE_MATCH (55–74), WEAK_MATCH
• Must-have and nice-to-have skills: matched vs missing (read from the JD's Requirements / Nice-to-have sections)
• Experience fit: years from job date ranges (education lines ignored) vs years required
• Gaps and interview questions for missing or thinly evidenced skills, with what a strong answer sounds like

Why this one

• Explainable: every point of the score traces to a listed skill or the experience rule. No black box.
• Fair by design: scores only skills and experience. Never name, age, gender, photo, caste, religion, marital status, location or college.
• Private: resume text is processed in memory, never stored, never returned. Output contains skill names and numbers only.
• Built by a recruiter who places senior AI/ML, MLOps and DevOps engineers.

Input

{ "resume_text": "…", "job_description": "…" }

Output (example)

{ "score": 85, "verdict": "STRONG_MATCH",
  "summary": "5/6 must-have skills, 1/2 nice-to-have; experience 8.3 years vs 5+ required.",
  "must_have": { "matched": ["Python","Kubernetes","Docker","CI/CD","GitHub Actions"], "missing": ["Terraform"] },
  "interview_questions": [{ "skill": "Terraform", "question": "Tell me about the last real project where you used Terraform…", "strong_answer": "…" }] }

Scoring

Must-have skills 65%, nice-to-have 15%, experience 20% (must-have 80% when the JD has no nice-to-have list). ~130 tech skills with common aliases (EKS → Kubernetes, PyTorch → Deep Learning).

Important

Decision support for a human recruiter — not an automated hiring decision. Plain text only in this version.

Pricing

Pay per match. Invalid input is not charged.