How to Prepare for a Job Interview: 10 Essential Steps

1. How to prepare for a job interview

Good job interview preparation is not about predicting every question. It is about arriving with a clear understanding of the employer, a short set of examples you can adapt to whatever is asked, and no unresolved practical details. Interviewers are generally trying to answer three questions: can you do the work, will you fit how the team operates, and do you actually want this job. Everything below is designed to give them evidence for those three questions.

Work through these ten steps in order. Early steps produce the raw material the later ones use, so skipping ahead usually means redoing work.

1. 1. Research the company. Understand what it sells, who it serves, and where this role sits.
2. 2. Understand the role and job description. Separate must-haves from nice-to-haves.
3. 3. Match your experience to what they need. Line up each requirement against evidence from your work.
4. 4. Prepare specific accomplishment examples. Three to five, each with a situation, an action, and a result.
5. 5. Practice common interview questions. Out loud, using talking points rather than a script.
6. 6. Prepare questions for the interviewer. Six to eight, so you still have some left after they answer a few unprompted.
7. 7. Research the market salary. Know the wage range for the occupation in your state.
8. 8. Prepare for salary-expectation questions. Decide your target and range before you are asked.
9. 9. Prepare logistics, attire, and technology. Route, timing, materials, camera and microphone.
10. 10. Do a final review. Skim your notes the day before and again shortly beforehand.

Preparation improves how clearly you present your experience and how well you judge the role. It cannot guarantee an offer — hiring depends on the other candidates, budget, internal politics, and factors nobody outside the room can see. What it does reliably change is that you leave the interview having said the things you meant to say.

2. Research the company

Useful company research is narrow and purposeful. You are not writing a report on the organization's history; you are gathering enough context to explain why this company, why this role, and how your experience could contribute. Thirty to sixty minutes on public sources is usually enough for that.

Start with the company's own website and the job posting itself, then widen out. Look at what the company actually does, its products or services, who its customers are, roughly how large it is, any recent public developments such as a new product, location, or funding announcement, the values and culture it describes publicly, and — where it is available — who leads the team or department you would join. If the employer publishes case studies, a blog, or news releases, those often reveal current priorities more clearly than a mission statement.

Pay particular attention to the business area the role sits in. A customer support role at a company selling to hospitals is a different job from the same title at a consumer app, even when the posting looks similar. Knowing which one you are walking into changes the examples you choose and the questions you ask.

Stick to what you can verify. Repeating an unverified figure or a rumour you found on a forum is worse than saying nothing, because the interviewer usually knows the real number. If you are unsure about something, turn it into a question instead of a claim.

3. Study the job description

The job description is the closest thing to a published answer key. Someone wrote it to describe what the successful candidate looks like, and interviewers frequently build their questions from the same document. Read it three times: once for the overall shape of the job, once with a highlighter on the requirements, and once looking for what is repeated.

Pull out each of these:

• • The core responsibilities — what you would actually do most days.
• • Required skills, stated as necessary.
• • Preferred skills, stated as a bonus.
• • Experience requirements, including years and type.
• • Tools, software, systems, or certifications named specifically.
• • Leadership or mentoring expectations, if any.
• • Measurable responsibilities — targets, volumes, deadlines, budgets.
• • Words and themes that appear more than once.

Repetition is the strongest signal in a posting. If "cross-functional" or "fast-paced" or "documentation" shows up three times, that is where the pain is, and it is likely to appear as a question. Separating must-haves from nice-to-haves also tells you where to spend your preparation: you need a solid answer for every required item, and you can handle a preferred item you lack by explaining the nearest thing you have done and how quickly you picked up something comparable.

Then build a two-column list. On the left, what the employer says it needs, in their words. On the right, evidence from your own experience. Working through it in writing exposes the gaps while you still have time to think about them.

If you are still preparing your application, our cover letter examples show how to connect your experience to the role before the interview.

The right-hand entries above are illustrative. Replace each one with something that genuinely happened in your own work.

Job description says: [Requirement in their words]
My evidence: [Specific project, task, or result that shows it]
Where I'll use it: [The interview question this example answers]

4. Match your experience to the role

A common mistake is trying to cover an entire career. Interviews are short, and a chronological walk through every job you have held leaves no room for the detail that actually persuades. Choose three to five experiences that map most directly onto this role and know them well enough to tell any part of the story on demand.

For each one, be clear on:

• • The situation and context — where, when, and what was happening.
• • What you were responsible for, as distinct from what the team was responsible for.
• • What you specifically did, including the decisions you made.
• • What changed as a result.
• • Which skill from the job description it demonstrates.

