Get the FREE Ultimate OpenClaw Setup Guide →

hiring-interview-workflows

Scanned
npx machina-cli add skill dzhibas/engineering-manager-plugin/hiring-interview-workflows --openclaw
Files (1)
SKILL.md
3.4 KB

Hiring and Interview Workflows

Job Description Drafting

  1. Ask for: role level, team, key technologies, and must-have vs. nice-to-have skills
  2. Draft JD with sections:
    • About the team: What the team does, its mission, and current challenges
    • What you'll do: 4-6 concrete responsibilities (not vague aspirations)
    • What we're looking for: Must-have and nice-to-have qualifications
    • Why join us: Team culture, growth opportunities, impact
  3. Flag exclusionary language and suggest inclusive alternatives
  4. Calibrate requirements to the level — avoid senior expectations for mid-level roles
  5. Include compensation range placeholder and growth trajectory

Interview Question Generation

Generate behavioral and technical questions organized by competency area:

Technical Depth

  • "Walk me through a system you designed that had to handle [relevant constraint]. What trade-offs did you make?"
  • "Describe a production incident you led the response for. What was your process and what did you change afterward?"
  • "Tell me about a time you inherited a legacy system. How did you approach improving it?"

Collaboration & Communication

  • "Tell me about a time you disagreed with a technical decision. How did you handle it?"
  • "Describe how you've mentored a junior engineer through a challenging project"
  • "Give an example of how you've communicated a complex technical concept to a non-technical stakeholder"

Problem-Solving

  • "Give an example of a time you identified a problem before it became urgent. What did you do?"
  • "Describe a situation where you had to make a decision with incomplete information"

Tag each question with the competency it assesses and the signal to look for in a strong answer.

Scorecard Template

Generate interview scorecards with:

  • Competency areas: technical depth, collaboration, problem-solving, culture add
  • Rating scale: 1-4 with behavioral anchors for each level
    • 1 = Does not meet bar — significant concerns
    • 2 = Below bar — some gaps in this area
    • 3 = Meets bar — demonstrated competency with solid examples
    • 4 = Exceeds bar — exceptional examples, would raise the team's level
  • Space for specific evidence and quotes from the interview
  • Overall recommendation: Strong hire / Hire / No hire / Strong no hire
  • Sections for red flags and bright spots

Debrief Facilitation

Prepare debrief structure:

  1. Independent assessment first: Each interviewer shares their rating and top evidence before group discussion (prevents anchoring bias)
  2. Competency review: Walk through each competency area, compare ratings
  3. Evidence check: Focus on specific examples, not impressions or gut feel
  4. Disagreement discussion: Explore areas where interviewers diverged
  5. Consensus: Reach a recommendation with documented rationale
  6. Decision documentation: Capture the final decision, key evidence, concerns, and any conditions

Generate a debrief summary template that captures the final decision and can be filed for future reference.

Source

git clone https://github.com/dzhibas/engineering-manager-plugin/blob/main/skills/hiring-interview-workflows/SKILL.mdView on GitHub

Overview

This skill provides a complete framework for creating job descriptions, interview questions, scorecards, and debriefs in engineering hiring. It helps ensure consistency, inclusivity, and clear evaluation criteria across the interview loop.

How This Skill Works

The skill prompts you to collect role specifics (level, team, key technologies) and then produce four artifacts: a structured job description, a categorized interview question bank, a competency-based scorecard, and a debrief template. It also emphasizes calibrating requirements to the role level and flagging exclusionary language.

When to Use It

  • When you need to write a job description for an engineering role
  • When you want to generate behavioral and technical interview questions
  • When you’re creating a candidate scorecard to standardize evaluation
  • When you’re preparing a debrief structure to document decisions
  • When you’re refining any part of the engineering hiring process (interview loop)

Quick Start

  1. Step 1: Gather role level, team, core technologies, and must-have vs nice-to-have skills
  2. Step 2: Draft the JD with sections About the team, What you'll do, What we're looking for, Why join us, plus a compensation placeholder
  3. Step 3: Generate a competency-based interview question set, build a 1-4 scorecard with evidence prompts, and prepare a debrief template

Best Practices

  • Collect role details up front: level, team, core technologies, must-have vs nice-to-have skills
  • Draft a JD with concrete responsibilities (4-6) and inclusive language
  • Calibrate requirements to the level and include a compensation range placeholder and growth trajectory
  • Generate a competency-based question bank organized by areas: technical depth, collaboration, problem-solving
  • Create a structured scorecard (1-4 with anchors), capture evidence/quotes, and include red flags and bright spots in the debrief

Example Use Cases

  • Drafted a JD for a mid-level backend engineer with 4 concrete responsibilities and inclusive language
  • Generated a set of technical depth and collaboration questions categorized by competency for an interview loop
  • Built a 1-4 scorecard with behavioral anchors and a field for interview quotes and evidence
  • Prepared a debrief template that records independent assessments and consensus rationale
  • Flagged non-inclusive language in a JD and revised it to be neutral and welcoming to underrepresented candidates

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers