Search "common interview questions" and you get the same twenty questions copy-pasted across a hundred sites, each one paired with a bland sample answer you're apparently supposed to memorize. I've sat on the other side of the table for enough of these to tell you why that approach fails: interviewers notice a memorized answer immediately, because it doesn't bend when you ask a follow-up. It just repeats itself, slightly louder.
None of these questions exist because the interviewer is curious about the literal words. "What's your greatest weakness" is not a request for a character flaw. "Tell me about a conflict with a coworker" is not a request for gossip. Every one of them is a wrapper around something the interviewer actually needs to figure out in forty-five minutes: can you do the job, do you actually want it, and can you be trusted to use judgment when nobody's checking your work. Once you see the real question underneath, you stop needing a script for the surface one.
The warm-up questions
"Tell me about yourself." This one gets a full article of its own because the failure mode is so specific and so common — people either recite their resume top to bottom or launch into their life story. The short version: it's asking for a two-minute pitch that connects your background to this role, not a biography. We cover the full structure in our breakdown of how to actually answer it, so I won't re-run the whole framework here.
"Walk me through your resume." People treat this as a rephrasing of "tell me about yourself" and answer it the same way, which is a mistake. The two questions are pulling for different things. "Tell me about yourself" wants a pitch: here's who I am and why I fit. "Walk me through your resume" wants chronology and reasoning — it's asking you to narrate the actual sequence of jobs and explain why you moved between them. The interviewer isn't looking for a highlight reel here, they're looking for the logic. Why did you leave the agency for the in-house role? Why the jump from design into product? A good answer spends more time on the hinges — the transitions — than on any single job, because the hinges are where they learn how you make decisions about your own career, which tells them something about how you'll make decisions about theirs.
The motivation questions
"Why do you want to work here?" and "Why should we hire you?" get asked in almost every interview, and almost every candidate answers both badly in the same two ways — either reciting facts off the company's About page, or making vague claims about being a hard worker. We've written a full piece on how to answer both without sounding arrogant or empty, including a worked example for each, so I'll point you there rather than duplicate it.
"Why are you leaving your current job?" deserves its own space because it's the question I've seen sink otherwise strong candidates the fastest. The real question is whether you're running away from a problem or running toward something, and interviewers are listening for which one it is because it predicts what happens after they hire you. Someone fleeing a bad situation without a clear sense of what they want next tends to land in the same bad situation again, just with a different logo on it.
The single most common way people torpedo this answer is badmouthing their current employer. It doesn't matter how justified the complaint is — a toxic manager, a company circling the drain, being passed over for a promotion that was clearly rigged. The moment you start venting, the interviewer isn't thinking "wow, that sounds unfair to you." They're thinking "this is how they'll describe us in eighteen months." It's an instant, almost involuntary calculation, and it happens whether or not your complaint is fair.
The fix isn't to lie about why you're leaving. It's to frame the departure around what you're moving toward instead of what you're escaping. If your manager genuinely doesn't give you room to grow, don't say "my manager doesn't let anyone grow." Say "I've gotten as much as I can out of my current scope, and I'm looking for a role where I can own a bigger piece of the roadmap" — which is true, doesn't require you to characterize anyone else's behavior, and answers the actual question: you're moving toward something specific, not just away from something unpleasant.
The self-assessment questions
"What's your greatest weakness?" The fake-weakness answer — "I work too hard," "I'm a perfectionist," "I care too much about quality" — has been the default advice for so long that it's become a worse answer than an honest one. Every interviewer who's done more than a handful of these has heard some version of it dozens of times, and at this point it doesn't read as humble-bragging so much as it reads as evasive. It tells the interviewer you either can't assess yourself honestly or don't trust them enough to try.
The real question behind "greatest weakness" is whether you have enough self-awareness to know where you're actually weak, and enough initiative to be doing something about it without being told to. That means the better move is a real, specific, professional weakness — not "I'm disorganized" in the abstract, but something like "I default to solving problems myself instead of looping in the team early, which has cost me time on a couple of projects." Pair it with a concrete thing you're actually doing about it: "I've started building a fifteen-minute check-in into the start of any new project specifically so I'm not the last one to flag a blocker." That answer costs you nothing — it's a minor, believable flaw — and it demonstrates exactly the self-awareness the question is trying to surface.
"What's your greatest strength?" The mirror-image mistake here is picking a strength because it sounds impressive rather than because it's relevant. The real question isn't "do you have a strength" — obviously you do, everyone claims one. It's whether your strength actually matches what this specific role needs. Saying "I'm a great public speaker" in an interview for a data analyst role that never touches a stage is technically an answer, but it doesn't do any work for you.
Say you're interviewing for a customer support lead role at a company that's scaling fast and drowning in ticket volume. The posting mentions "building repeatable processes" twice. A candidate who says "my greatest strength is that I'm really empathetic with customers" isn't wrong, but it's not what this role is straining against. A candidate who says "my greatest strength is turning a recurring mess into a documented process — at my last job our refund workflow was five people doing it five different ways, and I built a single decision tree that cut average handle time by 30% — and that's exactly the kind of chaos it sounds like you're dealing with right now" is answering the actual question, because the strength was chosen for this job, not pulled off a generic list of admirable traits.
The behavioral questions
"Tell me about a time you failed" or "made a mistake." This question is a straightforward test of accountability, and most people fail it not because the mistake they describe is bad, but because of how they narrate it. There's always a version of the story where the blame quietly drifts onto a teammate, a vague process failure, or bad luck. Interviewers hear that drift instantly, and it reads as someone who won't own problems when it matters.
A good failure story is short, specific, and ends with a change, not just a lesson learned in the abstract. Something like: "I shipped a pricing page update without checking it against our accessibility guidelines, and it broke keyboard navigation for a meaningful chunk of users before a customer flagged it. That one was entirely on me — I knew the guideline existed and didn't check against it because I was moving fast to hit a deadline. Afterward I built an accessibility check into our pre-launch checklist, and it's caught two similar issues since." Notice there's no hedging about whose fault it was, and the story doesn't end at the mistake — it ends at the fix that outlived it.
"Tell me about a conflict with a coworker." The real test here is whether you can disagree with someone professionally without either caving to keep the peace or escalating into something that needed a manager to referee. Structuring this kind of story well — situation, the actual friction, what you specifically did, and how it resolved — is its own skill, and we walk through that structure in detail in our piece on interview prep that actually works. The short version: the interviewer wants to see you name the disagreement plainly and describe how you moved it toward a resolution, not a story where the conflict conveniently resolves itself off-screen.
The closing question
"Do you have any questions for us?" Saying "no, I think you've covered everything" is about as close to a disqualifying answer as this list gets. It's not that the interviewer expected a specific question — it's that having zero questions after forty-five minutes of learning about a job you supposedly want reads as a lack of real interest, or worse, a lack of critical thinking about what you'd actually be walking into.
Skip "what's the culture like" — it's the interview equivalent of the fake-weakness answer, so overused it barely registers. Better questions are ones that show you've been listening and are actually evaluating the role back: "What does success look like in this role after the first six months?" gives you something concrete to hold yourself to and shows you're thinking past the offer stage. "What's the biggest challenge facing the team right now?" often gets you an honest answer you couldn't get any other way, and tells you what you'd actually be walking into. "How has this role changed since it was created, or since the last person held it?" surfaces turnover patterns and scope creep that a job posting will never admit to on its own.
Stop memorizing the list
If you take one thing from this, let it be that prepping answers to this exact set of questions is the wrong strategy, because the real interview you sit through will ask you something that isn't on any list. What doesn't change from interview to interview is what's being tested underneath: your competence, your actual motivation, and your judgment under pressure. A question about a hypothetical product decision, a weird curveball about how you'd handle an unhappy client, a "walk me through how you'd approach this" you never rehearsed — all of it maps back to the same three things.
That's a more useful thing to prepare than a script. Know your own track record well enough to pull a real, specific example for any of the three categories on demand, and you can answer a question you've never heard before just as well as one you've rehearsed a hundred times.