Interviewers ask a small, repeating set of questions because they are proxies for a handful of real doubts: can you do the job, will you show up and do it well, and will working with you be a net positive. Underneath 50 phrasings sit maybe six real questions, and once you see the pattern, preparation stops being about memorising 50 answers.
Below are the interview questions you will meet most often, grouped by what they are actually probing, with a preparation method built from your own projects rather than scripts you will forget under pressure.
Key takeaways
- Every common interview question belongs to one of six families: behavioural, motivation, competence, culture, curveball, or the questions you ask back.
- The families matter more than the exact wording. "Tell me about a conflict with a colleague" and "describe a time you disagreed with your manager" are the same question in different clothes.
- A one-line note per question below tells you what it is really checking for, so you can prepare the substance instead of guessing at phrasing.
- An answer bank built from 6 to 8 real projects covers nearly all of these questions, since most behavioural and competence questions can be answered from the same stories, retold with a different emphasis.
- Practising out loud against the actual job description catches the gap between knowing an answer and saying it under pressure. An AI coach that has read your CV and the JD can run this like a real interview.
Why interviewers keep asking the same questions
Interviewers are not being unoriginal when they ask "tell me about yourself" for the thousandth time. These questions survive because they are efficient, a single well-chosen question can surface competence, self-awareness, and communication style all at once.
The repetition also has a practical cause: most interviewers are not trained interviewers, they are specialists asked to run a 45-minute conversation and make a judgement call, so they reach for questions they have heard asked of them, or questions from a shared internal list. The result is a small, converging set of standard prompts, with local variation in wording but not in substance.
That convergence is good news for preparation. You are not preparing for 50 unpredictable questions, you are preparing to demonstrate a handful of things, competence, judgement, motivation, fit, then recognising which family a question belongs to so you can pull the right material.
The 6 question families
Behavioural. Questions that ask for a specific past example, signalled by "tell me about a time" or "describe a situation." These test whether you can turn a real experience into a clear, structured account.
Motivation. Questions about why this role, company, or move. These test whether you have actually thought about the decision or are treating this as one of many identical applications.
Competence. Direct questions about your skills or how you would approach a problem. These test whether you can do the job, sometimes through a hypothetical, sometimes through a role-specific probe.
Culture. Questions about how you work with others or fit the team. These test compatibility, not raw skill, and are often where strong candidates get rejected for reasons that have nothing to do with ability.
Curveball. Unusual or deliberately uncomfortable questions. These test composure and thinking under pressure more than the literal content of your answer.
Reverse (questions you ask). The questions you ask at the end. These test whether you have been paying attention and are evaluating the company as seriously as it is evaluating you.
The 50 questions
Behavioural
| Question | What it's really probing |
|---|---|
| Tell me about a time you failed. | Whether you can own a mistake without spiralling into excuses. |
| Describe a conflict with a colleague and how you resolved it. | Your default conflict style under real stakes. |
| Tell me about a time you missed a deadline. | How you handle pressure and whether you communicate problems early. |
| Give an example of when you had to persuade someone. | Influence without formal authority. |
| Tell me about a time you disagreed with your manager. | Whether you can push back respectfully or just comply or clash. |
| Describe a project that didn't go as planned. | Adaptability and honest self-assessment. |
| Tell me about a time you went above and beyond. | What "above and beyond" means to you, calibrated against effort you actually spent. |
| Describe a time you had to learn something quickly. | Speed of ramp-up and comfort with not knowing. |
| Tell me about a time you received difficult feedback. | Whether feedback changes your behaviour or just your mood. |
| Give an example of a time you took initiative. | Whether you wait for instructions or spot gaps yourself. |
Motivation
| Question | What it's really probing |
|---|---|
| Why do you want this role? | Whether you have a specific reason or a generic one. |
| Why do you want to work here? | Whether you researched the company or are applying broadly. |
| Why are you leaving your current job? | Red flags around conflict, integrity, or unrealistic expectations. |
| Where do you see yourself in five years? | Whether this role is a genuine step or a stopgap. |
| What are you looking for in your next role? | Alignment between your stated priorities and what this job offers. |
| What do you know about our company? | Basic diligence, filters out mass-applied candidates fast. |
| Why should we hire you over other candidates? | Whether you can state your value without deflecting or overselling. |
| What's your ideal work environment? | Compatibility with how this team actually operates. |
Competence
| Question | What it's really probing |
|---|---|
| Walk me through your resume. | Narrative coherence across your career, not a list recital. |
| What are your greatest strengths? | Self-awareness, and whether the strength is relevant to this job. |
| What is your biggest weakness? | Honesty calibrated against self-sabotage, a real weakness with a real mitigation. |
| How do you prioritise when everything feels urgent? | Judgement under competing demands. |
| How would you approach [a specific problem in the role]? | Applied thinking, not memorised theory. |
| Describe your process for [a core task in the role]. | Whether you have an actual method or improvise every time. |
| What tools or methods are you most comfortable with? | Fit with the team's existing stack and ways of working. |
| How do you stay current in your field? | Whether learning is active or incidental. |
| Tell me about the most complex project you've worked on. | Ceiling of difficulty you can actually handle. |
| How do you measure success in your work? | Whether your definition of success matches the team's. |
Culture
| Question | What it's really probing |
|---|---|
| How do you handle ambiguity? | Comfort operating without a full spec, common in fast-moving teams. |
| Describe your ideal manager. | What kind of oversight you need, and whether this manager can give it. |
| How do you handle working with someone whose style is very different from yours? | Flexibility versus rigidity in collaboration. |
| What does good teamwork look like to you? | Whether your definition matches how this team actually operates. |
| How do you handle receiving criticism in front of others? | Emotional regulation under a specific, common workplace stressor. |
| Tell me about a time you had to give unwelcome feedback. | Directness balanced with tact. |
| How do you approach onboarding into a new team? | Whether you integrate proactively or wait to be shown everything. |
| What's a workplace value that matters most to you? | Alignment with how this company actually behaves, not just its stated values. |
Curveball
| Question | What it's really probing |
|---|---|
| If you were a colour, what colour would you be? | Composure with an odd, low-stakes prompt. |
| What would your last manager say is your biggest weakness? | A second angle on self-awareness, harder to script. |
| How many [objects] would fit in this room? | Structured estimation under pressure, not the actual number. |
| What's a belief you hold that most people in your field disagree with? | Independent thinking versus consensus repetition. |
| If you had unlimited resources, what would you build? | Genuine interest and imagination, read for how it connects to the role. |
| What's something you've changed your mind about recently? | Intellectual flexibility. |
| Sell me this pen (or an equivalent object in the room). | Composure and persuasion on the spot, not sales technique. |
Reverse (questions you ask)
| Question | What it signals about you |
|---|---|
| What does success look like in this role after six months? | You are thinking about outcomes, not just getting hired. |
| What's the biggest challenge someone in this role would face right now? | You want the real picture, not the pitch. |
| How has this role or team changed in the last year? | You are evaluating trajectory, not a static snapshot. |
| What's your favourite part of working here? | Genuine interest in the interviewer as a person, and it usually gets an honest answer back. |
| How do you evaluate performance for this role? | You want clarity before you commit, a fair, practical question. |
| What made you decide to join this company? | Turns the interview briefly two-way, and often surfaces useful detail. |
| Is there anything about my background that gives you pause? | Confidence, and a rare chance to address an objection live. |
How to build an answer bank from your real projects
Trying to prepare a distinct answer for 50 questions is the wrong approach, memorised scripts fall apart the moment a question is phrased slightly differently from how you rehearsed it. The better approach: build a bank of 6 to 8 real projects, each detailed enough to answer several questions depending on the angle asked.
Pick projects that cover a spread: one where something went wrong, one where you led without formal authority, one with a measurable outcome, one involving conflict, one where you learned fast, one you are simply proud of. Write down the situation, what you did, and the outcome for each. The same project that answers "tell me about a time you failed" can answer "describe your process" from a different angle, since it is the same material, framed for what the question actually asks.
This is the same grounding principle behind tailoring a CV: your real experience is the fixed source of truth, and what changes is which part of it you surface for the audience in front of you. A project library that already holds the scope and outcome for each piece of work makes this fast, since you are not reconstructing the story from memory the night before. For the mechanics of turning one story into a clean answer, the STAR method breakdown covers structure, and if the opening question is the one giving you trouble, the tell me about yourself guide covers it specifically.
Practising with an AI coach that knows your CV and the job description
Reading this list and mentally rehearsing answers is weaker practice than saying them out loud, and that is weaker again than being asked a follow-up you did not expect. Interviews are conversations, not recitals, and the skill actually tested is whether you can think clearly when someone pushes back on your first answer.
RecastCV's interview prep coach is built around this gap. It reads your CV and the job description you are preparing for, then runs a practice conversation grounded in both, asking the questions most likely for that role and following up the way a real interviewer would, pushing on the parts of your answer bank that are thin for this specific job.
The day-before checklist
- Reread the job description once, noting the two or three requirements it emphasises most, these are most likely to come up in competence and motivation form.
- Pick your strongest 3 projects from your answer bank and re-read your notes, do not rewrite them from scratch the night before.
- Prepare 3 reverse questions from the list above, specific to this company, not generic ones.
- Say your "tell me about yourself" answer out loud once, timed, aiming for 60 to 90 seconds.
- Confirm logistics: link or address, interviewer names if you have them, and what to bring.
- Get a full night's sleep over one more hour of rehearsal, fatigue undermines composure more than an unpolished answer.
Frequently asked questions
What are the most common interview questions asked across almost every job?
"Tell me about yourself," "why do you want this role," "what are your strengths and weaknesses," and at least one behavioural question phrased as "tell me about a time when" are close to universal. Strong, honest answers to these four alone cover a large share of what most interviews open with.
How many interview questions should I actually prepare for?
Rather than 50 separate answers, prepare 6 to 8 real project stories that each cover a different angle: failure, leadership, conflict, a measurable result, fast learning, a piece of work you are proud of. Most behavioural and competence questions can be answered from that bank, retold with a different emphasis.
How long should my answers be in an interview?
Most answers should land between 60 and 90 seconds. Behavioural answers using a clear structure can run slightly longer if the story needs it, but past two minutes without a specific prompt to elaborate, you have likely lost the thread of what was asked.
Should I memorise word-for-word answers to common interview questions?
No. Memorised scripts fail the moment a question is phrased differently from how you rehearsed it, and they sound rehearsed even when they land correctly. Prepare the substance, the real situation, action, and outcome, and let the wording come out naturally each time.
What should I ask the interviewer at the end?
Ask something specific to the role or team, not a generic question you could ask anywhere. "What does success look like in this role after six months" and "what's the biggest challenge someone in this role would face right now" both signal genuine engagement.