AI-first CV screening rubric

AI-First CV Screening

Purpose

Rank a batch of CVs in minutes by looking for evidence of leverage and systems thinking, not for a checklist of tool names. The output is a triaged shortlist a hiring manager can act on.

What "leverage" looks like on a CV

• Connectors, not users. Tools that link systems (Make, Zapier, n8n, APIs, webhooks, custom scripts) signal someone who builds workflows. Listing "ChatGPT" or "Copilot" under skills signals a user, not a builder.
• Systematised away. Phrases like "eliminated manual X", "built a template that", "automated reporting" show the Architect pillar.
• Shared, not hoarded. Mentions of wikis, playbooks, team prompts, or onboarding docs show the Multiplier pillar.
• Verification habits. Any mention of QA, review steps, or fact-checking AI output shows the Auditor pillar.

The lazy-AI check

AI-assisted cover letters and summaries are fine. Flag — do not auto-reject — when:

• the prose is generic and robotic with no role-specific detail,
• it restates the job description back at you,
• the claims are unverifiable superlatives ("revolutionised", "game-changing") with no metric.

A robotic, unedited application is a quality-control failure, not a skills failure.

Instructions

1. Read each CV and extract: role title, the three most recent outcomes, and every tool mentioned.
2. For each CV, score 1-4 on three signals: Architect (built vs. used), Operator (drove vs. accepted the tool), Multiplier (shared vs. hoarded).
3. Run the lazy-AI check on any cover letter or summary. Note pass/fail and quote the offending line.
4. Produce one line per candidate: Name — Architect x/4 | Operator x/4 | Multiplier x/4 — pass | hold | decline — one-sentence reason.
5. Sort the list so all "pass" candidates appear first, then "hold", then "decline".

Output format

A markdown table:

| Candidate | Architect | Operator | Multiplier | Lazy-AI | Decision | Reason |

Followed by a shortlist of the top 5 candidates to advance to screening, each with the single strongest piece of evidence from their CV.

Rules

• A tool name alone is never evidence. Look for the verb next to it: built, automated, scripted, shared.
• Never decline a candidate solely for a lazy-AI cover letter — flag it and let the screening call confirm.
• If a CV has zero connectors and zero systematisation language, decline with confidence.