Build structured behavioral interview guides using the STAR method. Map job competencies to interview questions, provide scoring rubrics (1–5), and include follow-up probes and red/green flag indicators. Use when preparing for hiring interviews or standardizing interview practices.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
For each competency, create questions that elicit:
Include 1 primary question + 2 follow-up probes per competency.
| Score | Level | Description |
|---|---|---|
| 5 | Exceptional | Clear STAR, ownership, measurable impact, learning applied |
| 4 | Strong | Good STAR, solid actions, positive result |
| 3 | Adequate | Basic STAR, some vagueness, acceptable result |
| 2 | Weak | Incomplete STAR, unclear actions, minimal impact |
| 1 | Poor | No relevant example, hypothetical response, red flags |
| Input | Required | Format |
|---|---|---|
| Job description | Yes | Full JD text |
| Interview stage | Yes | Phone / Technical / Behavioral / Final |
| Competency model | Recommended | List of competencies with definitions |
| Time allocated | Recommended | Minutes per interview |
## Interview Guide — [Role] — [Stage]
### Competency 1: Problem Solving
**Primary Question:**
"Tell me about a time you faced a complex problem at work that didn't have an obvious solution. Walk me through how you approached it."
**Follow-up Probes:**
- "What alternatives did you consider before choosing your approach?"
- "What was the measurable outcome?"
**Scoring Rubric:**
| Score | Look For |
|-------|----------|
| 5 | Structured approach, evaluated multiple options, quantified result, applied learning |
| 4 | Clear problem definition, logical approach, positive outcome |
| 3 | Basic approach described, some structure, acceptable result |
| 2 | Vague description, no clear methodology, minimal impact |
| 1 | No relevant example, only hypothetical, blame-shifting |
**🟢 Green Flags:** Uses data, considers stakeholders, shows iterative thinking
**🔴 Red Flags:** Takes all credit in team settings, blames others, can't articulate approach
---
### Competency 2: Stakeholder Management
**Primary Question:**
"Describe a situation where you had to manage conflicting priorities from different stakeholders. How did you handle it?"
**Follow-up Probes:**
- "How did you communicate your decision to the stakeholder whose request was deprioritized?"
- "What would you do differently?"
[...repeat for each competency...]
---
### Interview Evaluation Summary
| Competency | Score (1–5) | Notes |
|------------|-------------|-------|
| Problem Solving | ___ | |
| Stakeholder Management | ___ | |
| Technical Depth | ___ | |
| Leadership | ___ | |
| **Overall** | ___ | |
**Recommendation:** ☐ Strong Hire ☐ Hire ☐ No Hire ☐ Strong No Hire
I'm interviewing candidates for a Senior Product Manager role.
This is a behavioral interview (45 minutes).
Key competencies: Strategic thinking, Stakeholder management, Data-driven decisions, Cross-functional leadership.
Build an interview guide with STAR questions and scoring rubrics.
| Check | Question |
|---|---|
| Correctness | Does the draft structure follow the stated framework or industry standard? |
| Completeness | Are all required sections present with substantive (not placeholder) content? |
| Context-fit | Does tone, detail level, and terminology match the intended audience? |
| Consequence | If sent to the intended recipient without further editing, what would fail? |
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.
中文简介正在准备中。当前显示原文说明。
Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.
中文简介正在准备中。当前显示原文说明。
Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.
中文简介正在准备中。当前显示原文说明。
Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.
中文简介正在准备中。当前显示原文说明。
Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.
中文简介正在准备中。当前显示原文说明。
Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.
中文简介正在准备中。当前显示原文说明。