50 Common Interview Questions and Answers (With Examples)

TL;DR — Here are the 50 most common interview questions and answers, each with what the interviewer is really asking, how to answer, and a sample answer you can adapt. You can't predict every question, but interviews recycle the same handful: "tell me about yourself," strengths and weaknesses, "why this job," and "tell me about a time…" Prepare a few framed answers and five to seven flexible stories, tie each to the specific role, keep answers to roughly one to two minutes, and you'll cover almost everything that comes up.

These are the interview questions and answers you're most likely to need, from "tell me about yourself" to "why should we hire you?", each answered one by one with a sample answer. The questions feel infinite until you notice the pattern. Across companies and roles, the same prompts come back over and over — and they're testing only a few things: can you do the job, do you actually want this one, and are you someone people want to work with. Once you see the categories, you stop preparing fifty separate answers and start preparing a small kit that flexes to fit most of them. This guide covers the four kinds first, then answers the 50 questions you're most likely to hear — what each is really asking, how to answer it, and a sample answer you can adapt.

The four kinds of questions you'll be asked

Almost every interview question is one of four types. Knowing which is which tells you how to answer:

• Opening / about-you — "Tell me about yourself," "Walk me through your résumé." A quick, framed pitch.
• Motivation / fit — "Why this job?" "Why us?" "Where do you see yourself in five years?" These test whether you researched them and actually want the role.
• Self-assessment — "What's your greatest strength?" "What's a weakness?" These test self-awareness.
• Behavioral and situational — "Tell me about a time…" (past) and "What would you do if…" (hypothetical). Princeton's career center draws the line cleanly: behavioral looks backward at your proven track record, situational looks forward at how you'd think. Both are answered best with a real, specific story.

Prepare one approach per category and you're ready for dozens of phrasings of the same underlying question. Technical roles add rounds of their own — live coding, system design, take-home projects — and tech job interview tips covers those.

How to answer "tell me about yourself"

This is usually the first question, and it's not an invitation to recite your life story. It's a 60-to-90-second pitch: a quick present, past, future arc that lands on why you're sitting in this room.

• Present — who you are right now (your year and field, or your current role).
• Past — one or two experiences that built the skills this job needs.
• Future — why this role is the logical next step.

"I'm a senior at State studying marketing, graduating in May. Over the last year I ran social media for our 300-member entrepreneurship club, where I grew our event attendance by about 40% by testing different post formats — which is where I found I really like turning data into decisions. That's exactly why this analyst role caught my eye: it's the same work at a bigger scale."

Notice it's tight, specific, and points at the job. For the full breakdown, see our guide on how to answer "tell me about yourself".

How to answer "why do you want this job?"

This is the question candidates fumble most, almost always because they skipped the research. MIT's Career Development Office recommends covering three things in one answer: why this company, why this position, and why you'll be good at it. Hit all three and you sound prepared instead of desperate.

What to do before you answer:

• Read past the homepage. Look at the company's "about" page, recent news or announcements, and the actual job description.
• Find one specific, true reason. A product you've used, a value that matches yours, a project mentioned in the posting.
• Connect it back to you. Why does that thing fit your skills or goals?

"I've followed how your team rebuilt the onboarding flow — I read the engineering blog post about cutting setup time in half, and that kind of focus on the actual user experience is what I want to work on. The role lines up with the front-end projects I've been doing, and I'd be coming in already excited about the problem."

Avoid the answers that sink you: "I need a job," "the pay looked good," or anything that's only about what you get. Keep it about the work and the fit.

How to answer strengths and weaknesses

For strengths, pick one that genuinely maps to the job, then prove it with a quick example — don't just claim it. "I'm a strong communicator" is empty; "I'm a strong communicator — I ran the weekly stand-up for my project team and rewrote our status updates so faculty could follow them" is evidence.

For weaknesses, the trap is the fake one. "I work too hard" and "I'm a perfectionist" read as dodges, and interviewers know it. The University of Illinois Chicago's business career center tells students to be ready with at least two real weaknesses — "I can't think of any" isn't an answer — and to explain how they're working to improve them. Add one rule of your own: don't pick something core to the role. The formula:

