"What engineering methodologies are you most familiar with, and tell me about a specific time you applied one to lead a team through a real project. Why did you choose that methodology, how did you adapt it to the situation, and what was the outcome?"
This question is not really about whether you can list Agile, Scrum, Kanban, or Waterfall. It tests whether you understand how engineering processes actually help teams deliver under real constraints. Interviewers want to see judgment: how you matched a methodology to the problem, handled ambiguity or resistance, and took ownership when the process needed adjustment.
Strong candidates show that methodologies are tools, not dogma. They explain the business context briefly, describe how they influenced the team or stakeholders, and show how they balanced delivery speed, quality, and coordination.
A strong answer uses one concrete example, not a tour of every framework you've seen. The best responses explain the situation, the trade-offs, the specific practices used, how the candidate led or influenced adoption, and a measurable result. Bonus points if you mention what you changed once you realized the textbook version of the methodology was not enough.