The Job Interview Questions People Actually Ask (And What to Say)

I've been asked "where do you see yourself in five years?" in approximately ten interviews across my career. I've also asked it probably thirty times myself as an interviewer. The thing I've come to understand is that this question — like most standard interview questions — isn't really asking what it sounds like it's asking. Once you understand what's actually being probed, the question becomes much easier to answer well.

The Questions That Seem Routine (But Aren't)

"Tell me about yourself" is the most common opening question and the one most candidates are least prepared for, despite having heard it a hundred times. The reason people fumble it: they're not sure whether to give a professional summary or a personal biography, and they don't know how long to go. The question is actually asking: can you tell a clear, confident story about who you are professionally and why you're sitting in this chair? A two-minute professional narrative — where you came from, what you've done, and why this role is the logical next step — is the right answer. Not a full resume recitation, not personal details the interviewer didn't ask for.

"Why do you want to work here?" is often answered with generic flattery about the company's reputation or culture. The answer that stands out is specific: something you know about the organization that's relevant to why you're genuinely interested. This requires actual research before you arrive — reading recent news about the company, understanding their products or services well enough to have a real opinion, knowing something about the team you'd be joining. An interview preparation guide that includes a research framework is worth its price for this question alone.

"What's your greatest weakness?" has had many fashionable answers over the years. "I work too hard" was an early cliche that interviewers have been rolling their eyes at for decades. The answer that actually works: a real weakness that you're actively working to address, described specifically. Not a strength disguised as a weakness, not a weakness so minor it's meaningless, but a genuine developmental area with evidence that you're taking it seriously. This answer takes more courage but it's significantly more credible.

The Salary Question and How to Handle It

Discussing compensation causes anxiety for most candidates because it feels like a negotiation with poor information. The most useful framing: you're not competing against the employer, you're trying to determine whether there's a match. Knowing your market rate before you walk in — based on real research rather than what you currently earn — puts you in a much better position to have this conversation calmly.

If you're asked about salary expectations before you have an offer, a range that reflects realistic market data is more useful than either refusing to answer or naming a specific number prematurely. A salary negotiation book helps calibrate your sense of what's reasonable, but the most important preparation is simply knowing what comparable roles at comparable companies in your location pay.

The Questions You Should Ask

Most interviewers will offer time at the end for your questions. This is not a courtesy — it's an opportunity that most candidates underuse. The questions you ask signal what you care about and how you think. Questions about the challenges of the role, what success looks like in the first 90 days, why the previous person in the role left or moved on — these produce genuinely useful information and they show that you're approaching this as a mutual evaluation, not just a one-sided audition.

Questions to skip: anything easily found on the company's website, anything about benefits before you have an offer, and questions that imply you're already planning to leave ("what's the typical path after this role?"). The last category makes you sound like you're treating the role as a stepping stone before you've even started.

What I'd Skip

I'd skip practicing interview answers until they're perfectly memorized. The problem with memorized answers is that they collapse when you get a follow-up question the script didn't anticipate. Practicing the key points and structure of an answer is useful; being able to recite it word for word is actually a liability because it sounds like a recitation rather than a person thinking through something real.

I'd also skip the temptation to embellish your qualifications in response to questions about your experience. If the interviewer is experienced, the embellishment will get caught. If they're not, you'll get a role that requires things you can't deliver. The better approach when you're genuinely lacking something they've asked about: name the gap honestly and explain specifically how you'd close it. That answer demonstrates self-awareness and problem-solving simultaneously, which is what most companies actually want to see.

The bottom line: interview questions are tools for having a real conversation about whether there's a match. The candidates who do well aren't the ones who had the most polished answers — they're the ones who were present enough to actually engage with the conversation, which is harder to prepare for but much more valuable to demonstrate.