How to Prepare for a Job Interview: A Practical Plan

To prepare for a job interview, work from the job posting and your own resume, not from a list of generic questions. Study what the role asks for, pick five to seven true stories from your career that prove you can do it, practice saying them out loud, and sort out the logistics early. This guide gives you that plan in the order to do it, plus a checklist for the final 24 hours.

Workhunt

workhunt.ai

Prepare for the Interview Ahead

WorkHunt offers tailored interview preparation, including coding practice relevant to the job posting and mock interviews with performance metrics.

Explore interview preparation

TL;DR

Start with the posting: list the top five requirements and match each to a real example from your work.
Build a bank of five to seven stories and shape each one with the STAR method (Situation, Task, Action, Result).
Be ready to walk through every line of your resume, including transitions, gaps and exits.
Practice out loud, ideally with a person, and use mock interviews to find weak spots before the real one.
Prepare two or three questions of your own, plus logistics, the day before.

Start with the job posting, not a question list
Know your resume better than the interviewer does
Build a story bank
Shape every answer with STAR
Prepare for the different kinds of interview
Practice out loud, and get feedback from people too
What to research about the company
Our perspective
Where WorkHunt fits in your preparation
The day-before checklist
During and after the interview
FAQ
Sources

Start with the job posting, not a question list

Most advice starts with "practice common questions." That works, but only after you know what this employer cares about. The posting is the closest thing you have to the interviewer's answer key.

The U.S. Department of Labor advises candidates to research the position and organization and to re-read the announcement's duties, requirements and evaluation methods before the interview. It also suggests reviewing the competencies listed in the posting, because they often point to the questions you will get.

Try this in 20 minutes:

Paste the posting into a document and highlight every verb and every tool or skill that appears more than once.
Pick the five requirements that look most important. Usually these are in the first third of the posting or in the job title.
Next to each, write one real example from your work: what you did, with what result.
Mark the gaps. If the posting asks for something you have not done, decide now how you will address it honestly: adjacent experience, fast learning, a relevant project.

That last step matters most. Interviewers probe the soft spots, so you want your answer ready before they ask.

If you want a deeper walkthrough of this method, our guide on interview prep from a job description shows how to predict questions from the posting's own wording.

Know your resume better than the interviewer does

The interview usually starts from the document you sent. A hiring manager will pick a line and ask you to expand on it. Practitioner accounts of Harvard Business School interviews describe a session that is mostly resume-based, with candidates expected to explain key transitions and why they took each job. That is an elite example, but the principle applies to an ordinary hiring screen too.

For every role on your resume, be able to answer:

Why did you take this job?
What was the hardest part, and what did you do about it?
What result are you proudest of, and how do you know it was a result?
Why did you leave, in one calm, neutral sentence?
What would you do differently?

The Senate employment office's interview guide makes a similar point: review your application so you can prepare real examples that support what the position requires.

If your resume has a gap or a pivot, rehearse the explanation now. We cover honest wording in how to explain a career gap, and the same logic applies to a career change resume.

One more check: the version of your resume the interviewer holds should match the job. If you applied with a generic version, you may be asked about things you would rather not lead with. Tailoring the resume to the posting before you apply keeps the conversation on your strongest material. Our guide to tailoring your resume for every job explains how, and matching keywords honestly keeps you from claiming what you cannot back up.

Build a story bank

Behavioral questions ("Tell me about a time when...") are the core of most interviews. You cannot predict the exact wording, but you can predict the themes: conflict, failure, leadership, tight deadlines, ambiguity, influencing without authority, a mistake you owned.

The efficient approach is a story bank: five to seven real episodes from your career that you can adapt to different questions. For each one, write down:

Context: what was at stake.
Your role: what you personally did. Say "I," not "we."
The complication: what went wrong or was hard.
The outcome: quantified where you can, such as revenue, time saved, error rate or team size.
The lesson: what you learned or would do differently.

That last element is the one candidates forget. Guidance from an MBA admissions prep firm notes that the self-awareness piece is often what interviewers listen for most. That advice is written for MBA applicants, yet a story with no reflection sounds like a résumé bullet read aloud in any field.

A good bank covers range. Do not use five stories from the same project. Aim for a mix: one win, one failure, one conflict, one piece of leadership or initiative, one story about learning something fast, and one about working across teams.

Shape every answer with STAR

STAR stands for Situation, Task, Action, Result. It stops rambling answers, which is the most common way strong candidates lose ground. A community college training deck describes STAR as a way to strategize answers to behavioral questions with forethought.

