Behavioral & Leadership Principles Rubric

Template Overview

Past behavior is the best predictor of future performance. When interviewers ask vague hypothetical questions (“How would you handle a difficult coworker?”), candidates respond with polished, rehearsed platitudes that reveal little about their true operating style.

A structured Behavioral Interview Rubric uses the STAR method (Situation, Task, Action, Result) to evaluate how candidates actually behaved during real high-stakes workplace challenges: resolving architectural conflict, taking extreme ownership of failures, and navigating ambiguity.

This template structures your evaluation around core leadership principles: deep-dive STAR answer breakdowns, red-flag detection, cultural alignment scoring, and final hiring recommendations.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Behavioral Interview: [Candidate Name]"
date: [YYYY-MM-DD]
candidate_name: "Candidate Morgan Rivera"
interviewer: "[[Head of Engineering / Product]]"
role_applied: "Staff Product Manager / Engineering Lead"
core_competencies_evaluated:
  - "Ownership & Accountability"
  - "Constructive Conflict Resolution"
  - "Navigating Ambiguity"
recommendation: [Strong Hire | Hire | Leaning Hire | Leaning No Hire | Strong No Hire]
tags: [interview, behavioral, star-method, leadership, hiring]
---

# Behavioral Interview: [Candidate Name] — [YYYY-MM-DD]

## 1. Competency 1: Extreme Ownership & Learning from Failure
- **Question Asked:** "Tell me about a high-stakes project or release that failed on your watch. How did you handle the aftermath?"
- **Situation:** Candidate led a major database migration at prior company that caused a 45-minute production outage.
- **Task:** Lead the incident response war room and communicate transparently with executive leadership.
- **Action:** Took direct accountability without deflecting blame to junior team members; stayed on-call for 36 hours to write hotfix; authored comprehensive blameless post-mortem.
- **Result:** Implemented automated canary deployment gates that prevented any recurrence; praised by CTO for extreme integrity.
- **Rating:** 🟢 Strong Hire (Demonstrated authentic vulnerability, personal accountability, and systemic problem solving).

## 2. Competency 2: Constructive Conflict Resolution
- **Question Asked:** "Describe a situation where you had a fundamental disagreement with an engineering lead or executive. How did you resolve it?"
- **Situation:** Disagreed with VP of Engineering over adopting cloud-based transcription versus local on-device models.
- **Task:** Build consensus without creating political factions or stalling release timelines.
- **Action:** Proposed a time-boxed technical spike and benchmarked latency and cloud privacy risks with hard data.
- **Result:** Data convinced the executive team to adopt the local architecture, saving $120k in cloud egress costs.
- **Rating:** 🟢 Strong Hire (Used empirical data and respectful persuasion rather than defensive arguments).

## 3. Red Flags & Growth Areas Observed
- Candidate occasionally tended to say "we" instead of "I"; required prompt follow-up questions to isolate personal contributions.
- Zero entitlement or arrogance observed; high intellectual humility.

## 4. Final Recommendation & Debrief Summary
> [!IMPORTANT] Recommendation: Strong Hire
> Morgan exemplifies our core leadership principles: extreme ownership of mistakes, rigorous data-driven persuasion, and exceptional empathy for engineering colleagues.

- [ ] Submit completed STAR scorecard to hiring portal.
- [ ] Attend candidate debrief session on [[YYYY-MM-DD]].

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Behavioral: Morgan Rivera"
date: 2026-10-06
candidate_name: "Morgan Rivera"
interviewer: "[[David Park]]"
recommendation: Strong Hire
tags: [interview, behavioral, leadership]
---

# Behavioral: Morgan Rivera — October 6, 2026

## 1. Core Competency Review
Morgan demonstrated extraordinary ownership when recounting a major production failure at their previous startup. Took total personal accountability.

## 2. Recommendation
Strong Hire. High emotional intelligence and deep alignment with our culture of blameless learning.

When to Use and When to Avoid

When to Use

• Use during behavioral and leadership interviews for engineering, product, and leadership candidates.
• Use to evaluate candidates against core organizational values using the disciplined STAR method.
• Use to document concrete evidence of candidate integrity, ownership, and conflict resolution.

When to Avoid

• Avoid using for pure algorithmic coding challenges (use [[technical-coding-interview]]).
• Avoid using for initial 15-minute recruiter screen calls (use [[recruiter-initial-screen]]).

On-Device AI Integration

Capture behavioral interview dialogues with Oyma on macOS:

Analyze the behavioral interview audio transcript:
1. Extract candidate responses and structure each into the STAR framework (Situation, Task, Action, Result).
2. Evaluate demonstrated competencies: accountability, constructive conflict, and handling ambiguity.
3. Note any red flags, defensive communication patterns, or unverified claims.
4. Record the interviewer's final recommendation and synthesis for the hiring committee.
Output in disciplined, evidence-based CommonMark.

Sensitive candidate interview notes and leadership evaluations stay completely private on your Mac.