The reason a small set works is that most examples answer several questions. A project you rescued after a supplier failed can serve as your difficult-situation answer, your problem-solving answer, your working-under-pressure answer, and part of your greatest accomplishment. Preparing five flexible examples beats preparing twenty single-use ones.

If you are early in your career or changing fields, the same structure applies to coursework, training, volunteer work, military service, or a side project. What matters is that you owned something, made decisions, and can describe the outcome.

5. Prepare examples of your accomplishments

Once you have chosen your examples, give each one a shape so it does not wander. The STAR framework is the simplest reliable structure: Situation, Task, Action, Result. It exists to stop two common failures — starting with so much background that you never reach the point, and stating a result without explaining what you did to produce it.

Do not over-engineer it. You are not reciting labels aloud; you are making sure that within ninety seconds the interviewer knows the context, your role, your actions, and the outcome. Here is one worked example, written out as a candidate might prepare it.

Use measurable evidence where you honestly have it: revenue, cost, time saved, customers served, projects completed, error rates, accuracy, deadlines met, growth, or team results. Numbers make a claim checkable, and interviewers notice.

But not every worthwhile achievement has a dollar amount attached. Plenty of valuable work — calming a distressed patient, training a replacement well, keeping a fragile client relationship alive through a bad quarter — is qualitative, and describing it plainly is better than attaching a percentage you cannot defend. Never invent a figure. A single unsupported number that unravels under a follow-up question does more damage than a story with no numbers at all.

Situation: [Where were you, what was the context, and what was going on?]
Task: [What were you responsible for, and what needed to happen?]
Action: [What did you actually do — the specific decisions and steps you took?]
Result: [What changed? Use a number if you have one, or describe the outcome clearly.]
What this demonstrates: [The skill the employer listed in the job description.]

6. Practice common interview questions

You do not need an answer for a hundred questions. Most interviews draw from a small set of recognizable categories, and your prepared examples will cover several of them at once. Focus your practice on these:

• • Tell me about yourself.
• • Why do you want this job?
• • Why do you want to work here?
• • What are your strengths?
• • Tell me about a challenge or a difficult situation you handled.
• • Tell me about an accomplishment you are proud of.
• • Why are you leaving your current job?
• • Why should we hire you?
• • What are your salary expectations?
• • Where do you see yourself in 5 years?

Prepare talking points, not a script. A memorized paragraph tends to come out flat, and it collapses the moment the question is phrased slightly differently. Three or four bullet points per question give you the same content with room to respond to what was actually asked. The opening question is worth extra attention — our guide to answering “Tell me about yourself” covers the structure and sample answers in detail.

Practice out loud. Answers that read well silently are often twice as long as they should be when spoken. Aim for roughly one to two minutes for a story-based answer and under a minute for a factual one, then stop and let the interviewer follow up — that is a conversation, not a monologue. Recording yourself once, or running through it with someone else, catches filler words and rambling faster than rereading notes.

One discipline matters more than any technique: answer the question that was asked. If they ask about a conflict with a colleague, do not substitute a technical problem because it flatters you more. Interviewers notice deflection, and the answer you substitute rarely scores.

Present: [Your current role, employer type, and the work you own day to day.]
Relevant background: [One or two earlier experiences that led to the skills this job needs.]
Why this role: [What connects your experience to this position and this company.]

Situation: [Where were you, what was the context, and what was going on?]
Task: [What were you responsible for, and what needed to happen?]
Action: [What did you actually do — the specific decisions and steps you took?]
Result: [What changed? Use a number if you have one, or describe the outcome clearly.]
What this demonstrates: [The skill the employer listed in the job description.]

Two frameworks are enough. Once you can move through a situation, an action, and a result comfortably, most behavioural questions become variations on the same skill.

7. Prepare questions to ask the interviewer

Nearly every interview ends with an invitation to ask questions, and it is a genuine part of the evaluation on both sides. Prepare six to eight in advance, because interviewers often answer several of them in the course of the conversation and you want some left. Write them down; there is nothing wrong with glancing at a notebook.

• • What does success look like in this role after six or twelve months?
• • What are the team's main priorities right now?
• • What would the first ninety days typically involve?
• • How is the team structured, and who would I work with most closely?
• • What is the biggest challenge facing whoever takes this role?
• • How is performance measured here?
• • How would you describe your management style and expectations?
• • What development or training opportunities are available?
• • Why is this position open?
• • What are the next steps in the process, and what is the timeline?

Avoid asking things the posting already answers clearly — it suggests you did not read it. The exception is genuine clarification: if the description lists a responsibility in vague terms, asking what it looks like in practice is useful to both of you. For a much longer list sorted by who you are meeting, see our guide to questions to ask in an interview.

