An Interview Prep Workflow (Candidate Side)

TL;DR: A five-stage interview prep workflow for candidates, covering company research, likely questions, mock practice, a salary and offer-talk prep step, and a follow-up note, built as saved prompts so prep takes the same effort for your fifth interview this month as your first. It picks up where a job search workflow leaves off, once an interview is actually on the calendar.

What Does an Interview Prep Workflow Cover, and What Doesn't It Cover?

This is the candidate's side of interview prep: what to do between getting a calendar invite and walking into the room. It doesn't cover finding the role, tailoring a resume, or tracking applications, since that's the job search stage and it has its own workflow. It also doesn't cover writing interview questions to ask someone else, which is a different task entirely, aimed at the person doing the hiring rather than the person being interviewed.

Five stages, roughly in the order you'd actually run them: research the company deeply enough to ask a real question back, anticipate what you're likely to be asked based on the actual job description, practice answering out loud rather than only in your head, think through compensation and offer questions before they come up rather than in the moment, and send a follow-up that references something specific from the conversation instead of a generic thank-you. Similar in shape to our 10-minutes-before meeting prep workflow, but built for the higher stakes and longer runway of an interview rather than a routine meeting: a meeting is often minutes away when you prep for it, while an interview usually gives you days, which is why this workflow front-loads more research and includes a rehearsal stage that a quick meeting prep doesn't need.

None of this is unique to a single kind of interview. A first-round phone screen, a technical interview, and a final-round conversation with a hiring manager all run through the same five stages, they just differ in how much weight each stage carries. A phone screen leans harder on the research stage, since it's often the interviewer's first real look at whether you understood the role; a technical round leans harder on practicing specific answers; a final round leans harder on the offer-talk stage, since compensation questions are more likely to come up once both sides are already leaning toward a yes.

Stage 1: How Do You Research a Company Well Enough to Ask a Real Question?

Reciting facts from the "About" page is easy to spot and doesn't land as insight. The goal here is finding something specific enough that asking about it signals you actually looked.

1. Company research brief

I have an interview at [company name] for a [role] position. Here's what I know: [paste job
posting, and any notes on the company]. Research and summarize: what the company does in plain
terms, anything notable they've done or announced recently, and how this role likely fits into their
broader goals. Flag anything you're not confident about rather than guessing.

Ask explicitly for the model to flag uncertainty. A confident-sounding wrong fact about the company, stated back to an interviewer, does more damage than admitting in prep that you weren't sure and verifying it yourself before the interview.

2. Turn research into one real question to ask them

Here's what I found about [company]: [paste research summary]. Suggest 2-3 specific questions I
could ask the interviewer that show I did real research, not generic questions like "what's the
culture like" that could apply to any company.

Stage 2: How Do You Anticipate What You'll Actually Be Asked?

Anticipating questions isn't about predicting the exact wording. It's about walking in having already thought through most of what's likely to come up, so nothing lands as a total surprise.

3. Likely questions from the actual job posting

Here's the job posting for the role I'm interviewing for: [paste posting]. Based on the
responsibilities and requirements listed, generate 10-12 questions I'm likely to be asked, mixing
behavioral questions ("tell me about a time...") with role-specific ones grounded in what's actually
in the posting.

Paste the real posting, not a paraphrase of it. The requirements section is usually the most direct source for role-specific questions, and a generic description of the role produces generic, less-useful questions in return.

Stage 3: How Do You Practice Without Just Reading Your Notes?

Reading a prepared answer silently in your head is a weak rehearsal for a conversation you'll have to have out loud. This stage is where practicing against a mock interview closes that gap.

4. Mock interview, one question at a time

Act as an interviewer for a [role] position at a [company type — e.g. "mid-size B2B SaaS company"].
Ask me one interview question at a time. After I answer, give brief feedback on what was strong and
what was vague or missing, then ask the next question. Start now.

Answer out loud, even alone, rather than typing. The gap between an answer that sounds fine written down and one that sounds fine spoken is exactly the gap this stage exists to close, and typing skips past it.

5. Tighten a specific weak answer

Here's how I answered "[paste the question]": [paste your answer]. It felt too long/vague/rambling.
Help me tighten it to the actual point in under 90 seconds of spoken time, keeping it in my own
words rather than rewriting it into something that doesn't sound like me.

Ask explicitly for it to stay in your own words. A rewrite that sounds polished but unlike you is harder to deliver naturally than a slightly rougher version that's actually yours.

Stage 4: How Do You Prepare for Salary and Offer Questions Before They Come Up?

Compensation questions catch a lot of candidates off guard not because they're unpredictable, they tend to follow a small set of patterns, but because most people never rehearse an answer until they're already in the moment, under some pressure to respond quickly.

6. A range and a rationale, worked out in advance

I'm interviewing for [role] at [company, or company type if unknown]. Based on typical ranges for
this role, level, and location [give what you know], help me think through a target compensation
range and a brief rationale for it, so I'm not guessing out loud for the first time when they ask.

