Behavioral interview questions
Stories from your own work, owned in the first person and short enough to leave room for follow-ups.
Questions 1 to 50 of 60.
- Tell me about a project you owned from the first customer conversation to production. Which decisions were yours alone?
- Tell me about a time you worked inside a customer’s environment rather than your own. What was hardest?
- Describe a stakeholder who was quietly working against your project. What did you do before you escalated?
- Tell me about a decision you made that turned out to be wrong. How did you find out, and how fast did you reverse it?
- Tell me about a failure that was your fault. What did it cost, and what do you do differently now?
- Tell me about a time you said no to a customer or senior stakeholder. What did the relationship look like a month later?
- FDE work can mean travel and constant context switching. Tell me how you have handled a sustained period of heavy load.
- Tell me about a time a user or customer showed you something that changed your mind about a technical approach.
- Tell me about a time you automated away work you used to do by hand for a customer.
- Tell me about a time you had to become useful in an unfamiliar domain within a couple of weeks. How did you learn it?
- Walk me through the career decisions that brought you here. Why did you make each move?
- What is the customer outcome you are proudest of, and what part of it was specifically you?
- What is the hardest piece of feedback you have received, and what did you change because of it?
- What is the most technically ambitious thing you took on outside your comfort zone, and how did it go?
- Describe a project where you measured the impact yourself. How did you pick the metric, and what did it show?
- Describe a time a salesperson promised something your team could not deliver. What did you do?
- Describe a time you deliberately chose speed over quality. How did you decide where the line was?
- Describe a time you slowed a project down on purpose because the quality risk was too high.
- Describe cutting scope to hit a date. What did you cut, who did you tell, and how did they react?
- Describe discovering, mid-project, that the customer’s data was far worse than promised. What did you do next?
- Describe shipping exactly what was asked and it still being wrong. What did you learn about gathering requirements?
- Describe shipping under a fixed deadline when important information was missing. What did you assume, and how did you protect against being wrong?
- Describe the most ambiguous assignment you have had. How did you turn it into a plan?
- On your last new project, who were the stakeholders, and which one did you misjudge?
- Tell me about a build-versus-buy decision you drove. What would have changed your mind?
- Tell me about a commitment you missed. When did you tell people, and what did you offer?
- Tell me about a customer request marked urgent that turned out not to be. How did you find out what was really driving it?
- Tell me about a decision you made with too little data. What made you comfortable deciding?
- Tell me about a pattern you noticed across several customers that changed what your team built.
- Tell me about a problem other people had given up on that you solved.
- Tell me about a production incident you led. What did you do first, and why that?
- Tell me about a prototype that ended up in production. What did you have to fix first?
- Tell me about a time you disagreed with a decision, lost the argument and then committed to it. What did committing look like?
- Tell me about a time you disagreed with your manager’s technical decision. What did you do, and what happened?
- Tell me about a time you got a group that did not report to you to hit a date.
- Tell me about a time you had to understand an undocumented system. How did you build your map?
- Tell me about a time you taught a customer’s engineers to run something you built. How did you know they could?
- Tell me about a time you threw away something you had built because it was not delivering value.
- Tell me about a time you were out of your depth technically. How did you close the gap without the customer losing confidence?
- Tell me about a time your personal values were tested at work.
- Tell me about delivering bad news to an executive. How did you prepare?
- Tell me about getting a project through a strict security or compliance review.
- Tell me about getting two teams to agree on a plan when you had authority over neither.
- Tell me about leaving a customer able to run what you built without you.
- Tell me about taking over a customer relationship from someone else. What did you do in the first meetings?
- Tell me about working with a legal or compliance team that slowed you down. How did you work with them rather than around them?
- Walk me through a customer escalation you owned personally, from the first alert to the last follow-up.
- Walk me through a launch that needed engineering, sales and support to move together. What was your part?
- What is the biggest technical risk you chose to take on a project, and how did you limit the damage if it failed?
- Tell me about a decision on an AI project where safety or misuse risk changed what you built.