Many interview guides treat preparation as performance: memorize the right answers, control every gesture, wear the approved clothes, avoid the wrong questions. I have accumulated and used versions of that advice in career-development work, and returning to older materials makes its limitations especially visible.
The more useful model is simpler: interview preparation is an evidence problem.
An employer is trying to reduce uncertainty. Can this person do the work? Can they learn what they do not know? How do they make decisions? How do they work with other people? Why are they interested in this particular role?
A candidate is trying to reduce uncertainty, too: What is the work actually like? What would success require? How does the team operate? Do the conditions of the job make sense for me?
That changes how I would tell someone to prepare.
Start with the job, not a list of questions
Before rehearsing “Tell me about yourself,” identify what the employer appears to need most. A posting usually contains far more language than can matter equally. Pull out the responsibilities and qualifications that recur, occupy the most space, or seem central to the purpose of the role.
Then map evidence to them.
If the role requires project management, “I’m organized” is weak evidence. A better preparation question is: Which project best demonstrates how I established a plan, coordinated stakeholders, handled dependencies, responded to a problem, and delivered an outcome?
The interview question may never contain the words “project management.” The evidence remains useful.
Build stories, not scripts
This is why I prefer a story bank to a bank of memorized answers. Six or eight well-understood examples can often support dozens of questions.
A useful story contains enough context to make the problem intelligible, a clear account of what you were responsible for, specific actions you took, and a result. I also add reflection: what did the experience teach you, and what changed afterward?
The point is not to force every answer into a formula. The structure is a diagnostic. If I cannot identify what I actually did, the story may give too much credit to the team. If I cannot identify a result, I may need a different example—or I may need to explain that the meaningful result was qualitative. If the context takes three minutes to explain, I probably have not decided what the interviewer needs to know.
Research should produce better questions
Research is not a trivia contest. Knowing the year an organization was founded is rarely useful unless it affects the work under discussion.
Useful research changes the conversation. It may reveal a new initiative connected to the role, a shift in organizational priorities, a product or program the candidate would support, or something in an interviewer’s background that helps explain their perspective.
The strongest interview questions often emerge from that research. They are specific enough that the answer teaches the candidate something they could not learn from the posting alone.
Professionalism should help people communicate, not police them
Some older interview guidance turns “professionalism” into an elaborate behavioral code: prescribed clothing, handshakes, eye contact, posture, gestures, makeup, jewelry, hair, note-taking, and rules about which employment conditions a candidate is permitted to ask about.
That is not the part worth preserving.
Preparation should reduce avoidable distractions and help someone communicate clearly. Test the technology. Know where you are going. Wear something appropriate that allows you to focus on the conversation. Listen. Give specific answers. Ask for clarification when necessary. Take brief notes if they help. Request an accommodation if you need one.
There is no benefit in teaching candidates that successful interviewing requires performing a narrow physical or cultural stereotype.
The candidate is also collecting evidence
This is the part of interview preparation that deserves more attention. A candidate should leave with better information than they arrived with.
What problem is the new hire expected to solve? What would success look like after six months? How are priorities set? What resources are available? Why is the role open? How do people on the team disagree and make decisions? What remains unclear about compensation, schedule, advancement, management, or working conditions?
An interview is therefore not merely a performance followed by a verdict. It is a structured exchange of evidence under conditions of incomplete information.
Once I frame it that way, the preparation process becomes much more useful: identify the important questions, assemble the strongest evidence available, investigate what remains uncertain, and leave with enough information for both sides to make a better decision.
Use the companion tools
I developed two reusable resources from the same method: the Modern Interview Preparation Checklist and the Interview Story Bank & Answer Planner. Together they turn the argument above into a practical preparation workflow.
Resource note
This post accompanies the Modern Interview Preparation Checklist and Interview Story Bank & Answer Planner, newly developed from methods and archived career-development materials in my files. The newer resources preserve useful preparation practices while deliberately revising advice that is dated, overly rigid, or based on narrow conventions of professional behavior.