Interview preparation does two jobs: it puts your story in your hands and takes the surprises out of the room. Do it as a pack you write before the day: your research, a career story under three minutes, three to five proof stories, honest answers to the hard questions, and what you will ask at the end.
By the time you are invited to interview, the people in the room already believe you can broadly do the job. What the interview decides is whether they trust you with it, and that hour is where your next pay packet, and the security that comes with it, is won or lost. Most of it is settled before you walk in.
How do you prepare for an interview?
You do two jobs in advance. You control the narrative, so the interviewer leaves with the story you meant to tell. And you remove surprises, so the question that would have rattled you has already been thought through, calmly, days before anyone asks it.
Do both in a prep pack: a few pages you write beforehand and reread on the day. It holds five things:
- notes on the company, the role and the people you are meeting;
- your career story, under three minutes;
- three to five proof stories, each a real result;
- honest answers to the questions you would rather not be asked;
- the questions you will ask at the end, and how you will close.
Writing it down is what lets you check it, trim it and say it out loud.
How long should you prepare for an interview?
Plan on three short sittings over the days before, not one long night: one to research, one to write your stories into the pack, and the rest to say them out loud. The night before is for reading the pack, not writing it.
The stage changes the load. A screening call with a recruiter mostly checks that you are a credible fit and a safe hire, so have your reason for moving, your notice period and your salary expectations ready. For a later round, reread what you said last time, so you build on it rather than repeat it.
What should you research before an interview?
Three things: the company, the role and the people you are meeting.
The company. What it is trying to do now, in its own words: its website, its news and, if it is listed, its latest results. Look for what has changed, such as a new leader, an acquisition or a restructure. Change is often why a role opens.
The role. Why it exists now: is it new, a replacement, or growth? Read the job description for the problem behind it, and pick the three or four requirements that carry the most weight. Those decide which stories you tell.
The people. Find out who you are meeting, and what each of them is judging. A recruiter checks fit and risk, a hiring manager whether you will solve their problem, and a future peer whether they would want to work beside you. Look each one up on LinkedIn for their background and anything you share, then turn one thing you found into a question you will ask.
Which interview questions should you prepare for?
Three kinds: the opener, the predictable hard ones, and the ones that ask for a story.
The opener is “tell me about yourself”, and it wants a career story in under three minutes, not your resume read aloud. Your career story in under three minutes walks through its four parts, with a before and after.
The hard ones are why you are leaving, a time you failed, a gap or a short stay, and where you want to be in a few years. Each needs an honest answer worked out in advance, so it comes out steady, not defensive. The interview questions almost everyone gets takes them one at a time.
The rest will mostly be behavioural questions that begin “tell me about a time”. You cannot predict the wording, but you can predict the stories. Prepare three to five that cover the requirements you picked out; one good story can answer several questions.
Build each story from four things: one real situation, what you did, a number that shows the result, and why it worked. Say “I” for the parts that were yours. The team delivered, but the interviewer is hiring one person.
Before: We had a lot of onboarding complaints, so we worked on the process and things got much better.
After: New customers were waiting three weeks to go live, and it was the biggest source of complaints to support. I mapped every step, found two of them waiting on the same sign-off, and moved it to the start. Within a quarter, go-live was down to eight days. It worked because the delay was never the work; it was the queue in front of it.
No measured result? Give the nearest honest one, such as a count, a time or a before and after, and never round it up. A small number survives a follow-up question. An inflated one does not.
How do you practise interview answers out loud?
Say each answer out loud, timed, and to a person if you can: a friend, a former colleague, or a mentor or coach if you work with one. An answer that reads well on paper can still sound wrong out loud.
Then check it against the same four things. Was there one real situation? Did you say what you did, or what “we” did? Is there a number that shows the result, and did you say why it worked?
The fourth is the easiest to leave out, because it feels obvious to you. It is also what tells the interviewer you could do it again. Don’t script every word: know the facts of each story cold, and let the wording come fresh.
FutureDay’s Interview Prep uses the same four checks. Pick a role from your Job Tracker once it reaches Screening or Interviewing, and it builds the pack from your resume: likely questions by area, each with a model answer, and questions to ask back. In practice mode you type or dictate each answer, and it tells you which of the four your answer has and what to add, rather than giving it a mark. The rehearsing is still yours.
What questions should you ask at the end of an interview?
One or two questions that show you are already thinking like the person in the role, built from your research. Not “what’s the culture like?” but closer to “what would make the first six months a clear win in your eyes?” Then ask what happens next, say plainly that you want the role, and thank them.
Plan those last two minutes, because the end carries more weight than the middle. People judge an experience mostly by its most intense moment and by how it ended, not by the average, a pattern the psychologist Daniel Kahneman called the peak-end rule.
Follow up the same day with a short note that thanks them and restates the fit in two lines.
Where FutureDay fits
FutureDay's Interview Prep builds this pack from a tracked application in a minute or two: interviewer focus, tailored questions with model answers, red flags, closing strategy and questions to ask back. Practice mode turns it into rehearsal, checking your spoken or typed answers for the four things interviewers listen for.
Preparation does two jobs: it controls the narrative and removes surprises.
Build a pack: research, your career story, proof stories, the hard questions and your close.
Every story needs one real situation, what you did, a number that shows the result, and why it worked.
Practise out loud, to a person if you can, until you know each story cold.
Plan the last two minutes, say you want the role, and follow up the same day.
21 pages, a 15-minute read
