agentleFS
leoleolroleoleolro/career-os/.claude/skills/interview-prep/SKILL.md

interview-prep

Skill0 starsChanged 55 days agoMITView on GitHub

Build an interview pack (predicted questions, STAR answers, technical/case drills) for a job folder, then run mock interviews. Use when the candidate says "interview prep", "prepare me for", "mock interview", "what will they ask", "/interview-prep".

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use application-tracker, interview-debrief and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xiding-codeSkill

    application-tracker

    Automatically log and track all job applications submitted. Use this skill after every application submission to record the details in a tracking spreadsheet and save relevant documents. Also trigger when the user asks "application status", "what have I applied to", "tracking", or wants to review their application history. Maintains a single source of truth for all job search activity.

    Also in 4 projects that use this

  • jackhendonSkill

    interview-debrief

    Structure notes from a user research session into a clean debrief with insights, quotes, and implications. Paste your raw notes in and get a formatted summary ready for Notion.

    Also in 3 projects that use this

  • proficientlyjobsSkill

    job-search

    Search for jobs matching my resume and preferences

    Also in 9 projects that use this

  • claude-office-skillsSkill

    cover-letter

    >

    Also in 7 projects that use this

  • xiding-codeSkill

    cover-letter-writer

    Write and iteratively refine cover letters using a 3-agent debate team (2 Opus critics + 1 Sonnet judge). Use this skill whenever a job application allows cover letter upload, whenever the user asks to write or improve a cover letter, or whenever the job-screener skill returns APPLY for a position. The must-write rule (if enabled in config) applies: if the application system has a cover letter upload field, a cover letter MUST be written. Trigger on: "write cover letter", "cover letter", any application form with a cover letter upload option, or after a job-screener APPLY decision.

    Also in 3 projects that use this

  • claude-office-skillsSkill

    company-research

    Conduct comprehensive company research and due diligence. Analyze business model, competitive landscape, management, and market position.

    Also in 5 projects that use this

  • +1 more from claude-office-skills

The file

Files
SKILL.md

/interview-prep <jobs/<slug>> [mock]

Inputs

jobs/<slug>/jd.md, jobs/<slug>/resume.md (the version they submitted), profile/story-bank.md, profile/master-resume.md, profile/career-context.md. If any [FILL: …] markers in the story bank matter for this role, ask the candidate for them first — answers must be true.

1. Classify the interview

  • Consulting (BCG / Big 4 / boutique): fit + behavioural (BCG "personal experience interview"), case interview (market sizing, profitability, structure), sometimes a written case. BCG X graduate: add a technical screen (Python/ML/coding challenge) and a case.
  • AI engineer / FDE / solutions: system design for LLM apps, agent architecture, tool/MCP design, evals, prompt engineering, a coding exercise, customer-facing scenario ("client says the model hallucinates — walk us through").
  • Oracle EPM / ERP consulting: functional depth (Planning forms, rules, Data Management/EDMCS, Smart View), implementation lifecycle, client-handling.
  • Data / analytics: SQL, Python/pandas, stats, a take-home.

2. Write jobs/<slug>/interview-prep.md

  1. Role in one paragraph — what they will probe, based on the JD's "What you'll bring".
  2. Predicted questions (25–40) grouped: opener/motivation ("why BCG", "why leave your current employer after ~2 years" — prepare this one carefully), behavioural mapped to their competencies, technical, case/scenario, closing.
  3. STAR answers for the 8–10 most likely behavioural questions, each drawn from a named story in story-bank.md; 90–120 seconds spoken; end with the result and what the candidate learned. Mark anything they must verify.
  4. Technical drill sheet — 10–15 questions with model answers at the depth of the JD (for BCG X: Python data handling, model selection, overfitting, evaluation metrics, deploying a model; for AI engineer: RAG vs fine-tune, tool-calling loops, context management, evals, guardrails).
  5. Case practice (consulting only) — 3 mini cases with a framework and a worked answer; one mining/energy case (the candidate's client domain).
  6. Gaps to study before the interview — ranked, with a 1-line resource each (free).
  7. Questions to ask them — 6, specific to this team.
  8. Logistics — format/rounds from the JD or the company's known process, what to bring.

3. Mock mode (mock)

Ask one question at a time. Wait for the candidate's answer. Score 1–5 on structure / evidence / concision / relevance, give a 3-line improvement, show a tightened version of their answer, then ask the next. After 6–8 questions, summarise patterns and save a short note to jobs/<slug>/notes.md with date + weakest areas. Never answer for them unprompted; never invent facts about their experience.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.