You have an interview scheduled. You Google "how to prepare for an interview." You get a list of 11 steps that tells you to research the company, bring copies of your resume, and arrive on time.
You already knew all of that.
This guide skips the obvious and focuses on what actually separates candidates who get offers from candidates who wonder what went wrong.
Start with the job description — not the company website
Most candidates do their research in the wrong order. They spend an hour reading the company's About page and mission statement, then skim the job description five minutes before the interview.
Flip it.
The job description is the closest thing you have to a list of questions you'll be asked. Every requirement is a signal. "Strong cross-functional collaboration skills" means they're going to ask you about a time you worked with difficult stakeholders. "Data-driven decision making" means they want metrics in your answers.
Read the job description and ask yourself: what story proves I can do each of these things? That's your prep work.
Once you've done that, research the company — but research with intent. Look for context that makes your answers more specific. If they just launched a new product line, that's relevant when they ask why you want to work there. If they've had layoffs in the past year, that's relevant if they ask about navigating uncertainty.
Generic research produces generic answers. Specific research produces specific answers. Specific answers get offers.
Prepare stories, not answers
Most candidates try to prepare answers. That's the wrong unit of preparation.
An answer is a response to a specific question. A story is a flexible asset you can deploy across multiple questions. A well-constructed story about a project that nearly failed can answer questions about failure, pressure, leadership, problem-solving, and conflict — depending on which angle you lead with.
Build a bank of 5–7 strong stories from your work history. Each one should cover:
- The situation: one or two sentences of context
- What was at stake: why it mattered, what could go wrong
- What you specifically did: not your team, not your manager — you
- The outcome: ideally with a number attached
The most useful stories tend to involve: delivering something under pressure, navigating conflict or misalignment, making a judgment call with limited information, recovering from a mistake, and influencing someone you had no authority over.
If you can cover those five, you can handle most behavioral interviews without running out of material.
The detail that most candidates skip
Here's the thing about specificity: it's not just about having numbers. It's about being specific enough that your answer could only have come from you.
Compare these two answers to "Tell me about a time you had a conflict with a colleague":
Version A: "I had a disagreement with a colleague about the direction of a project. We talked it through and eventually found a solution that worked for both of us."
Version B: "My colleague and I disagreed on whether to rebuild our onboarding flow or patch it. I pulled three months of drop-off data and found that 60% of users were abandoning at a single step. That reframed the conversation — we weren't debating philosophy, we were looking at a specific problem. We scoped a targeted fix, shipped it in two weeks, and saw a 22-point improvement in completion rate."
Version A could be said by anyone. Version B can only be said by you. That's what specificity does: it makes you memorable and it makes you credible.
When you're rehearsing your stories, keep asking yourself: would anyone else be able to say exactly this? If yes, add more detail.
Prepare your three non-negotiable answers
There are three questions that appear in almost every interview, in some form. You should have polished answers for all three before you walk in.
"Tell me about yourself." This is not an invitation to recite your resume. It's an opportunity to frame your career narrative in a way that makes your interest in this specific role feel inevitable. Keep it to 90 seconds. End with why you're here.
"Why do you want this role / this company?" The answer needs to be specific enough that it couldn't apply to any other company. "I'm excited about your growth trajectory" is not specific. "I've been following how you've been expanding into enterprise accounts after starting in SMB — that's a transition I've lived through and I think I can contribute to it" is specific.
"What are your weaknesses?" Don't say you're a perfectionist. Pick something real that you've actively worked to improve, show what you did about it, and show the current state. Interviewers aren't looking for perfection — they're looking for self-awareness and a growth pattern.
Practice out loud with someone who pushes back
This is the part most people skip, and it's the part that matters most.
Reading through your answers in your head is not practice. It feels like practice because it's effortless — but that effort is exactly what you need to train for. Speaking clearly under mild social pressure, while being observed, while tracking time, while trying to remember what you planned to say — that's the actual skill.
Practice changes the experience. Not just your confidence, but your actual performance. Answers that sound clear in your head often come out muddled when spoken. You discover which stories fall apart under follow-up questions. You find out that your "tell me about yourself" is three minutes long, not 90 seconds.
The ideal practice involves another person asking questions, not letting you off the hook when you get vague, and following up the way a real interviewer would. Most people don't have easy access to that — friends and family tend to be too supportive to be useful.
That's exactly what kalbeki is designed to do.
Prepare questions that are actually good
Most candidates treat "do you have any questions for us?" as a formality. Thoughtful candidates use it as a second chance to show how they think.
Avoid questions you could answer with a Google search. Avoid questions that are clearly about salary and benefits before an offer exists. And avoid the trap of asking nothing — it reads as disengagement.
Good questions are specific, curious, and reveal that you've thought about the role:
- "What does success look like in this role after the first six months — and how would you know?"
- "What's the hardest part of this role that the job description doesn't capture?"
- "Is there anything from our conversation today that I can address or clarify?"
That last one is underused and genuinely useful. It invites the interviewer to surface any hesitation they have — and gives you a chance to respond to it directly rather than wonder about it afterward.
The day before matters more than the day of
The morning of an interview is the wrong time to review your notes, research the company, or stress about what to wear. By then, your preparation should be complete. What you actually need is to be calm and rested.
The night before: confirm the logistics (time, location, format, who you're meeting), lay out what you're wearing, and review your stories one more time out loud. Then stop.
The interview itself is a performance. Performances don't improve on the day — they reflect the quality of the rehearsals before it.
Prepare seriously. Practice out loud. Walk in knowing your stories cold. That's the whole system.