IntermediateBEHAVIORAL
Describe a situation where a non-technical stakeholder (e.g., product, marketing, or business) pushed for a UI or UX decision you disagreed with. How did you handle that conversation, and what was the final outcome?
Frontend Developer
General

Sample Answer

On a previous project, marketing wanted a full-screen pop-up modal collecting emails the moment users landed on our pricing page. I was worried it would hurt conversion and feel really intrusive. Instead of just saying no, I pulled data from Hotjar and Google Analytics and showed that similar full-page modals on our site had a 65% close rate and a 12% higher bounce rate. I proposed an alternative: a smaller slide-up panel that appeared after 20 seconds or on exit intent, and we A/B tested both versions across ~40k sessions. The intrusive modal performed worse: +9% bounce and –6% trial signups. The slide-up version actually improved email capture by 18% with no meaningful impact on signups. Because I framed it as an experiment, not a battle of opinions, marketing felt heard, we made a data-informed decision, and the test results became a pattern we reused on other campaigns.

Keywords

Used data and prior analytics to challenge a proposed UX patternSuggested an A/B test instead of a hard no to maintain partnershipMeasured concrete outcomes on bounce rate, signups, and email captureTurned the result into a reusable pattern for future campaigns