ChatGPT Prompts for Reviewing and Scoring Resumes

Tested prompts for chatgpt prompt to review resumes compared across 5 leading AI models.

BEST BY JUDGE SCORE Claude Haiku 4.5 8/10

You are probably staring at a stack of resumes and trying to figure out which ones are actually worth your time. Maybe you are a recruiter, a hiring manager, or a founder doing your first hire. Either way, manually reading every resume for the same checklist items is slow, inconsistent, and draining. A well-structured ChatGPT prompt can scan a resume against your specific job requirements, flag gaps, score fit, and surface the candidates worth a closer look in seconds.

The problem most people run into is that a vague prompt gets vague output. Typing 'review this resume' into ChatGPT produces a generic summary that tells you nothing useful. The prompts that actually work are structured: they define the role, list the must-have criteria, specify a scoring format, and tell the model exactly what to flag.

This page gives you tested prompts, real output examples across different roles and industries, and the specific mechanics that make resume-review prompts produce actionable results. If you want to cut your screening time without sacrificing quality, this is the direct answer to what you searched for.

When to use this

This approach works best when you have a clearly defined role with specific, checkable requirements and more than a handful of applicants. It is the right tool when you need consistent scoring across many resumes, when you are screening solo without an HR team, or when you want a fast first pass before a human takes a deeper look.

  • Screening 10 or more applicants for a single open role and needing consistent scoring criteria across all of them
  • Solo founders or small teams without a dedicated recruiter who need structured candidate comparison
  • Recruiters doing a first-pass filter before deciding which resumes go to the hiring manager
  • Hiring managers who want a second opinion on whether a candidate's experience matches a highly technical job description
  • Teams re-opening an old role and reviewing a backlog of previously submitted resumes against updated requirements

When this format breaks down

  • The job description is vague or not yet written. The model scores against what you give it, so undefined criteria produce meaningless scores.
  • You are evaluating creative portfolios, design work, or roles where the actual work samples matter more than listed credentials. ChatGPT cannot view linked portfolios or attached files.
  • You need a legally defensible hiring record. AI-generated scores are not auditable in the same way structured human evaluation rubrics are, and using them as the sole filter in regulated industries can create compliance risk.
  • The resume is heavily formatted with columns, graphics, or tables. Poorly parsed text fed to ChatGPT produces inaccurate output, especially when copying from PDF.

The prompt we tested

You are an expert technical recruiter and hiring manager with 15+ years of experience screening resumes across industries. Review the resume provided below against the role or criteria specified and deliver a structured evaluation.

Be direct, specific, and evidence-based—quote exact phrases from the resume when citing strengths or weaknesses. Keep the total response under 600 words, use clear headings and bullet points, and avoid generic advice that could apply to any resume.

Resume and role context:
Role: Senior Product Manager at a B2B SaaS startup (Series B, fintech). Resume: Jane Doe — 7 years experience. Led cross-functional teams at Acme Corp to 'drive growth and improve KPIs.' Launched mobile app that 'increased engagement.' MBA from State University 2018. Skills: Agile, Jira, stakeholder management, roadmapping. Previous roles: PM at Acme (2021-present), Associate PM at BigCo (2019-2021), Business Analyst at Consulting Firm (2017-2019).

Provide your review with these sections:
1. Overall Fit Score (1-10) with one-sentence justification
2. Top 3 Strengths (tied to the role)
3. Top 3 Weaknesses or Gaps (with specific examples from the resume)
4. Red Flags (employment gaps, job hopping, vague claims, missing metrics)
5. ATS & Formatting Issues (keywords, structure, readability)
6. Specific Rewrite Suggestions (at least 3 bullet-point improvements with before/after examples)
7. Interview Questions to Probe Weak Areas (3-5 questions)
8. Final Recommendation: Advance / Hold / Reject, with reasoning

Model comparison

ModelQualityCostLatencyTokens
Claude Opus 4.7 8 $0.1322 28.8s 585 / 1646
Claude Haiku 4.5 8 $0.0078 17.3s 403 / 1487
GPT-5.4 8 $0.0178 19.6s 341 / 1133
Gemini 2.5 Pro 7 $0.0012 21.0s 358 / 160
Grok 4.1 Fast Reasoning 7 $0.0005 13.7s 486 / 831

