Adapting Is the Job

I have been in product management for over twenty-five years. I came up in the early days when the role barely existed as a defined function. We were figuring it out as we went, making up frameworks, explaining our value to every new stakeholder, and generally operating in a state of permanent uncertainty.

Over time, the field matured. Companies learned how to hire product managers at scale. That standardization was good for the profession and frustrating for those of us who had built our careers in the pre-standardization era. The informal, scrappy experience I had accumulated did not always translate to what structured hiring processes were looking for. I had to adapt. I had to learn new vocabulary. I had to rebuild how I talked about my own work.

And more recently, like everyone else in any knowledge work field, I have had to reckon with what artificial intelligence means for the role itself. The tools change. The questions change. What does not change is the need to know how to communicate your value in the language your audience is using right now.

The Problem With Most Preparation

Most people prepare for interviews the same way they cram for a test. They read some common questions, think through a few answers, maybe do a mock session or two, and call it done. The problem is that this approach treats the interview as an event to survive rather than a performance to deliver.

In a series of surveys, Eurich found that 95% of people think they're self-aware, but only 10-15% truly are.

This gap matters enormously in interviews. Most candidates believe they are giving clear, compelling answers. Many are not. Without structured feedback and deliberate practice, there is no way to close that gap. You cannot self-correct what you cannot see.

The research on learning tells us that spaced repetition, retrieval practice, and active recall are significantly more effective than passive re-reading or simple rehearsal. Yet the vast majority of interview prep involves exactly that: re-reading a resume, skimming common questions, and hoping the answers will come when the moment arrives.

What Structured Preparation Actually Does

When you build a story library, you are not just preparing answers. You are cataloguing your own experience in a way that makes it retrievable under pressure. Stories you have written out, structured, refined, and practiced multiple times become available to you in a way that vague memories of what happened at work never will be.

The same principle applies to knowledge. Cards, spaced repetition, and retrieval practice create durable understanding rather than temporary familiarity. You do not just remember what an agile retrospective is. You can explain it clearly, connect it to your experience, and discuss it with the fluency that signals genuine expertise.

Building a Real Preparation System

• Separate building from practicing. Write your stories completely before you try to rehearse them. Preparation and practice are different activities that require different kinds of focus.
• Use spaced repetition for knowledge areas. Study your knowledge cards repeatedly over days, not in one long session the night before.
• Practice retrieving, not just reviewing. Close your notes and try to answer questions from memory. The difficulty of retrieval is what makes the learning stick.
• Get honest feedback early. The hardest feedback to hear is usually the most valuable. Find someone who will not soften the critique.
• Update your preparation as you learn more about the specific process. Preparation should be a living document, not something you complete once and file away.

The difference between preparation and practice is the difference between building something and running in circles. InterviewBump was designed to help you build.