Interview questions, and what they are really for
A list of questions is not preparation. What helps is knowing what the interviewer is listening for, which follow-up a vague answer earns, and what a specific answer sounds like when someone says it out loud. That is what each of these pages is.
Product manager interview questions
Product interviews rarely test whether you know what a roadmap is. They test whether you can say what you decided, why, and what you gave up — in an organisation where almost every decision was made by several people at once. Most weak answers are not wrong; they are unattributable.
Read it →Software engineer behavioural interview questions
The behavioural round is where engineering offers are usually lost, and it is the half most people do not rehearse. The questions look soft. They are not: they are looking for whether you can be trusted with a decision when nobody is watching, and whether you can explain a technical choice to someone who will not be impressed by the details.
Read it →Data analyst interview questions
Analyst interviews test something narrower than "can you use SQL": whether the numbers you produce change what anybody does. The questions are usually about a time you were believed, a time you were ignored, and a time you were wrong.
Read it →Customer success interview questions
Customer success interviews are looking for something quite specific: whether you can be honest with a customer who is paying you, and honest internally about a customer you like. Most of the questions are about the moment those two pull apart.
Read it →
Or practise against your own résumé
Add your résumé and the job description, and the questions ask about your work by name. You answer out loud, read the conversation on screen, and the feedback quotes what you actually said.
Build my interview