1. Name a genuine weakness that won't disqualify you (don't say "writing" for a writing job).
2. Show the fix — the concrete step you're taking.

"I used to undersell my own work — I'd finish something solid and not say anything about it. I've started keeping a short running log of what I shipped each week, partly so I get more comfortable talking about it, like right now. It's still a work in progress, but I'm much better at it than I was a year ago."

That's honest, specific, and shows growth — which is the whole point of the question.

How to answer behavioral and situational questions

Behavioral questions — "tell me about a time you…" — are the heart of most interviews. Yale's Office of Career Strategy notes most interviews are behavioral, on the logic that past behavior predicts future performance. The reliable way to answer is the STAR method: Situation, Task, Action, Result — keep the setup short, spend most of the answer on what you did, and always land on a result. It's worth its own deep dive, which we wrote here: the STAR method for behavioral interviews.

Situational questions are the hypothetical cousins — "what would you do if a teammate missed a deadline?" Answer by walking through your reasoning out loud, and if you've actually faced something similar, tell that real story instead.

The high-leverage prep move: build a story bank of five to seven experiences from jobs, projects, clubs, and volunteering, tagged by theme. A small bank covers a huge range of prompts. Most behavioral questions are some version of these:

• A time you led something or took initiative.
• A time you worked through conflict or disagreement.
• A time you failed or made a mistake — and what you did next.
• A time you handled a tight deadline or competing priorities.
• A time you faced ambiguity with no clear answer.
• A time you worked on a team to deliver something.

50 common interview questions and answers

You won't get all of these, but you'll get a slice — and every one maps to a category you've now prepared. Each question below has three parts: what they're really asking (the thing being scored), how to answer (the shape that works), and a short sample answer to adapt. The samples come from different jobs and backgrounds on purpose; swap in your own facts, and never borrow a story you didn't live.

Opening and about-you questions

1. Tell me about yourself

What they're really asking: Can you summarize yourself in about a minute, and do you know why you're in this room?

How to answer: Present, past, future — who you are now, one or two experiences that built the skills this job needs, and why this role is the next step. The full method is above.

"I've spent three years as a pharmacy technician, and the part of the job I liked most turned out to be inventory — I rebuilt our reorder sheet, and we stopped running out of the medications people asked for most. That pulled me toward operations, so I finished a supply-chain certificate this spring. This inventory analyst role is the work I've been doing on the side, as the whole job."

2. Walk me through your résumé

What they're really asking: Is there a thread through your history, and can you tell it without reading the page aloud?

How to answer: Pick two or three stops, newest last. For each, say what you did and why you moved on, then land on why this role follows. Ninety seconds, no bullet-by-bullet recital.

"I started on the sales floor at a big-box store in college and was closing supervisor by my second year — that's where I learned scheduling and cash reconciliation. After graduating I took a coordinator job at a logistics company, where I run the daily carrier schedule for two warehouses. The common thread is keeping a lot of moving parts on time, and this operations role is the bigger version of that."

3. How would a friend or professor describe you?

What they're really asking: How self-aware are you, and what would you be like to work with?

How to answer: Two or three words that matter for this job, each with a quick piece of evidence. Quoting real feedback you've received is stronger than describing yourself.

"My lab professor wrote 'reliable' in my recommendation — I was the one who kept our shared protocol document current all semester. My friends would say I'm the organizer, which is fair: I plan our trips down to the spreadsheet."

4. What are you passionate about?

What they're really asking: What gives you energy, and does any of it overlap with the work?

How to answer: One genuine interest and why it matters to you. If it connects to the role, say so in a sentence; don't manufacture a passion for their product.

"Helping people understand things that intimidate them. I've volunteered at a tax-preparation clinic for two seasons, and the best moment is when someone realizes they can read their own return. That's a big part of why customer education roles appeal to me."

5. Why did you choose your major?

What they're really asking: How do you make decisions, and can you connect what you studied to this job?

How to answer: One honest reason, then what the major taught you that applies here. If the major is unrelated, lead with the transferable skill rather than apologizing for it.

"I picked psychology because I wanted to understand why people make the choices they do. What I didn't expect was how much statistics it involved — I ended up loving research methods, which is how I found my way into user research."

