I would slow the comparison down and make the tradeoff visible. Price matters, but only in the context of what the business can actually tolerate if service slips. So I would compare not just quoted cost, but delivery performance, lead-time stability, quality history, responsiveness, and the operational consequence of failure in that category.
If the cheaper supplier creates a high risk of line disruption, customer impact, or repeated expediting, then they may not really be cheaper. I want the recommendation to reflect total business impact, not just unit price, and I want stakeholders to see that logic clearly before we commit.
The main thing I want the interviewer to hear is that I do not make supplier decisions in a vacuum. I want the recommendation to hold up commercially and operationally, and I want stakeholders to understand why it makes sense beyond the quote sheet.
I also try to keep the internal conversation honest about what can actually be controlled. Sometimes the right move is a supplier change. Sometimes it is a stronger recovery plan or a cleaner internal requirement. The point is to avoid guesswork.
"I would usually choose the cheaper supplier unless there is a major quality issue."
That answer is too vague. It sounds reasonable on the surface, but it does not show how the candidate would actually structure the decision.
It shows sequencing, tradeoff awareness, and practical communication instead of generic procurement language.
easy
easy
easy
easy
easy
easy