Outputs

Claude Opus 4.7 8/10
# Resume Review: Jane Doe — Senior PM, B2B SaaS Fintech

## 1. Overall Fit Score: 4/10
Solid PM tenure and trajectory, but the resume shows zero evidence of B2B SaaS or fintech experience and relies on vague, unquantified accomplishments.

## 2. Top 3 Strengths
- **Progressive PM trajectory**: BA → APM → PM over 7 years suggests steady growth and earned promotions.
- **Relevant core toolkit**: "Agile, Jira, stakeholder management, roadmapping" directly match baseline Senior PM requirements.
- **MBA + consulting foundation**: Business Analyst at a consulting firm plus an MBA signals structured problem-solving—valuable for a Series B environment requiring commercial judgment.

## 3. Top 3 Weaknesses or Gaps
- **No B2B or fintech signal**: Nothing in the resume references enterprise customers, API products, compliance (SOC2, PCI, KYC), payments, or financial workflows—core to this role.
- **Vague, unquantified impact**: "drive growth and improve KPIs" and "increased engagement" are meaningless without numbers. Which KPIs? By how much? Over what baseline?
- **Missing Senior PM scope indicators**: No mention of owning P&L, pricing, go-to-market, discovery frameworks, or leading other PMs—expectations at the Senior level, especially at Series B where ambiguity is high.

## 4. Red Flags
- **Chronic vagueness**: Two of the only two accomplishments cited ("drive growth," "increased engagement") lack metrics—suggests either weak impact or poor self-advocacy.
- **Mobile app launch in a B2B role?**: "Launched mobile app" at Acme Corp is unexplained—consumer-facing work may not transfer.
- **No employment gaps or hopping concerns**: Tenure pattern (2+ years each) is healthy.
- **"Cross-functional teams"** used without naming functions (eng, design, data, sales) is a tell of copy-paste resume writing.

## 5. ATS & Formatting Issues
- **Missing high-value keywords**: SQL, experimentation/A-B testing, PLG, API, SaaS metrics (ARR, NRR, churn), discovery, OKRs, Figma, Amplitude/Mixpanel.
- **No fintech vocabulary**: payments, ledger, compliance, underwriting, reconciliation, etc.
- **Unknown structure**: Summary is absent; a tailored 2-line summary naming "B2B SaaS" would lift both ATS and human screens.

## 6. Specific Rewrite Suggestions
- **Quantify the mobile app line.**
  - Before: "Launched mobile app that increased engagement."
  - After: "Led 6-person squad to launch iOS/Android app; grew DAU 38% and lifted 30-day retention from 22% → 41% within two quarters."
- **Replace the generic Acme bullet.**
  - Before: "Led cross-functional teams at Acme Corp to drive growth and improve KPIs."
  - After: "Owned checkout roadmap across engineering (8), design (2), and data; shipped 14 experiments that increased conversion 12% and drove $4.2M incremental ARR."
- **Add a targeted summary line.**
  - Before: (none)
  - After: "Senior PM with 7 years shipping data-driven products; seeking B2B SaaS fintech role. Experienced in API-first products, stakeholder alignment across GTM + Eng, and 0→1 discovery."
- **Reframe Associate PM role** to highlight discovery, customer interviews, or experimentation—not just execution.

## 7. Interview Questions to Probe Weak Areas
1. Walk me through the mobile app launch—what was the business goal, what metrics moved, and what would you do differently?
2. Describe a B2B or enterprise-adjacent problem you've solved. How did you handle competing stakeholder priorities across sales, CS, and engineering?
3. What's your experience with fintech-specific constraints—compliance, fraud, reconciliation, or regulated workflows?
4. Tell me about a product decision you made using quantitative data. Which tools, and what was the counterfactual?
5. At Series B, PMs often own ambiguous 0→1 bets. Give an example where you defined scope without a clear brief.