6. What's a project you're proud of?

What they're really asking: What do you count as good work, and how clearly can you describe your own part in it?

How to answer: A compressed STAR story — the problem, what you did, and a result. Choose a project that resembles the job if you can.

"Last spring I rebuilt the volunteer sign-up for our food pantry. Shifts were scheduled over group text and we had no-shows every weekend. I moved it to a shared sign-up sheet with an automatic reminder the day before; no-shows dropped from four or five a weekend to about one, and the coordinator still uses it."

7. What do you do outside of class or work?

What they're really asking: Are you a person with interests, and is anything there a sign of follow-through?

How to answer: One real activity and one sentence on why you like it. Keep it brief and steer clear of anything divisive.

"I run — I trained for my first half-marathon last year, which mostly taught me that a plan you follow beats a perfect plan you don't. I also cook for my roommates on Sundays, which is my version of project management."

8. How do you handle stress?

What they're really asking: Will you fall apart under pressure, and do you have a method?

How to answer: Name what you actually do — list the work, sequence it, tell people early — and back it with a real moment. "I don't really get stressed" isn't believable.

"I make it concrete. When finals and a big week at work overlapped last term, I wrote out everything due with dates, did first whatever would unblock someone else, and told my manager on Monday which shift I'd need to swap rather than the night before. Writing it down takes away most of the panic."

Motivation and fit questions

9. Why do you want this job?

What they're really asking: Did you research the role, and are you choosing this one or any one?

How to answer: MIT's three parts — why this company, why this position, why you'll be good at it. The full method is above.

"Three reasons. Your clinic serves mostly Spanish-speaking families, and I'm bilingual and grew up translating at my own family's appointments. The role is front desk plus insurance verification, which is exactly what I did at my last practice. And I'd rather do that work somewhere it so clearly matters."

10. Why do you want to work here specifically?

What they're really asking: What sets us apart for you, beyond the fact that we're hiring?

How to answer: One specific, true observation — a product, how they operate, something they've done — and why it fits you. "Great culture" with no example is a non-answer. More research steps and examples: how to answer "why do you want to work here?".

"I've been a customer for two years, and what stood out was your returns process: a real person, no argument, resolved in a day. When I read that support reports straight into the product team here, that explained it. I want to work somewhere that treats support as information, not a cost."

11. What do you know about our company?

What they're really asking: Did you do the homework?

How to answer: Three facts at three levels — what they do and for whom, something recent, and where this role fits — then a genuine question back.

"You make scheduling software for independent clinics, mostly physical therapy. You launched text-message reminders for patients this year, and from the posting, this role onboards new clinics onto it. What I couldn't find is how many clinics a new specialist usually onboards in a month — what does that look like?"

12. Where do you see yourself in five years?

What they're really asking: Will you stay long enough to be worth training, and does this role lead where you want to go?

How to answer: Describe growth in skill and responsibility in a direction this job actually leads. Don't name a different career, and don't say you want the interviewer's job. More examples: how to answer "where do you see yourself in 5 years?".

"I'd like to be the person on the team others come to with the hard accounts — genuinely expert at this work, and probably helping train new hires. Whether that's a formal lead role depends on what I turn out to be best at, but I want the next few years to be about depth in this field."

13. What are you looking for in a role?

What they're really asking: Does what you want match what we have?

How to answer: Two or three things that are both true for you and offered by this job — read the posting first. Perks alone make you sound like you'd leave for better ones.

"Work where I can see the result — I like a queue I can clear; a manager who gives direct feedback; and room to learn the technical side. From the posting and what you said about weekly one-on-ones, this looks like a strong match on all three."

14. Why are you leaving your current job? / Why now?

What they're really asking: Are you running from a problem that will follow you here, or toward something?

How to answer: Point toward this role, never against your employer. If you were laid off, say it in one plain sentence and move on.

"My role was eliminated in a March restructuring, along with the rest of the regional team. It clarified things, honestly: the part of that job I want to keep doing is the client work, and this role is almost entirely that."

If you're still employed: "I've learned a lot there, but there's no path to my own accounts for at least two more years, and this role starts there."