Treat the output as a starting point for your own research, not a verified number. A model's sense of a "typical" range is a rough estimate at best, and it can't see current, location-specific market data the way a salary-benchmarking site or a recruiter conversation can. Use this prompt to organize your thinking, then verify the actual number elsewhere before you commit to it out loud.

7. Practice answering "what are your salary expectations?"

Practice this with me: you're the interviewer and you just asked "what are your salary
expectations?" I'll answer, then give me feedback on whether my answer sounded confident and
specific, or hesitant and vague. Ask a natural follow-up if I gave a range instead of a number.

Stage 5: How Do You Follow Up Without Sending a Generic Thank-You?

The last stage is easy to skip under the relief of the interview being over, which is exactly why most follow-ups end up generic.

8. A follow-up note that references the real conversation

I just interviewed for [role] at [company]. Here's what stood out from the conversation:
[paste 2-3 specific things discussed]. Write a short follow-up email that thanks them and references
one of those specifics, rather than a generic "thank you for your time" note.

Send it within a day, while the specifics are still fresh enough to reference accurately. A follow-up sent a week later, referencing details vaguely, reads as an afterthought regardless of how well it's written.

How Do You Adjust Prep for a Panel Interview or Multiple Rounds?

A single one-on-one interview and a panel of four people asking questions in turn require the same five stages underneath, but the practice stage in particular benefits from a small adjustment.

9. Practice fielding a panel-style question

I have a panel interview coming up with [number] interviewers, roles: [list roles if known, e.g.
"hiring manager, a future teammate, someone from another team"]. Simulate one round: ask me a
question, tell me which panelist is asking and why they'd care about that particular angle, then give
feedback on whether my answer addressed that person's actual concern.

The reason this differs from the standard mock interview above is that a panel question often carries an unstated angle specific to who's asking it. A future teammate asking about your process is usually listening for something different than a hiring manager asking the same question, and an answer aimed at the wrong angle can feel technically fine but somehow miss.

If your process involves multiple separate rounds rather than one panel, rerun the research and anticipate stages (1-3) before each round with anything new you learned in the previous one. A second- round interviewer often already has notes from the first round, and a candidate who can reference something discussed earlier, without being prompted to, tends to read as more engaged than one starting from zero each time.

What Does a Full Prep Cycle Look Like End to End?

What Goes Wrong Most Often in Interview Prep?

• Reciting a memorized answer instead of practicing a conversation. It's usually audible to the interviewer, and it costs more credibility than a slightly less polished, genuine answer.
• Asking about the job posting instead of the actual job posting. A vague description of the role produces vague, generic anticipated questions in return.
• Improvising a compensation number in the moment. A range worked out calmly beforehand sounds more confident than one worked out under mild pressure with the interviewer waiting for an answer.
• Skipping the follow-up entirely, or sending a fully generic one. A follow-up that references something specific from the actual conversation is one of the cheapest ways to stand out afterward.
• Trusting the research summary without verifying anything uncertain. A confidently wrong fact stated to an interviewer does more damage than the gap it was meant to fill.
• Treating this page in isolation from the search that got you here. If you don't have a system for finding and tracking roles yet, the job search workflow is the stage before this one.

What About Remote or Video Interviews Specifically?

The five stages above don't change for a video call, but a couple of small logistics are worth adding to your prep specifically because a remote interview removes some of the cues an in-person one gives you for free.

10. A pre-call technical and framing check

I have a video interview tomorrow for [role]. Help me build a short checklist to run through the
day before: camera framing and lighting, internet connection backup plan, a quiet space and backup
location, and anything in the video platform's settings worth checking (virtual background, mute
default) before the call actually starts.

Running this the day before, not ten minutes before, gives you time to actually fix anything the checklist turns up. A lighting problem discovered two minutes before the call starts is a problem you live with; one discovered the day before is one you solve.

A video call also removes some of the small in-person signals, like a shared laugh in the hallway before you sit down, that make an interview feel less like a formal exam. That's not something a prompt fixes directly, but knowing it going in is itself useful: expect the conversation to feel a touch more clinical on video than it would across a table, and don't read that as a sign the interview is going badly.

Where Does This Fit With Prompt Architects?

Every prompt above runs as plain text in ChatGPT, Claude, or Gemini, at no cost. What turns four separate prompts into an actual workflow is running them in sequence without retyping your resume, target roles, and standing preferences into a fresh prompt for every new interview. Our meeting prep workflow covers the same research-then- practice shape for lower-stakes recurring meetings, if that's a closer fit for what you need day to day.

Prompt Architects' library saves this four-stage sequence as a linked set you can reuse for every interview, and a saved context holds your resume, target roles, and talking points so the research and practice prompts pull from it automatically instead of you repasting the same details each time. Running any single prompt above exactly as written, for as many interviews as you want, is free; saving the sequence as a reusable set is a Pro-and-above feature.