No specific question guarantees a good impression. What tends to help is asking about things you would actually need to know in order to do the job well, and listening to the answers closely enough to follow up. Their answers also tell you a great deal about whether you want the role.

8. Research salary before the interview

Compensation can surface at any point, sometimes in the first ten minutes of a recruiter screen. If you have not looked at the numbers, you are choosing between naming something arbitrary and deflecting awkwardly. Ten minutes of research beforehand removes that problem entirely, and it also tells you whether the job is worth your time.

Base your view on:

• • The occupation, using the closest standard job title rather than an internal one.
• • The location, since wages vary substantially between states.
• • Your years and depth of experience.
• • The scope of the responsibilities described in the posting.
• • Seniority — an entry-level and a lead version of one title are different jobs.
• • Any range the employer has disclosed in the posting or by law.
• • Published market wage data for the occupation and area.
• • Total compensation, where bonus, overtime, or benefits are a real part of the package.

9. Prepare for salary-expectation questions

The question arrives in several places: on the application form, during a recruiter screen, in a first interview, or late in the process just before an offer. Whenever it comes, the answer should be one you decided in advance rather than a number you produced under pressure.

Preparation is short. Check the market wage for the occupation and state, note any range the employer has published, consider how the scope of this role compares with your last one, settle on a defensible target and a range around it, factor in bonus and benefits where they are material, and keep enough flexibility that a reasonable conversation can continue. Being able to say where your number came from matters more than the number itself.

Our dedicated guide covers the wording in depth, including what to say when you are asked before you know the scope of the job. See how to answer salary expectations for the full set of example answers. If you are still at the application stage and the form has a compensation box, that is a separate problem — what to put for desired salary on a job application covers it. For turning a target into a specific figure, see what salary you should ask for.

10. Plan what to wear and bring

There is no single dress code that applies everywhere. What looks appropriate depends on the employer, the industry, the role, the interview format, and local norms. A law firm, a hospital, a construction contractor, and a software startup do not share a standard, and dressing for the wrong one is a small but avoidable distraction.

Use what you know about the employer. Photos on their website, the tone of the job posting, or what you saw if you have visited a site are all reasonable signals. If you genuinely cannot tell, ask the recruiter — it is a normal question and nobody thinks less of it. Our guide to what to wear to an interview covers formal, business-casual, practical and virtual settings. Absent any signal, choose something clean, comfortable and appropriate to the environment. The aim is to keep the conversation about your work.

For an in-person interview, bring only what is useful. Do not bring sensitive documents — tax records, bank details, social security card, medical information — unless the employer has specifically asked for them as part of a documented process.

11. Prepare for a virtual interview

A video interview adds a layer that can fail, so test it rather than assume it works. Run the check at least a day ahead, on the same device and connection you will use, and using the same meeting software the employer named — installing an unfamiliar application five minutes before the call is a predictable way to start late.

Framing and lighting are simple to get right. Put the camera at roughly eye level so you are not looking down at it, sit far enough back that your head and shoulders are in frame, and face a window or a lamp rather than having a bright light behind you. That is the whole of it — you do not need equipment.

Keep notes to a few bullet points. Reading from a document is audible in your voice and visible in your eyes. If the connection does drop, say so plainly, reconnect, and carry on; interviewers deal with this constantly and it is not held against you.

12. What to do the day before your interview

The day before is for review and logistics, not for learning anything new. Cramming fresh material tends to crowd out the examples you already prepared. Work through a short list instead:

1. 1. Reread your company research and the job description once.
2. 2. Skim your three to five strongest examples — the headlines, not the full text.
3. 3. Review your salary research and the target range you settled on.
4. 4. Print or write out your questions for the interviewer.
5. 5. Confirm the date, start time, and time zone against the invitation.
6. 6. Confirm the address and parking, or the meeting link and joining details.
7. 7. Check the route and travel time, allowing for traffic or transit delays.
8. 8. Choose and check your clothes.
9. 9. Pack your materials, or run the technology test if the interview is virtual.
10. 10. Note the interviewer's name and the contact number for the day.
11. 11. Finish preparing early enough to stop and rest properly.

On the day itself, leave a buffer. Arriving with ten minutes to spare, or joining a call a few minutes early, means the first thing the interviewer sees is not someone apologizing. Use that buffer to reread your questions and one example.

13. Job interview preparation checklist

Run through this before any interview. If you can tick most of it, you have done the work that is within your control.

After the conversation, a short thank-you email after the interview can help you close it professionally.

Frequently asked questions