Hiring patterns
Skill Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack/plugins/devtools-pack/skills/hiring-patterns
A curated pack of custom Claude Code skills for developers — installable as a Claude Code plugin marketplace.
npx -y skills add Mattakushi432/Claude-Code-Skills-Custom-DevTools-Pack --skill hiring-patternsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
When to activate: job description writing, structured interviews, hiring rubrics, interview panel design, offer calibration, candidate pipeline management, recruiting process
SKILL.md
8.0 KB, as published. Nobody here has run it
Hiring Patterns
Job Description Template
[Title] — [Team] at [Company]
About the role (3–4 sentences):
What will this person own? What does success look like in 12 months?
What makes this role uniquely interesting?
What you'll do (5–7 bullets — outcomes, not tasks):
- [Outcome-oriented bullet: "Own X to achieve Y"]
- [Outcome-oriented bullet]
- [Outcome-oriented bullet]
What we're looking for (split must-have from nice-to-have):
Must-have:
- [Specific skill / experience — be concrete, avoid vague adjectives]
- [Minimum years of relevant experience, if necessary]
Nice-to-have (do NOT gatekeep on these):
- [Domain knowledge]
- [Tooling familiarity]
What we offer:
- Salary range: $X–$Y (be transparent — it widens your funnel)
- Equity: [range or description]
- Benefits: [2–3 lines]
- Location: [remote / hybrid / onsite + timezone expectations]
Interview process (set expectations up front):
1. Application review (1 week SLA)
2. Recruiter screen — 30 min
3. Hiring manager interview — 45 min
4. Technical / skills assessment — [format]
5. Panel interviews — 3 × 45 min
6. Offer
[Company] is an equal opportunity employer.
JD Anti-Patterns to Avoid
- "Rock star," "ninja," "wizard" — exclusionary
- 10+ years required for junior roles
- Long lists of technologies without context
- No salary range — reduces diverse applicant pool
- Culture-fit language without definition
- "Fast-paced" / "dynamic" with no substance
Structured Interview Design
Interview-to-Criteria Mapping
Map each interview to specific competencies. No competency assessed twice unless it's critical.
| Interview | Competencies assessed | Format |
|---|---|---|
| Recruiter screen | Communication, baseline fit, logistics | Phone/video, 30 min |
| Hiring manager | Role motivation, strategic thinking, leadership | Behavioral, 45 min |
| Technical | Domain skill, problem-solving, code quality | Skills assessment |
| Cross-functional | Collaboration, communication style | Behavioral, 45 min |
| Values / culture | Integrity, growth mindset, values alignment | Behavioral, 30 min |
Behavioral Question Formula (STAR)
"Tell me about a time when you [situation requiring competency]."
- Situation: what was the context?
- Task: what were you responsible for?
- Action: what specifically did you do?
- Result: what was the measurable outcome?
Sample Questions by Competency
Execution / Ownership
- Tell me about a project where you drove something to completion despite significant obstacles.
- Describe a time you took ownership of something outside your formal role.
Strategic Thinking
- Walk me through how you'd prioritize [relevant problem] if you had limited resources.
- Tell me about a decision you made that required thinking 12+ months ahead.
Collaboration
- Describe a time you had to influence someone without authority over them.
- Tell me about a disagreement with a peer or manager — how did you handle it?
Growth Mindset
- What is a significant professional mistake you've made? What did you learn?
- How do you stay current in [relevant domain]?
Values-Based
- Tell me about a time you had to choose between what was easy and what was right.
- Describe a situation where you had to deliver difficult feedback.
Hiring Rubric
Scoring Scale
| Score | Label | Definition |
|---|---|---|
| 4 | Strong Yes | Exceptional evidence; would advocate loudly |
| 3 | Yes | Clear evidence; comfortable hiring |
| 2 | No | Weak or missing evidence; significant concerns |
| 1 | Strong No | Disqualifying signals |
Rubric Template per Competency
Competency: [Name]
Definition: [2-sentence description of what this looks like in practice]
4 — Strong Yes:
[Concrete behavioral description of exceptional performance]
3 — Yes:
[Concrete behavioral description of solid performance]
2 — No:
[Concrete behavioral description of insufficient evidence]
1 — Strong No:
[Concrete behavioral description of disqualifying behavior]
Debrief Protocol
- All interviewers submit scores before debrief (no anchoring)
- Recruiter reads scores aloud — highest first, lowest last
- Start with dissenters: ask "Strong No" to share reasoning first
- Hiring manager gives final recommendation
- Document decision rationale in ATS for every candidate
- No hiring committee majority required if hiring manager has clear conviction + no Strong No from functional expert
Panel Design
Interview Panel Composition (5-person example)
| Panelist | Relationship to role | Focus |
|---|---|---|
| Hiring manager | Direct supervisor | Role fit, strategy, leadership |
| Senior peer | Daily collaborator | Technical depth, collaboration style |
| Cross-functional stakeholder | Partner team lead | Cross-functional working style |
| Skip-level manager | Future growth manager | Long-term potential, values |
| HR / recruiter | Process owner | Values, culture, logistics |
Panel Coordination Rules
- Brief every panelist before interviews (share role criteria, JD, candidate context)
- Each panelist covers different competencies — no duplicates
- Panel feedback submitted within 24h of interview
- Hiring manager is final decision authority, not consensus vote
Offer Calibration
Offer Components
| Component | Considerations |
|---|---|
| Base salary | Market data (Levels.fyi, Radford, Option Impact), internal equity, location |
| Equity | Stage-appropriate, strike price, vesting schedule (4yr / 1yr cliff standard) |
| Bonus | Target %, metrics, payout frequency |
| Signing bonus | Use to bridge unvested equity gap — make explicit in offer |
| Benefits | Health, dental, vision, 401k match, PTO policy |
| Start date | Negotiate — candidates need time for transitions |
Compensation Bands
- Maintain salary bands per level per function
- Publish bands internally (reduces inequity)
- Offer within band — exceptions require VP+ approval
- Review bands annually vs. market data
Offer Delivery Best Practices
- Deliver verbally first — gives you ability to negotiate in real-time
- Follow up in writing within 24h
- Set a deadline (5–7 business days standard)
- Assign a buddy to answer questions during decision period
- Close the loop immediately if declined — ask for specific reason
Pipeline Management
ATS Stage Definitions
| Stage | Definition | SLA to advance or disposition |
|---|---|---|
| Applied | Application received | 5 business days |
| Recruiter screen | Scheduled or completed | 3 business days post-screen |
| HM interview | Scheduled or completed | 3 business days post-interview |
| Assessment | Sent or in progress | 5 business days |
| Panel | Scheduling or in progress | 5 business days |
| Offer | Extended, negotiating, or closed | 7 business days |
| Closed | Hired / rejected / withdrew | — |
Pipeline Health Metrics
| Metric | Formula | Target |
|---|---|---|
| Time to fill | Req open date → accepted offer | < 45 days |
| Offer acceptance rate | Accepted / offers extended | ≥ 85% |
| Pipeline conversion | Hired / total applicants | Benchmark by role type |
| Diverse slate rate | % roles with diverse finalist | ≥ 50% |
| Interviewer calibration | % scorers whose ratings correlate with performance | Track quarterly |
Candidate Experience Standards
- Acknowledge every application within 5 business days
- No interview ghost — disposition every candidate you interview
- Provide feedback when declined post-panel (if legal / policy allows)
- Send surveys after each stage — act on low scores