ATS Software That Automatically Screens and Ranks Resumes

Tested prompts for ats resume screening software compared across 5 leading AI models.

BEST BY JUDGE SCORE Claude Opus 4.7 9/10

The prompt we tested

You are an ATS (Applicant Tracking System) resume screening assistant for recruiters. Analyze each candidate resume against the provided job requirements, extract key qualifications, score the fit, and rank candidates.

Instructions:
For each candidate, output: Rank, Candidate Name, Match Score (0-100), Key Matched Skills, Missing Requirements, Years of Relevant Experience, and a 1-sentence Recommendation (Advance / Maybe / Reject). Present results as a ranked table followed by brief notes, keep scoring criteria consistent across all candidates, and flag any disqualifying gaps (missing must-have skills, insufficient experience, location mismatch).

Job Requirements and Candidate Resumes:
Job: Senior Python Backend Engineer — must-have: 5+ years Python, AWS, PostgreSQL, REST APIs; nice-to-have: Kubernetes, FastAPI. Candidate 1: Maria Chen — 7 yrs Python at fintech, built REST APIs on AWS (Lambda, RDS/Postgres), led team of 4, some Docker exposure. Candidate 2: James Patel — 3 yrs Python/Django, MySQL, no cloud experience, CS degree 2021. Candidate 3: Priya Shah — 6 yrs Python + FastAPI, deep AWS + Kubernetes, PostgreSQL daily, open-source contributor.

Produce a structured screening report that ranks candidates from best to worst fit, with clear reasoning a recruiter can act on.

Model comparison

ModelQualityCostLatencyTokens
Claude Opus 4.7 9 $0.0950 17.6s 532 / 1160
Claude Haiku 4.5 8 $0.0062 10.9s 329 / 1180
GPT-5.4 8 $0.0106 12.8s 284 / 656
Grok 4.1 Fast Reasoning 8 $0.0003 8.1s 432 / 428

Outputs

Claude Opus 4.7 9/10
# ATS Screening Report: Senior Python Backend Engineer

## Ranked Candidate Summary

| Rank | Candidate | Match Score | Key Matched Skills | Missing Requirements | Relevant Experience | Recommendation |
|------|-----------|-------------|-------------------|---------------------|---------------------|----------------|
| 1 | Priya Shah | 98 | Python, AWS, PostgreSQL, REST APIs (implied), FastAPI, Kubernetes | None | 6 yrs | **Advance** |
| 2 | Maria Chen | 88 | Python, AWS (Lambda, RDS), PostgreSQL, REST APIs, leadership | FastAPI, Kubernetes (Docker only) | 7 yrs | **Advance** |
| 3 | James Patel | 25 | Python (Django) | AWS ❌, PostgreSQL ❌, 5+ yrs exp ❌ | 3 yrs | **Reject** |

---

## Scoring Criteria (applied consistently)
- **Must-haves (70 pts total):** Python 5+ yrs (20), AWS (20), PostgreSQL (15), REST APIs (15)
- **Nice-to-haves (20 pts):** Kubernetes (10), FastAPI (10)
- **Bonus (10 pts):** Seniority signals — leadership, OSS, domain depth

---

## Candidate Notes

### 🥇 Rank 1 — Priya Shah (Score: 98) — **Advance**
- **Strengths:** Hits every must-have and both nice-to-haves. 6 yrs Python with production FastAPI, deep AWS, daily PostgreSQL, and Kubernetes experience. Open-source contributions signal strong engineering craft.
- **Gaps:** REST API experience not explicitly stated but implied via FastAPI.
- **Action:** Fast-track to technical interview; likely top-of-funnel hire.

### 🥈 Rank 2 — Maria Chen (Score: 88) — **Advance**
- **Strengths:** Exceeds Python experience (7 yrs), strong AWS stack (Lambda + RDS/Postgres), proven REST API delivery in fintech, team lead experience (4 reports).
- **Gaps:** No FastAPI or Kubernetes exposure (Docker only) — nice-to-haves only, not disqualifying.
- **Action:** Advance to technical + systems design round; strong senior candidate with leadership upside.

