Why your interview answers should come from your own material

There is a fast way to prepare for interviews and a way that works, and the difference shows up at exactly the same moment every time: the follow-up.

The follow-up is the whole test

An interviewer asks about a project. You give a clean, well-structured answer. Then they ask the question that decides the interview:

"What would you do differently?"

Or: Why that approach and not the obvious one? What did the person who disagreed with you say? What broke?

These are unanswerable from a prepared paragraph, because a prepared paragraph contains only the version you rehearsed. They are easy if you were there. The follow-up is not a harder question — it is a check on whether the first answer was yours.

This is why generated answers fail. Not because they read badly; they often read better than what you would have said. They fail because they have no second layer. There is nothing underneath.

What "your own material" actually means

Three things, and the third is the one people skip.

Your resume gives the skeleton — roles, dates, headline outcomes. On its own it is too thin; nobody ever answered a behavioural question from a bullet point.

Your notes are where the substance is. What went wrong in the migration. Who objected and why. The number you remember because you watched it move. Most people have never written these down, which is why they cannot retrieve them under pressure.

The job description decides which of the above matters. The same career produces different answers for different roles, and the filter is the JD.

Write the notes

Twenty minutes with a blank page, listing what you have actually done in the last two or three years. Two lines each, unpolished. Incidents, launches, disagreements, things that failed.

Do this and two things happen. You remember far more than you expected. And when a question arrives in the interview, you are searching a list you wrote rather than an empty room.

Everything downstream depends on this file existing. A tool that draws on your material cannot help you if there is no material — which is why InterviewShadow flags when your profile lacks the detail for a question rather than inventing something to fill the space.

Grounded beats fluent

Two answers to "tell me about a time you led a challenging project":

"In my previous role I spearheaded a cross-functional initiative that drove significant impact across the organisation."

"I led four people across design and support. The hard part was the timeline and getting the two teams to agree. The new workflow cut onboarding time by about thirty percent."

The first is smoother. The second is the one that gets a job, because it survives "what did design disagree about?" and the first does not.

Fluency is not the scarce resource in interviews. Specificity is.

The honest limitation

Preparing from your own material will not make you a stronger candidate than you are. If the experience is not there, no amount of framing puts it there, and an interviewer who probes twice will find the edge.

What it does is stop you being a weaker candidate than you are — which, for most people who leave an interview thinking "I know more than that", is the actual problem.

---

That is the whole design principle here: cues drawn only from your resume, your notes and the role, never invented. See what that looks like.