## 8. Final Recommendation: **Hold**
Do not advance to a hiring manager screen on this resume alone. Request a tailored version with quantified outcomes and any fintech/B2B exposure. If the rewrite surfaces enterprise or payments work, move to phone screen; if it remains consumer-mobile and vague, **Reject**—the Series B fintech context demands domain signal this resume does not yet provide.
Judge notes: The output is production-ready and genuinely specific—quoting exact resume phrases, providing real before/after rewrites, and tailoring every section to the fintech/Series B context—but the "after" rewrite examples invent precise metrics (38% DAU, $4.2M ARR) that don't exist in the source material, which could mislead a user who mistakes illustrative fabrication for actual resume guidance.
Claude Haiku 4.5 8/10
# Resume Review: Jane Doe – Senior Product Manager, B2B SaaS Fintech

---

## 1. Overall Fit Score
**5/10** — Mid-level PM experience exists, but resume lacks the specificity, metrics, and fintech domain expertise required for a Series B senior role demanding high ownership and impact.

---

## 2. Top 3 Strengths

• **Cross-functional leadership demonstrated**: "Led cross-functional teams" shows exposure to coordinating engineering, design, and go-to-market functions—essential for Series B complexity.

• **Progression trajectory**: Four distinct roles over 7 years (BA → Associate PM → PM → [implied senior scope]) shows career progression aligned with PM career ladder.

• **Core PM toolkit**: Agile, Jira, stakeholder management, and roadmapping are table-stakes for any PM role and suggest operational competence.

---

## 3. Top 3 Weaknesses

• **Vague, unmeasurable claims**: "Drive growth and improve KPIs" and "increased engagement" are marketing-speak with zero quantification. What growth rate? Which KPIs? Engagement increased by 5% or 50%? This is the single biggest red flag.

• **No fintech or B2B SaaS evidence**: The resume mentions Acme Corp and BigCo generically with no context on their industry, business model, or product type. For a fintech role, absence of regulatory, compliance, or payments domain knowledge is a critical gap.

• **Missing monetization and business impact metrics**: Series B fintech roles require PMs who own revenue, unit economics, or customer acquisition cost. Resume shows *feature launches* but no evidence of P&L responsibility, ARR growth, or churn reduction.

---

## 4. Red Flags

| Issue | Severity | Evidence |
|-------|----------|----------|
| **Vague metrics** | 🔴 Critical | "Increased engagement" (by how much? over what period?) |
| **No quantified outcomes** | 🔴 Critical | All achievements lack hard numbers—growth %, revenue impact, user adoption % |
| **Generic company context** | 🔴 High | "Acme Corp" and "BigCo" tell us nothing; no B2B SaaS or fintech signals |
| **No domain specificity** | 🔴 High | Zero mention of compliance, payments, security, or SaaS metrics (CAC, LTV, retention) |
| **Lightweight mobile app launch** | 🟡 Medium | "Mobile app" as headline achievement is vague; unclear if this was a pivot, feature, or full product |

---

## 5. ATS & Formatting Issues

• **Weak keyword density**: Missing critical fintech keywords (payments, compliance, KYC, API integrations, SaaS metrics like CAC/LTV, churn, NPS).

• **No metrics anchors for ATS**: Systems may flag resume as under-detailed; lack of numbers makes keyword matching difficult.

• **Job title clarity**: "PM at Acme (2021-present)" doesn't indicate *seniority level*—was this a Senior PM role or individual contributor? Ambiguity hurts both ATS parsing and hiring manager confidence.

---

## 6. Specific Rewrite Suggestions

| Before | After |
|--------|-------|
| "Led cross-functional teams to drive growth and improve KPIs." | "Led product roadmap for [fintech product] across eng (8), design (2), and marketing; grew monthly active users 42% YoY and reduced customer churn from 8% to 5.2% via retention-focused feature releases." |
| "Launched mobile app that increased engagement." | "Shipped iOS/Android mobile payment app in Q3 2023; drove 28% of new customer acquisitions and achieved 4.8-star app store rating across 15K+ downloads within 6 months." |
| "Skills: Agile, Jira, stakeholder management, roadmapping." | "Skills: Agile/Scrum, Jira, Figma, SQL (data analysis), stakeholder management, roadmapping, SaaS metrics (CAC, LTV, NPS), compliance/regulatory awareness (KYC frameworks), B2B GTM strategy." |
| "Associate PM at BigCo (2019-2021)" | "Associate PM, [Division Name], BigCo (2019-2021) – B2B SaaS: Owned [specific product area], managed $X budget, drove Q2 2021 feature adoption to 65% (target: 50%)." |