### 🚫 Rank 3 — James Patel (Score: 25) — **Reject**
- **Strengths:** Python/Django foundation, recent CS degree.
- **🚩 Disqualifying Gaps:**
  - Only **3 yrs experience** (must-have: 5+) ❌
  - **No AWS / cloud experience** ❌
  - **MySQL, not PostgreSQL** ❌
- **Action:** Reject for this senior role. Consider for a mid-level opening if one exists.

---

## Recruiter Summary
Two strong advances (Shah, Chen). **Priya Shah is the standout** — rare full-stack match including both nice-to-haves. **Maria Chen is a close second** with superior leadership signals and domain experience, making her a compelling alternative if cultural/team fit favors fintech background. **James Patel should be declined** for this requisition due to three disqualifying must-have gaps.
Judge notes: Virtually production-ready with consistent scoring, clear disqualifier flags, and actionable recruiter guidance — the only nitpick is the minor hedging on Priya's REST APIs ("implied via FastAPI") when FastAPI is inherently REST-based and should be stated with confidence rather than flagged as a gap.
Claude Haiku 4.5 8/10
# ATS Screening Report: Senior Python Backend Engineer

## Ranked Candidates Table

| Rank | Candidate Name | Match Score | Key Matched Skills | Missing Requirements | Years Relevant Experience | Recommendation |
|------|---|---|---|---|---|---|
| 1 | Priya Shah | 95/100 | Python (6 yrs), FastAPI, AWS, Kubernetes, PostgreSQL, REST APIs | None significant | 6 years | **ADVANCE** |
| 2 | Maria Chen | 82/100 | Python (7 yrs), AWS, PostgreSQL, REST APIs, Team Leadership | Kubernetes, Limited FastAPI mention | 7 years | **ADVANCE** |
| 3 | James Patel | 35/100 | Python (3 yrs), Django, CS Degree | AWS, PostgreSQL, REST APIs, Kubernetes | 3 years | **REJECT** |

---

## Detailed Analysis

### 🟢 **Rank 1: Priya Shah — 95/100**
**Recommendation: ADVANCE to interview**

**Matching Strengths:**
- ✅ **5+ years Python requirement**: 6 years experience confirmed
- ✅ **AWS**: Deep expertise (exceeds requirement)
- ✅ **PostgreSQL**: Daily usage (exceeds requirement)
- ✅ **REST APIs**: Implied through FastAPI work
- ✅ **Kubernetes** (nice-to-have): Strong expertise
- ✅ **FastAPI** (nice-to-have): Primary framework used

**Gaps:** Minimal; no disqualifying issues.

**Recruiter Notes:** Ideal candidate who exceeds must-haves and checks all nice-to-haves. Open-source contributor suggests strong engineering practices and community engagement. Ready for immediate advancement.

---

### 🟡 **Rank 2: Maria Chen — 82/100**
**Recommendation: ADVANCE to interview**

**Matching Strengths:**
- ✅ **5+ years Python requirement**: 7 years at fintech (exceeds requirement)
- ✅ **AWS**: Proven hands-on experience (Lambda, RDS)
- ✅ **PostgreSQL**: RDS/Postgres experience confirmed
- ✅ **REST APIs**: Built APIs on AWS Lambda
- ✅ **Team Leadership**: Led team of 4 (valuable for senior role)

**Gaps:**
- ⚠️ **Kubernetes**: No mention (nice-to-have, but increasingly expected at senior level)
- ⚠️ **FastAPI**: Not mentioned; likely using different framework
- ⚠️ **Docker**: Only "some exposure" (modern backend engineering expectation)

