Skip to content

The-AI-Directory-Company/agents-and-skills / skills/hiring-rubric

hiring-rubric

Verified

Build structured hiring rubrics — defining evaluation dimensions, behavioral interview questions, scoring criteria, and calibration processes that maximize signal and minimize bias.

examples/product-manager-mid-level.md

View on GitHub
# Hiring Rubric Example: Mid-Level Product Manager

This example applies the hiring rubric template to a non-technical role where evaluation dimensions shift from code-centric skills to product thinking, stakeholder communication, and prioritization.

## Role Profile

```
Role:            Product Manager (Mid-Level, L4)
Team:            Growth — Activation Squad
Reports to:      Director of Product, Growth
Level:           IC4 (3-5 years PM experience)
Headcount type:  Backfill

6-month goals:
1. Own the activation funnel end-to-end — from signup to first value moment
2. Ship two experiments that measurably improve Day-7 retention
3. Build a working relationship with engineering, design, and data science
   stakeholders without requiring Director escalation
```

## Evaluation Dimensions

| Dimension                  | Weight | Assessed In              |
|----------------------------|--------|--------------------------|
| Product thinking           | 30%    | Case study interview     |
| Stakeholder communication  | 25%    | Behavioral interview     |
| Prioritization & tradeoffs | 20%    | Case study interview     |
| Data fluency               | 15%    | Take-home + discussion   |
| Execution & follow-through | 10%    | Behavioral interview     |

## Scoring Criteria

### Product Thinking (30%)

```
4 - Strong Hire:  Frames problems from user outcomes, not feature requests.
                  Identifies hidden assumptions in the case prompt. Proposes
                  a measurement plan alongside the solution. Articulates what
                  success and failure look like before describing the solution.

3 - Hire:         Connects the proposed solution to a user need. Considers at
                  least one alternative approach. Defines a reasonable success
                  metric when prompted.

2 - Weak:         Jumps straight to a solution without exploring the problem
                  space. Success metric is vague ("improve engagement").
                  Needs repeated prompts to consider the user perspective.

1 - No Hire:      Describes a feature list with no connection to user outcomes.
                  Cannot articulate why a user would care about the proposal.
```

### Stakeholder Communication (25%)

```
4 - Strong Hire:  Describes past situations where they aligned stakeholders
                  with competing priorities — names the tension, what they
                  did, and the result. Adjusts communication style to audience
                  (executive summary vs. technical detail). Gives a specific
                  example of saying "no" to a stakeholder and preserving the
                  relationship.

3 - Hire:         Provides a concrete example of cross-functional alignment.
                  Demonstrates awareness that different audiences need different
                  framing. Describes a conflict with a reasonable resolution.

2 - Weak:         Examples are vague ("I worked with engineering"). Cannot
                  recall a specific disagreement or how it was resolved.
                  Defaults to "I just made sure everyone was on the same page"
                  without explaining how.

1 - No Hire:      Cannot provide a real example of stakeholder management.
                  Describes only top-down communication (telling, not aligning).
```

### Prioritization & Tradeoffs (20%)

```
4 - Strong Hire:  Uses a structured framework (impact vs. effort, RICE, or
                  similar) and explains its limitations. Identifies second-order
                  consequences of prioritization choices. Articulates what they
                  would cut and why, not just what they would build.

3 - Hire:         Applies a reasonable prioritization approach to the case.
                  Can explain why one item ranks above another. Acknowledges
                  tradeoffs when prompted.

2 - Weak:         Lists priorities without explaining the ranking logic.
                  Treats prioritization as a single pass rather than iterative.
                  Cannot explain what would change if a constraint shifted.

1 - No Hire:      Says "everything is a priority" or defers to stakeholders
                  without taking a position. No evidence of structured thinking.
```

### Data Fluency (15%)

```
4 - Strong Hire:  Defines metrics that directly tie to the business outcome.
                  Distinguishes leading and lagging indicators. Identifies
                  potential confounders in an A/B test setup. Describes a time
                  data changed their mind about a product decision.

3 - Hire:         Selects reasonable metrics for the case. Can interpret a
                  simple funnel chart and draw conclusions. Knows when to use
                  an A/B test vs. a rollout with monitoring.

2 - Weak:         Picks vanity metrics (page views, signups) without
                  connecting them to outcomes. Cannot explain statistical
                  significance in practical terms.

1 - No Hire:      No evidence of data-informed decision making. "I trust my
                  gut" without acknowledging when data should override instinct.
```

### Execution & Follow-Through (10%)

```
4 - Strong Hire:  Describes a shipped product with specifics: scope, timeline,
                  obstacles, and what they personally drove. Gives an example
                  of catching a risk early and adjusting the plan.

3 - Hire:         Provides a concrete shipped example. Can describe the
                  sequence from spec to launch. Mentions at least one obstacle
                  and how it was handled.

2 - Weak:         Describes projects in vague terms ("we launched a feature").
                  Cannot distinguish their contribution from the team's.

1 - No Hire:      No examples of shipped work. Describes only strategy or
                  planning, never delivery.
```

## Interview Questions

### Product Thinking (Case Study — 45 minutes)

1. "Our Day-7 retention is 22% and our target is 30%. Walk me through how you would diagnose this and decide what to build."
   - Follow-up: "You have three candidate solutions. How do you decide which to test first?"
   - Follow-up: "What would make you kill this initiative entirely?"

2. "A senior stakeholder wants you to build a feature that a large enterprise client requested. Walk me through how you evaluate this."
   - Follow-up: "The data shows only 3% of users would benefit. The stakeholder insists. What do you do?"

### Stakeholder Communication (Behavioral — 30 minutes)

1. "Tell me about a time you had to get buy-in from someone who disagreed with your product direction."
   - Follow-up: "What specifically changed their mind — or didn't?"
   - Follow-up: "What would you do differently?"

2. "Tell me about a time you had to communicate a significant scope cut or delay to stakeholders."
   - Follow-up: "How did you frame it? What was the reaction?"

### Prioritization (Case Study — integrated)

1. "Here are six potential projects for the activation squad next quarter. You can only do two. Walk me through your ranking."
   - Follow-up: "Your eng lead says one of your top picks is 3x the estimated effort. What changes?"

### Data Fluency (Take-Home Discussion — 20 minutes)

Provide a pre-read: a one-page summary of activation funnel data with conversion rates, cohort breakdowns, and an A/B test result with ambiguous significance.

1. "Walk me through what you see in this data. What would you investigate next?"
2. "The A/B test shows p=0.08. A stakeholder says 'close enough — let's ship it.' What do you recommend?"

## Scorecard

```
Candidate: _______________    Interviewer: _______________
Role: Product Manager (L4)    Date: _______________
Round: _______________

| Dimension                  | Score (1-4) | Evidence (required)           |
|----------------------------|-------------|-------------------------------|
| Product thinking           |             |                               |
| Stakeholder communication  |             |                               |
| Prioritization & tradeoffs |             |                               |
| Data fluency               |             |                               |
| Execution & follow-through |             |                               |

Overall recommendation:  [ ] Strong Hire  [ ] Hire  [ ] Weak  [ ] No Hire

Key strengths:
Key concerns:
```

## Calibration Notes

For this role, the most common calibration disagreement is on **product thinking** vs. **stakeholder communication**. A candidate who scores 4 on product thinking but 2 on stakeholder communication may be a strong IC PM but will struggle in a cross-functional growth role. Weight stakeholder communication accordingly — this squad requires daily alignment with engineering, data science, and marketing.
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 196kUpdated Claude CodeCodexVerifiedInstall