| name | hr-interviewing | ||||
|---|---|---|---|---|---|
| description | Help HR managers, recruiters, hiring managers, and interview panels design structured, competency-based interview questions, interview guides, and evaluation scorecards for any role. Use when asked to design structured interview questions or scoring rubrics, design a structured interview, generate behavioral questions, build an interview scorecard, evaluate candidates consistently, reduce interview bias, or any interview planning and assessment task. | ||||
| metadata |
|
Comprehensive guidance for designing structured, competency-based interviews that improve hiring quality, reduce interviewer bias, and produce consistent candidate evaluations across technical and non-technical roles.
- Generating structured interview questions for any role and seniority
- Designing competency-based interview guides
- Creating behavioral (STAR) interview questions
- Creating situational and hypothetical interview questions
- Designing technical, leadership, and collaboration interview questions
- Writing standardized follow-up probing questions
- Building interview scorecards and scoring rubrics
- Defining strong answer indicators and hiring signals
- Identifying weak answers and interview red flags
- Reducing interviewer bias through structured interviewing
- Creating interview plans for hiring managers and interview panels
- Standardizing interviews across multiple interviewers
A structured interview is a consistent hiring process where every candidate is evaluated using the same competencies, core questions, and scoring criteria.
Rather than relying on intuition or conversational interviews, structured interviewing emphasizes:
- predefined competencies
- standardized interview questions
- consistent follow-up prompts
- objective scoring criteria
- evidence-based evaluation
- comparable candidate assessments
Structured interviews generally provide more reliable and fair hiring decisions than unstructured interviews while improving consistency across interview panels.
Every interview should be aligned with:
- the responsibilities of the role
- required competencies
- seniority expectations
- business context
- measurable evaluation criteria
Questions should evaluate how candidates think, make decisions, communicate, collaborate, and solve problems rather than simply recalling information.
For each competency, generate:
Create one behavioral question that encourages candidates to answer using the STAR framework:
- Situation
- Task
- Action
- Result
Behavioral questions should focus on real experiences rather than hypothetical opinions.
Create one hypothetical scenario that reflects realistic workplace challenges and assesses judgment, prioritization, and decision-making.
Generate two or three probing questions that:
- clarify ownership
- explore reasoning
- validate decision-making
- understand collaboration
- uncover lessons learned
Avoid repeating the original question.
Describe what excellent responses typically demonstrate, including:
- clear ownership
- structured thinking
- measurable outcomes
- business impact
- effective communication
- sound judgment
- self-awareness
- learning from experience
Identify common warning signs such as:
- vague examples
- lack of ownership
- blaming others
- inconsistent reasoning
- inability to explain decisions
- no measurable outcomes
- poor reflection
- weak collaboration
Interview questions may be generated for competencies including:
- technical expertise
- problem solving
- analytical thinking
- communication
- collaboration
- stakeholder management
- leadership
- influence
- adaptability
- learning agility
- prioritization
- decision making
- ownership
- customer focus
- conflict resolution
- innovation
- strategic thinking
- project execution
- coaching and mentoring
A balanced interview should include multiple question styles.
Assess past experiences that demonstrate relevant competencies.
Evaluate how candidates would respond to realistic workplace scenarios.
Assess applied knowledge, reasoning, architecture, or domain expertise appropriate to the role.
Evaluate influence, coaching, delegation, decision-making, and organizational impact.
Assess cross-functional communication, stakeholder management, and teamwork.
Explore how candidates operate with incomplete information or changing priorities.
Evaluate accountability, resilience, continuous improvement, and self-reflection.
Evaluation criteria should be defined before interviewing begins.
Scorecards should include:
- competency
- evidence observed
- interviewer notes
- strengths
- concerns
- overall rating
- hiring recommendation
Interviewers should record evidence rather than opinions whenever possible.
Design interviews that minimize unconscious bias by:
- asking every candidate the same core questions
- using predefined scoring criteria
- evaluating observable evidence
- separating evidence from interpretation
- documenting ratings before panel discussion
- focusing on job-related competencies
Avoid evaluating candidates based on "gut feeling" or cultural similarity. Structured interviews improve consistency and fairness by standardizing both questions and evaluation criteria.
Do not generate questions related to:
- age
- marital status
- family plans
- pregnancy
- religion
- nationality
- ethnicity
- disability (unless legally appropriate and job-related)
- political views
- financial status
- other protected characteristics
Also avoid:
- leading questions
- trivia or memory tests
- irrelevant brainteasers
- subjective "culture fit" questions without defined competencies
- "Create a structured interview guide for a [Senior Backend Engineer]."
- "Generate competency-based interview questions for a [Product Manager]."
- "Design a complete interview plan for hiring a [Head of HR]."
- "Create a structured interview for a [Customer Success Manager] with scoring guidance."
- "Build a panel interview guide for a [Staff AI Engineer]."
- "Generate behavioral interview questions for assessing [leadership]."
- "Create STAR interview questions for [stakeholder management]."
- "Write behavioral questions that evaluate [problem solving] for a [Senior Software Engineer]."
- "Create follow-up questions to verify ownership and accountability."
- "Generate behavioral interview questions for [cross-functional collaboration]."
- "Generate technical interview questions for a [DevOps Engineer] with scoring guidance."
- "Create competency-based interview questions for an [AI Engineer]."
- "Design technical interview questions that evaluate systems thinking."
- "Generate architecture-focused interview questions for a [Staff Backend Engineer]."
- "Create interview questions that distinguish junior, mid-level, and senior candidates."
- "Create a structured interview scorecard for a [Product Designer]."
- "What does an excellent answer look like for this interview question?"
- "Identify red flags in this interview response."
- "Evaluate these interview notes against predefined competencies."
- "Recommend a hiring decision using evidence from the interview."
- Start by defining the competencies the role requires before writing any interview questions — question design follows competency definition, not the other way around, and skipping this step produces inconsistent, subjective interviews.
- Ask every candidate the same core questions for the same role.
- Use follow-up questions to explore depth, ownership, and decision-making — a well-placed 'what was your specific role in that?' or 'what would you do differently?' reveals far more than the initial answer.
- Evaluate the quality and specificity of evidence candidates provide, not their confidence or presentation style — articulate candidates can mask thin experience, and quieter candidates may have stronger track records.
- Focus on behaviors, reasoning, and observable evidence, and score responses independently before interviewer calibration meetings.