CV screening

Assesses a CV against a role and says yes, no or maybe — with reasons.

HR · produces a Review · built in, ready to run

What you give it

Something like this:

Role: Backend engineer, 3+ yrs, PHP/Laravel, we run a multi-tenant order platform on SAP integrations. Must have shipped and maintained something in production.

CV — Usman Tariq, Lahore
- 4 yrs at a software house, 'worked on 12+ projects using cutting-edge technologies'
- Laravel, PHP, MySQL, React, Node, Python, Docker, AWS, Kubernetes, ML
- 'Led a team of developers to deliver enterprise-grade solutions'
- Built an inventory system for a retail client, 'handling thousands of records'
- Side project: a Laravel package for CSV imports, 40 stars on GitHub, last commit 2 years ago
- BS Computer Science, 2021
- No mention of integrations, testing, or being on call

What you get back

This is a real run of the skill on the input above, not a mock-up:

## Assessment: Usman Tariq vs. Backend Engineer Role

**Verdict: maybe**

---

**Strengths:**

1. **Experience depth matches requirement** — 4 years at a software house exceeds the 3+ year threshold, and the inventory system project demonstrates he's shipped something handling scale ("thousands of records"), which satisfies the production maintenance bar.

2. **Core stack alignment** — Laravel and PHP are explicitly listed and match the role's primary requirements; MySQL experience covers the data layer needed for multi-tenant order systems.

3. **Infrastructure familiarity** — Docker, AWS, and Kubernetes experience suggests he can operate in complex deployment environments, relevant for a platform running SAP integrations.

---

**Gaps:**

1. **No demonstrable integration work** — The CV lists 12+ projects but gives no detail on SAP, ERP systems, or third-party API integrations. For a role built around "SAP integrations," this is a material blind spot.

2. **Production operations unclear** — No mention of monitoring, debugging, on-call support, incident response, or ongoing maintenance of live systems. "Delivered" projects doesn't prove he's managed production issues.

3. **Testing discipline not evident** — No reference to automated tests, test coverage, or QA practices. Critical for order/payment systems where bugs are costly.

---

**Questions to ask:**

1. **"Can you walk through one of the 12 projects—specifically how you handled integrating external systems or APIs, and what broke in production that you had to fix?"** — This tests whether "12 projects" means shipped breadth or depth, and whether he's actually debugged production code.

2. **"The inventory system handling thousands of records—what was your approach to data consistency and migrations, and did you own that system after launch or hand it off?"** — This clarifies whether he's maintained a live system through its lifecycle, which is different from building and shipping.

---

*Recommendation:* Screen him, but ask these questions early. The experience level is there, but the CV lacks proof he's worked on integration-heavy or operationally demanding systems. If his answers to these two questions are strong and specific, move to technical interview; if vague, likely a no.

The wording changes a little every run. The shape does not — that is what the procedure below is for.

Tools it uses

None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.

The procedure it follows

This is the skill, in full. Add it to your own skills to change any of it.

Assess the CV below against the role described in it.

Reply in this shape:
Verdict: interview | maybe | no
Strengths: <up to three, each tied to something in the CV>
Gaps: <up to three>
Questions to ask: <two, specific to this person>

Judge evidence, not vocabulary. Never infer anything about age, gender, nationality, or anything else not relevant to doing the job.

How to run it

In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.

New to skills? Start with what a skill is.