Behavioral questions

Apple

Tell me about a time you had to stop a project.

BehavioralLast seen Oct 31, 2026 · Software engineer
AmbiguityPrioritization

What they're looking for

The interviewer wants to see that you can make a hard call when the facts are unclear, and that you can let go of work you already invested in. A strong answer shows how you decided the project was no longer worth it, how you weighed what else the team could do with the time, and how you told people.

What works

  • Pick a project you had real input on stopping, not one that was cancelled far above you.
  • Explain what signal made you doubt the project, such as a missed metric, a changed need, or a cost that kept growing.
  • Show that you looked at the alternatives and the cost of continuing, not just that you felt uneasy.
  • Say how you shared the decision with the people who worked on it and what you did with their work.
  • End with what the team did next and what you now check earlier in a project.

What hurts

  • Telling a story where the project simply died and you had no part in the decision.
  • Blaming the people who started it instead of explaining the tradeoff.
  • Skipping how the team felt about stopping, which makes you sound cold.
  • Describing a stop that was obvious from day one, so no real judgment shows.

Sample answer

Think of your own story first, then compare.