Tips for interview preparation that start with the job description
The most useful tips for interview preparation begin with the job ad, because it tells you what they will ask. Here is a 12-step, 48-hour plan, a requirement-to-question map, a worked STAR answer, and what to do on the day and after.
By the JobTailor teamUpdated
On this page11 sections
How to prepare for an interview: start from the job ad
To prepare for an interview, work backwards from the job description. List what the role needs, turn each need into the question it will probably trigger, and prepare one true story that answers it. Then research the company, rehearse out loud, and sort logistics the night before. Most people spend their time on generic question lists instead.
Generic lists still help with the standard openers, such as why this company or what is your biggest weakness. But the questions that decide an offer come from the posting: its responsibilities, its tools, its problems. A hiring manager has usually read that ad more recently than you have, so start there.
This page is the full plan around the interview. If you only want help generating questions from a posting, our guide on interview questions from a job description goes deeper on that single step. What follows covers everything before, during and after.
Interview preparation for a job: the 12-step, 48-hour plan
Short on time? Steps 1 to 4 and 7 matter most. With a week to spare, spread the same steps out and add a mock interview.
- 148 hours out: read the job ad three times
Once for the overall picture, once underlining every responsibility verb, once circling hard requirements. Note anything repeated, because repetition shows what the team cares about most.
- 248 hours out: turn every requirement into a question
For each responsibility and requirement, write the question it would trigger and what you must prove. The table below shows how. Aim for 8 to 10 questions.
- 348 hours out: build a bank of five stories
Pick five real projects or moments: a win, a conflict, a failure you learned from, a deadline, a time you led or taught. One good story can answer several questions.
- 436 hours out: write each story in STAR form
Four lines per story in note form, not paragraphs. Include one concrete result for each, a number if you have one, or a before and after if you do not.
- 536 hours out: research the company in 30 minutes
Use the checklist below. The goal is not trivia. It is one sentence connecting your experience to a problem they currently have.
- 636 hours out: look up your interviewers
Find their roles and backgrounds on LinkedIn or the company site. Note one point of common ground, and what each person is likely to care about given their job.
- 724 hours out: script your 90-second introduction
Tell me about yourself is almost always first. Use three beats: what you do now, one or two relevant things from before, and why this role is the logical next step.
- 824 hours out: prepare the awkward questions
Employment gaps, why you are leaving, a weakness, salary expectations. Write a calm, honest, two-sentence answer for each. Research the pay range for the role so your number is grounded.
- 924 hours out: choose your questions for them
Pick five and rank them, since some will be answered during the conversation. At least one should come from a specific line of the job description.
- 1024 hours out: rehearse out loud, twice
Silent reading hides rambling. Answer each question aloud, ideally to a friend or a recording. Aim for 60 to 90 seconds per behavioral answer.
- 11The night before: sort logistics, then stop
Confirm the time, time zone, address or video link, and who you are meeting. Lay out clothes, a printed resume and a pen. Stop studying and sleep.
- 12Within 24 hours after: send a short thank-you
Three or four sentences, naming one specific thing you discussed. Details are in the follow-up section further down.
Interview preparation questions: map the job ad to what you will be asked
Examples from a mix of roles. Do the same with every line of the posting you are preparing for.
| Job ad line | Likely question | What to prove |
|---|---|---|
| Manage a portfolio of 20+ client accounts | How do you prioritize when three clients need you at the same time? | A repeatable method, shown with one real example and its outcome. |
| Build and maintain dashboards in Tableau | Walk me through a dashboard you built. Who used it, and what changed because of it? | Tool fluency plus business impact, not just chart-making. |
| Collaborate with engineering and design | Tell me about a disagreement with an engineer. How did it end? | You can disagree and keep the relationship intact. |
| Experience with HIPAA-regulated data | What does handling protected data look like in your day-to-day work? | Specific habits and controls, not just awareness of the rules. |
| Reduce customer churn | If churn rose two points next quarter, what would you check first? | A structured way to break a metric into causes. |
| Thrive in a fast-paced environment | Tell me about a week when your priorities changed twice. | Calm re-planning, plus what you dropped and why. |
The STAR method, with one worked example
STAR stands for Situation, Task, Action and Result. It keeps behavioral answers short and finishes them with an outcome. Spend about a fifth of your time on the situation and task, most of it on what you personally did, and the last fifth on the result. Say I, not we, when describing your own actions.
Keep each answer to about 60 to 90 seconds, which is shorter than it feels when you are nervous. If you have no hard number for the result, a before and after works just as well: how long a task took, how many errors you saw, or what decision changed. Below is a worked example for the question Tell me about a time you improved a process.
STAR example: improving a process
A condensed version, invented for illustration. Replace every detail with your own. With natural detail added, it runs about 90 seconds spoken.
| Part | What you say |
|---|---|
| Situation | I led a support team at a 40-person software company. New hires took about six weeks before they could handle tickets alone. |
| Task | I was asked to shorten onboarding without lowering our quality scores. |
| Action | I reviewed 50 recent escalated tickets, found five repeat issue types, wrote a one-page guide for each, and gave every new hire a buddy. |
| Result | The next two cohorts worked alone in about four weeks, with quality scores matching the team average. The guides are still in the team wiki. |
Company research checklist (30 minutes)
Enough to sound informed without turning it into a project.
- Product: what they sell, who buys it, and how it makes money. Try it or watch a demo if you can.
- Recent news: the last three months of press, launches, funding or leadership changes.
- Competitors: two names, and one line on how this company differs.
- The role: team size, who it reports to, and whether it is a new role or a backfill. The ad often hints.
- Values: read the careers page and pick one or two values you can back with a real story.
- Employee reviews: one-sided by nature, so use them to shape your questions, not as facts.
Questions to ask the interviewer
Having none signals low interest. Asking thoughtful ones is part of the interview.
- The work: What would the first 90 days look like in this role?
- Success: How will you measure whether I am doing well at six and twelve months?
- Challenges: What is the hardest part of this job that the ad does not mention?
- The team: How does the team decide priorities when everything is urgent?
- Next steps: What does the rest of the process look like, and when should I expect to hear back?
- Don't: ask anything the careers page already answers, or open with vacation and benefits in a first conversation.
The day itself: in person, phone and video interviews
The basics catch more people out than the hard questions do.
- In person: arrive about ten minutes early and be polite to everyone you meet. Bring a printed resume and your questions.
- Video: test the link, camera and microphone the day before. Use Zoom, Teams or Google Meet exactly as the invite specifies.
- Video setup: camera at eye level, light in front of you, a plain background, notifications off, headphones on.
- Notes: keep a one-page list of your five stories beside the screen. Glance at it. Do not read from it.
- Phone: take the call somewhere quiet, standing up if it helps your voice, with water within reach.
- If it goes wrong: if the connection drops, rejoin quickly and say so calmly. If you blank, ask for a moment to think.
After the interview: the thank-you note and follow-up
Send a thank-you within 24 hours, to each interviewer if you have their addresses, or through the recruiter if you do not. Keep it to three or four sentences: thanks for their time, one specific thing you discussed, and one line on why the role still appeals. A note rarely decides an outcome, but it is cheap and it is another chance to restate your fit.
Write down every question you were asked while it is fresh, and what you would answer differently. If the date they gave you for a decision passes, wait one business day and send a brief, polite check-in. Then stop. Chasing more than that rarely helps.
JobTailor's job tracker keeps your stage, notes and contacts in one place, and it is free on every plan. Its interview prep pulls likely questions from the posting, each with a tip and a sample answer, which is a useful first draft. Rewrite every answer around your own experience.
Frequently asked
How early should I start preparing for an interview?
Ideally two to three days before, which lets you write and rehearse your stories without cramming. If the interview is tomorrow, the highest-value work is reading the job ad, mapping it to likely questions, writing three or four STAR stories and rehearsing your introduction aloud. That takes about three to four focused hours.
What are the most common interview preparation questions?
Tell me about yourself, why this role, why this company, a strength and a weakness, a time you handled conflict, a time you failed, why you are leaving, and do you have questions for us. Prepare these first, then add the role-specific questions you map from the job description.
How many stories do I need to prepare?
Five or six real stories cover most behavioral questions, since each can be reframed. A project you led can answer questions about ownership, deadlines, conflict and results. Choose stories with a clear outcome, and make sure at least one shows a mistake and what you changed afterwards.
How do I answer "Tell me about yourself"?
Keep it to 60 to 90 seconds and use three beats: what you do now, one or two relevant things from earlier in your career, and why this role is the next step. Tailor it to the job description. It is a professional pitch, not a life story.
How do I prepare for a video interview?
Test your link, camera and microphone the day before, sit with light in front of you and the camera at eye level, silence notifications, and keep a one-page list of your stories beside the screen. Look at the camera when making key points. Have a backup plan, such as a phone hotspot, in case your connection fails.
Can AI help with interview preparation?
Yes, mainly for generating likely questions from a posting, outlining STAR answers and running practice questions. Treat any sample answer as a draft. Build the final answer from your real experience, and never claim a story that is not yours, because interviewers ask follow-up questions. JobTailor's interview prep lists likely questions from the posting, each with a tip and a sample answer.
When should I send a thank-you note?
Within 24 hours of the interview, ideally the same evening. Keep it to three or four sentences, mention one specific topic from the conversation, and restate your interest. If you do not have each interviewer's email address, send one note to the recruiter and ask them to pass it on.
Get the likely questions from the job ad
Paste a posting and JobTailor lists the questions to expect, each with a tip and a sample answer you can rewrite with your own experience. Free plan, no credit card.