Most common interview questions test three things: can you do the job, will you stay motivated, and will you work well with the team. Answer them well by preparing short, specific stories from your own work, linking each one to the role, and practicing out loud until they sound natural.

You do not need a script for every possible question. You need about six solid stories from your recent jobs and a clear idea of why you want this particular role. Almost every question below can be answered by picking the right story and framing it well.

What are the most common interview questions?

The wording changes between companies, but these questions show up in some form in most first and second round interviews:

  1. Tell me about yourself.
  2. Why do you want to work here?
  3. Why are you leaving your current job?
  4. What are your greatest strengths?
  5. What is your greatest weakness?
  6. Tell me about a time you dealt with a difficult situation.
  7. Where do you see yourself in five years?
  8. What are your salary expectations?
  9. Why should we hire you?
  10. Do you have any questions for us?

Below is what the interviewer is really listening for in each, with a sample answer for the trickiest ones.

How should you answer questions about yourself and your motivation?

"Tell me about yourself"

This is a request for a two-minute career summary, not your life story. Use a simple order: what you do now, one or two achievements that matter for this job, and why you are interested in this role.

"I'm a customer success manager at a mid-sized software company, where I look after about 40 accounts. Over the last year I rebuilt our onboarding calls, and the number of customers asking for help in their first month dropped noticeably. I'm looking for a bigger book of enterprise accounts, which is why this role caught my eye."

"Why do you want to work here?"

Generic praise ("you're a great company") falls flat. Mention something specific: the product, a market they are moving into, the way the team is described in the job posting. Then connect it to what you want to do next. Reading the company page and the job description twice before the interview gives you plenty of material.

"Why are you leaving your current job?"

Keep it forward-looking and brief. Talk about what you are moving toward, not what you are running from. Never criticize your current manager, even if they deserve it.

"I've learned a lot in three years, but the team is small and there isn't a clear next step for me. I want to work on larger projects with more senior people around me, and this role offers that."

How do you answer strengths and weaknesses questions?

"What are your greatest strengths?"

Pick two strengths that the job description actually asks for, and back each one with a short example. A strength without evidence sounds like a guess.

"I'm good at turning messy data into something people can act on. In my last role, sales leaders were working from three different spreadsheets. I built one dashboard they now use in their weekly meeting."

"What is your greatest weakness?"

Choose a real but manageable weakness, show you know about it, and explain what you are doing to improve. Avoid fake weaknesses such as "I work too hard."

"I used to take on too much myself instead of delegating. On a busy quarter-end that meant I was the bottleneck. Now I agree on owners for each task at the start of a project, and I check in weekly instead of doing the work myself."

How do you handle behavioral questions?

Any question starting with "Tell me about a time..." or "Give me an example of..." is a behavioral question. The interviewer wants evidence of how you actually behaved, not how you think you would behave.

Use the STAR structure:

Step What to say Rough share of your answer
Situation Where you were and what was going on Short, one or two sentences
Task What you were responsible for One sentence
Action What you specifically did The bulk of the answer
Result What happened, ideally with a number One or two sentences

"Last spring our biggest client threatened to cancel after two late deliveries. I was the account lead, so it was my job to keep them. I called the client the same day, admitted the mistakes, and agreed on a weekly status call. Internally, I set up a shared tracker so the delivery team could flag delays early. They renewed six months later, and the tracker is now used across the team."

Say "I," not "we." Interviewers want to know what you did, not what your team did.

How do you answer questions about the future and money?

"Where do you see yourself in five years?"

The interviewer is checking whether your goals fit the role and whether you are likely to stay a while. Be honest but connected to the job.

"I'd like to be the person the team relies on for the hardest analytics problems, and ideally be mentoring newer analysts. This role looks like a good place to build that depth."

"What are your salary expectations?"

Research before you answer. Look at the salary pages for your role, such as software engineer salaries or data analyst salaries, and check whether the job posting lists a pay range. Several US states and cities require pay ranges in job postings, so it is often there.

Give a range rather than a single number, and anchor the bottom of your range at a figure you would genuinely accept.

"Based on the posted range and what similar roles pay in this area, I'm looking for something between $95,000 and $110,000, depending on the full benefits package."

If you want to rehearse this conversation, the offer and salary negotiation tool helps you plan what to say.

"Why should we hire you?"

Summarize your fit in three points: a skill they need, evidence you have it, and why you want the job. Keep it under a minute.

What questions should you be ready for that are not allowed?

Employers should not make hiring decisions based on protected characteristics such as race, religion, sex, national origin, age, disability or genetic information. The EEOC explains prohibited employment practices, including how questions about these topics can be used as evidence of discrimination.

If you get a question like "Are you planning to have kids?", you can redirect politely:

"I'm fully able to meet the schedule this role needs. Is there something about availability you'd like me to speak to?"

Rules vary by state, so check the EEOC page or your state labor department if you think something crossed a line.

How should you practice before the interview?

Reading answers is not the same as saying them. Most people who freeze in interviews knew the content; they just had not said it out loud before.

  • Write your six stories in bullet points, not full sentences, so you do not sound memorized.
  • Say each answer out loud and time it. Most answers should land between one and two minutes.
  • Run a practice session with the free mock interviewer, which asks you realistic questions and gives feedback on your answers.
  • Update your resume so every story you plan to tell is backed up on paper. The resume builder can help.
  • Prepare two or three questions to ask at the end. "No, I think you covered everything" is a missed chance.

Once you feel ready, look through open roles on the jobs page and apply to a few where your stories fit well.

Frequently asked questions

How many interview questions should I prepare for?

Prepare answers for the ten common questions above and about six detailed work stories. Those stories can be adapted to most behavioral questions, so you do not need a separate answer for every possible wording.

How long should my interview answers be?

Aim for one to two minutes for most answers. If an answer runs past two minutes, stop and ask, "Would you like more detail on any part of that?" Interviewers appreciate candidates who read the room.

Is it OK to bring notes to an interview?

Yes, a short page of notes is generally fine, especially for your questions at the end. Glance at them rather than reading from them, and never read your answers word for word.

What if I don't know the answer to a question?

Say so honestly, then explain how you would find out or approach it. A calm "I haven't faced that exact situation, but here's how I'd handle it" is far better than inventing an example.