interview-scheduler
Design and coordinate efficient interview processes with optimal panel composition, scheduling logistics, and candidate experience
What this skill does
# Interview Scheduler > Design efficient interview processes with optimal panel composition, logical scheduling flow, and positive candidate experience. ## When to Use This Skill - Setting up interview loops - Coordinating panel schedules - Designing interview stages - Optimizing candidate experience - Creating interview runbooks ## Methodology Foundation Based on **structured interviewing best practices** and **candidate experience research**, combining: - Stage-appropriate assessment - Panel diversity requirements - Time-to-hire optimization - Candidate communication ## What Claude Does vs What You Decide | 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 | ## Instructions ### Step 1: Define Interview Process **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 | ### Step 2: Panel Composition **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:** - Minimum 2 different perspectives on panel - Gender diversity when possible - Tenure diversity (new and experienced) - Function diversity for cross-team roles ### Step 3: Schedule Optimization **Scheduling Principles:** 1. Candidate availability first 2. Minimize calendar fragmentation 3. Allow buffer between interviews 4. End with positive impression interview 5. Same-day feedback when possible **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 | ### Step 4: Communication Templates **Key Touchpoints:** 1. Interview confirmation 2. Day-before reminder 3. Day-of logistics 4. Post-interview next steps 5. Status updates ### Step 5: Feedback Coordination **Debrief Structure:** - Schedule within 24 hours of final interview - Collect written feedback before meeting - Structured discussion format - Clear decision criteria - Documented outcome ## Examples ### Example 1: Full Interview Loop Design **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 - Behavi
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.