product-os: Command for Claude Code

Interview Feedback Scorecard

Generate a rigorous, objective interview feedback scorecard for a PM candidate based on the Granola meeting transcript, assessed against our PM hiring competencies and the role's job description.

Instructions

Phase 1: Gather Context

1. Parse the arguments

   • The user provides arguments in the format: $ARGUMENTS
   • Expected format: [Candidate Name], [Target Level], [Interview Type]
   • Example: Jane Smith, Senior PM, product case study
   • If any of the three required fields are missing or unclear, ask ONLY for the missing information. Do not re-ask for fields already provided.
   • Check the auto-memory (MEMORY.md) for the interviewer's name — use this in the scorecard header

2. Find the interview in Granola

   • Use mcp__claude_ai_Granola__list_meetings (with a custom date range if the interview date is known, or last_30_days) to find candidate meetings, then filter by the candidate's name in the title or participants
   • If multiple meetings are found, ask the user to confirm which one
   • Use mcp__claude_ai_Granola__get_meeting_transcript to retrieve the full transcript

3. Fetch the job description from Notion

   • The job library is at: {your-notion-scorecard-url}
   • Use mcp__claude_ai_Notion__notion-fetch to retrieve the job library page
   • Find the job description matching the target role and level, then fetch that specific JD page
   • If the JD is not found in the library, ask the user to provide a Notion link or paste it in. Note this limitation in the output.

4. Read the PM hiring competencies

   • Read the file at team/hiring/best-practice-pm-hiring.md
   • This contains the full competency framework with excellent/poor indicators for all skills and attitudes

Phase 2: Analyse the Transcript

1. Map competencies to interview type
   • Not all competencies are equally assessable in every interview type. Based on the interview type, identify which competencies are:
     • Primary (should be thoroughly assessed in this interview type)
     • Secondary (some signal may be present)
     • Not assessable (no meaningful signal expected)
   • Use this mapping as a guide:
     • Screening call: Communication (primary), Delivering Impact (primary), Curiosity (primary), Growth Mindset (secondary), Hunger for Impact (secondary), Product Process (secondary)
     • Product case study: Product Process - all sub-competencies (primary), Delivering Impact (primary), Communication (primary), Experiment Design (primary), Measurement (primary)
     • Stakeholder interview: Collaboration (primary), Communication (primary), Project Management (primary), Ownership (primary), Growth Mindset (secondary)
     • Technical deep-dive: Product Process - Build (primary), Experiment Design (primary), Measurement (primary), Project Management (primary), Solutionisation (primary)
     • Culture/values interview: All Attitude competencies (primary), Communication (secondary), Collaboration (secondary)
   • If the interview type does not match the above, use judgement to assign primary/secondary/not assessable