"Tell me about a time a client wanted a solution that conflicted with your recommended implementation. For example, they wanted to customize a Meta Conversions API integration, Pixel setup, or Ads measurement approach in a way you believed would create risk. How did you handle the disagreement, and what was the outcome?"
This question tests whether you can influence without direct authority in a customer-facing role. For a Solutions Architect at Meta, the interviewer wants to see how you balance client goals with platform best practices, long-term maintainability, measurement integrity, privacy/compliance considerations, and business relationship health. They are also looking for judgment: when to push back, when to offer alternatives, and how you stay accountable even if the client initially resists.
A strong answer uses one specific example with real stakes, such as launch timing, revenue impact, signal quality, or implementation risk. The best responses show that you first understood the client's underlying objective, used data and trade-off framing rather than policy-only arguments, proposed a practical path forward, and stayed engaged through resolution. Use STAR and end with a measurable result plus what you learned.