interview-coach

Original source / Raw SKILL.md

---
name: interview-coach
description: Professional interview preparation and practice coach for job seekers. Use when Codex needs to help users prepare for job interviews, practice common interview questions, refine their answers, or understand interview strategies. Supports multiple interview types (technical, behavioral, case studies) and provides feedback on responses.
---

# Interview Coach

## Overview

This skill transforms Codex into a professional interview coach that helps users prepare for job interviews through realistic practice sessions, question banks, and answer feedback. Based on proven interview preparation methodologies and role-playing techniques from top career coaches.

## Core Capabilities

### 1. Mock Interview Sessions

Conduct realistic interview practice by acting as an interviewer:

**Basic Usage:**
```
User: "I have a software developer interview tomorrow. Can you practice with me?"
Codex: "Great! Let's start with a common technical question: Can you explain the difference between a stack and a queue, and when you would use each?"
```

**Interview Types Supported:**
- **Technical Interviews**: Algorithm questions, system design, coding challenges
- **Behavioral Interviews**: STAR method questions, situational scenarios
- **HR/General Interviews**: Strengths/weaknesses, career goals, culture fit
- **Case Studies**: Business problems, analytical thinking
- **Leadership Interviews**: Management scenarios, team dynamics

**Interviewer Persona:**
Act as a professional interviewer who:
- Asks questions one at a time
- Waits for complete answers
- Provides constructive feedback
- Asks follow-up questions
- Remains professional but approachable

**Do NOT:**
- Write the entire conversation at once
- Provide explanations during the interview
- Skip questions or rush the process
- Break character during the session

### 2. Question Banks

Access categorized interview questions for preparation:

**Technical Questions (examples):**
- "Explain a complex technical concept to someone non-technical"
- "What's the most challenging bug you've fixed?"
- "How do you approach learning new technologies?"

**Behavioral Questions (examples):**
- "Tell me about a time you had to deal with a difficult team member"
- "Describe a situation where you had to meet a tight deadline"
- "How do you handle constructive criticism?"

**HR Questions (examples):**
- "What do you know about our company?"
- "Why do you want to work here?"
- "Where do you see yourself in 5 years?"

Load `references/questions.md` for the complete categorized question bank.

### 3. Answer Refinement

Help users improve their interview answers with specific feedback:

**Feedback Structure:**
1. **Strengths**: What worked well in the answer
2. **Areas for Improvement**: Specific suggestions
3. **Refined Version**: A polished example response
4. **Tips**: General advice for similar questions

**Example:**
```
User: "I'm good at coding"
Codex: "This is a good start, but let's make it stronger:

Strengths: Clear and concise
Areas for Improvement:
- Add specific examples or achievements
- Mention relevant technologies or projects
- Connect to the job requirements

Refined Version: 'I have 5 years of experience in full-stack development, specializing in React and Node.js. In my last role, I led a team of 4 developers and reduced page load times by 40%. I'm particularly strong at debugging complex issues and mentoring junior developers.'

Tips: Use the STAR method (Situation, Task, Action, Result) for behavioral questions."
```

### 4. STAR Method Training

Teach and practice the Situation-Task-Action-Result (STAR) framework:

**STAR Structure:**
- **Situation**: Set the context
- **Task**: Explain what needed to be done
- **Action**: Describe what you did
- **Result**: Share the outcome with metrics when possible

**STAR Examples:**
See `references/star_examples.md` for detailed examples across different industries and roles.

## Quick Start

**Scenario 1: Practice Interview**
```
User: "I have a data analyst interview at Google. Can we practice?"
Codex: [Starts interview with a relevant question]
```

**Scenario 2: Get Question Ideas**
```
User: "What are common questions for a product manager interview?"
Codex: [Provides categorized questions from reference bank]
```

**Scenario 3: Refine an Answer**
```
User: "How would you answer 'Tell me about a time you failed'?"
Codex: [Provides a STAR-based answer example]
```

## When to Use This Skill

Use this skill when:
- User is preparing for a job interview
- User wants to practice common interview questions
- User needs help refining their interview answers
- User asks about interview strategies or tips
- User mentions "job interview", "preparing for interview", "mock interview"
- User wants to understand different interview types (technical, behavioral, etc.)

## Advanced Features

### Company-Specific Preparation

When the user mentions a specific company:
1. Research the company's interview style if possible
2. Tailor questions to the company's culture and role
3. Incorporate company-specific technical topics

Example: "For Google interviews, expect heavy emphasis on algorithms and data structures..."

### Follow-Up Practice

After an interview, help users:
- Analyze what went well
- Identify areas to improve
- Prepare for next round interviews
- Handle salary negotiations

### Multiple Interview Scenarios

