A product of theProductPath
The Candidate Interview Kit is an AI-powered workflow for hiring teams. It gives every interviewer consistent, evidence-based preparation before an interview — and a structured way to capture and compare assessments after. When the hire is made, the kit gets retired. It’s a Burner App for the hiring process.
The impermanence is the point. This kit is bespoke for one role, one hiring cycle. It’s not a platform. It has no login, no database, no ongoing subscription. When you’ve made your hire, delete the folder.
Landing page: candidate-interview-kit-site
One interviewer. One role. Full pipeline.
The interviewer (or hiring manager working alone) uses the kit to:
No shared infrastructure required. One folder, one person, one decision.
Multiple interviewers. Same role. Coordinated assessments.
Each interviewer gets personalized prep briefs based on their focus areas. Each submits independent assessments. The hiring manager sees all assessments in one comparison tool, with the ability to toggle each interviewer’s input on and off.
| Role | Who They Are |
|---|---|
| Setup | Whoever initializes the folder — loads the JD, adds resumes as candidates arrive |
| Hiring Manager | Defines focus areas for the interviewer; makes the final call |
| Interviewer | Uses the prep brief before interviews; submits assessments after |
In a solo hiring loop, one person plays all three roles.
{Company}-{Role}/
├── job-description.md ← JD text (source of truth, static)
├── interviewer-notes.md ← Hiring Manager's focus areas for the interviewer
├── candidates/
│ └── {candidate-name}/
│ ├── resume.pdf ← source resume
│ ├── brief.md ← AI-generated pre-interview prep
│ └── assessment.md ← AI-structured post-interview notes
└── comparison.html ← Burner App comparing all candidates (generated by skill)
The kit runs through three steps, in order, for each candidate:
1. Prep — Point the skill at a candidate folder. It reads the JD, the interviewer notes, and the resume. It produces a prep brief: competency scores, areas to probe, suggested questions, red flags.
2. Assess — After the interview, share your raw notes with the skill. It structures them into a clean assessment: qualitative scores, evidence, strengths, concerns.
3. Compare — Once you have assessments for all candidates, the skill generates comparison.html — a self-contained Burner App showing all candidates side-by-side. Open it in a browser. Make your decision. Delete the folder.
candidate-interview-kit/
├── README.md ← This file
├── individual-kit/ ← One interviewer, one role, full pipeline
│ ├── SKILL.md ← The AI skill (copy this to your kit folder)
│ ├── skill/ ← Supporting skill files (copy this too)
│ └── example/ ← Working example (AirCorp — Product Analyst)
│ └── AirCorp-ProductAnalyst/
│ ├── job-description.md
│ ├── interviewer-notes.md
│ ├── candidates/
│ └── comparison.html
├── team-kit/ ← Multiple interviewers, coordinated assessments
│ ├── SKILL.md ← The team AI skill
│ ├── skill/ ← Team-specific scripts and comparison template
│ └── example/ ← Working example (AirCorp — 4 interviewers, 4 candidates)
│ └── AirCorp-ProductAnalyst/
│ ├── _team.md
│ ├── job-description.md
│ ├── candidates/
│ └── comparison.html
individual-kit/ as the working directoryinitialize — the LLM scaffolds a fresh working kitcd individual-kit
node skill/scripts/init-kit.js /path/to/new-kit-folder
team-kit/ as the working directoryinitialize — the LLM scaffolds a team kit with _team.md_team.md with your interviewer roster and focus areascd team-kit
node skill/scripts/init-team-kit.js /path/to/new-kit-folder
The skill handles the rest.
job-description.md, jd.pdf, role-description.docx_team.md is required — it defines the interviewer roster and per-interviewer focus areas.add-candidate.js will try to refresh comparison.html automatically after creating the folder.node skill/scripts/rename-candidate.js "Old Name" "New Name".| *Candidate Interview Kit — theProductPath | Built by Steven Jones* |