The proportions matter as much as the letters. Guidance in the Senate's applicant preparation document, as summarized in our research, splits response time roughly like this:

STAR part	Share of your answer	What to do
Situation	About 20%	Set the scene in two sentences.
Task	About 10%	State your responsibility or goal.
Action	About 50%	Explain what you did, using "I."
Result	About 20%	Give the outcome, with numbers if possible.

If you notice yourself spending half the answer on background, cut it. Interviewers want your decisions and your behavior.

A worked example

Question: "Tell me about a time you had to deal with a difficult stakeholder."

Situation: "Our largest internal client kept changing requirements two days before each release."
Task: "I was the project lead and needed to stabilize the schedule without losing the relationship."
Action: "I set up a short weekly review, wrote down what was in and out of each release, and showed the cost of late changes in days. When a change came in late, I offered a choice: move the date or move the scope."
Result: "Late changes dropped over the next two quarters, and we shipped the next three releases on the planned date. I now bring that trade-off conversation up at kickoff."

That example is illustrative, not a script. Use your own facts, and only claim numbers you can defend if the interviewer asks a follow-up.

Prepare for the different kinds of interview

The format changes the preparation. Find out early, ideally from the recruiter, what you are walking into. The Department of Labor also suggests asking whether there will be one interviewer or several, and requesting accommodations as early as possible if you need them.

Phone or recruiter screen

Expect a short conversation about your background, salary expectations, location and timing. Have a 30 to 60 second summary of your experience ready; the Department of Labor recommends being able to summarize your experience in about that time and say what you bring to the role. Know your salary range before the call, based on public data for the role and location, so the question does not catch you cold.

Behavioral or hiring manager interview

This is where the story bank pays off. Expect follow-up questions that test how real your stories are: "What was your exact contribution?" "What would you do differently?" Short, specific answers beat polished ones.

Technical or coding interview

If you are interviewing for engineering roles, preparation has to include writing code under observation, not only reading solutions. Research from a 2025 study on mock technical interviews points out that preparation for these assessments is often done in isolation, and that candidates found AI-generated code feedback useful, though they trusted human feedback more. A 2024 paper on whiteboard problem solving notes that vocalizing your thought process is one of the things evaluators look at.

In practice:

Practice talking while you code. Silence is hard for interviewers to score.
Do timed problems that resemble the job's stack, not random puzzles.
Spend as much practice time on implementation as on planning. A 2026 study of software engineers and AI coding assistants found that evaluators weigh implementation and planning differently, and that explaining your approach and then correctly implementing it remains the strongest demonstration of skill.
Review the fundamentals the posting names: languages, frameworks, system design if the level calls for it.

Panel or final-round interview

Treat each panelist as a separate audience. Look at the person who asked the question, then include the others. Learn each person's role beforehand, and prepare one question tailored to each.

Video interview

Test your camera, microphone, lighting and internet connection the day before. Close other apps, silence notifications and place the camera at eye level. Keep a short list of your key stories on a sticky note outside the frame, as prompts rather than a script.

Practice out loud, and get feedback from people too

Reading your answers silently feels fine and fails in the room. Saying them aloud exposes where you ramble, hedge or go blank.

Practice out loud, and get feedback from people too — overview diagram

The mock technical interview study in our research suggests that mock interviews, even with AI feedback, can reveal deficiencies and improve comfort, while candidates tend to find human feedback more trustworthy. Our reading is that both have a place. Use automated mock interviews for volume, since you can run one at 11 p.m. with no scheduling, and ask a friend, mentor or former colleague for a real-person run-through before an important round.

A practical practice schedule for one week before the interview:

Day 7 to 6: Posting analysis, resume walk-through, first draft of your story bank.
Day 5 to 4: Say each story out loud with a timer. Aim for about two minutes each.
Day 3: Full mock interview, recorded if possible. Note filler words, long openings, and any question that made you freeze.
Day 2: Fix those weak spots. Research the company and your interviewers again.
Day 1: Light review only, logistics, and sleep.

Performance anxiety is normal and not a sign you are unqualified. The research linked above treats it as a constant factor across skill levels. Repetition is the practical remedy, because familiar material is easier to retrieve when your pulse is up.

What to research about the company

Skim the homepage and you will learn little. Go for specifics you can use in conversation:

