The complete interview question prep bank

Behavioral questions look infinite. In practice, they cluster into five underlying prompts: leadership, problem solving, conflict, measurable impact, and learning from failure. Prepare one strong story for each category and you will be able to answer roughly ninety percent of the behavioral questions you are asked in any round.

Structure each story as CGARL: Context in one sentence, Goal in one sentence, Action in three to five sentences (always first-person: I did, not we did), Result in one sentence with a number if possible, and Learned in one sentence that hints at self-awareness. The full delivery should run 90 to 120 seconds.

Write each story on one index card. If it does not fit, tighten. Long stories signal disorganization; short precise stories signal seniority.

The most common failure is speaking in the collective. "We shipped" tells the interviewer nothing about you. Practice re-recording your stories with only "I" as the subject until it becomes automatic.

Tell me about a time you led without authority. Tell me about a project that failed and what you learned. Tell me about a conflict with a peer. Tell me about a time you disagreed with your manager. Tell me about a decision you made with incomplete data. Tell me about a time you had to influence someone senior.

Tell me about a time you missed a deadline. Tell me about the hardest feedback you have received. Tell me about a time you had to say no. Tell me about a time you had to change direction late in a project. Tell me about a time you had to work with someone difficult. Tell me about the most ambiguous problem you have owned.

For each of these, decide in advance which of your five stories you will use. The same story can serve two or three prompts with small reframing. What matters is not that the story is perfectly matched — it is that you deliver a real, specific, first-person story with a real result.

"Why did you leave your last role?" "Walk me through your transition." "I see you have been at your last job for X years — what happened?" These are all the same question. Answer it the same way every time.

Reusable script: "My role was impacted by a company-wide restructuring in [month/year]. I am proud of what I built there, and I am now focused on roles where I can bring [two or three skills that map to the job]." Roughly fifteen seconds. Then pause.

If the interviewer follows up — "Was it performance-related?" — answer plainly: "No. Roughly [X] percent of the company was affected, mostly across [function or region]." Then pivot back to the role in front of you. Confidence in this answer sets the tone for everything after it.

Technical rounds — coding, systems design, case, financial modeling, portfolio walkthrough — are not graded primarily on the final answer. They are graded on how you decompose a problem, which assumptions you name, and how you respond when a constraint changes mid-round. Narrate your thinking out loud.

State assumptions first. "I am assuming the read/write ratio is roughly 100:1 and that eventual consistency is acceptable here." This signals seniority even if the numbers later change.

Sanity-check the shape of the answer at the end. "That gives us roughly ten million events per day, which feels reasonable given the user base — let me flag that if the assumption on session length is off by 2x, this number moves proportionally." That single sentence often closes the round on your terms.

If you get genuinely stuck, describe what you would do next with more time or more data, and offer a partial hypothesis. Silence is expensive; visible reasoning is cheap and almost always credited.

Managers screen for two things: whether you can do the job, and whether you will be low-drama once hired. The first is answered by your stories; the second is answered by your body language, your listening quality, and the calibration of your questions.

Prepare three questions specifically for the manager: What does success look like in the first ninety days? What is the biggest gap on the team that this hire is expected to close? How do you make decisions when the data is incomplete? These questions do the double work of demonstrating judgment and giving you real signal about the role.

Skip-level interviewers screen for strategy fit, communication with executives, and whether you will scale with the team's growth. Their questions tend to be broader: How do you think about our market? What would you do in your first six months? What would you change about our public strategy? Prepare short, opinionated answers — not comprehensive ones. Opinions signal seniority.

Peer rounds screen for collaboration risk. They are usually more relaxed in tone and more revealing in signal — a peer will notice if you speak dismissively about past teammates, if you take credit for work that clearly required others, or if you cannot describe a disagreement without turning it into a complaint.

Prepare two peer-specific questions: How does the team make decisions when there is disagreement? What is the on-call or after-hours expectation? What is the one thing about working here you wish someone had told you before you joined? The last question consistently produces the most useful answer of the entire loop.

If you are asked for a salary expectation in an early screen, either name a range wider than you think you need (top of range 20–25% higher than your last comp) or defer politely: "I would love to understand the scope of the role and the full compensation package before naming a number. Do you have a range budgeted for the role?" Two-thirds of the time they will share a range.

Never lie about your current or last compensation. Some states make asking illegal, and many companies verify offers. If a recruiter presses in a legal state, redirect: "I would rather focus on what the role is worth in market terms — my target is [range]."

Ask questions that show judgment: What would success look like in the first ninety days? What problem does this hire need to solve first? How does the team make decisions when the data is incomplete? What is the biggest gap on the team today that this role is expected to close?

Avoid questions whose answers are on the company website. "What do you do?" and "What is the culture like?" waste your best remaining minutes and quietly signal that you did not prepare.

End every round by asking about next steps and timeline. "What are the next steps in the process, and when would you expect to be in touch?" It is a professional courtesy that also gives you honest information about your position.

Send a follow-up note within twenty-four hours. Three sentences. Reference one business priority the interviewer raised, restate in one line how your experience maps to it, and close with a forward-looking sentence. Do not attach anything unless they asked. Do not send the same note to every interviewer — each note should reflect the specific conversation you had.

If a week passes without an update, send one short check-in email to the recruiter. "Just checking in on the [role] process — happy to answer any follow-up questions and looking forward to next steps." One follow-up is professional. Three is anxious.

The goal is not to memorize answers. Memorized answers sound worse than unrehearsed ones because the tone drifts into recitation. The goal is to know your stories so well that you can deliver each one three different ways depending on which angle of the question is emphasized.

Practice out loud. Record yourself once and listen to the playback. It will be uncomfortable and it is the single fastest way to improve. Mock interviews with a peer in your field beat mock interviews with a coach who does not know your field.

Ninety minutes before the interview, re-read the job description, re-read your resume as the interviewer will see it, and pick the three stories you will lean on. Take five minutes of quiet before the call to breathe and reset. Preparation removes friction; presence closes offers.