Most people walk into interviews underprepared. They've skimmed the company website, glanced at their resume, and figured they'll just "think on their feet." Then the interviewer asks, "Can you walk me through a time you managed a cross-functional project?" — and their mind goes blank.
I've used the same preparation method for every single interview throughout my career. It's gotten me every offer I actually wanted. Here's how it works.
Why "thinking on your feet" isn't actually prep
The mistake most people make is treating interview prep like studying for a quiz — reviewing facts and hoping they'll remember the right things under pressure. That doesn't work. When you're nervous and answering in English, the details evaporate. You stumble, you leave out the most important parts, and the interviewer can tell immediately that you're improvising.
Write it down, then practice out loud
My approach is different. Instead of trying to recall stories on the spot, I write them down first. For each relevant experience, I put together high-level bullet points — the context, what I was responsible for, what I actually did, and the result. Then I practice saying it out loud, record myself on my phone, play it back, and refine until it sounds completely natural. The goal isn't to memorize a script. It's to know the story so well that telling it feels effortless.
Three areas you need to cover
There are three areas every interview covers. The first is your self-introduction. Most people underestimate how much this two-minute answer sets the tone for the entire conversation — nail this and you start ahead. The second is your knowledge of the company and role. You need to actually understand what they do, who their competitors are, and why this specific role exists. Not just a glance at the About page. The third — and the most important — is your project and campaign experience, prepared specifically around the requirements and responsibilities listed in the job description.
How to use the JD to predict what they'll ask
When I get a new JD, I read through the requirements carefully and highlight the keywords that come up most. Those are the hints for what the interviewer will focus on. Then I go back through my experience and match my strongest stories to those themes. The closer the match, the more convincing you'll sound.
Behavioral questions don't need a separate prep track
One thing that surprises people: you don't need a separate set of answers for behavioral questions. If you've prepared solid project stories in the format of context, goal, action, and result, you've already got answers to "tell me about a time you dealt with a difficult stakeholder" or "describe a project that didn't go as planned." The same stories cover most of it.
The final step most people skip
After you've written everything out, close the document and say each story out loud without looking at your notes. If you get stuck, take a quick look and try again. Keep going until you can tell every story cleanly without the notes in front of you. This is what makes the difference between someone who sounds fluent and someone who sounds like they're reciting answers. Practice a few more times before you walk into the room — it feels different.
I turned this framework into a free template — download it from the resources page and fill it in before your next interview.
© 2026 Rachel Hong · Accelerator Consulting