Interview question pack
Get questions to expect — and questions to ask — for common roles.
They may ask
- Tell me about yourself in two minutes.
- Why this role, and why this company?
- Describe a time you solved a problem with limited information.
- How do you prioritize when everything feels urgent?
- What is a weakness you are actively working on?
You can ask
- What does success look like in the first six months?
- How is feedback given on this team?
- What is the next step in the process?
Reading a list of a hundred generic interview questions the night before a final round rarely helps anyone. You end up with a vague sense of familiarity and absolutely no structured answers. What actually works is mastering a much smaller, highly targeted set of questions—the questions your specific role and round will almost certainly include.
Interviews are a performance skill. You cannot get better at a performance skill by reading a PDF in silence. You only get better by practicing out loud until the first fifteen seconds of every answer comes automatically to your mouth without a single 'um' or 'uh'.
This pack builds that precise, smaller set of questions for you. Choose the role you are interviewing for and the stage you are at, and it returns the exact behavioral questions to expect, the smartest questions worth asking them back, and a rigid structure for answering. Use it as a literal mock interview: say every single answer aloud, once, before you let yourself read the next question on the screen.
Why generic question lists do not work
A mega-list of two hundred questions creates a false feeling of preparation without producing a single finished answer. Interviews are not a trivia recall test; they are a stress test of whether you can tell a relevant, concise story clearly under mild pressure. Reading does not build that muscle.
There is also a massive structural problem with giant lists. Most questions in any interview are just slight variations on four core things: Can you do the job? Have you done something exactly like it before? How do you behave when everything goes horribly wrong? And why do you want this specific role?
If you prepare four incredibly strong stories that can be angled and pivoted to answer any of those four themes, you have successfully covered more ground than someone who memorized a hundred shallow answers.
The STAR method in four lines
Behavioral questions—the ones that start with 'Tell me about a time when...'—are explicitly asking for a story with a measurable result. The STAR method is a guardrail that keeps your story from wandering off a cliff. Aim for roughly four to five sentences maximum.
Situation — Provide exactly one sentence of context. Where were you, when was it, and what was at stake? Resist the desperate urge to explain your entire company's org chart.
Task — What specifically was yours to solve? Say 'I' here, not 'We.' Interviewers are actively trying to work out what you personally did, not what your team accomplished while you watched.
Action — The two or three steps you actually took, in order. This is the bulk of the answer and the part people rush through. What was your strategy?
Result — What changed? Always end with a number if you have one. If the project went badly, say so immediately and add exactly what you changed afterwards. A failure with a learned lesson scores much higher than a vague, unbelievable success.
How to use this pack as a mock interview
Pick your target role and stage, then run the list once end to end without stopping to polish. Say the answers out loud—not in your head, which is infinitely more forgiving than your mouth. Notice which questions produced a long, awkward pause. Those are the only ones worth a second pass.
On the second pass, write down the first sentence of each weak answer and nothing else. Openings are where people flounder; once you are moving, the rest usually follows naturally.
If you want to be ruthless, record one run on your phone's voice memo app and listen back at normal speed. It is deeply uncomfortable, but it will instantly catch the filler words, the trailing sentences, and the rambling two-minute answer that you thought was only thirty seconds.
Questions worth asking them
The questions you ask at the end of the interview are read as a direct signal of how seriously you are evaluating the job. Two or three highly specific questions always beat a long list of generic ones, and 'I have no questions' is the absolute worst available answer you can give.
The strongest questions are about the reality of the work itself: 'What does the first 90 days look like for whoever takes this role?', 'What would make you say this hire went incredibly well after six months?', or 'What is the part of this role people historically find the hardest?'
Each one gives you information you actually need and demonstrates that you are already thinking about executing the job rather than just getting an offer letter.
Phone screens, panels, and final rounds are different
Preparation the night before should be light. Cramming raises anxiety and rarely adds anything.
- Re-read the job posting and pick the three requirements you will make sure to evidence.
- Have four STAR stories ready — one success, one failure, one conflict, one thing you led.
- Write your two questions down. You will forget them otherwise.
- Confirm the format, the platform, and who you are meeting. Test the link if it is a video call.
- Have one clear sentence for why you are leaving your current role, and keep it neutral.
Frequently asked questions
What are good mock interview questions to practise with?
Start with the four that underpin most interviews: walk me through your experience, tell me about a time something went wrong, why this role, and what are your weaknesses. Practise those aloud before adding role-specific questions.
How do I answer behavioural interview questions?
Use STAR in about four sentences: one line of situation, what specifically was yours to do, the two or three actions you took, and the result. Say “I” rather than “we” so the interviewer can tell what you did.
How many interview questions should I prepare?
Fewer than you think. Four solid stories that can be angled at most questions beat a hundred memorised answers, because almost every question is a variation on four underlying themes.
What questions should I ask the interviewer?
Two or three specific ones about the work: what the first 90 days look like, what would make this hire a success after six months, and which part of the role people find hardest. Leave pay and holiday for the recruiter or the offer stage.
How is a phone screen different from a full interview?
A phone screen is a filter, so keep answers to sixty or ninety seconds and expect questions on experience fit and salary range. Full rounds go deep on your stories and follow up to test whether you really did what you described.