The 12 most common interview questions, decoded
Every common interview question is really asking something else underneath. Knowing what's actually being assessed lets you answer it once and well.
Interview questions sound like they're asking about your past. They're really asking about your future — specifically, your future at this company. Once you understand the underlying assessment, the same answer can serve a dozen variations of the question.
"Tell me about yourself"
What they're actually asking: can you summarize who you are professionally without rambling, and is the trajectory you've been on heading toward this role? Your answer should be three beats — what you've been doing, what you want to do next, why this role is the bridge. 90 seconds, no resume play-by-play.
"Why are you leaving your current role?"
What they're actually asking: are you running from something, and will you do the same thing here? Never criticize the current company or manager — even if it's deserved, you'll come across as someone who'll talk about this team the same way next year. Frame the answer as growth: what you've gotten out of the current role and what's now missing.
"What's your greatest weakness?"
What they're actually asking: do you have self-awareness, and have you done the work to address what you're not naturally good at? "I'm a perfectionist" reads as either dishonest or shallow. The better answer names a real weakness and shows the system you've built around it. "I tend to under-communicate when I'm heads-down on a problem; I now share weekly written updates so my team isn't guessing."
"Where do you see yourself in five years?"
What they're actually asking: are you going to stick around long enough for the company to get a return on hiring you? Hint at growth that's plausible inside this company. Don't promise to still be there — that reads as performative. Don't describe a future that's obviously incompatible with this role either.
"Tell me about a time you failed"
What they're actually asking: do you take responsibility, and what do you do with hard lessons? The trap is choosing a fake failure ("I worked too hard"). Pick a real one — small enough to not disqualify you, big enough to be honest. Spend most of the answer on what you changed afterward, not the failure itself.
"Why do you want to work here?"
What they're actually asking: did you do your homework, or did you mass-apply? The answer needs at least one specific thing about this company that you couldn't have said about a competitor — a recent product decision, a values statement that resonated, something one of their engineers wrote. Generic "I admire the company" answers tank you.
"Tell me about a difficult coworker"
What they're actually asking: how do you handle conflict, and are you mature about it? Don't villainize anyone. Show that you tried to understand the other person's perspective, took action, and learned something about yourself. The story matters less than the tone you tell it in.
"What's your salary expectation?"
What they're actually asking: where can we anchor the negotiation? If you have to give a number, give a range — and make the bottom of the range a number you'd actually accept. Better answer when possible: "I'd love to learn more about the role and the comp band before I anchor on a number — what range are you thinking for this position?"
"Walk me through your resume"
What they're actually asking: can you tell a coherent story about your career, or is it a list of jobs? Connect each role to the next with a "because of X, I wanted Y" structure. Spend the most time on the most relevant role, the least on roles 5+ years ago.
"Do you have any questions for us?"
What they're actually asking: are you taking this interview seriously, and are you assessing them too? Have at least three questions ready. Skip questions about salary, benefits, and remote policy in early rounds. Best questions are about how decisions actually get made, what surprised them when they joined, and what someone in this role would have to be doing 90 days in for the team to feel the hire was a win.
"Why should we hire you?"
What they're actually asking: can you advocate for yourself without bragging? Pick the two or three things you bring that you suspect other candidates won't, and connect each one to something specific about the role. End with a one-line summary.
"Is there anything you'd like to add?"
What they're actually asking: did you cover everything you wanted to, and do you have a closing instinct? Use this to land one thing you wish you'd said earlier — a strength you didn't get to demonstrate, a question you didn't get to ask, or a clear statement of interest in the role. Don't waste it on "no, I think we covered everything."
Apply this to your own resume in 5 minutes
Pick a template, paste in any job description, and the AI rewrites your bullets to mirror what the role asks for — using your real experience.