Common Interview Questions

Interviewers are rarely evaluating your answer. They are evaluating what happens when they ask the next question.

A memorised paragraph sounds polished and has nothing underneath it. One "can you walk me through how you decided that?" and it falls apart. An answer built from something you actually did can absorb any number of follow-ups, because there is real detail behind it.

So the goal is never to learn a script. It is to know which of your own experiences answers each question, and to be able to tell it clearly.

Being assessed: can you communicate clearly and judge what is relevant? It is a filter, not a warm-up.

Structure: where you are now, one or two things you have done that matter for this role, why you are in this conversation. Sixty to ninety seconds.

Common failure: starting at university and working forward chronologically. By the time you reach anything relevant, attention is gone. Start with the present.

Being assessed: self-awareness, and whether you act on it. Not the weakness itself.

Structure: a real limitation, the concrete thing you changed, where it stands now. The third part is what people skip and it is the part that counts.

Common failure: the disguised strength — "I care too much", "I work too hard". Interviewers have heard it thousands of times and it reads as evasive. A genuine, manageable weakness with evidence of work on it is far stronger.

Being assessed: whether you can disagree without damage, and whether you can describe someone else's position fairly.

Structure: situation, what you did, outcome — and crucially, what the other person's reasoning actually was. Candidates who cannot articulate the opposing view sound like they never understood it.

Common failure: choosing a conflict you clearly won against someone unreasonable. It reads as score-settling. A disagreement you partly lost, handled well, is more convincing.

Being assessed: whether your direction and this role point the same way. It is a retention question.

Structure: the kind of problems you want to be solving, the responsibility you want, and how this role is a step toward it. Ambition without a plan sounds unserious; a plan that clearly routes around this job answers the question badly.

Being assessed: did you do any work before showing up?

Structure: something specific about what they do, connected to something specific about you. One concrete detail beats three paragraphs of flattery.

Common failure: praise that would apply to any company — "great culture", "exciting mission". If your answer would survive a find-and-replace of the company name, it is not an answer.

Being assessed: do you take responsibility, and do you learn?

Structure: what went wrong, your part in it specifically, what you changed as a result. The middle part is the test. Failures that were entirely someone else's fault are not failures, they are complaints.

Common failure: choosing something trivial to stay safe. It signals either poor judgement about what matters or unwillingness to be honest.

The clause that separates a real answer from a recital is "and why that over the alternative". It demonstrates judgement, which is the thing actually being assessed. Most candidates describe what they did; few explain what else they considered.

"Do you have questions for us?" is part of the assessment. "No, I think you covered everything" is a poor answer.

Prepare five, expect to ask two. Good ones are specific: how the team decides what to build, what happened to the last person in this role, what the first ninety days look like, what makes this job harder than it appears from outside.

Do not rehearse by reading. Answer out loud and transcribe yourself — reading your own spoken words is uncomfortable and the fastest way to find the padding, the circling, the point that never quite arrives.

Then attack your own answers: what is the weakest claim here, what would a sceptical interviewer probe, where does this sound rehearsed? Fix it at your desk rather than discovering it live.