The best interview questions to ask (and the ones to finally retire)

Ask a hundred hiring managers for their favorite interview question and most will give you some version of "where do you see yourself in five years" or "what is your greatest weakness." These questions have survived for decades not because they work but because they are easy to ask and candidates have learned exactly how to answer them. A prepared answer to a predictable question tells you almost nothing about how someone will actually perform in the role.

The interview questions that produce real signal share a few traits the clichés lack: they are specific rather than hypothetical, they ask for evidence rather than opinion, and they are hard to fully prepare for because they require the candidate to reconstruct something that actually happened. A structured interview process built around questions like these is one of the few remaining steps in hiring that reliably separates candidates who can do the job from candidates who are good at interviews.

This matters more than most hiring teams treat it. The cost of a bad hire runs well into the tens of thousands of dollars once you count lost productivity, management time, and the cost of restarting the search, and a meaningful share of bad hires trace back to an interview process that never asked the questions that would have surfaced the mismatch. Here is what to ask instead, organized by what each question is actually trying to find out.

Questions that test for real experience, not rehearsed answers

The single most reliable interview technique is also the simplest: ask for a specific example instead of a general characterization. "Tell me about a time you had to deliver bad news to a stakeholder" produces a different quality of answer than "are you a good communicator." The first requires the candidate to reconstruct an actual event, with actual constraints and actual outcomes. The second invites a confident generalization that tells you nothing.

The follow-up questions matter as much as the opening prompt. When a candidate describes a project, ask what specifically they did versus what the team did. Ask what they would do differently with what they know now. Ask how they knew the approach was working, or how they found out it was not. Candidates who were genuinely close to the work described can answer these follow-ups fluently and specifically. Candidates who are describing a team effort they were loosely adjacent to start speaking in generalities the moment you ask for detail.

"Walk me through the last time you had to learn something new quickly for a role" is a particularly useful variant for roles in fast-changing environments, because the answer tells you about learning speed, resourcefulness, and comfort with ambiguity all at once, through a real example rather than a self-assessment.

Questions that reveal how someone handles disagreement

Almost every job eventually requires disagreeing with a manager, a peer, or a client, and almost no standard interview process tests for it directly. "How do you handle conflict" is too abstract to be useful. "Tell me about a time you disagreed with a decision your manager made and what you did about it" forces a concrete answer and, more usefully, forces the candidate to reveal what they actually did rather than what they believe about conflict in the abstract.

The content of the answer matters less than the pattern it reveals. A candidate who describes raising a concern directly, making their case with evidence, and then supporting the final decision once it was made is describing a healthy, functional approach to disagreement regardless of the specific topic. A candidate who cannot produce an example at all, or whose example involves going around their manager rather than through them, is telling you something worth taking seriously.

This question is particularly diagnostic for workstyle fit, because how someone handles disagreement is closely tied to how much autonomy and how much structure they actually want, independent of what they say they want when asked directly. A candidate who describes escalating every disagreement to a formal process may be a poor fit for a fast-moving team that expects people to work disagreements out directly and quickly, even if nothing else about their answers suggests a problem.

Questions that test judgment instead of knowledge

Knowledge questions, the kind with a correct answer that a candidate either knows or does not, have a place in technical screening but are a poor use of interview time with a senior decision-maker in the room. Judgment questions, the kind with no single correct answer but a range of defensible ones, are far more revealing and far harder to prepare a canned response for.

"If you had to deprioritize one of three competing deadlines this week, how would you decide which one" is a judgment question. There is no correct answer, but a strong answer reveals how the candidate weighs stakeholder impact, reversibility, and downstream consequences, which is exactly the kind of thinking the role will actually require once they are hired. A weak answer reveals someone who has not had to make that kind of tradeoff before, or who defaults to whichever option avoids immediate conflict rather than whichever option is actually best for the business.

For roles with a strong evaluative or decision-making component, a useful variant is presenting a real, simplified version of a decision your team recently had to make and asking how the candidate would approach it. This is more work to design than a generic prompt, but it produces an answer you can compare directly against how your own team actually reasoned through the same problem, which is a far more specific signal than any hypothetical scenario pulled from a question bank.

Questions that uncover self-awareness