---

## 7. Interview Questions to Probe Weak Areas

1. **On fintech domain**: "Walk us through your experience with regulatory constraints in product decisions. Have you navigated KYC, PCI compliance, or payment processor integrations?"

2. **On quantification**: "You mentioned increasing engagement with the mobile app. What was the baseline, the target, and the final metric? How did you measure success?"

3. **On B2B SaaS economics**: "Describe a time you optimized for unit economics or churn reduction. What were the business levers, and what was the financial impact?"

4. **On Series B scaling**: "Series B means we're scaling from product-market fit to efficient growth. Walk us through how you'd prioritize between new features, customer retention, and sales efficiency."

5. **On stakeholder conflict**: "Tell me about a time product priorities conflicted with sales or engineering roadmap demands. How did you resolve it?"

---

## 8. Final Recommendation

**HOLD – Request Resubmitted Resume Before Advancing**

**Reasoning:**

- **Qualified in experience level** (7 years, progression to PM) but **unqualified in specificity and domain fit** for Series B fintech.
- **All achievements lack quantification**—this is non-negotiable for a senior role where you'll own OKRs and board-level metrics.
- **Zero fintech or B2B SaaS signals**—cannot assess true product acumen or regulatory/compliance awareness critical to fintech.

**Path forward**: Conditional advance if candidate can resubmit with (a) specific, numbered outcomes on prior launches, (b) clear fintech or B2B SaaS experience highlighted, and (c) evidence of P&L or retention ownership. Otherwise, consider stronger candidates with demonstrated fintech domain expertise.
Judge notes: The output is well-structured and largely production-ready, but the "rewrite suggestions" table includes fabricated specifics (e.g., "42% YoY," "28% of new customer acquisitions") presented as model rewrites rather than clearly flagged as illustrative placeholders, which could mislead users into inserting false metrics into a real resume.
GPT-5.4 8/10
## 1. Overall Fit Score: 5/10
Reason: She has relevant PM tenure and startup-adjacent skills, but the resume lacks the fintech, B2B SaaS, senior-level ownership, and quantified impact expected for a **Senior Product Manager** at a **Series B fintech startup**.

## 2. Top 3 Strengths
- **Progressive product experience**
  - Clear trajectory: **“Business Analyst at Consulting Firm (2017-2019), Associate PM at BigCo (2019-2021), PM at Acme (2021-present)”**
  - Shows movement into product and increasing responsibility over 7 years.

- **Cross-functional product exposure**
  - The phrase **“Led cross-functional teams”** is relevant for a senior PM role where alignment across engineering, design, GTM, and leadership matters.

- **Core PM toolkit is present**
  - Skills listed include **“Agile, Jira, stakeholder management, roadmapping”**
  - These are baseline requirements for PM execution in a scaling SaaS environment.

## 3. Top 3 Weaknesses or Gaps
- **No fintech or regulated-domain evidence**
  - For a fintech role, there is no mention of payments, lending, compliance, risk, KYC, fraud, financial operations, or regulated workflows.
  - This is a major gap for a Series B fintech startup.

- **Weak business impact and missing metrics**
  - Claims are vague: **“drive growth and improve KPIs”** and **“increased engagement”**
  - No numbers, baseline, timeframe, or KPI names. Senior PM candidates should show measurable outcomes.

- **Unclear B2B SaaS product scope and ownership**
  - The resume does not specify whether Acme or BigCo products were B2B, SaaS, enterprise, or platform products.
  - No evidence of senior PM-level ownership such as product strategy, P&L influence, pricing, customer discovery, or leading a product area end-to-end.