Support multiple interview rounds:
- **Phone Screen**: Quick questions, basic fit
- **Technical Screen**: Coding challenges, technical depth
- **Onsite**: Multiple interviews, lunch, culture fit
- **Final Round**: Executive interview, offer negotiation

## Best Practices

1. **Be Realistic**: Simulate actual interview conditions
2. **Provide Specific Feedback**: Give actionable advice, not just praise
3. **Adapt to User's Level**: Adjust difficulty based on experience
4. **Encourage Practice**: Recommend multiple practice sessions
5. **Stay Positive**: Build confidence while providing honest feedback

## Resources

### references/questions.md
Comprehensive interview question bank categorized by:
- Industry (tech, finance, healthcare, etc.)
- Role (developer, manager, designer, etc.)
- Type (technical, behavioral, HR)
- Difficulty (entry, mid, senior)

### references/star_examples.md
STAR method examples with detailed breakdowns for various scenarios.

### references/tips.md
Additional interview tips, common mistakes to avoid, and success strategies.

## Tips for Codex

- Always ask about the target role/company before starting practice
- Start with easier questions and increase difficulty
- Use the user's industry knowledge to tailor questions
- Provide feedback after every 2-3 answers during practice
- Encourage users to be specific in their answers
- If users struggle, provide gentle prompts or hints
- Remember to congratulate users on good answers


---

## Referenced Files

> The following files are referenced in this skill and included for context.

### references/questions.md

```markdown
# Interview Question Bank

This reference file contains categorized interview questions for various roles and industries.

---

## Technical Questions

### Software Engineering

**Core Concepts:**
- "Explain the difference between a stack and a queue. When would you use each?"
- "What is the difference between process and thread?"
- "Explain the concept of Big O notation and why it matters"
- "What's the difference between SQL and NoSQL databases?"

**System Design:**
- "How would you design a URL shortener?"
- "Design a real-time chat application"
- "How would you scale a web application to millions of users?"

**Coding/Algorithms:**
- "Write a function to reverse a linked list"
- "How would you detect a cycle in a graph?"
- "Implement a caching mechanism for an API"

**Debugging:**
- "Tell me about a challenging bug you fixed"
- "How do you approach debugging a complex issue?"
- "Describe your process for troubleshooting production issues"

### Data Science / Analytics

**Technical Skills:**
- "Explain overfitting and how you prevent it"
- "What's the difference between supervised and unsupervised learning?"
- "How do you handle missing data in your analysis?"

**Problem-Solving:**
- "How would you analyze user churn for a subscription service?"
- "Design an A/B test to improve conversion rates"
- "How would you detect fraudulent transactions?"

### DevOps / Engineering

**Infrastructure:**
- "Explain CI/CD and why it's important"
- "How do you manage configuration across environments?"
- "Describe your experience with containerization (Docker/Kubernetes)"

**Monitoring & Reliability:**
- "How do you set up monitoring for a distributed system?"
- "What's your approach to incident response?"
- "How do you ensure high availability?"

---

## Behavioral Questions

### Leadership & Teamwork

- "Tell me about a time you had to lead a project with limited resources"
- "Describe a situation where you had to deal with a difficult team member"
- "How do you motivate team members who are underperforming?"
- "Tell me about a time you had to make an unpopular decision"
- "How do you handle conflict within your team?"

### Problem-Solving

- "Describe a time when you identified a problem before anyone else"
- "How do you approach solving problems you've never encountered before?"
- "Tell me about a time when you had to think outside the box"
- "Describe a situation where you had to adapt quickly to changing circumstances"

### Communication

- "Explain a complex technical concept to a non-technical audience"
- "How do you keep stakeholders informed about project progress?"
- "Describe a time when your communication style caused a misunderstanding"

### Failure & Learning

- "Tell me about a time you failed at something important"
- "What's the biggest mistake you've made in your career?"
- "Describe a time when you received harsh criticism"
- "How do you handle rejection?"

---

## HR / Culture Fit Questions

### Company Knowledge

- "What do you know about our company?"
- "Why do you want to work here?"
- "How do you think our company differs from competitors?"
- "What about our mission resonates with you?"

### Career Goals

- "Where do you see yourself in 5 years?"
- "What are your long-term career objectives?"
- "Why are you interested in this specific role?"
- "What would your ideal next job look like?"

### Strengths & Weaknesses

- "What are your top 3 strengths?"
- "What's your biggest weakness?"
- "How would your former manager describe you?"
- "What skills are you looking to develop?"

### Work Style

- "Describe your ideal work environment"
- "How do you handle tight deadlines?"
- "What motivates you at work?"
- "How do you handle multiple priorities?"

---

## Industry-Specific Questions

### Product Management

- "How do you prioritize features for a product roadmap?"
- "Describe a product you launched and its impact"
- "How do you gather user feedback?"
- "Tell me about a time you had to say 'no' to a stakeholder's request"

### Marketing

- "How do you measure the success of a marketing campaign?"
- "Describe a campaign you're particularly proud of"
- "How do you stay current with marketing trends?"
- "How would you approach launching a new product?"

### Sales

- "Walk me through your sales process"
- "How do you handle objections?"
- "Describe your most challenging sale"
- "How do you build long-term client relationships?"

### Finance

- "How do you analyze financial statements?"
- "What's your approach to risk management?"
- "Describe a complex financial analysis you performed"
- "How do you stay updated with market trends?"

---

## Senior-Level Questions

### Strategy & Vision

- "What's your vision for this role/team in the next year?"
- "How do you align team goals with company objectives?"
- "Describe a strategic initiative you led"

### Management

- "What's your management philosophy?"
- "How do you develop talent on your team?"
- "How do you handle performance issues?"
- "Describe your approach to hiring"

### Stakeholder Management

- "How do you manage competing stakeholder interests?"
- "Describe a situation where you had to influence without authority"
- "How do you get buy-in for your ideas?"

---

## Entry-Level Questions

### Education & Learning

- "What's your favorite project from school?"
- "What courses are most relevant to this role?"
- "How do you stay current with industry trends?"

### Potential

- "Why should we hire you over other candidates?"
- "What unique perspective do you bring?"
- "What are you most excited to learn in this role?"

### Motivation

- "What interests you about this industry?"
- "What are you most passionate about professionally?"
- "How do you handle repetitive tasks?"

---

## Tips for Using This Question Bank

1. **Tailor to the Role**: Select questions relevant to the specific position
2. **Adjust Difficulty**: Match question complexity to the candidate's experience level
3. **Follow Up**: Use follow-up questions to dig deeper
4. **Take Notes**: Record key points for later evaluation
5. **Be Flexible**: Adapt questions based on the conversation flow
6. **Stay Legal**: Avoid questions about protected characteristics (age, religion, etc.)

```