15. What's your ideal work environment?

What they're really asking: Will you do well here, specifically?

How to answer: Describe conditions you thrive in that are true of this workplace — check whether it's remote, in-office, fast, or methodical before you answer. If there's a real mismatch, better to learn it now.

"Somewhere with clear priorities and room to figure out the how. I do my best work when I know what matters most this week. I also like having people nearby to ask quick questions, which is part of why an in-office team appeals to me."

16. What motivates you?

What they're really asking: What keeps you going on an ordinary Tuesday when nobody is watching?

How to answer: One specific motivator, a quick example, and a link to the actual work of this role.

"Closing loops. At the help desk, my favorite part of the day was taking a ticket that had bounced around for a week, actually resolving it, and writing up the fix so it didn't come back. This role has a lot of that."

17. Why should we hire you?

What they're really asking: Make the case — what's the match between their need and your proof?

How to answer: Restate their top need from the posting, match it with evidence, and add one thing that sets you apart. Thirty to sixty seconds, confident without comparing yourself to people you've never met. The formula with examples by level: how to answer "why should we hire you?".

"You need someone who can run the front desk alone on weekends and keep the schedule full. I've done exactly that for two years at a busy dental office, including setting up reminder calls that roughly halved our weekly no-shows. And I'm bilingual, which with your patient mix sounds like it would get used every day."

18. What other companies are you interviewing with?

What they're really asking: How in-demand are you, how committed are you to this field, and will you accept?

How to answer: Honest and general — the kind of roles, not necessarily the names. Show consistency, and say where this one ranks if it's true.

"I'm in process for a couple of other operations roles at logistics companies, which is the field I'm committed to. This one is at the top of my list because of the training program you described."

19. Are you willing to relocate or work in the office?

What they're really asking: Is there a logistics dealbreaker?

How to answer: A clear, honest answer, with any condition stated plainly. Never agree to something you won't do — it only moves the problem to your first month.

"Yes to four days in the office — I'm about 25 minutes away. On relocation, I'd consider it for the right role after the first year, but I'd want to know where and when before committing."

20. What are your salary expectations?

What they're really asking: Are you inside the budget? It's also an anchor — the first number named pulls the offer toward it.

How to answer: On a first call, deflect once and ask for their budgeted range. If they press, give a tight, researched range whose bottom is your target, not your floor. The full playbook is in how to answer "what are your salary expectations?".

"I'd like to understand the scope first — do you have a budgeted range for the role? I can tell you quickly whether we're aligned." If pressed: "Based on what similar roles pay in this area, I'm targeting $58,000 to $64,000."

Self-assessment questions

21. What's your greatest strength?

What they're really asking: Do you know what you're good at, and is it what this job needs?

How to answer: One strength that maps to the role, proven with a quick example rather than claimed. The full method is above.

"Staying calm with upset people. On the night shift at the hotel front desk, I handled most of our escalations — overbookings, lost reservations — and my manager started routing complaints to me because guests usually left with a solution instead of a demand for a refund."

22. What's your greatest weakness?

What they're really asking: Are you honest about yourself, and do you work on what you're not good at?

How to answer: A real weakness that isn't core to the job, plus the concrete step you're taking. Skip "perfectionist." The full method is above, and sample answers by career stage are in how to answer "what is your greatest weakness?".

"Presenting to a group. One-on-one I'm fine, but I used to rush through presentations. This semester I volunteered to present at our team's monthly review every time, just for the reps, and I record a practice run the night before. I'm slower and clearer than I was in the fall, though it's still not my favorite thing."

23. What's your biggest accomplishment?

What they're really asking: What do you count as success, and at what scale have you worked?

How to answer: Something recent and relevant with a clear result, told as a compressed STAR story, plus one line on why it mattered to you.

"Paying my way through my last two years of school while working 25 hours a week, and still graduating with a 3.4. It isn't glamorous, but it's the clearest proof I have that I can carry a heavy load without dropping things — and I was promoted to shift lead in the middle of it."

24. How do you define success?

What they're really asking: What do you value, and does it line up with how this job is measured?

How to answer: A concrete definition tied to outcomes, then an example of meeting it.