## 4. Red Flags
- **Vague claims**
  - **“drive growth and improve KPIs”** is too broad to assess contribution.
  - **“increased engagement”** lacks metric, segment, and business relevance.

- **Missing metrics throughout**
  - No revenue impact, adoption, retention, NPS, churn, activation, conversion, or ARR-related outcomes.

- **Potential mismatch with role seniority**
  - Title is **“PM”** rather than Senior PM, and the resume lacks evidence of strategic ownership expected at this level.

- **No visible startup/0-to-1 context**
  - Nothing indicates comfort with ambiguity, rapid iteration, or resource constraints typical of a Series B environment.

## 5. ATS & Formatting Issues
- **Missing high-value keywords for this role**
  - Add terms like: **B2B SaaS, fintech, payments, compliance, customer discovery, product analytics, experimentation, go-to-market, API/platform, enterprise, onboarding, retention, monetization**
- **Skills section is too generic**
  - Current skills are table stakes; missing tools and analytical keywords (e.g., SQL, Amplitude, Mixpanel, Tableau, Segment).
- **Experience bullets likely too high-level**
  - ATS may parse it fine, but recruiter screening will stall without concrete product names, user types, and metrics.

## 6. Specific Rewrite Suggestions
- **Add measurable impact**
  - Before: **“Launched mobile app that increased engagement.”**
  - After: **“Launched mobile app for [customer type], increasing weekly active users by 28% and 30-day retention by 11% within 6 months.”**

- **Clarify senior ownership**
  - Before: **“Led cross-functional teams at Acme Corp to drive growth and improve KPIs.”**
  - After: **“Owned roadmap for [product area], leading engineering, design, sales, and customer success to improve trial-to-paid conversion from 14% to 19%.”**

- **Make company/product context explicit**
  - Before: **“PM at Acme (2021-present)”**
  - After: **“Product Manager, Acme — B2B SaaS workflow platform serving mid-market finance teams.”**

- **Show discovery and strategy work**
  - Before: generic PM bullets
  - After: **“Conducted 25+ customer interviews and analyzed funnel drop-off data to prioritize onboarding improvements.”**

## 7. Interview Questions to Probe Weak Areas
- What exact KPIs did you own when you **“drive growth and improve KPIs”** at Acme?
- Tell me about the mobile app: who was the user, what problem did it solve, and how much did **“engagement”** increase?
- Was Acme a B2B SaaS product? What were the customer segments, ACV, and sales motion?
- Describe a product decision you made using customer research and data rather than stakeholder opinion.
- What exposure have you had to fintech, compliance, payments, or other regulated product environments?

## 8. Final Recommendation: Hold
Reasoning: She has a credible PM background and could fit a mid-level PM role, but this resume does not yet support a **Senior Product Manager** decision for a **Series B B2B fintech SaaS** company. Advance only if the candidate can substantiate metrics, B2B SaaS ownership, and domain adaptability in screening.
Judge notes: Excellent specificity and structure throughout, but the rewrite suggestions occasionally fabricate plausible-sounding but entirely invented metrics (e.g., "28% WAU," "14% to 19% conversion") that a reviewer should flag rather than invent from thin air.
Gemini 2.5 Pro 7/10
Here is a structured evaluation of the resume for the Senior Product Manager role.

### **1. Overall Fit Score: 5/10**

The candidate has a logical career progression into product management, but the resume lacks the specific, quantified B2B SaaS achievements and senior-level strategic impact required for this role.

### **2. Top 3 Strengths**

*   **Clear Career Progression:** The trajectory from "Business Analyst" to "Associate PM" at BigCo to "PM" at Acme Corp shows a deliberate and successful transition into the product management field.
*   **Experience at Scale:** Working at "Acme Corp" and "BigCo" suggests experience with established processes, managing complex dependencies, and navigating large organizations, which can be valuable for scaling
Judge notes: The output is well-structured and directly references resume text, but it's cut off mid-response—missing sections 3 through 8—making it incomplete and unusable in production without significant continuation.
Grok 4.1 Fast Reasoning 7/10
### 1. Overall Fit Score
**5/10** – Adequate PM skills and progression, but 7 years total experience falls short of senior-level expectations for a Series B fintech SaaS startup, with no domain-specific expertise or metrics.