The company's current products, customers and recent news, such as a launch, funding, a leadership change or a layoff.
The team you would join: who leads it, what they have published or presented.
The problems the posting implies. A posting that mentions "scaling," "migration" or "new market" tells you what the first year looks like.
Competitors and how this company differs, so you can speak about the market intelligently.

The Ivy Coach guide to Harvard interviews recommends having two or three researched, genuine questions that show curiosity about the institution's culture and resources. Job candidates can borrow the idea: questions that could only be asked of this employer show real interest.

Good questions to adapt:

"What would success look like in the first 90 days?"
"What is the hardest part of this role that is not in the posting?"
"How does the team handle disagreement about priorities?"
"What are the next steps and timeline?"

Avoid asking about anything answered on the careers page. Hold pay and benefits questions for when the employer raises them or an offer is near, unless a recruiter invites them earlier.

Our perspective

At WorkHunt, we see interview preparation as a continuation of the job application, not a separate task. The same posting that should shape your resume should shape your preparation, and the same facts should appear in both. If your resume claims a skill, you should be ready to tell a story that proves it.

That is why we build around the posting. You paste a job link, see edits to your resume beside the original, and approve or revert each change, so nothing in the document is something you cannot defend. From the same posting we generate interview prep, including coding practice and mock interviews with performance metrics. We think it is a mistake to prepare from a pile of generic questions when the employer has already told you what it values.

We also want to be honest about limits. Automated practice is good for repetition and for finding gaps. It does not replace a thoughtful friend who knows your work, and we encourage you to do at least one run with a person before a final round. Your data is also yours: we keep it private and do not use it to train AI.

— CoffeeDrop

Where WorkHunt fits in your preparation

If you are juggling several applications, the hardest part is keeping each one's resume, prep and status straight. WorkHunt lets you tailor your resume to each posting, practice with questions based on that job description, run voice or text mock interviews, and track every application from submission to offer. There is a free plan with limited features, and Pro starts from $15 per month and unlocks the full set, including interview prep, coding practice and application tracking. See the plans on our site to compare.

The day-before checklist

Print it or copy it into your notes.

Content

Top five requirements matched to examples
Five to seven stories, each in STAR shape, each practiced aloud
Your 30 to 60 second introduction
A calm, short explanation of any gap, move or exit
Two or three questions for the interviewer, tailored to the company
A salary range you can support with data

Logistics

Time, place or link, and a named contact
Number and names of interviewers
Route and arrival buffer, since the Department of Labor advises planning to arrive early and allowing for building security
Outfit that fits well and is ready
A folder with a few printed resumes, a pen, a notepad and your logistics page
For video: camera, mic, lighting, charger and a quiet room tested

Mindset

A plan for the first 60 seconds, since a first impression forms fast
One sentence that sums up why you want this particular job
Sleep and a meal planned

During and after the interview

Listen to the whole question before answering. If it is unclear, ask the interviewer to restate it; the Department of Labor lists that as acceptable. Answer directly, then stop. Candidates often lose ground by talking too long and drifting from their narrative, a pattern the Senate guide also describes in its advice to stay conversational and reflective.

Stay positive about past employers. Describe what you learned, not who was at fault.

At the end, ask your questions, confirm the next steps and timeline, and thank each interviewer. Send a short thank-you note within a day that mentions one specific thing you discussed. Then write down the questions you were asked while they are fresh, and add any good new stories to your bank. That log makes the next interview easier, and a tracker that keeps your notes next to each application makes it easier still.

For more guides like this, browse our interview prep articles.

FAQ

How early should I start preparing for an interview?

Start as soon as you get the invitation, and aim for about a week if you can. That is enough time to analyze the posting, build your stories, and do a few timed rehearsals. If you have only a day, focus on the posting, your top three stories and your questions for the interviewer.

What is the STAR method?

STAR stands for Situation, Task, Action, Result. You use it to answer behavioral questions in a clear sequence. Senate guidance suggests spending about half your time on the action you took, with the rest split between context and the result.

What should I bring to a job interview?

Bring a few printed copies of your resume, a pen, a notepad and a page with the logistics. The Department of Labor suggests keeping them in a clean, neutral-colored folder. For a video interview, bring nothing but a tested setup and a short list of prompts out of frame.

Is practicing with AI mock interviews worth it?

Yes, for repetition and for spotting weak answers. Research on mock technical interviews found that they reveal deficiencies and improve comfort, though candidates trusted human feedback more. Use both: AI for volume and a person for a final check.