Product Sense & Execution Interview
Evaluate product manager candidates on user empathy, product design trade-offs, metric selection, and strategic execution.
Template Overview
Great product managers combine deep customer empathy with ruthless prioritization. When evaluating product management candidates, interviewers must test how the candidate decomposes ambiguous market opportunities, navigates complex trade-offs, and designs simple, elegant solutions.
Without a structured evaluation rubric, product interviews degenerate into superficial conversations about trendy consumer apps rather than disciplined product thinking.
This template provides an objective Product Sense evaluation framework: customer problem framing, persona segmentation, creative solution generation, metric architecture, and edge-case risk mitigation.
Markdown Template Structure
Copy the block below or click Download .md File to add this template directly to your personal vault:
---
title: "Product Sense Interview: [Candidate Name]"
date: [YYYY-MM-DD]
candidate_name: "Candidate Taylor Brooks"
interviewer: "[[VP Product / Lead PM]]"
role_applied: "Senior Product Manager — Core Desktop Experience"
interview_prompt: "Design a private, local-first meeting notes experience for legal professionals."
recommendation: [Strong Hire | Hire | Leaning Hire | Leaning No Hire | Strong No Hire]
tags: [interview, product, product-sense, execution, hiring]
---
# Product Sense Interview: [Candidate Name] — [YYYY-MM-DD]
## 1. Problem Framing & User Persona Segmentation
- **Problem Statement:** Trial attorneys and corporate counsel attend hours of confidential client depositions daily but cannot use cloud meeting transcription bots due to attorney-client privilege.
- **Candidate User Segmentation:** Segmented into Corporate Litigation Attorneys (strict compliance), Solo Practitioners (cost & speed sensitive), and Paralegals (formatting & archiving).
- **Selected Target Persona:** Corporate Litigation Attorneys facing highest legal liability.
- **Rating:** 🟢 Exceeds Expectations (Immediately anchored discussion in legal compliance risk rather than generic productivity).
## 2. User Journey & Core Pain Points
1. Transcripts must be verified against verbatim audio recordings during deposition cross-examinations.
2. Notes must export into clean, tamper-evident Markdown formats that can be archived in client case files.
3. Zero third-party telemetry or cloud persistence can be permitted.
## 3. Product Solution Architecture & Feature Prioritization
- **Core Feature 1:** On-device audio recording with timestamped speaker quote attribution.
- **Core Feature 2:** One-click legal deposition template generator conforming to Federal Rules of Evidence.
- **Core Feature 3:** Local cryptographic SHA-256 hash generation on note save to prove document immutability.
- **Trade-Off Navigated:** Explicitly chose to forgo real-time cloud multi-user collaboration to defend strict local data sovereignty.
## 4. Success Metrics & Guardrails
| Metric Tier | Metric Selected | Justification |
| :--- | :--- | :--- |
| **North Star Metric** | Weekly Verified Deposition Notes Shipped | Captures core utility and habitual retention. |
| **Input Metric** | Template completion rate (>85%) | Measures workflow friction in template layout. |
| **Guardrail Metric** | Audio frame drop rate (<0.001%) | Protects data integrity; deposition audio cannot be lost. |
## 5. Final Hiring Recommendation & Synthesis
> [!IMPORTANT] Recommendation: Strong Hire
> Taylor demonstrated exceptional product intuition, quickly grasping our local-first privacy thesis and designing an elegant workflow for legal professionals with strong metric guardrails.
- [ ] Submit scorecard to hiring portal.
- [ ] Attend committee debrief on [[YYYY-MM-DD]].
Filled Real-World Example
Here is a realistic example demonstrating how this template captures actual deliberations:
---
title: "Product Sense: Taylor Brooks"
date: 2026-10-07
candidate_name: "Taylor Brooks"
interviewer: "[[David Park]]"
recommendation: Strong Hire
tags: [interview, product]
---
# Product Sense: Taylor Brooks — October 7, 2026
## 1. Summary
Taylor designed a compelling legal deposition note workflow. Demonstrated clear understanding of attorney-client privilege constraints.
## 2. Trade-Offs
Rightly prioritized audio integrity and cryptographic hashing over social sharing features.
## 3. Recommendation
Strong Hire for Senior Product Manager.
When to Use and When to Avoid
When to Use
- Use during product management product sense, design, and execution interviews.
- Use to evaluate candidates on user empathy, persona segmentation, metric selection, and trade-offs.
- Use to benchmark candidate intuition against local-first privacy and product sovereignty principles.
When to Avoid
- Avoid using for pure engineering systems architecture interviews (use [[system-design-interview]]).
- Avoid using for coding interviews (use [[technical-coding-interview]]).
On-Device AI Integration
Capture product sense interviews with Oyma on macOS:
Analyze the product sense interview transcript:
1. Synthesize the candidate's problem framing, persona segmentation, and target user selection.
2. Outline the user journey pain points identified and proposed feature solutions.
3. Document the trade-offs navigated and the metrics architecture (North Star, inputs, guardrails).
4. Record the final hiring recommendation with supporting product evidence.
Output in clean, structured CommonMark.
Your candidate scorecards and product interview notes stay strictly confidential on your Mac.
Frequently Asked Questions
What is 'Product Sense' in a PM interview?
Product sense is the ability to deeply understand user psychology, identify underserved customer problems, design intuitive solutions, and navigate trade-offs between user delight and technical feasibility.
How does this template evaluate metric selection?
It evaluates whether the candidate defines a true North Star metric paired with guardrail metrics to prevent unintended negative consequences.
Why evaluate candidate understanding of privacy and local architecture?
For local-first sovereign software, PMs must understand why users care about privacy and how local architecture alters product design.
Write product sense & execution interview in plain Markdown.
Store notes in your local vault, transcribe meetings on-device, and retain 100% data sovereignty.