### 2. Top 3 Strengths (tied to the role)
- **Cross-functional leadership**: "Led cross-functional teams at Acme Corp" aligns with B2B SaaS needs for coordinating engineering, sales, and stakeholders in fast-paced environments.
- **Core PM skills**: Lists "Agile, Jira, stakeholder management, roadmapping," directly matching startup roadmapping and iterative development in fintech products.
- **Product launch experience**: "Launched mobile app that 'increased engagement'" demonstrates end-to-end execution, relevant for SaaS feature releases.

### 3. Top 3 Weaknesses or Gaps
- **Limited seniority**: Only 3 years as PM ("PM at Acme (2021-present)"), with prior roles as "Associate PM" and "Business Analyst," insufficient for senior-level strategic ownership in a Series B startup.
- **No fintech/SaaS relevance**: Resume lacks any mention of B2B, SaaS, or fintech (e.g., payments, compliance), with examples like "mobile app" suggesting consumer focus.
- **Vague impact**: Claims like "drive growth and improve KPIs" and "increased engagement" provide no quantifiable results, critical for growth-stage fintech PMs.

### 4. Red Flags
- **Vague claims & missing metrics**: Phrases like "drive growth and improve KPIs" and "increased engagement" are unsubstantiated, raising doubts on true impact.
- **Job hopping**: Short stints ("Associate PM at BigCo (2019-2021)", "Business Analyst (2017-2019)") suggest <2-year average tenure, risky for startup stability.
- No employment gaps, but rapid progression from analyst to PM without deep expertise.

### 5. ATS & Formatting Issues
- **Keyword gaps**: Missing high-value terms like "SaaS," "B2B," "fintech," "Aha!," "user analytics," "go-to-market," hindering ATS parsing for fintech PM roles.
- **Structure/readability**: Narrative summary feels unstructured; roles lack bullet achievements, making it hard to scan metrics or impact in <10 seconds.

### 6. Specific Rewrite Suggestions
- **Quantify achievements**: Before: "Launched mobile app that 'increased engagement'." After: "Launched mobile app increasing daily active users 35% and retention 22% YoY."
- **Add domain keywords**: Before: "Skills: Agile, Jira, stakeholder management, roadmapping." After: "Skills: Agile/Scrum, Jira/Aha!, stakeholder management, SaaS roadmapping, fintech GTM."
- **Detail leadership scale**: Before: "Led cross-functional teams at Acme Corp to 'drive growth and improve KPIs'." After: "Led 12-person cross-functional team (eng, design, sales) at Acme Corp, driving 28% revenue growth via KPI-optimized features."

### 7. Interview Questions to Probe Weak Areas
- Can you walk us through the "mobile app launch" – what were the exact engagement metrics (e.g., DAU/MAU growth %) and how did it tie to business KPIs?
- Describe a time you managed fintech-specific challenges like regulatory compliance or B2B sales cycles – what tools/metrics did you use?
- Why only 3 years as PM? How have you scaled from "Associate PM" to handle senior strategic roadmapping in a startup?
- For "drive growth and improve KPIs" at Acme, what were the specific KPIs improved and by how much?
- How would you adapt your consumer app experience to B2B SaaS fintech product prioritization?

### 8. Final Recommendation
**Hold** – Promising skills and MBA, but probe metrics, domain fit, and tenure in interview; reject if no quantifiable fintech-adjacent wins emerge. 

(Word count: 498)
Judge notes: The output competently executes all 8 required sections with specific resume quotes and actionable rewrites, but the rewrite "before/after" examples invent specific numbers (35%, 22%, 28%) not present in the resume, undermining the "evidence-based" mandate and making at least one section unreliable for production use without editing.