**Recruiter Notes:** Strong foundational fit with proven AWS + Python depth and leadership experience. Lacks containerization/orchestration skills that Priya has. Would need to assess learning velocity on Kubernetes during interview. Fintech background is valuable for reliability requirements.

---

### 🔴 **Rank 3: James Patel — 35/100**
**Recommendation: REJECT**

**Matching Strengths:**
- ✅ **Python**: 3 years experience
- ✅ **CS Degree**: Formal education (2021 graduate)
- ✅ **Framework experience**: Django (different from REST API context but transferable)

**Critical Gaps (Disqualifying):**
- ❌ **Experience shortfall**: 3 years << 5+ years requirement (40% below minimum)
- ❌ **AWS**: No cloud experience mentioned (must-have requirement)
- ❌ **PostgreSQL**: MySQL background, no PostgreSQL experience
- ❌ **REST APIs**: No explicit mention
- ❌ **Kubernetes**: Not mentioned
- ❌ **FastAPI**: Not mentioned

**Recruiter Notes:** Junior-level candidate (2021 grad, ~3 years experience) does not meet senior role requirements. Missing ALL must-have technical skills except Python. Better positioned for Mid-Level Python Developer role after 2+ more years of AWS/cloud experience. Recommend rejection for this position.

---

## Summary & Recommendations

| Action | Candidates |
|--------|---|
| **ADVANCE** | Priya Shah, Maria Chen |
| **HOLD/MAYBE** | — |
| **REJECT** | James Patel |

**Key Observations:**
1. **Top tier (Priya)**: Exceeds all requirements; ready for immediate interview loop
2. **Strong candidate (Maria)**: Meets all must-haves; Kubernetes gap is trainable given 7 yrs Python + AWS mastery
3. **Misfit (James)**: Junior candidate; 2-year experience and cloud skills gap are disqualifying for senior role

**Recruiter Next Steps:**
- Schedule Priya for technical round immediately
- Schedule Maria with focus on containerization/orchestration learning plan
- Decline James professionally; suggest revisiting in 2-3 years or alternative junior roles
Judge notes: Output is thorough, accurate, and immediately actionable, but the detailed analysis adds minor redundancy (re-listing obvious gaps like "FastAPI not mentioned" twice) and the note that Django is "different from REST API context" is slightly inaccurate since Django REST Framework is a common REST API tool—small errors that would prompt a light edit before production use.
GPT-5.4 8/10
## ATS Screening Report — Senior Python Backend Engineer

### Ranked Candidates

| Rank | Candidate Name | Match Score (0-100) | Key Matched Skills | Missing Requirements / Gaps | Years of Relevant Experience | Recommendation |
|---|---|---:|---|---|---:|---|
| 1 | Priya Shah | 96 | 6 yrs Python, FastAPI, AWS, Kubernetes, PostgreSQL, REST API-aligned backend experience, open-source contributions | No clear gap stated; REST APIs not explicitly named but strongly implied by FastAPI/backend background | 6 | **Advance** — Strong match across all must-haves plus both nice-to-haves, with no obvious disqualifying gaps. |
| 2 | Maria Chen | 90 | 7 yrs Python, AWS, REST APIs, PostgreSQL (RDS/Postgres), fintech backend experience, leadership experience | Kubernetes not mentioned; FastAPI not mentioned; only some Docker exposure | 7 | **Advance** — Meets all core must-haves solidly and brings strong backend/AWS experience, though missing the preferred modern framework/container orchestration signals. |
| 3 | James Patel | 38 | 3 yrs Python, Django, backend development foundation, CS degree | **Disqualifying gaps:** under 5 years Python, no AWS, no PostgreSQL, must-have experience shortfall; MySQL instead of Postgres | 3 | **Reject** — Lacks multiple must-have requirements, especially minimum Python experience, AWS, and PostgreSQL. |

---