### references/star_examples.md

```markdown
# STAR Method Examples

This reference file contains STAR (Situation, Task, Action, Result) method examples for various interview scenarios.

---

## What is STAR?

**STAR** is a structured method for answering behavioral interview questions:

- **Situation**: Set the context and background
- **Task**: Explain what needed to be done
- **Action**: Describe what you actually did
- **Result**: Share the outcome, preferably with metrics

---

## Example 1: Leadership

**Question:** "Tell me about a time you led a team through a challenging project"

**STAR Response:**

**Situation:**
"In my previous role as a senior developer, our team was tasked with migrating our payment system to a new provider with only 3 months' notice, while the original estimate was 6 months."

**Task:**
"I needed to lead a team of 5 developers to complete this migration within the 3-month deadline without disrupting our existing customer experience."

**Action:**
"I took several key actions:
1. **Planning**: Broke down the migration into weekly milestones and created a detailed risk matrix
2. **Team Management**: Assigned each developer to specific modules based on their expertise
3. **Communication**: Set up daily stand-ups and weekly stakeholder updates
4. **Risk Mitigation**: Implemented feature flags to safely roll back if issues arose
5. **Support**: Created comprehensive documentation and ran training sessions for the QA team"

**Result:**
"We successfully completed the migration on time, reducing transaction costs by 40% and improving processing speed by 25%. The migration had zero downtime and received positive feedback from customers. The approach I developed is now being used for all future system migrations."

---

## Example 2: Problem-Solving

**Question:** "Tell me about a time you solved a complex problem"

**STAR Response:**

**Situation:**
"At my previous company, our application's performance degraded significantly after we added new features, causing page load times to increase from 2 seconds to 8 seconds."

**Task:**
"I was tasked with identifying the root cause and restoring performance to acceptable levels before our peak traffic season started in 2 weeks."

**Action:**
"I approached this systematically:
1. **Analysis**: Used APM tools to identify database queries taking 4+ seconds
2. **Investigation**: Discovered that our ORM was generating N+1 queries on the dashboard
3. **Optimization**: Rewrote the queries using proper JOINs and implemented caching for frequently accessed data
4. **Testing**: Set up load testing to verify improvements under stress
5. **Monitoring**: Added performance metrics and alerts for future issues"

**Result:**
"Page load times dropped from 8 seconds back to 1.8 seconds—actually better than before. The optimization reduced our database load by 60%, saving us approximately $2,000/month in infrastructure costs. I also documented the issue and created a checklist for future development to prevent similar problems."

---

## Example 3: Dealing with Conflict

**Question:** "Tell me about a time you had to deal with a difficult colleague"

**STAR Response:**

**Situation:**
"In a cross-functional project, a designer consistently delivered assets late, which was blocking our engineering team and putting our launch timeline at risk."

**Task:**
"I needed to resolve the conflict without damaging our working relationship and get the project back on track."

**Action:**
"I took a collaborative approach:
1. **Private Conversation**: Scheduled a one-on-one meeting to understand their challenges
2. **Root Cause**: Discovered they were overwhelmed with conflicting priorities from multiple projects
3. **Solution**: Worked with them to reprioritize and established clear delivery dates
4. **Communication**: Created a shared project timeline with clear dependencies
5. **Follow-up**: Set up weekly check-ins to address issues early"

**Result:**
"We successfully launched the project on time. The designer appreciated being heard and continued to be a strong collaborator on future projects. Our cross-functional communication improved significantly, and our team adopted this approach for all future projects."

---

## Example 4: Innovation

**Question:** "Tell me about a time you identified an opportunity for improvement"

**STAR Response:**

**Situation:**
"I noticed that our customer support team was spending an average of 15 minutes per call answering the same 5 basic questions about our product setup."

**Task:**
"I wanted to reduce support team workload and improve the customer onboarding experience."

**Action:**
"I took initiative:
1. **Analysis**: Recorded and categorized 100 support calls to identify the top 5 questions
2. **Solution**: Created an interactive onboarding guide with video tutorials and step-by-step instructions
3. **Implementation**: Added a 'Quick Start' section to our product dashboard
4. **Promotion**: Trained support agents to direct users to the guide
5. **Iteration**: Based on usage analytics, I continuously improved the content"

**Result:**
"Average call duration dropped from 15 minutes to 6 minutes—a 60% reduction. Customer satisfaction scores increased by 35%. The support team was able to handle 40% more calls without adding staff, saving the company approximately $50,000 annually in support costs."

---

## Example 5: Failure

**Question:** "Tell me about a time you failed"

**STAR Response:**

**Situation:**
"In a previous role, I led a project to implement a new CRM system. I was confident in the vendor's claims about ease of implementation and allocated only 2 months for deployment."

**Task:**
"I needed to implement the CRM and train 50 employees to use it within 2 months."

**Action:**
"I made several mistakes:
1. **Assumption**: Trusted the vendor's timeline without independent verification
2. **Planning**: Didn't account for data migration complexities
3. **Communication**: Didn't set realistic expectations with stakeholders
4. **Testing**: Skipped thorough user acceptance testing
5. **When issues arose, I tried to push through instead of pausing to reassess**"

**Result:**
"The project took 6 months instead of 2, and initial user adoption was very low. However, the failure taught me critical lessons:
- Always validate vendor claims with references
- Involve end-users early in the process
- Build in buffer time for unexpected issues
- Be transparent with stakeholders about timeline risks

I used these lessons to successfully implement our next project (the payment system migration mentioned earlier) on time and under budget."

---

## STAR Method Best Practices

### Situation (20% of response)
- Keep it brief and relevant
- Provide enough context for the interviewer to understand
- Avoid unnecessary details

### Task (10% of response)
- Clearly state your role and responsibility
- Explain what needed to be done
- Show you understood the objectives

### Action (50% of response)
- Focus on **your** actions, not team actions
- Use specific examples and details
- Show your thought process and decision-making
- Highlight skills relevant to the job

### Result (20% of response)
- Quantify when possible (numbers, percentages, money)
- Connect back to the business impact
- Mention what you learned (especially for failure questions)
- Keep it positive, even when discussing failures

---

## Common Mistakes to Avoid

❌ **Too vague**: "I worked hard and we succeeded"
✅ **Specific**: "I implemented automated testing, which reduced bugs by 40%"

❌ **Focus on team**: "We decided to..."
✅ **Focus on self**: "I proposed and led the initiative to..."

❌ **No metrics**: "It improved things"
✅ **With metrics**: "Customer satisfaction increased from 75% to 92%"

❌ **Situation too long**: Spent 3 minutes setting context
✅ **Balanced**: Situation is 15-20 seconds, then move to action

❌ **Negative result only**: "It was a disaster"
✅ **Learning-focused**: "It didn't go well, but I learned X and Y"

```



---

## Skill Companion Files

> Additional files collected from the skill directory layout.

### _meta.json

```json
{
  "owner": "hhhh124hhhh",
  "slug": "interview-coach",
  "displayName": "Interview Coach",
  "latest": {
    "version": "1.0.0",
    "publishedAt": 1769912174818,
    "commit": "https://github.com/clawdbot/skills/commit/5e2797d60c2616376326d122fa430d696534685d"
  },
  "history": []
}

```