"Success is when the thing I'm responsible for works without me hovering over it. At my internship, that meant the weekly report I built was still in use after I left, by people who never had to ask me how it worked."

25. What would you improve about yourself?

What they're really asking: Often a second weakness question — do you have a plan for your own growth?

How to answer: A skill you're actively building, ideally one that would help you grow in this role, and the specific plan.

"My spreadsheets are strong, but my SQL is beginner-level, and most of the analysts here use it daily. I'm working through an online course two evenings a week, and at my current job I've started pulling my own data instead of waiting for IT to do it."

26. How do you handle criticism?

What they're really asking: Are you coachable, or defensive?

How to answer: A real piece of feedback you received, what you did with it, and what changed. Show you can separate your ego from your work.

"I ask for a specific example first so I understand it, then I fix it before I argue with it. My first manager told me my client emails were too long. I started putting the answer in the first line and the detail underneath, and within a month she'd stopped rewriting my drafts."

27. What are you learning right now?

What they're really asking: Are you curious, and do you take initiative without being told?

How to answer: Something real you're learning now — ideally near the job — what prompted it, and how far you've gotten.

"Spanish, mostly for work — about a third of our customers at the store speak it as a first language. I practice fifteen minutes a day and with a coworker on slow afternoons, and I can now handle returns and basic questions without calling her over."

28. What's a skill you wish you had?

What they're really asking: How self-aware are you, and is the gap a problem for this job?

How to answer: A skill that's useful but not required for this role, and what you're doing to close the gap.

"Design. I can build a clean spreadsheet, but my slides look like spreadsheets. I've been studying our marketing team's templates to understand why they work, which has helped more than I expected."

Behavioral questions (tell me about a time…)

Every answer in this group is a STAR story: a sentence or two of setup, most of the time on what you did, and a result. The samples are compressed to show the shape; a real answer runs a minute or two.

29. Tell me about a time you led a team or took initiative

What they're really asking: Will you step up without being asked, and can you bring people with you?

How to answer: Leadership without a title counts. Show how you got buy-in, not just what you decided.

"Our store's closing checklist lived in one coworker's head, so closes ran late whenever she was off. I wrote it down, walked the other closers through it, and asked for their edits so it was ours rather than mine. Our average close dropped from about 50 minutes to 35, and the manager made it the standard."

30. Tell me about a time you handled a conflict

What they're really asking: Do you go to people directly, understand their side, and get to a resolution?

How to answer: A disagreement about work, not personal drama. Describe the other person fairly — if they come off as a villain, you come off as hard to work with.

"Another tutor and I disagreed about giving students answer keys. Instead of arguing in the group chat, I asked her to grab coffee and learned she was worried about students who got stuck at home. We agreed on hint sheets instead of full keys, and both our groups' quiz scores held up."

31. Tell me about a time you failed or made a mistake

What they're really asking: Do you own mistakes, and do you learn from them?

How to answer: A real mistake with real stakes — but not an ethical lapse. Own it in one sentence and spend most of the answer on the recovery and what you changed.

"At my internship, I sent a client report with last month's numbers in one table — I'd copied the template and missed a tab. I told my manager as soon as I caught it, sent a corrected version within the hour, and since then I check every table's date before anything goes out. It hasn't happened again."

32. Tell me about a time you met a tight deadline

What they're really asking: Can you plan under pressure, or do you just work harder and hope?

How to answer: Show the plan and the tradeoffs, not only the late nights. Mention how you kept people informed.

"Our team got a grant application three days before it was due instead of two weeks. I split it into sections by who already had the data, set a short check-in at noon each day, and drafted the budget narrative myself. We submitted with six hours to spare, and it was funded."

33. Tell me about a time you dealt with a difficult person

What they're really asking: Can you stay professional and find out what's actually going on?

How to answer: Describe behavior, not character. Show that you looked for the reason behind it and changed something.

"A regular at the café complained loudly about every order. I noticed it only happened when we were slammed, so I started taking her order first when she came in and telling her the wait honestly. The complaints mostly stopped, and she started asking for me by name."

34. Tell me about a time you went above what was asked

