The 10 Most Common Interview Questions and Answers

You have probably seen a dozen lists of common interview questions, and most of them stop at the list. This section names the ten that recur and what each one measures. Read the pairing, not just the question; the thing being measured is what your answer has to hit.

• Tell me about yourself. Can you frame your own history around this job?
• Why do you want this role? Have you read past the job title?
• What are your strengths? Do you know what you are actually good at?
• What is your greatest weakness? Are you honest, and are you working on it?
• Describe a conflict at work. How do you behave when people disagree with you?
• Tell me about a failure. Do you own outcomes or assign blame?
• What project are you proud of? Can you separate your contribution from the team's?
• Where do you see yourself in five years? Is this role a step or a stopgap?
• Why are you leaving your current job? Will you speak badly about people?
• What questions do you have for us? Did you come prepared to evaluate them back?

The last one is the one candidates most often waste. There is a longer treatment of it, and of each question above, in the mock interviews and practice section.

Three structures cover all ten. Behavioral questions (conflict, failure, proud project) take situation, action, result: one sentence of context, two or three on what you specifically did, one on the measurable outcome. Opener questions (tell me about yourself, why this role) take present, past, future: what you do now, the experience that got you here, why this job is the next step. Self-assessment questions (strengths, weakness, five years) take claim, evidence, correction: name the trait, give one example, say what you are doing about the gap.

A backend engineer interviewing for a senior role at a payments company was asked about a failure. She named a rewrite that shipped six weeks late, spent one sentence on the deadline, three on the retry logic she got wrong and how she found it in production, and one on the review step her team added afterward. The interviewer moved straight to a follow-up about that review step, which is the signal that an answer landed.

Aim for roughly 90 seconds per answer. Much shorter reads as thin, much longer buries the point you were making.

Reading a question and working through the answer silently is not practice. The gap between a rehearsed thought and a spoken answer is where interviews are lost: filler words, a buried result, a story that runs four minutes. Say each answer out loud, once, timed.

A solo run works if you record yourself and listen back. A structured mock interview works better because it asks follow-ups, which is where prepared answers usually break. SubcueAI runs practice sessions with an AI interviewer on the mock interview page.

Do not memorize the wording. Memorize which story goes with which question, and let the sentences come out slightly different each time.

During a real interview, SubcueAI listens to the meeting audio and puts a scaffold on a local overlay: the structure to use, the points worth hitting. The desktop app on macOS and Windows captures system audio and your microphone; the browser extension side panel captures the meeting tab's audio only, so it hears the interviewer and never transcribes you. No bot joins the call and nothing is injected into the meeting page.

The limits are real. If you are screen sharing, an overlay is visible inside what you share. Proctored assessments, recorded sessions, and company-managed machines are out of scope, and no tool should be described as universally undetectable. The honest framing is that an assistant keeps a prepared answer organized; it does not supply experience you do not have. Credit costs are on the pricing page.