agentleFS
Sign inStart free
Arnav-0Arnav-0/claude-code-setup/skills/interview-system-designer/SKILL.md

interview-system-designer

Skill0 starsChanged 7 months agoMITView on GitHub

This skill should be used when the user asks to "design interview processes", "create hiring pipelines", "calibrate interview loops", "generate interview questions", "design competency matrices", "analyze interviewer bias", "create scoring rubrics", "build question banks", or "optimize hiring systems". Use for designing role-specific interview loops, competency assessments, and hiring calibration systems.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to create structured interview loops, standardize question quality, and keep hiring signal consistent across interviewers.

    line 12
  2. Very specific:

    Run scripts/interview_planner.py to generate a baseline loop.

    line 34
  3. Distinctive:

    Keep round objectives explicit and non-overlapping.

    line 56
  4. Distinctive:

    Use the same baseline rubric across comparable roles.

    line 58

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview System Designer

Comprehensive interview loop planning and calibration support for role-based hiring systems.

Overview

Use this skill to create structured interview loops, standardize question quality, and keep hiring signal consistent across interviewers.

Core Capabilities

  • Interview loop planning by role and level
  • Round-by-round focus and timing recommendations
  • Suggested question sets by round type
  • Framework support for scoring and calibration
  • Bias-reduction and process consistency guidance

Quick Start

# Generate a loop plan for a role and level
python3 scripts/interview_planner.py --role "Senior Software Engineer" --level senior

# JSON output for integration with internal tooling
python3 scripts/interview_planner.py --role "Product Manager" --level mid --json

Recommended Workflow

  1. Run scripts/interview_planner.py to generate a baseline loop.
  2. Align rounds to role-specific competencies.
  3. Validate scoring rubric consistency with interview panel leads.
  4. Review for bias controls before rollout.
  5. Recalibrate quarterly using hiring outcome data.

References

  • references/interview-frameworks.md
  • references/bias_mitigation_checklist.md
  • references/competency_matrix_templates.md
  • references/debrief_facilitation_guide.md

Common Pitfalls

  • Overweighting one round while ignoring other competency signals
  • Using unstructured interviews without standardized scoring
  • Skipping calibration sessions for interviewers
  • Changing hiring bar without documenting rationale

Best Practices

  1. Keep round objectives explicit and non-overlapping.
  2. Require evidence for each score recommendation.
  3. Use the same baseline rubric across comparable roles.
  4. Revisit loop design based on quality-of-hire outcomes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free