What they're really asking: Do you take initiative, and do you have judgment about what's worth the extra effort?

How to answer: Extra effort that served a real need — not just long hours — and the result it produced.

"I was asked to update our club's sponsor list. While doing it, I noticed half the contacts had left their companies, so I called each sponsor, got the right names, and wrote a short history note on each. The next year's treasurer told me it saved her the first month of the job."

35. Tell me about a time you had to learn something fast

What they're really asking: How quickly do you get useful in unfamiliar territory? For entry-level roles, this is often the question that matters most.

How to answer: The method — what you read, who you asked, how you practiced — and how fast you became useful.

"Our clinic switched scheduling systems my first week as a scheduler. I went through the vendor's training videos at night, made a one-page cheat sheet of the ten screens we used most, and sat with the one nurse who'd tested it. By Friday, the rest of the front desk was using my cheat sheet."

36. Tell me about a time you juggled competing priorities

What they're really asking: How do you decide what comes first, and do you tell people?

How to answer: Show your logic — deadline, impact, who's waiting on you — and how you communicated the tradeoff.

"During inventory week, I was also covering the register and training a new hire. I asked my manager which mattered most that day, did the counts before opening when it was quiet, and trained the new hire beside me at the register so training happened during the shift instead of on top of it. We finished the counts a day early."

37. Tell me about a time you persuaded someone

What they're really asking: Can you influence people with reasoning rather than authority?

How to answer: Understand their concern first, bring evidence, and be willing to compromise. A trial or pilot is often the winning move.

"My manager wanted to keep paper timesheets. Instead of arguing, I tracked how long payroll corrections took over two pay periods — about four hours each time — and showed her a scheduling app that handled it. She agreed to a one-month trial, and we never went back."

38. Tell me about a time you received tough feedback

What they're really asking: Are you coachable when it stings?

How to answer: What you heard, how you responded without getting defensive, and the measurable change.

"After my first presentation at my internship, my supervisor told me I'd buried the recommendation on slide nine. It stung, but she was right. I rebuilt the deck to open with the recommendation and the one number behind it, and the next review took 15 minutes instead of 45."

39. Tell me about a time you solved a hard problem

What they're really asking: How do you think — do you diagnose, or just patch?

How to answer: Walk through how you found the cause — what you compared, what you ruled out — then the fix and the result.

"Our shop's website kept showing items in stock that weren't. Instead of fixing orders one by one, I compared three weeks of errors and found they all involved deliveries received on Saturdays, which weren't scanned until Monday. We moved scanning to the receiving shift, and oversold orders all but disappeared."

40. Tell me about a time you worked with little direction

What they're really asking: Can you set your own direction, and do you know when to check in?

How to answer: How you defined the goal, how you confirmed it with someone, and what you delivered.

"My internship manager went on leave in my second week and told me to see what I could do with the customer survey data. I wrote down three questions I thought the team cared about, got a quick yes from her backup, and built the analysis around them. The summary went into the quarterly planning deck."

Situational questions (what would you do if…)

There's no story to retrieve here, so walk your reasoning out loud and land on a decision. We cover 36 of these in depth in situational interview questions.

41. What would you do if a teammate wasn't pulling their weight?

What they're really asking: Do you diagnose before you blame, and do you escalate the right way?

How to answer: Check your assumption, talk to the person directly, offer help, and escalate around the deadline rather than the person.

"I'd ask them first what's in the way — sometimes it's a blocker, not effort. If the work still isn't moving, I'd raise the schedule risk with whoever owns the project, framed around the deadline rather than the person."

42. What would you do if you disagreed with your manager?

What they're really asking: Can you disagree well, and then commit?

How to answer: Make your case once, privately, with evidence; ask what you might be missing; then commit — unless it's unsafe or dishonest.

"I'd make my case once, in private, with whatever evidence I have, and ask what context I might be missing. If they still chose their way, I'd commit to it fully. The exception is anything unsafe or dishonest, which I'd escalate."

43. What would you do if you were assigned something you'd never done?

What they're really asking: Are you resourceful, and will you ask for help early?

How to answer: Find existing examples, borrow fifteen minutes from someone who's done it, and confirm your approach before you're deep in.

