interview-preparation
Prepare for job interviews across formats—behavioral, technical, portfolio reviews, and negotiations. STAR/CAR frameworks for stories, common question patterns, research strategies, and follow-up templates. Triggers on interview prep, job interviews, behavioral questions, or salary negotiation requests.
Best use case
interview-preparation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Prepare for job interviews across formats—behavioral, technical, portfolio reviews, and negotiations. STAR/CAR frameworks for stories, common question patterns, research strategies, and follow-up templates. Triggers on interview prep, job interviews, behavioral questions, or salary negotiation requests.
Teams using interview-preparation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/interview-preparation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How interview-preparation Compares
| Feature / Agent | interview-preparation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Prepare for job interviews across formats—behavioral, technical, portfolio reviews, and negotiations. STAR/CAR frameworks for stories, common question patterns, research strategies, and follow-up templates. Triggers on interview prep, job interviews, behavioral questions, or salary negotiation requests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Interview Preparation Turn experience into compelling interview performance. ## Interview Types | Type | Focus | Preparation | |------|-------|-------------| | Behavioral | Past experiences, soft skills | Story bank, STAR method | | Technical | Skills assessment, problem-solving | Practice problems, fundamentals | | Portfolio/Case | Work samples, process | Presentation prep, talking points | | Culture Fit | Values alignment, team dynamics | Company research, questions | | Executive | Leadership, vision | Strategic narratives | --- ## Story Banking ### The STAR Method ``` Situation: Set the context (brief) Task: Your specific responsibility Action: What YOU did (detailed) Result: Quantified outcome + learning ``` ### The CAR Variant ``` Challenge: Problem faced Action: Steps taken Result: Outcome achieved ``` ### Story Bank Template Build 8-12 stories covering: | Category | Example Prompts | |----------|-----------------| | Leadership | Led team, made tough call, influenced without authority | | Conflict | Disagreement with colleague, difficult stakeholder | | Failure | Mistake made, project that failed, lesson learned | | Achievement | Proudest accomplishment, exceeded expectations | | Initiative | Self-started project, identified opportunity | | Collaboration | Cross-functional work, built relationships | | Problem-solving | Ambiguous situation, creative solution | | Growth | Learned new skill, received feedback, adapted | ### Story Format ```markdown ## [Story Title] **Tags**: #leadership #conflict #technical **STAR**: - **Situation**: [2-3 sentences of context] - **Task**: [Your specific role/responsibility] - **Action**: [Detailed steps YOU took—use "I" not "we"] - **Result**: [Quantified outcome + what you learned] **Variations**: Can adapt for questions about [X], [Y], [Z] **Duration**: ~2 minutes when told aloud ``` --- ## Common Question Patterns ### Opening Questions | Question | What They Want | Strategy | |----------|----------------|----------| | "Tell me about yourself" | Relevant narrative | Present → Past → Future (2 min) | | "Walk me through your resume" | Career logic | Transitions + growth + why here | | "Why this role/company?" | Genuine interest | Specific research + fit | ### Behavioral Questions | Pattern | Example | Story Category | |---------|---------|----------------| | "Tell me about a time when..." | ...you led a team | Leadership | | "Describe a situation where..." | ...you faced conflict | Conflict | | "Give an example of..." | ...a difficult decision | Problem-solving | | "What would you do if..." | ...deadline was impossible | Hypothetical (use real example) | ### Challenging Questions | Question | Strategy | |----------|----------| | "What's your greatest weakness?" | Real weakness + mitigation steps | | "Why did you leave X?" | Positive framing, growth focus | | "Why the gap in employment?" | Honest + productive use of time | | "Where do you see yourself in 5 years?" | Ambitious but realistic, aligned with role | ### Questions to Ask Them **Role Understanding**: - "What does success look like in the first 90 days?" - "What are the biggest challenges facing the team?" - "How is performance measured?" **Team/Culture**: - "Can you describe the team I'd be working with?" - "What's the collaboration style here?" - "How does the team handle disagreements?" **Growth**: - "What growth opportunities exist?" - "How do people typically advance?" - "What learning resources are available?" **Closer**: - "Is there anything about my background that gives you pause?" - "What are the next steps in the process?" --- ## Technical Interview Prep ### Coding Interviews ``` 1. Clarify the problem (ask questions) 2. Work through examples 3. Explain your approach before coding 4. Write clean code, talk through it 5. Test with edge cases 6. Analyze complexity (time/space) ``` ### System Design ``` 1. Clarify requirements (functional + non-functional) 2. Estimate scale (users, data, QPS) 3. High-level design (components, data flow) 4. Deep dive on key components 5. Address bottlenecks, trade-offs 6. Discuss monitoring, failure modes ``` ### Technical Discussion - Know your resume deeply—anything listed is fair game - Prepare to explain past projects in detail - Have opinions on tools/technologies (with reasoning) - Admit what you don't know, show how you'd learn --- ## Portfolio Review Prep ### Presentation Structure ``` 1. Brief intro (30 sec) 2. Project 1: Deep dive (5-7 min) - Context + challenge - Your role + process - Key decisions + rationale - Results + learnings 3. Project 2: Medium depth (3-5 min) 4. Project 3: Overview (2-3 min) 5. Q&A (remaining time) ``` ### Talking Points Per Project - Why you chose this project to show - What made it challenging - Decisions you made and why - What you'd do differently - How it relates to their needs ### Common Portfolio Questions - "Walk me through your process" - "What was the biggest challenge?" - "How did you handle feedback/pushback?" - "What would you do differently?" - "How did you measure success?" --- ## Company Research ### Before the Interview | Research | Where to Find | |----------|---------------| | Company mission/values | About page, annual report | | Recent news | Google News, press releases | | Products/services | Website, product pages | | Competitors | Industry analysis | | Interviewer background | LinkedIn | | Glassdoor reviews | Interview questions, culture | | Company challenges | News, earnings calls | ### Synthesis Questions - How does this role contribute to their mission? - What challenges might they be facing? - Why might they be hiring for this role now? - What unique value can I bring? --- ## Salary Negotiation ### Research Phase - Levels.fyi, Glassdoor, Payscale for ranges - Consider: location, company stage, your experience - Know your minimum, target, and stretch numbers ### Negotiation Principles 1. **Don't give a number first** (if possible) 2. **Anchor high** (within reason) 3. **Negotiate the whole package** (base, equity, bonus, benefits, start date) 4. **Get it in writing** 5. **Be gracious** regardless of outcome ### Scripts **When asked for expectations early**: > "I'm focused on finding the right fit. I'm confident we can find something that works if we're aligned on the role. What's the range budgeted for this position?" **Responding to an offer**: > "Thank you, I'm excited about this opportunity. I'd like to take some time to review the full package. When do you need a response?" **Counter-offering**: > "I'm very excited about joining [Company]. Based on my research and the value I'll bring, I was hoping for [X]. Is there flexibility there?" **If they can't move on salary**: > "I understand the constraints. Are there other elements we could discuss—signing bonus, equity, PTO, start date, or title?" --- ## Day-of Checklist ### Before - [ ] Review company research notes - [ ] Review your story bank - [ ] Prepare questions to ask - [ ] Test tech setup (if virtual) - [ ] Prepare materials (resume, portfolio, notes) - [ ] Plan arrival (15 min early) - [ ] Dress appropriately ### During - [ ] Listen fully before answering - [ ] Ask for clarification if needed - [ ] Use specific examples - [ ] Show enthusiasm - [ ] Take notes - [ ] Ask your prepared questions ### After - [ ] Send thank-you within 24 hours - [ ] Note what went well/poorly - [ ] Follow up on timeline given --- ## References - `references/story-bank-template.md` - Full story bank format - `references/question-bank.md` - 100+ common questions - `references/follow-up-templates.md` - Thank you and follow-up emails
Related Skills
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.
coliseum-dispatch
Dispatches a composed set of assignment envelopes to domain-expert subagents in parallel, in a single message with multiple Agent tool calls. Enforces the no-pingpong gate via the pingpong-detector agent before any dispatch fires. Use when invoked by the coliseum-orchestrator as Phase 3; when envelopes are already composed and the next step is parallel execution; or when the user asks to "fan out" or "dispatch in parallel." Produces a dispatch log capturing what was sent, when, and where returns land.
assignment-composition
Wraps each surfaced dimension as a self-contained 9-section autonomous-work-assignment envelope — scope, context, success criteria, allowed tools, return format, handoff — all the recipient subagent needs to execute without coming back. Use when invoked by coliseum-orchestrator as Phase 2; when dimensions are named and the next step is to make each independently dispatchable; or when the user asks "compose this as an assignment." The no-pingpong gate validates each envelope before dispatch.
workspace-autopsy-governance
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
workshop-presentation-design
Design engaging workshops, conference talks, and educational presentations. Covers learning objectives, activity design, slide craft, and facilitation techniques. Triggers on workshop design, presentation prep, talk structure, or training session requests.
webhook-integration-patterns
Designs reliable webhook systems with proper delivery guarantees, retry logic, signature verification, and idempotent processing for event-driven integrations.