Answering the Interview Questions Everyone Gets Wrong

Shvii Team | | 7 min read
Two people in conversation across a table during a job interview

Every question is testing something other than what it asks

Common interview questions have a reputation for being pointless. They are not, but they are indirect, and candidates answer the surface question rather than the real one.

Once you know what each is actually assessing, you stop needing a memorised script, because you can construct an answer from your own history in real time. That is also what makes the answer sound like a person rather than a recital.

Tell me about yourself

This is not a request for your life story and it is not small talk. It is a test of whether you can judge what is relevant, which is a proxy for how you will communicate once hired.

The failure is chronological. Candidates start at university and work forward, and by minute four the interviewer has stopped listening.

Work backwards instead. Start with what you do now, spend most of the time there, and reach back only for the parts that explain how you arrived. Two minutes, three at the outside.

Finish by connecting to the role. "Which is why this position interested me, because it is the same problem at larger scale" gives the interviewer somewhere to go next, and controls what they ask about.

What is your greatest weakness

The question is assessing self-awareness and whether you can discuss your own shortcomings without either collapsing or deflecting.

The disguised-strength answer, perfectionism or caring too much, has been recognised for a decade and now signals evasion rather than modesty. Interviewers hear it as an unwillingness to be straight, which is a worse trait than the weakness would have been.

Name something real, then say what you do about it. "I am slow to delegate, particularly early in a project when I understand the detail better than anyone else. I have started handing over the second piece of work rather than the fifth, and forcing myself to review rather than redo it."

The structure matters more than the weakness. Real thing, its consequence, the specific mechanism you use to manage it. Avoid anything central to the job, and avoid anything that suggests unreliability.

Why did you leave, or why are you leaving

Underneath this is a single check: how do you talk about people who are not in the room.

Criticising a former employer, however justified, is the most reliable way to lose an interview at this question. The interviewer is not evaluating whether your old manager was difficult. They are imagining you describing them the same way in a year.

Keep it short, factual and forward-looking. Redundancy, a company that changed direction, a role that stopped growing, wanting something the current job cannot offer. One or two sentences, then stop talking. Over-explaining reads as defensiveness even when the reason is entirely reasonable.

If you were dismissed, say so plainly and briefly, with what you took from it. The discovery later is much worse than the disclosure now.

Why do you want this job

This separates candidates faster than almost any other question, because most people answer it with praise for the company.

Telling an interviewer their company is an industry leader with an exciting culture conveys that you read the homepage. Everyone read the homepage.

Answer about the work instead. Something specific in the job description that you want to do, connected to something you have done before or want to do next. "You mentioned rebuilding the forecasting process, and that is the part of my current job I have enjoyed most" is an answer only you could give.

Where you genuinely admire the company, be specific about why, and make it something that required looking. A product decision, a public position they took, how they handled a problem.

One clear takeaway: any answer that would fit another company is not an answer.

Where do you see yourself in five years

The real question is whether you have thought about your direction and whether this role fits it. Nobody expects an accurate forecast.

The answers that fail are the joke, the one that names the interviewer's job, and the one so vague it says nothing. Also risky is naming an ambition the role plainly cannot serve, which invites the reasonable conclusion that you will leave quickly.

Describe a direction rather than a title. Deeper in a discipline, broader across a function, eventually leading a team. Then connect it to what this job would build. That answers the underlying worry without pretending to certainty you do not have.

Tell me about a time you failed

Candidates hedge here more than anywhere else, choosing a failure so minor it does not count or one that was clearly somebody else's fault.

Interviewers are checking two things: whether you can own something, and whether you learned in a way that changed your behaviour.

Pick something genuinely yours, with a real consequence. Say what you misjudged, not what circumstances conspired. Then say what you do differently now, concretely enough that it is checkable.

The instinct to protect yourself is exactly what costs you the answer. A candidate who describes a real failure clearly reads as more senior, not less.

What are your salary expectations

This arrives early, often in the screening call, and it is the question people are least prepared for despite knowing it is coming.

Give a researched range with a basis. "Based on what I have seen for this level in this city, I have been looking at somewhere in this range, and I am flexible depending on the whole package." That is a professional answer that does not commit you and does not stall the process.

Refusing to answer at all reads as awkward more often than it reads as strategic, particularly with a recruiter who needs a number to proceed. Where you are asked what you currently earn, note that in some jurisdictions employers may not ask, and redirecting to your expectation for this role is always reasonable.

Do the research first. Our salary calculator takes your role, city and experience so you are not guessing on the call.

Do you have any questions for us

This is assessed, not a formality, and answering no is close to fatal at any level above entry.

Ask about the work and the team rather than about benefits, which belong to a later conversation. What does success look like in six months. What is slowing the team down. Why is the role open. What has already been tried for the problem you raised.

Prepare six, since several get answered as you go. Our guide to questions to ask an interviewer covers this properly.

Why should we hire you

Asked directly, this feels aggressive, and candidates either become falsely modest or produce a list of adjectives.

It is a closing question. The interviewer is giving you the chance to make the argument in your own words, and they are checking whether you understood what the job needs.

So make the argument, in three parts. The main thing the role requires, based on what they have told you in the conversation. The evidence you have that you can do it. The thing you would want to get moving on first.

Do not claim to be the best candidate, because you have not met the others and the claim is unverifiable. Claim fit for the specific problem they described, which is checkable and much more persuasive.

Questions that have no good scripted answer

Some questions exist to see how you think when there is nothing to recite. What would you do in your first ninety days. How would you approach this problem we have. What would you change about how we do this.

The failure is answering with confidence you have not earned. A candidate who proposes a detailed plan for a business they have known for forty minutes signals that they do not know what they do not know.

The answer that works starts with what you would need to find out, says what you would expect to find, and then commits to a first step for each case. That is how the work actually happens, and interviewers recognise it.

Asking what has already been tried is nearly always the right move before proposing anything.

The pattern underneath all of them

Every question above rewards the same two things: a specific real example, and a straightforward account of your own part in it.

Which is why preparing six to eight detailed stories from your career beats preparing answers to twenty questions. The stories recombine. The scripts do not, and they break on the first follow-up.

Our interview prep tool generates questions for your actual role, which is a more useful rehearsal than a generic list.

Questions people ask

How long should my answer to "tell me about yourself" be?

Two minutes, three at most. Start with what you do now and work backwards only as far as it explains your path.

What is a good answer to the greatest weakness question?

A genuine limitation, its consequence, and the specific thing you do to manage it. Disguised strengths are recognised immediately and read as evasion.

Should I say I was fired?

Yes, briefly and factually, with what you took from it. Being found out later is considerably worse than saying it yourself.

How do I answer salary expectations without underselling myself?

Give a researched range with the basis for it, and stay flexible on the overall package. Refusing to answer usually creates friction rather than an advantage.

Is it acceptable to have no questions at the end?

No. It reads as lack of interest or lack of preparation. Have six ready, because several will be answered during the conversation.

Related reading

Rehearse with questions for your role

Open interview prep

Useful next steps from this article - tools to apply the advice, plus related career guides.