"What is your greatest weakness" fails because every candidate has rehearsed a version of it that is actually a disguised strength. "What is something you had to work on developing in your last role, and what did that process actually look like" is a better version of the same intent, because it asks for a specific developmental arc rather than a label, and arcs are much harder to fabricate convincingly than adjectives.

A strong answer describes a concrete gap, what the candidate did to close it, and what measurable change resulted, even if the change was modest. A weak answer stays abstract, describes a trait rather than a behavior, or reveals that the candidate has not actually reflected on their own development in any specific way. The absence of a real answer is itself informative: people who have grown meaningfully in their careers usually have at least one story about a real area of weakness and what they did about it.

"What feedback have you gotten that was hard to hear but turned out to be right" is a related question that works especially well for more senior candidates, because it requires acknowledging that someone else's critical assessment of them was accurate, which is a genuinely uncomfortable thing to do in an interview and therefore hard to fake convincingly on the spot.

Questions to finally retire

"Where do you see yourself in five years" rarely produces a useful answer because almost no candidate has a real five-year plan that they are willing to share honestly in an interview, and the ones who do have one are usually describing aspirations loosely connected to the role in front of them. It mostly tests how well a candidate can improvise a plausible-sounding career narrative on demand.

"What is your greatest strength" and its inverse "what is your greatest weakness" belong on the same list. Both questions have been asked so consistently for so long that nearly every candidate who has interviewed more than a handful of times has a polished, low-risk answer ready before they walk in the door. The answer you get is a measure of interview preparation, not of the trait the question claims to probe.

"Why should we hire you" and "why do you want to work here" are worth retiring in their generic form, not because the underlying questions are bad but because asking them this broadly invites a generic, rehearsed answer. A sharper version, "what specifically about this role made you apply, as opposed to similar roles at other companies," forces a more concrete answer and filters out candidates who are applying broadly without having actually considered the specific fit.

Brainteasers and puzzle questions, once popular at large technology companies, have been largely abandoned for good reason: research summarized by Harvard Business Review and other sources on hiring assessment found they have little to no correlation with actual job performance and mostly measure whether a candidate happens to have seen the puzzle before. They survive mostly as interviewer theater.

Calibrating questions to seniority and function

The same question does not work equally well across every role and level, and a common mistake is applying a single generic question bank regardless of who is sitting across the table. For entry-level and early-career candidates with limited work history, questions should lean more heavily on academic projects, internships, extracurricular leadership, and how the candidate approaches learning, since the depth of professional experience to draw on is naturally thinner.

For mid-career individual contributors, the emphasis should shift toward depth in their specific domain: specific projects, specific technical or functional decisions, and specific outcomes they can speak to in detail. This is where skills-based evaluation earns its value, since a candidate's ability to walk through the actual mechanics of work they have done is a far better predictor than a credential or a job title on a resume.

For senior and leadership candidates, the questions should shift again toward judgment, influence, and how the candidate has handled ambiguity and organizational complexity, since the core evaluation question for a senior hire is less "can they do the work" and more "can they be trusted to make good calls when the right answer is not obvious." A single interview guide used identically across junior and senior candidates is usually a sign that the questions were written for convenience rather than designed around what each level of the role actually requires.

Building a question bank your whole team can use

Individual interviewers asking their own favorite questions, with no shared structure, is the most common reason a company's interview process produces inconsistent signal across candidates. SHRM's guidance on structured interviewing is consistent on this point: standardizing the core question set across interviewers for a given role, while still allowing follow-up questions to go wherever the candidate's answer leads, produces more comparable and more predictive results than letting every interviewer freelance.

A practical way to build this is to map each open role to three to five core competencies the role actually requires, assign one or two of the questions above to each competency, and give every interviewer on the panel the same core set with instructions to probe follow-ups naturally. This does not make the interview feel scripted to the candidate. It makes the evaluation comparable across candidates, which is the entire point of running more than one interview per role in the first place.

LinkedIn Talent Solutions research has found that companies with a standardized interview question framework report meaningfully higher confidence in hiring decisions and lower disagreement among interviewers during debrief, which translates directly into fewer stalled decisions and faster time to offer. Better questions do not just produce better hires. They produce faster, more defensible decisions along the way, which is reason enough for most hiring teams to invest the hour it takes to build a real question bank instead of relying on whatever each interviewer happens to remember from their own last interview.