When to activate
Post-application screening. Quickly identify qualified candidates, surface concerns, and flag no-gos before phone screen scheduling.
When NOT to use
Not for deep reference checks — that happens post-offer. Not for skill verification — that's the interview panel's role. Not as sole criterion for hiring decisions; this is rapid qualification only.
Candidate Screening Checklist
Execute in order:
- Establish role context — Must-haves (5–7), nice-to-haves, title precedent, seniority level
- Define red flags — Gaps, misalignments, or concerning signals that warrant deeper investigation
- Screen resume — Parse work history, company/team scope, roles, and timeline
- Check against must-haves — For each candidate, mark present/absent/partial
- Assess resume quality — Grammar, clarity, format signal preparation level (minor signal)
- Flag red flags — Multiple short stints, significant gaps, title inflation, unclear scope
- Check cover letter — If submitted: Does it signal genuine interest and understanding of role?
- LinkedIn validation — Cross-check resume claims; look for gaps or inconsistencies
- Rank candidates — Green (strong), Yellow (investigate further), Red (pass)
Must-Have Definition
From job description, extract 5–7 must-haves:
Example: Staff Backend Engineer
- 5+ years building distributed systems (Python, Go, Java, Rust)
- Experience with database optimization (PostgreSQL, DynamoDB, or equivalent)
- Message queue expertise (RabbitMQ, Kafka, SQS)
- Track record owning system reliability; experience defining SLOs
- Mentoring experience or demonstrated leadership
When screening:
Resume Red Flags
Timeline & Gaps
| Signal |
Severity |
What To Check |
Action |
| 3+ jobs in 5 years |
Yellow |
Avg tenure <2 years. Ask about growth/context. May indicate flight risk if pattern. |
Phone screen question: "Walk us through your moves — what drew you to each?" |
| 1+ year gap |
Yellow |
Medical, sabbatical, family care, burnout, layoff. |
Ask directly in phone screen: "Tell us about the [gap]." |
| Very short tenure (<6 months) |
Yellow–Red |
Left quickly. Possible: bad cultural fit, role mismatch, or external factor. |
Ask: "Why did you leave after 6 months?" Red if evasive. |
| Consistent 2–3 year tenure |
Green |
Shows stability + room for growth. Good pattern. |
No action needed. |
Title & Scope Mismatch
| Signal |
Check |
Action |
| Job title inflation ("VP of Something" at 5-person startup) |
Company size + role scope |
Clarify actual scope in phone screen. Not disqualifying. |
| Scope unclear ("Responsible for XYZ") with no metrics |
Ask for context |
Phone screen: "Walk us through how you measured impact in that role?" |
| No management experience listed, but applying for manager role |
Check for technical lead / mentoring |
If absent, may be premature for manager hire (consider IC track or manager coaching). |
Experience Relevance
| Signal |
Check |
Action |
| 10 years experience but industry unrelated (e.g., marketing to engineering) |
Transfer skills |
Evaluate transfer skills. May require longer ramp. Consider as Yellow. |
| Candidate claims expertise in 15+ technologies on 1-page resume |
Depth vs. breadth |
Usually indicates shallow knowledge. Phone screen deep dives on 2–3 core skills. |
| No recent projects/technical work (all management) |
If IC role sought |
Assess if candidate has hands-on chops or has drifted into pure management. |
Cover Letter (if submitted)
| Signal |
Green |
Red |
| References specific team/product insight |
"I've used [your product] and loved [specific feature]" |
Generic: "I'm excited to join a tech company" |
| Shows understanding of role |
"You're scaling recommendation systems — my work at [X] on real-time ranking aligns" |
No reference to actual role or company |
| Personalized |
Uses hiring manager name; researched company |
"To the hiring team..." |
| Grammar/clarity |
Well-written, clear |
Multiple typos, unclear intent |
Screening Grid Template
# Candidate Screening — [Role] [Date]
**Role:** [Title, Level]
**Posting date:** [Date]
**Applications reviewed:** [N]
---
## Must-Have Checklist
| Must-Have | Definition | Green | Yellow | Red |
|-----------|---|---|---|---|
| 5+ years distributed systems | Python, Go, Java, Rust | Clear evidence in job descriptions | Adjacent (3 years, strong foundation) | Missing or very junior (<2 years) |
| Database optimization | PostgreSQL, DynamoDB, query tuning | Explicit experience listed | Related (some DB work, not optimization-focused) | No mention |
| Async/concurrency patterns | Message queues, RabbitMQ, Kafka, async/await | Multiple projects using | One mention or strong transfer | Absent |
| Reliability ownership | SLO definition, on-call, incident response | Led reliability initiatives | Participated in on-call rotation | No mention |
| Mentoring | Explicit mentoring or lead IC role | Mentored 2+ juniors, led design reviews | Technical lead or senior IC title | None |
---
## Candidates
### [Candidate 1] — STRONG (Green)
**Resume summary:**
- Staff Engineer at [Company], 6 years; led platform scaling project; 3 direct reports
- Previous: Senior Engineer at [Company], 4 years; built recommendation engine using Kafka, PostgreSQL
- Education: BS Computer Science, [University]
**Must-haves assessment:**
- 5+ distributed systems: ✓ (6 years at platform-heavy company, led scaling)
- Database optimization: ✓ (Built rec engine, explicit PostgreSQL optimization mentioned)
- Async patterns: ✓ (Kafka expertise in previous role)
- Reliability ownership: ✓ (On-call, defined SLOs for recommendation service)
- Mentoring: ✓ (3 direct reports as Staff Engineer)
**Red flags:** None noted.
**Cover letter:** Strong — references our product, specific feature, scaling challenge alignment.
**LinkedIn:** Matches resume; good engagement profile; published 2 technical blog posts on distributed systems.
**Recommendation:** PHONE SCREEN. Very strong candidate. Priority for scheduling.
---
### [Candidate 2] — INVESTIGATE (Yellow)
**Resume summary:**
- Senior Engineer at [Company], 2.5 years; worked on payment systems, Java backend
- Previous: Engineer at [Company], 2 years; full-stack (Node.js + React)
- Senior Engineer at [Company], 1.5 years; backend systems (Python)
- [1-year gap, 2022–2023]
- Education: Bootcamp graduate, 2019
**Must-haves assessment:**
- 5+ distributed systems: Partial (5 years total, but varied stack; not clear on scale)
- Database optimization: Partial (payment systems likely DB-heavy; no explicit mention)
- Async patterns: Partial (Java backend suggests some async; not explicit)
- Reliability ownership: Unclear (payment systems require it; not mentioned)
- Mentoring: None noted
**Red flags:**
- Multiple short tenures (2.5, 2, 1.5 years); pattern of ~2-year stays
- 1-year gap unexplained
- Bootcamp background (not a blocker; check coding fundamentals)
- No explicit async/message queue experience
**Cover letter:** None submitted.
**LinkedIn:** Matches resume; no technical writing or open-source contributions visible.
**Recommendation:** PHONE SCREEN, BUT WITH CAUTION. Ask about:
1. Why the pattern of 2-year tenures?
2. The 1-year gap?
3. Deep dive on database work at payments company
4. Async/concurrency experience (Java, Python)
5. On-call/reliability experience
Probe retention risk; assess fit for messaging-heavy architecture. Consider coding screen focused on async patterns.
---
### [Candidate 3] — PASS (Red)
**Resume summary:**
- Senior Engineer at [Company] (10 years); title VP of Engineering (role scope unclear)
- Previous: Staff Engineer at [Company], 5 years
- No other roles listed
- Education: BS, [University], 1999
**Must-haves assessment:**
- 5+ distributed systems: Unclear (10-year tenure but no project detail)
- Database: Not mentioned
- Async: Not mentioned
- Reliability: Not mentioned
- Mentoring: Implied (VP of Engineering) but no direct IC mentoring shown
**Red flags:**
- VP title after 10 years at one company; scope/team size unclear
- Very limited detail on technical contributions; reads as "moved into management then stayed"
- No evidence of hands-on IC work in past 5+ years
- Cover letter submitted but generic; no reference to specific role or product
**Additional concern:** Candidate may have drifted out of hands-on technical work. IC role requires current technical chops.
**Recommendation:** PASS. Not right fit for IC role. If manager role opens, revisit; may need technical refresh for IC return.
---
## Summary Stats
| Category | Count |
|----------|-------|
| **Green (phone screen)** | 3 |
| **Yellow (phone screen + probe)** | 5 |
| **Red (pass)** | 2 |
**Next action:** Schedule phone screens for 3 Green + 5 Yellow candidates (8 total). Aim for 3–4 interviews over next 2 weeks.
---
Phone Screen Question Prompts
Once you've identified Green/Yellow candidates, use these prompts in phone screening:
Timeline & Trajectory
- "Walk us through your moves over the past 5 years. What drew you to each role?"
- "How have your responsibilities grown? What's the biggest system you've owned?"
Technical Depth
- "Tell us about the most complex distributed system you've built. What made it hard?"
- "Describe how you approach database optimization. Walk us through an example."
Reliability & On-Call
- "What's your on-call experience? What incident sticks with you most?"
- "How do you think about defining SLOs for a service?"
Scope & Leadership
- "Have you mentored or led engineers? Tell us about that."
- "Describe a technical decision you made that affected your team."
Motivation
- "Why are you interested in this role? What's missing from your current situation?"
- "What matters most to you in your next role?"
Bad Hires: Patterns to Catch Early
Candidates who seem good on paper but often underperform:
- All experience at 1 company: May lack exposure to different approaches; may struggle with change.
- No failure or challenge mentioned: Everyone has hard projects. Vague answers can indicate lack of depth or reflection.
- Overly focused on money/compensation: Risk of leaving when competitor offers 10% more.
- Blame culture for departures: "Company culture was bad," "managers were incompetent." May not own their growth.
- Rapid escalation without depth: "Promoted to manager after 3 years." Assess if earned or just timeline.
1---2name: candidate-screener-23description: Rapidly screens candidates against role fit, red flags, and must-have criteria. Returns screening-{role}-{date}.md with candidate rankings and interview recommendations.4allowed-tools: Read, Write, WebSearch5effort: low6metadata:7 source: https://skillmd.com/skills/uitbreidenos/candidate-screener-28---910## When to activate1112Post-application screening. Quickly identify qualified candidates, surface concerns, and flag no-gos before phone screen scheduling.1314## When NOT to use1516Not for deep reference checks — that happens post-offer. Not for skill verification — that's the interview panel's role. Not as sole criterion for hiring decisions; this is rapid qualification only.1718## Candidate Screening Checklist1920Execute in order:21221. **Establish role context** — Must-haves (5–7), nice-to-haves, title precedent, seniority level232. **Define red flags** — Gaps, misalignments, or concerning signals that warrant deeper investigation243. **Screen resume** — Parse work history, company/team scope, roles, and timeline254. **Check against must-haves** — For each candidate, mark present/absent/partial265. **Assess resume quality** — Grammar, clarity, format signal preparation level (minor signal)276. **Flag red flags** — Multiple short stints, significant gaps, title inflation, unclear scope287. **Check cover letter** — If submitted: Does it signal genuine interest and understanding of role?298. **LinkedIn validation** — Cross-check resume claims; look for gaps or inconsistencies309. **Rank candidates** — Green (strong), Yellow (investigate further), Red (pass)3132## Must-Have Definition3334From job description, extract 5–7 must-haves:3536**Example: Staff Backend Engineer**371. 5+ years building distributed systems (Python, Go, Java, Rust)382. Experience with database optimization (PostgreSQL, DynamoDB, or equivalent)393. Message queue expertise (RabbitMQ, Kafka, SQS)404. Track record owning system reliability; experience defining SLOs415. Mentoring experience or demonstrated leadership4243When screening:44- [ ] Present (candidate clearly has it)45- [ ] Partial (related experience; good transfer skills)46- [ ] Absent (no evidence; will require ramp)4748---4950## Resume Red Flags5152### Timeline & Gaps5354| Signal | Severity | What To Check | Action |55|--------|----------|---|---|56| 3+ jobs in 5 years | Yellow | Avg tenure <2 years. Ask about growth/context. May indicate flight risk if pattern. | Phone screen question: "Walk us through your moves — what drew you to each?" |57| 1+ year gap | Yellow | Medical, sabbatical, family care, burnout, layoff. | Ask directly in phone screen: "Tell us about the [gap]." |58| Very short tenure (<6 months) | Yellow–Red | Left quickly. Possible: bad cultural fit, role mismatch, or external factor. | Ask: "Why did you leave after 6 months?" Red if evasive. |59| Consistent 2–3 year tenure | Green | Shows stability + room for growth. Good pattern. | No action needed. |6061### Title & Scope Mismatch6263| Signal | Check | Action |64|--------|-------|--------|65| Job title inflation ("VP of Something" at 5-person startup) | Company size + role scope | Clarify actual scope in phone screen. Not disqualifying. |66| Scope unclear ("Responsible for XYZ") with no metrics | Ask for context | Phone screen: "Walk us through how you measured impact in that role?" |67| No management experience listed, but applying for manager role | Check for technical lead / mentoring | If absent, may be premature for manager hire (consider IC track or manager coaching). |6869### Experience Relevance7071| Signal | Check | Action |72|--------|-------|--------|73| 10 years experience but industry unrelated (e.g., marketing to engineering) | Transfer skills | Evaluate transfer skills. May require longer ramp. Consider as Yellow. |74| Candidate claims expertise in 15+ technologies on 1-page resume | Depth vs. breadth | Usually indicates shallow knowledge. Phone screen deep dives on 2–3 core skills. |75| No recent projects/technical work (all management) | If IC role sought | Assess if candidate has hands-on chops or has drifted into pure management. |7677### Cover Letter (if submitted)7879| Signal | Green | Red |80|--------|-------|-----|81| References specific team/product insight | "I've used [your product] and loved [specific feature]" | Generic: "I'm excited to join a tech company" |82| Shows understanding of role | "You're scaling recommendation systems — my work at [X] on real-time ranking aligns" | No reference to actual role or company |83| Personalized | Uses hiring manager name; researched company | "To the hiring team..." |84| Grammar/clarity | Well-written, clear | Multiple typos, unclear intent |8586---8788## Screening Grid Template8990```markdown91# Candidate Screening — [Role] [Date]9293**Role:** [Title, Level]94**Posting date:** [Date]95**Applications reviewed:** [N]9697---9899## Must-Have Checklist100101| Must-Have | Definition | Green | Yellow | Red |102|-----------|---|---|---|---|103| 5+ years distributed systems | Python, Go, Java, Rust | Clear evidence in job descriptions | Adjacent (3 years, strong foundation) | Missing or very junior (<2 years) |104| Database optimization | PostgreSQL, DynamoDB, query tuning | Explicit experience listed | Related (some DB work, not optimization-focused) | No mention |105| Async/concurrency patterns | Message queues, RabbitMQ, Kafka, async/await | Multiple projects using | One mention or strong transfer | Absent |106| Reliability ownership | SLO definition, on-call, incident response | Led reliability initiatives | Participated in on-call rotation | No mention |107| Mentoring | Explicit mentoring or lead IC role | Mentored 2+ juniors, led design reviews | Technical lead or senior IC title | None |108109---110111## Candidates112113### [Candidate 1] — STRONG (Green)114115**Resume summary:**116- Staff Engineer at [Company], 6 years; led platform scaling project; 3 direct reports117- Previous: Senior Engineer at [Company], 4 years; built recommendation engine using Kafka, PostgreSQL118- Education: BS Computer Science, [University]119120**Must-haves assessment:**121- 5+ distributed systems: ✓ (6 years at platform-heavy company, led scaling)122- Database optimization: ✓ (Built rec engine, explicit PostgreSQL optimization mentioned)123- Async patterns: ✓ (Kafka expertise in previous role)124- Reliability ownership: ✓ (On-call, defined SLOs for recommendation service)125- Mentoring: ✓ (3 direct reports as Staff Engineer)126127**Red flags:** None noted.128129**Cover letter:** Strong — references our product, specific feature, scaling challenge alignment.130131**LinkedIn:** Matches resume; good engagement profile; published 2 technical blog posts on distributed systems.132133**Recommendation:** PHONE SCREEN. Very strong candidate. Priority for scheduling.134135---136137### [Candidate 2] — INVESTIGATE (Yellow)138139**Resume summary:**140- Senior Engineer at [Company], 2.5 years; worked on payment systems, Java backend141- Previous: Engineer at [Company], 2 years; full-stack (Node.js + React)142- Senior Engineer at [Company], 1.5 years; backend systems (Python)143- [1-year gap, 2022–2023]144- Education: Bootcamp graduate, 2019145146**Must-haves assessment:**147- 5+ distributed systems: Partial (5 years total, but varied stack; not clear on scale)148- Database optimization: Partial (payment systems likely DB-heavy; no explicit mention)149- Async patterns: Partial (Java backend suggests some async; not explicit)150- Reliability ownership: Unclear (payment systems require it; not mentioned)151- Mentoring: None noted152153**Red flags:**154- Multiple short tenures (2.5, 2, 1.5 years); pattern of ~2-year stays155- 1-year gap unexplained156- Bootcamp background (not a blocker; check coding fundamentals)157- No explicit async/message queue experience158159**Cover letter:** None submitted.160161**LinkedIn:** Matches resume; no technical writing or open-source contributions visible.162163**Recommendation:** PHONE SCREEN, BUT WITH CAUTION. Ask about:1641. Why the pattern of 2-year tenures?1652. The 1-year gap?1663. Deep dive on database work at payments company1674. Async/concurrency experience (Java, Python)1685. On-call/reliability experience169170Probe retention risk; assess fit for messaging-heavy architecture. Consider coding screen focused on async patterns.171172---173174### [Candidate 3] — PASS (Red)175176**Resume summary:**177- Senior Engineer at [Company] (10 years); title VP of Engineering (role scope unclear)178- Previous: Staff Engineer at [Company], 5 years179- No other roles listed180- Education: BS, [University], 1999181182**Must-haves assessment:**183- 5+ distributed systems: Unclear (10-year tenure but no project detail)184- Database: Not mentioned185- Async: Not mentioned186- Reliability: Not mentioned187- Mentoring: Implied (VP of Engineering) but no direct IC mentoring shown188189**Red flags:**190- VP title after 10 years at one company; scope/team size unclear191- Very limited detail on technical contributions; reads as "moved into management then stayed"192- No evidence of hands-on IC work in past 5+ years193- Cover letter submitted but generic; no reference to specific role or product194195**Additional concern:** Candidate may have drifted out of hands-on technical work. IC role requires current technical chops.196197**Recommendation:** PASS. Not right fit for IC role. If manager role opens, revisit; may need technical refresh for IC return.198199---200201## Summary Stats202203| Category | Count |204|----------|-------|205| **Green (phone screen)** | 3 |206| **Yellow (phone screen + probe)** | 5 |207| **Red (pass)** | 2 |208209**Next action:** Schedule phone screens for 3 Green + 5 Yellow candidates (8 total). Aim for 3–4 interviews over next 2 weeks.210211---212213214```215216---217218## Phone Screen Question Prompts219220Once you've identified Green/Yellow candidates, use these prompts in phone screening:221222### Timeline & Trajectory223- "Walk us through your moves over the past 5 years. What drew you to each role?"224- "How have your responsibilities grown? What's the biggest system you've owned?"225226### Technical Depth227- "Tell us about the most complex distributed system you've built. What made it hard?"228- "Describe how you approach database optimization. Walk us through an example."229230### Reliability & On-Call231- "What's your on-call experience? What incident sticks with you most?"232- "How do you think about defining SLOs for a service?"233234### Scope & Leadership235- "Have you mentored or led engineers? Tell us about that."236- "Describe a technical decision you made that affected your team."237238### Motivation239- "Why are you interested in this role? What's missing from your current situation?"240- "What matters most to you in your next role?"241242---243244## Bad Hires: Patterns to Catch Early245246Candidates who seem good on paper but often underperform:2471. **All experience at 1 company:** May lack exposure to different approaches; may struggle with change.2482. **No failure or challenge mentioned:** Everyone has hard projects. Vague answers can indicate lack of depth or reflection.2493. **Overly focused on money/compensation:** Risk of leaving when competitor offers 10% more.2504. **Blame culture for departures:** "Company culture was bad," "managers were incompetent." May not own their growth.2515. **Rapid escalation without depth:** "Promoted to manager after 3 years." Assess if earned or just timeline.252253---