What makes these work

  1. 01
    Define the scoring criteria explicitly

    ChatGPT cannot guess what matters to you. List your must-haves, nice-to-haves, and dealbreakers directly in the prompt. When you make the criteria explicit, the model grades against your actual rubric instead of a generic one, and you get scores that are actually comparable across candidates.

  2. 02
    Specify the output format you need

    Ask for a score, a bulleted match list, and a one-line recommendation every time. Consistent output format means you can scan results faster and drop them into a spreadsheet without reformatting. If you need a comparison table for two candidates, say so in the prompt.

  3. 03
    Paste clean resume text, not PDF formatting

    Copy and paste plain resume text rather than uploading a formatted PDF. Columns, graphics, and special characters often parse badly and cause the model to miss skills or misread dates. If the text looks broken after pasting, clean it up before submitting or the output will be unreliable.

  4. 04
    Use a risk flag instruction for red flags

    Add a line to your prompt asking the model to flag anything inconsistent, unexplained, or missing context, such as employment gaps, vague job titles, or responsibilities that seem misaligned with seniority claims. This turns the prompt from a simple matcher into an early-warning screen.

More example scenarios

#01 · Software engineering role with specific stack requirements
Input
You are a technical recruiter screening candidates for a mid-level backend engineer role. Required: 3+ years Python, experience with REST APIs, PostgreSQL, and at least one cloud platform (AWS, GCP, or Azure). Nice to have: FastAPI, Docker, CI/CD experience. Review the following resume and return: a fit score out of 10, a list of matched requirements, a list of missing requirements, and one sentence on whether this candidate should advance to a phone screen. Resume: [paste resume text here]
Expected output
Fit Score: 7/10. Matched: 4 years Python, REST API experience at two roles, PostgreSQL mentioned in project section, AWS certified. Missing: No explicit FastAPI or Docker mention, CI/CD not referenced. Recommendation: Advance to phone screen to confirm hands-on cloud deployment depth before moving forward.
#02 · Marketing manager role at a consumer brand
Input
You are screening resumes for a marketing manager at a DTC skincare brand. Must-haves: 4+ years marketing experience, demonstrated ownership of paid social campaigns, experience with email marketing platforms, and measurable revenue or ROAS results. Review this resume and return a fit score out of 10, bullet points for what qualifies and what is missing, and a one-line recommendation. Resume: [paste resume text here]
Expected output
Fit Score: 6/10. Qualifies: 5 years marketing experience, managed Meta and TikTok paid campaigns, used Klaviyo for email flows. Missing: No quantified ROAS or revenue impact stated anywhere in the resume. Recommendation: Request a cover note asking for specific campaign performance numbers before advancing.
#03 · Entry-level data analyst with no experience requirement
Input
You are reviewing applications for a junior data analyst role. Candidates may be recent graduates. Evaluate fit based on: proficiency in SQL and Excel or Google Sheets, any exposure to Python or R, coursework or projects involving data analysis, and communication clarity based on how the resume is written. Score out of 10 and list strengths and weaknesses. Resume: [paste resume text here]
Expected output
Fit Score: 8/10. Strengths: SQL listed in skills and used in two capstone projects, strong Excel experience from internship, Python course completed with GitHub link provided, resume is clearly written and well-organized. Weaknesses: No real-world work experience beyond internship, R not mentioned. Strong candidate for a junior role given project depth.
#04 · Operations manager role for a logistics company
Input
Screen this resume for an operations manager position at a regional freight and logistics company. Requirements: 5+ years in operations or supply chain, experience managing teams of 10 or more, familiarity with WMS or TMS software, and a track record of process improvement with measurable outcomes. Return a fit score, a breakdown of matched and unmatched criteria, and a risk flag if anything looks inconsistent or unexplained. Resume: [paste resume text here]
Expected output
Fit Score: 7/10. Matched: 6 years in logistics operations, managed a team of 14 at current employer, references SAP WMS. Unmatched: No explicit process improvement metric cited, only general language about 'improving efficiency.' Risk flag: Two-year employment gap from 2019 to 2021 with no explanation. Recommend asking about the gap and requesting one specific process improvement example during screening.
#05 · Comparing two finalists for a finance role
Input
I am choosing between two candidates for a senior financial analyst role. Requirements: CPA or CFA preferred, advanced Excel and financial modeling, experience in FP&A or corporate finance, and strong presentation skills. Review both resumes below and produce a side-by-side comparison table scoring each candidate on each criterion from 1 to 3, plus an overall recommendation. Candidate A resume: [paste here]. Candidate B resume: [paste here]
Expected output
Candidate A scores: CPA/CFA: 3 (CPA certified), Excel/modeling: 3 (DCF and LBO models listed), FP&A experience: 2 (one year in FP&A, rest in accounting), Presentation skills: 2 (no mention of executive presentations). Total: 10/12. Candidate B scores: CPA/CFA: 1 (neither listed), Excel/modeling: 3 (extensive modeling background), FP&A experience: 3 (5 years in FP&A), Presentation skills: 3 (board-level reporting mentioned). Total: 10/12. Recommendation: Advance both but prioritize Candidate B for FP&A depth if the role is forward-looking; prioritize Candidate A if accounting accuracy is the core need.