### Scoring Notes
Consistent criteria used across all candidates:
- **Must-haves weighted most heavily:** 5+ years Python, AWS, PostgreSQL, REST APIs
- **Nice-to-haves as differentiators:** Kubernetes, FastAPI
- **Additional positives:** leadership, relevant backend domain depth, strong technical signals
- **Disqualifiers flagged:** missing must-have skills, insufficient years of experience, location mismatch if stated

---

### Candidate Notes

**1) Priya Shah**
- Best overall fit for the role.
- Clearly satisfies all stated must-haves: 6 years Python, deep AWS, PostgreSQL, and likely REST/backend API work through FastAPI.
- Exceeds baseline with both nice-to-have skills: **Kubernetes** and **FastAPI**.
- Open-source contribution adds positive signal for engineering maturity.

**2) Maria Chen**
- Strong, recruiter-ready candidate with all core must-haves covered.
- 7 years of Python plus direct AWS and Postgres-backed REST API experience make her a high-confidence fit.
- Leadership of a team of 4 is a bonus for a senior-level role.
- Slightly below Priya only because **Kubernetes** and **FastAPI** were not mentioned.

**3) James Patel**
- Has some backend Python experience, but not enough for this senior role.
- Falls short on minimum required experience and lacks two critical stack requirements: **AWS** and **PostgreSQL**.
- Better suited for a junior or mid-level backend opening rather than this requisition.

### Final Recruiter Action
- **Advance:** Priya Shah, Maria Chen
- **Reject:** James Patel
Judge notes: The output is well-structured and actionable, but Priya Shah's 96 score versus Maria Chen's 90 is somewhat arbitrary given the thin resume data provided, and the note about REST APIs being "strongly implied" for Priya while not flagging it more critically slightly undermines the scoring consistency it claims.
Grok 4.1 Fast Reasoning 8/10
### ATS Screening Report: Senior Python Backend Engineer

| Rank | Candidate Name | Match Score (0-100) | Key Matched Skills | Missing Requirements | Years of Relevant Experience | Recommendation |
|------|----------------|---------------------|--------------------|----------------------|------------------------------|---------------|
| 1    | Priya Shah    | 100                 | 6+ yrs Python, FastAPI (REST APIs), deep AWS, PostgreSQL (daily), Kubernetes | None | 6 | Advance: Perfect match on all must-haves plus both nice-to-haves and open-source contributions. |
| 2    | Maria Chen    | 90                  | 7 yrs Python, REST APIs, AWS (Lambda/RDS), PostgreSQL (RDS/Postgres), leadership/Docker | Kubernetes, FastAPI | 7 | Advance: Strong fit on all must-haves with bonus leadership and Docker exposure. |
| 3    | James Patel   | 35                  | 3 yrs Python/Django (implies some REST APIs) | 5+ yrs Python, AWS, PostgreSQL (uses MySQL) | 3 | Reject: Disqualifying gaps in experience years, AWS, and database (MySQL instead of PostgreSQL). |

### Screening Notes
- **Scoring Criteria**: Must-haves (Python 5+ yrs: 25pts, AWS: 25pts, PostgreSQL: 25pts, REST APIs: 25pts = 100pts max); nice-to-haves add no points but confirm top fits (e.g., Priya at 100). Partial matches deduct proportionally (e.g., James: Python 15/25, REST partial 10/25, zeros on AWS/Postgres).
- **Overall Ranking Rationale**: Priya is ideal (all reqs + extras); Maria excels on must-haves with leadership edge over juniors; James has disqualifying gaps (under 5 yrs, no AWS/cloud, wrong DB).
- **Recruiter Action Items**: Advance top 2 to interviews; reject #3. No location mismatches noted. Consistent evaluation based solely on provided resume data vs. job reqs.
Judge notes: The output is clean and actionable, but giving Priya a perfect 100 when scoring criteria exist (and no candidate can realistically be "flawless" against a job spec without an interview) slightly undermines credibility, and the scoring methodology explanation, while helpful, feels retrofitted rather than principled.

Related queries