How to prepare for an interview so your stories survive the follow-up
Here is how to prepare for an interview, and the big-tech interview I lost that taught me how.
I once lost a seven-round process on my fourth story.
The role was Customer Success Manager at a world-famous tech company: one screening call, five interviews, a final. After more than 10 years in consulting, in the Big Four, with C-level clients, I had prepared hard. A very big spreadsheet turned each of my consulting projects into a STAR story, mapped to what the role and the company's own values asked for.
The first three stories went well. On the fourth, the interviewer, with more than 20 years in the industry, asked me to justify the data volumes and the complexity of a transformation I had led. I had my numbers: thousands of interfaces and APIs, the departments affected, the FTEs, the money at stake. His answer: "Not precise enough. You're still too vague."
That's when I knew I wouldn't go further. I didn't.

This guide is what I would do differently: six steps, from mapping the process to practicing with someone who follows up. It is built for interviews where the bar is high: consulting, big tech, large companies.
Why most interview prep falls short
Most interview preparation tips stop at "research the company" and "practice common questions". That prepares you for an average interview.
In my own search, I saw fewer open roles, more competition and longer processes. Every application deserves more intensity than it used to. Not more applications. Better ones.
How to prepare for an interview in six steps
- Map the process before you prepare anything.
- Read the job description with three highlighters.
- Turn the job description into likely interview questions.
- Build four to six stories that survive the follow-up.
- Practice with a sparring partner who follows up.
- Prepare your own questions.

Step 1: map the process before you prepare anything
Ask the recruiter how many rounds there are and who you will meet. Recruiter screen, hiring manager, case study, offer negotiation: each round tests something different, so each needs its own prep.
Then write a checklist for each round, and ask for a referral if someone in your network works there. It is a lot of work. It is also what the people across the table expect.
Step 2: read the job description with three highlighters
The posting is the employer's own list of what they will check. Copy it into your notes first: postings are often taken down before your interview.
Then highlight three things:
- The responsibilities: what you will do day to day.
- The requirements: skills, experience, tools, languages. The ones repeated or stressed ("must have", "essential") are the ones that will be tested.
- The context: team, customers, current challenges ("newly created role", "fast growth"): why the role exists, and so what will be expected first.
Step 3: turn the job description into likely interview questions
For each highlighted line, ask yourself: how will the interviewer check that I have this?
| What the job description says | Likely question |
|---|---|
| "Manage a portfolio of accounts" | "Tell me about a customer who almost left. What did you do?" |
| "Work cross-functionally with product teams" | "Tell me about a disagreement with another team. How did you resolve it?" |
| "Drive large transformation programs" | "How big was the largest program you led? What exactly changed because of you?" |
These job description interview questions are the easiest to predict: the employer wrote them down first.
Then add the questions that come up almost everywhere: tell me about yourself (yes, every single time), why this company, why this role, why you are leaving, your salary expectations.
Step 4: build four to six stories that survive the follow-up
You don't need one answer per question. You need four to six true stories, each able to answer several questions. Tell them with a simple structure such as the STAR method: the situation, your task, what you did, the result.
Then map your stories against the requirements, and against the company's values when it publishes them. An important requirement with no story next to it? That's the next story to prepare.
Now the part that cost me that seven-round process. My fourth story had numbers. It didn't have precision. Before the interview, put each story through the follow-up test:
- Where does each number come from, and what was it before?
- What exactly did you do, as opposed to the team?
- What changed because of it, said in one sentence?
If you can't answer one of the three in two sentences, the story isn't ready yet. Precise, and concise.
Step 5: practice with a sparring partner who follows up
Getting hired is like a marathon. It takes regular training. It takes increasing the load. It takes being pushed to your limits. It takes staying sharp and staying motivated, across three to five interviews, sometimes on the same day.
On paper, every answer looks fine. Out loud, under follow-up questions, some of them fall apart. Do at least one mock interview on the questions from step 3, with someone who follows up: "Specifically, what did you do?", "Compared to what?", "What was the result?". Note the answers that get stuck and rework them.
Step 6: prepare your own questions
Prepare two or three questions that show you have read the job description: the role's main challenge, how success will be measured, the team. Avoid questions whose answer is on the company's website.
The day before, and the day itself
- The job description, read one last time.
- Your four to six stories, with their numbers and sources.
- Your two-minute introduction and your two or three questions.
- The people you will meet, and the time, place or video call link, tested.
After each round: debrief before you forget
Write down the questions you were asked, the answer that got stuck, and what the next round is likely to test. Rework that answer, then send a short thank-you note.
Why I built Raise, and what it does
I built the predecessor to Raise as a very big spreadsheet with VBA macros, started years before the rise of AI and ChatGPT and improved over many years. When I looked for a tool to prepare for interviews at that level, I found nothing.
So I built Raise, to give candidates the interview prep tool I wished I'd had: a sparring partner that follows up.
Here is what Raise does to help you prepare for an interview:
- Likely questions drawn from the job posting: Raise generates the questions a tracked job makes likely.
- A written mock interview with feedback: strengths, areas to work on, and the method steps (STAR, CAR, Minto, MEDDIC or SPIN) present or missing, quoting your own words. The interviewer is a fictional AI character.
- Prep round by round: the application, each interview round (three by default, up to ten), then the offer negotiation, with actions for each step.
- Four interview situations: recruiter call, hiring manager, case study, offer negotiation.
- What companies say about their interviews: for eleven companies, a summary of how they describe their own interviews, with a link.
- Something concrete to show: on the Max plan, three prototype ideas for the role, which you build in Lovable on your own account, with fictional data.
Whatever you use to prepare, the method is the same: map the process, read the job description, build stories that survive the follow-up, and practice until your fourth story is as solid as your first. That is how you walk into the room ready.
Frequently asked questions
How long does it take to prepare for an interview?
It depends on the role, the number of rounds and what you already know about the company. Spread your prep over several days: your stories mature, and there is time left for a mock interview.
How do I find interview questions based on the job description?
Highlight the responsibilities, the requirements and the context, then turn each requirement into the question that will check it, as in step 3. Then add the classics that come up in almost every interview.
What if the job description is vague?
Compare it with two or three postings for the same role at similar companies: the requirements they share are the ones you will be tested on. Then ask the recruiter what success in the role looks like.
Can AI help with interview preparation?
Yes, before the interview: an AI tool can suggest interview questions based on the job description, and help you practice in writing with feedback. Reread everything it produces, and keep it out of the real interview: your answers have to be yours.