How do I prepare for a job interview?
Preparing examples rather than answers, researching what matters, and the practical logistics that go wrong.
- Difficulty
- beginner
- Time
- 2 hr
- Read
- 2 min
Short answer
Prepare six or seven concrete examples from your experience rather than scripted answers — most questions can be answered from a good example. Then check the logistics, because those are what actually go wrong on the day.
Interviews mostly test whether you can give specific evidence for general claims. Preparing examples rather than answers means you can respond to questions you did not anticipate, which is most of them.
What you'll need
- The job description
- Your CV (optional)
- Paper for notes (optional)
Step by step
- Read the job description and list what they are actually looking for.The requirements are the question bank. Almost every question maps to one of them, so preparing against that list covers most of the interview.
- Prepare six or seven concrete examples.Situations you handled, with what you did and what resulted. A good example can answer many different questions, which is why examples beat scripted answers.
- Structure each example clearly.The situation, what you did specifically, and the outcome. Keep the situation short and spend most of the time on your own actions.
- Research the organisation properly.What they do, recent news, who you are meeting. Not to recite it, but so your answers connect to their actual situation.
- Prepare questions to ask.Two or three genuine ones about the role, the team or how success is measured. Having none reads as lack of interest.
- Prepare for the difficult questions.Gaps, a departure, a weakness, why you are leaving. Have a brief, honest, unapologetic answer ready rather than improvising under pressure.
- Check the logistics the day before.Location and travel time, or the video link and your camera and microphone. Technical problems and lateness are what actually go wrong.
- Practise out loud.Saying an example aloud is completely different from thinking it. Two or three run-throughs makes an obvious difference to fluency.
Tips
- Take notes into the interview. Nobody minds, and it prevents the blank moment where a prepared example disappears.
- It is entirely acceptable to pause before answering. A considered answer after three seconds is better than an immediate rambling one.
- If you do not know something, say so and say what you would do to find out. It is a better answer than a bluff, which is usually obvious.
Common mistakes
- Scripting answers to predicted questions — The questions will be different and scripted answers sound rehearsed. Prepared examples adapt to whatever is asked.
- Giving general claims without evidence — 'I'm a good communicator' is unverifiable. A specific example of communicating something difficult is what the question is actually asking for.
- Having no questions to ask — It reads as a lack of interest or preparation, and it wastes the one part of the interview you control entirely.
Questions people ask
How should I structure an interview answer?
Briefly set the situation, spend most of the time on what you specifically did, and finish with the outcome. Keep the context short — they want to hear about your actions.
What should I ask at the end of an interview?
Two or three genuine questions about the role, the team, or how success would be measured in the first six months. Avoid questions answered on their website.