The interview invitation arrives. You have a week — maybe less. You have the job description and your resume. What you need is a structured way to turn those two documents into actual preparation: the specific questions this interviewer is likely to ask, the best answers drawn from your own experience, and an honest assessment of where the gaps are.

The Interview Prep workflow does exactly that. It reads both documents, cross-references them, and produces a role-specific prep pack you can work through before the interview.

The Situation

You just got the email: "We'd love to schedule an interview for the [Role] position." The excitement lasts about 30 seconds before the reality hits — you haven't interviewed in two years, you're not sure what they'll focus on, and you need to prepare without spending every waking hour on it.

Generic interview prep is easy to find. Lists of "most common interview questions." Articles about the STAR method. None of it is calibrated to the role you're interviewing for. The questions a product company asks a Senior Engineer are different from what a consulting firm asks the same candidate for a Strategy role. The JD tells you exactly what they care about — if you know how to read it that way.

Reading a JD as a preparation document takes practice. You have to identify which requirements are mandatory versus nice-to-have, what the implicit priorities are based on how responsibilities are ordered, and where your own background creates the strongest argument. Most candidates don't do this systematically. The ones who do tend to perform notably better.

The Workflow: Interview Prep

Upload your resume and the job description. The agent reads both and builds a cross-reference model: your experience mapped against their requirements, identifying strong alignments and visible gaps.

Role-Specific Question Bank

The agent generates a question bank calibrated to this specific role. It includes two types:

Behavioral questions are derived from the role's responsibility language. If the JD lists "lead cross-functional initiatives," the agent will flag a likely question about a time you led something across teams, and point to the experience in your resume that best supports your answer.

Technical or domain questions are generated from the required skills and qualifications. If the role requires "proficiency in financial modeling," the agent flags that as a likely technical probe and notes whether your resume demonstrates this directly, indirectly, or not at all.

Model Answer Frameworks

For each behavioral question, the agent provides an answer framework: not a scripted response, but a structured outline using the STAR method (Situation, Task, Action, Result) mapped to the specific experiences in your resume that are most relevant. You fill in the details. The structure is already there.

Skills Gap Notes

Where your resume doesn't clearly address a stated requirement, the agent flags it explicitly. This isn't designed to discourage — it's designed to help you prepare a response for the predictable question. "I see your background doesn't include [X] — how would you approach this?" is a question you can answer well if you've thought about it in advance. It's a question that catches you off guard if you haven't.

Key Talking Points

The agent also surfaces a short list of the strongest arguments in your favor — the three or four experiences in your background that best match the role's priorities. These are your anchors. Work them into the conversation naturally. They're the things the interviewer should come away remembering about your background.

What You Do With It

The output is a structured document. Work through the questions the way an athlete watches game tape: methodically, before the actual event. Practice saying your answers out loud. The written framework is the scaffold — your actual delivery is what makes the difference.

Run the workflow again for each new interview. Each role produces a different question set and a different gap analysis. The prep is always specific, never generic.

Inputs and Outputs

Inputs: Your resume (PDF or DOCX) + the job description (TXT paste or PDF upload).

Output: A structured interview prep document with question bank, answer frameworks, skills gap analysis, and key talking points (DOCX/PDF).

Estimated time: About 3–4 minutes to generate.