Common mistakes to avoid

  • Using a vague prompt

    Prompts like 'review this resume and tell me if it is good' produce summaries, not evaluations. Without defined criteria, the model has no basis for judgment and defaults to describing what is on the page. Always anchor the prompt to the specific role and requirements.

  • Treating the score as final

    A ChatGPT fit score is a first-pass filter, not a hiring decision. The model cannot verify claims, detect tone in an interview, or assess culture fit. Use the score to prioritize who gets a call, not to replace human judgment at any later stage.

  • Screening without a written job description

    If you have not written down the role requirements before prompting, you will keep adjusting the prompt mid-process and end up with inconsistent scores across candidates. Write your requirements first, then build the prompt around them and keep it identical for every resume you screen.

  • Ignoring model hallucinations on specifics

    ChatGPT can occasionally misread dates, infer credentials that were not explicitly stated, or fill in gaps with plausible-sounding details. Always cross-check the model's output against the actual resume text before acting on a specific factual claim.

  • Running multiple resumes in one long prompt

    Pasting five resumes into a single message often causes the model to conflate candidate details or lose track of which credential belongs to which person. Screen one resume per prompt unless you are explicitly asking for a structured comparison between two finalists.

Related queries

Frequently asked questions

Can ChatGPT read a resume PDF directly?

In ChatGPT with the file upload feature enabled, yes, you can upload a PDF and the model will attempt to extract the text. However, heavily formatted resumes with columns or graphics often parse poorly. For best results, copy and paste the resume text as plain text directly into the prompt, which gives you more control over what the model actually reads.

How do I make sure I score every candidate consistently?

Write your prompt once with a fixed scoring rubric and reuse the exact same prompt for every resume you screen. Do not tweak the criteria mid-process. Saving the prompt as a template and pasting each resume into the same structure is the simplest way to keep scoring consistent across a large applicant pool.

Is using ChatGPT to screen resumes legal?

In most jurisdictions, using AI as a screening aid is not prohibited, but using it as the sole automated decision-maker in a hiring process can trigger compliance issues, especially in the EU under GDPR or in certain US states with AI in employment laws. Use AI output as a tool for human review, not as an automated rejection system, and document your process.

What is the best ChatGPT model to use for resume review?

GPT-4o produces more nuanced and reliable output for structured evaluation tasks like this compared to GPT-3.5. It handles longer resumes better, follows multi-part prompt instructions more accurately, and is less likely to skip criteria you listed. If you are screening regularly, using GPT-4o via the ChatGPT interface or API is worth the cost difference.

Can I use these prompts in bulk through the API to screen hundreds of resumes?

Yes. The same prompt structure works through the OpenAI API, where you can loop through a list of resumes programmatically. You would pass the job description and scoring criteria as the system prompt and each individual resume as the user message. This is how recruiting tools and ATS integrations are typically built on top of these models.

How do I handle resumes with employment gaps or non-traditional backgrounds?

Add an explicit instruction to your prompt telling the model to flag gaps without penalizing them automatically, and to evaluate transferable skills for candidates with non-traditional paths. Something like 'Note any employment gaps but do not deduct points unless the gap is unexplained and longer than 12 months' gives the model a rule to apply consistently rather than letting it make a judgment call.