---
name: interview-prep-coach
description: Use when the user has an interview scheduled or an invite arrives. Reads the invite and the application they sent, researches the company and each interviewer's public professional background, and builds a prep brief with logistics, likely technical and behavioral questions, the user's matching stories, questions to ask, mismatches to be ready for, and practice problems. It then links the brief on the calendar event.
metadata:
  id: interview-prep-coach
  version: "1.0.0"
  author: BotPlaza
---

# Interview Prep Coach

> Drafts only: nothing is submitted, applied for, or sent without your explicit OK.

## What it does

Gets you ready for an interview the way a good mentor would. It reads exactly what you sent the company, figures out what they'll probably ask, lines up your best true stories against each requirement, flags the gaps an interviewer might probe, and gives you sharp questions to ask them. The brief is linked right on the calendar event, so it's there when you need it.

## When to use

- An interview invite lands in the inbox or on the calendar. "Prep me for my Thursday call with Cohere", "make me practice problems for the technical round".
- For non-interview meetings, use Meeting Prep Brief.

## Requires

A calendar connector (Google Calendar or Outlook) and an email connector to read the invite. The application record: the posting, the resume version sent, and any answers or cover letter. Web search for company and interviewer research. Optional: a docs app (Google Docs, Notion) for the brief.

## Schedule

Default: a daily check at 7:00 AM for new interview invites, plus on demand. Briefs are ready at least 24 hours before each interview when the invite allows.

## Inputs

| Setting | Default | Notes |
|---|---|---|
| `lookahead` | 7 days | How far ahead to scan for interviews. |
| `brief_location` | a docs folder named "Interview Prep" | |
| `practice_problems` | 3 to 5 for technical rounds | Matched to the posting's level. |
| `story_bank` | from the resume sent | Optional: the user's own STAR stories (situation, task, action, result). |

## Steps

1. **Logistics:** date, time and zone, format (phone, video, onsite, technical, behavioral), length, interviewer names, and the join link.
2. **Pull the application:** the posting, the resume version actually sent, and any form answers or cover letter.
3. **Research:** the company's product, recent news, and team. Each interviewer's public professional role and background only.
4. **Map:** for each of the top requirements, pick the user's best true story from the resume sent.
5. **Predict questions:** 5 to 8 technical (based on the posting) and 5 behavioral.
6. **Mismatches:** anything in the posting the user doesn't meet, with an honest way to address it.
7. **Questions to ask:** 3 to 5 specific ones.
8. **Practice:** for technical rounds, 3 to 5 problems at the right level, with links.
9. **Deliver:** save the brief, add the link to the end of the calendar event's description (keeping existing details), and tell the user in two lines.

## Output format

```markdown
# Interview prep: {Company}, {Role}
**{Day, date, time zone}** · {format}, {length} · [Join]({link})
**With:** {name}, {title} (one line on their background)

## The role in one paragraph
## Your stories, matched
| They want | Tell this story |
|---|---|
## Likely questions
### Technical
### Behavioral
## Be ready for
- {Mismatch, and an honest answer}
## Ask them
1. {Question}
## Practice
- [{Problem}]({link}), {level}
```

## Edge cases

- **The interview is in the next few hours:** send a one-screen quick brief first, then the full brief.
- **Interviewer names aren't given:** prep for the team's likely roles and say so.
- **The resume sent can't be found:** use the master resume and flag it.
- **The interview is rescheduled:** move the brief link to the new event.

## Boundaries

- Professional public information about interviewers only.
- Stories come from what the user actually did. Never coach them to claim something untrue.
- Never accept, decline, or reschedule interviews on the user's behalf.