"I'd look for anything similar that's been done before, ask whoever did it for fifteen minutes, and send my manager a short outline of my approach before going deep. A correction on day one is cheaper than one on day five."

44. What would you do if two deadlines collided?

What they're really asking: Do you make tradeoffs visible, or silently pick one?

How to answer: Check which deadline is truly fixed, ask the requesters if you can't tell, and tell both where things stand.

"I'd check which one is actually fixed — usually one is external and one can move. If I couldn't tell, I'd ask both people which one can give, and send each of them a status so nobody is surprised."

45. What would you do if you noticed a mistake after it shipped?

What they're really asking: Integrity and containment — do you speak up, even when it's yours?

How to answer: Flag it fast with the impact, help contain it, and suggest the check that would have caught it.

"I'd tell whoever owns it right away — what's affected and what I've already checked — even if the mistake was mine. Then I'd help fix it and suggest the step that would have caught it, so it doesn't happen twice."

Closing questions

46. What questions do you have for us?

What they're really asking: Are you interested enough to have prepared? You're being graded on this one, so never answer "none."

How to answer: Two or three prepared questions about the role, the team, and growth. We cover the good ones in questions to ask the interviewer.

"Yes — what would you want the person in this role to have accomplished in the first 90 days? And what's the biggest challenge the team is working through right now?"

47. Is there anything you'd like to add?

What they're really asking: This is your last chance to close a gap they're unsure about.

How to answer: Two or three sentences: anything important you didn't get to, a one-line summary of your fit, and a clear statement that you want the job. Not a new ten-minute story.

"Just that I'm very interested. We didn't get to my availability — I can work any weekend shift, which I know matters for this location. And from everything you've described, this is the team I'd want to join."

48. What's your availability, or when could you start?

What they're really asking: Logistics — and whether you'll leave your current employer well.

How to answer: Specific and honest. If you're employed, build in your notice period; leaving properly reflects well on you.

"I can start two weeks after an offer — I'd want to give my current employer full notice. Within that window, I'm flexible on the exact date."

49. Can you describe your dream job?

What they're really asking: Does this job resemble what you actually want?

How to answer: Describe the qualities — the kind of work, the environment, the impact — rather than a title at another company, and make sure they overlap with this role.

"Work that mixes people and problem-solving — part of the day with customers, part figuring out why something keeps going wrong — on a team that writes things down. Honestly, the coordinator role you've described has most of that."

50. Why should we pick you over other candidates?

What they're really asking: The same as "why should we hire you," with a test of whether you can stay confident without putting anyone down.

How to answer: Don't speculate about the other candidates. Name the combination you bring and tie it to what they need.

"I can't speak to the other candidates, but I can tell you the combination I bring. I've worked the warehouse floor, so I know what the people you'd have me schedule actually deal with, and for the last year I've built the shift schedule for 40 people. Most coordinators have one side of that; I have both."

Common mistakes across every question

• Rambling. Most answers should land in 60 to 120 seconds. If you're past two minutes, you've over-explained the setup.
• Generic answers. "I'm a hard worker" applies to anyone. Specifics — a number, a name, a project — make you memorable.
• No research. A vague "why us" answer tells the interviewer you'd take any job. Tie at least one answer to something specific about them.
• Reciting scripts. Know your beats; don't memorize word-for-word. Scripted answers sound hollow and fall apart the moment a follow-up question lands.
• Skipping the result. Especially on behavioral questions — always say how it turned out.

The single best preparation isn't reading more lists like this one. It's saying your answers out loud until they sound like you instead of a script. Rehearsing in your head hides the rough spots; hearing yourself form the sentences is what closes the gap — which is exactly what a mock interview is for. Run through your story bank, your "tell me about yourself," and one "why this job" answer a few times, and you'll walk in steady.

Sources

• Princeton University Center for Career Development — Behavioral or Situational Interview Questions
• Yale University Office of Career Strategy — The Behavioral Interview
• MIT Career Development Office — 3 Tips for Answering "Why Do You Want to Work Here?"
• University of Illinois Chicago Business Career Center — Career Compass: Talking About Your Strengths & Weaknesses