Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
日本語の概要は準備中です。原文の説明を表示しています。
Design and coordinate efficient interview processes with optimal panel composition, scheduling logistics, and candidate experience
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Design efficient interview processes with optimal panel composition, logical scheduling flow, and positive candidate experience.
Based on structured interviewing best practices and candidate experience research, combining:
| Claude Does | You Decide |
|---|---|
| Designs interview stages | Final panel selection |
| Suggests panel composition | Scheduling conflicts |
| Creates question banks | Interview format (virtual/onsite) |
| Drafts communications | Offer timing |
| Identifies bottlenecks | Business priorities |
Stage Design:
| Stage | Purpose | Format | Duration |
|---|---|---|---|
| Phone Screen | Basic qualification | Remote | 30 min |
| Technical | Skills assessment | Remote/Onsite | 60 min |
| Hiring Manager | Fit and depth | Remote/Onsite | 45 min |
| Team/Culture | Team dynamics | Onsite | 45 min |
| Executive | Final approval | Onsite | 30 min |
Process Variations:
| Role Level | Stages | Total Time |
|---|---|---|
| Individual Contributor | 3-4 | 3-4 hours |
| Manager | 4-5 | 5-6 hours |
| Director+ | 5-6 | 6-8 hours |
| Executive | 6+ | 8+ hours |
Panel Selection Criteria:
| Role | Include | Rationale |
|---|---|---|
| Hiring Manager | Always | Final decision authority |
| Direct Reports | If managing | Two-way assessment |
| Cross-functional | Recommended | Collaboration preview |
| Skip Level | Senior roles | Leadership alignment |
| HR/Recruiting | Screen/Final | Process consistency |
Diversity Requirements:
Scheduling Principles:
Optimal Day Structure:
| Time | Interview | Why |
|---|---|---|
| 9:00 | Technical | Fresh candidate, complex assessment |
| 10:30 | Break | Decompression |
| 11:00 | Hiring Manager | Core conversation |
| 12:00 | Lunch | Culture signal, informal |
| 1:00 | Team | Energy after lunch |
| 2:00 | Executive | Final impression |
Key Touchpoints:
Debrief Structure:
Input:
Design interview process for:
- Role: Senior Software Engineer
- Team: 5 engineers, 1 manager
- Timeline: Hire within 3 weeks
- Format: Hybrid (some remote, some onsite)
Output:
## Interview Process: Senior Software Engineer
### Process Overview
| Stage | Format | Duration | Interviewers | Turnaround |
|-------|--------|----------|--------------|------------|
| 1. Recruiter Screen | Phone | 30 min | Recruiter | Same day |
| 2. Technical Screen | Video | 60 min | Engineer | 24 hours |
| 3. Onsite Loop | In-person | 4 hours | Panel | 24 hours |
| 4. Debrief | Internal | 30 min | All | Same day |
| 5. Offer | Call | 15 min | HM + Recruiter | 48 hours |
**Total Timeline:** 10-14 business days
---
### Stage 1: Recruiter Screen
**Format:** Phone/Video call
**Duration:** 30 minutes
**Interviewer:** Recruiter
**Purpose:** Basic qualification, logistics, motivation
**Questions:**
1. Walk me through your background (5 min)
2. Why are you interested in this role? (3 min)
3. What's your ideal next role? (3 min)
4. Salary expectations? (2 min)
5. Timeline and availability? (2 min)
6. Candidate questions (10 min)
**Pass Criteria:**
- [ ] Meets minimum experience (5+ years)
- [ ] Reasonable salary alignment
- [ ] Available within timeline
- [ ] Genuine interest
---
### Stage 2: Technical Screen
**Format:** Video call with code sharing
**Duration:** 60 minutes
**Interviewer:** Senior Engineer (Sarah)
**Purpose:** Technical depth, problem-solving, code quality
**Structure:**
- 5 min: Introductions
- 10 min: Technical background discussion
- 35 min: Coding problem (medium difficulty)
- 10 min: System design discussion
- 5 min: Candidate questions
**Assessment Areas:**
| Area | Weight | Signals |
|------|--------|---------|
| Problem solving | 40% | Approach, communication |
| Code quality | 30% | Clean, tested, efficient |
| Technical depth | 20% | Language mastery, patterns |
| Collaboration | 10% | Receptive to hints, explains well |
**Pass Criteria:** Score 3+ on each area (1-5 scale)
---
### Stage 3: Onsite Loop (4 Hours)
**Panel Composition:**
| Time | Interview | Interviewer | Focus |
|------|-----------|-------------|-------|
| 9:00 | System Design | Tom (Staff Eng) | Architecture thinking |
| 10:00 | Code Review | Lisa (Senior Eng) | Code quality, feedback |
| 11:00 | Hiring Manager | Mike (Eng Manager) | Fit, growth, expectations |
| 12:00 | Lunch | Any team member | Culture, informal |
| 1:00 | Behavioral | Sarah (Senior Eng) | STAR examples |
**Detailed Interview Guides:**
#### System Design (Tom, 9:00-10:00)
**Question:** "Design a real-time notification system for a social media platform"
**Assessment:**
| Criterion | What to Look For |
|-----------|------------------|
| Requirements gathering | Clarifies scale, features |
| High-level design | Components, data flow |
| Deep dive | Storage, queuing, delivery |
| Trade-offs | Articulates decisions |
| Scale | Handles growth scenarios |
#### Code Review (Lisa, 10:00-11:00)
**Exercise:** Review prepared PR with intentional issues
**Assessment:**
| Criterion | What to Look For |
|-----------|------------------|
| Bug detection | Finds logic errors |
| Style feedback | Constructive, specific |
| Security awareness | Identifies vulnerabilities |
| Communication | Kind, actionable feedback |
#### Hiring Manager (Mike, 11:00-12:00)
**Topics:**
1. Career trajectory and goals
2. Management style preferences
3. Conflict resolution examples
4. Growth areas and learning
5. Questions about team/role
#### Behavioral (Sarah, 1:00-2:00)
**STAR Questions:**
1. "Tell me about a time you disagreed with a technical decision"
2. "Describe a project that failed and what you learned"
3. "Give an example of helping a teammate grow"
4. "Tell me about navigating ambiguity"
---
### Stage 4: Debrief
**Timing:** Same day, 4:00 PM
**Attendees:** All interviewers + Recruiter
**Format:** 30-minute structured discussion
**Agenda:**
| Time | Activity |
|------|----------|
| 0-5 | Written feedback review (pre-submitted) |
| 5-20 | Round-robin: Each interviewer shares (3 min each) |
| 20-25 | Discussion of concerns/questions |
| 25-30 | Decision: Strong Yes / Yes / No / Strong No |
**Decision Criteria:**
- Strong Yes from HM required
- No more than 1 "No" vote
- Technical interviewers must be Yes+
---
### Communication Templates
**Interview Confirmation:**
Subject: Interview Confirmation - Senior Software Engineer
Hi [Name],
We're excited to have you visit for your onsite interviews!
Date: [Date] Time: 9:00 AM - 2:00 PM Location: [Address]
Your schedule: 9:00 - System Design with Tom 10:00 - Code Review with Lisa 11:00 - Hiring Manager with Mike 12:00 - Lunch with the team 1:00 - Behavioral with Sarah
Please bring a laptop and valid ID. Parking validation available.
Reply to confirm or if you have any questions.
Best, [Recruiter]
**Post-Interview Next Steps:**
Subject: Thank You & Next Steps
Hi [Name],
Thank you for spending time with our team today!
Our team will be debriefing this afternoon, and you'll hear from us within 48 hours on next steps.
In the meantime, please don't hesitate to reach out with any questions.
Best, [Recruiter]
Input:
Need to schedule 4 interviews for tomorrow:
- Candidates: Alice, Bob, Carol
- Interviewers available: Mike (9-12), Sarah (10-2), Tom (11-4)
- Each interview: 45 minutes
Output:
## Optimized Interview Schedule
### Tomorrow's Schedule
| Time | Mike | Sarah | Tom |
|------|------|-------|-----|
| 9:00 | Alice | - | - |
| 10:00 | - | Bob | - |
| 11:00 | Carol | - | Alice |
| 12:00 | - | Carol | Bob |
| 1:00 | - | - | Carol |
### By Candidate
| Candidate | Interview 1 | Interview 2 |
|-----------|-------------|-------------|
| Alice | Mike @ 9:00 | Tom @ 11:00 |
| Bob | Sarah @ 10:00 | Tom @ 12:00 |
| Carol | Mike @ 11:00 | Sarah @ 12:00 |
### Notes
- Alice: 2-hour gap between interviews (offer coffee/workspace)
- Bob: Back-to-back, efficient
- Carol: Back-to-back, efficient
### Calendar Invites Needed
1. Alice + Mike: 9:00-9:45
2. Bob + Sarah: 10:00-10:45
3. Alice + Tom: 11:00-11:45
4. Carol + Mike: 11:00-11:45
5. Bob + Tom: 12:00-12:45
6. Carol + Sarah: 12:00-12:45
7. Carol + Tom: 1:00-1:45
Follow-up Prompts:
resume-screener - Pre-interview evaluationonboarding-guide - Post-hire processemployee-support - New hire supportまだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
Measure and optimize growth using the AARRR (Pirate Metrics) framework with stage-specific KPIs and funnel analysis
日本語の概要は準備中です。原文の説明を表示しています。
Calculate A/B test statistical significance. Use when: determining if test results are significant; calculating required sample size; estimating test duration; analyzing conversion experiments; making data-driven decisions
日本語の概要は準備中です。原文の説明を表示しています。
Assess customer account health using product usage, support sentiment, payment status, and relationship signals
日本語の概要は準備中です。原文の説明を表示しています。
Analyze paid advertising performance across channels and recommend budget reallocation to maximize ROAS and minimize CAC. Use when: planning quarterly ad budget allocation, diagnosing underperforming ad channels, deciding whether to scale spend on a channel, calculating marginal ROI across Google Ads, Meta, LinkedIn, or TikTok, rebalancing media mix after performance shifts, or setting up a test-and-scale framework for new channels.
日本語の概要は準備中です。原文の説明を表示しています。
Use when testing skills, commands, or agents for quality. Use after creating new skills, before deploying agents, or when debugging inconsistent agent behavior. Triggers on "evaluate", "test quality", "is this skill working", or QA of AI workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use when analyzing server logs to understand how AI crawlers (GPTBot, ClaudeBot, PerplexityBot) interact with your site. Use when optimizing content placement for LLM retrieval, diagnosing why AI search isn't citing your content, or auditing crawl patterns to find optimization gaps.
日本語の概要は準備中です。原文の説明を表示しています。