Tell me about a time you disagreed with a cross-functional partner.

On a recent feature, our designer wanted to include several extra error states before launch, and I was worried we were adding risk when the main flow still needed testing. Instead of just saying no, I asked if we could talk through what problem they were most concerned about. I learned they had seen users get confused in a similar flow, so their goal was reducing drop-off, not adding polish. I suggested we implement the two highest-risk states now and capture the rest for the next iteration, and I put together a quick example so we could compare effort and user impact. We launched on time with those changes, and afterward the designer started pulling me in earlier when we were scoping edge cases.

On a project to improve onboarding metrics, a data analyst asked that we include users' email addresses in event payloads so they could join datasets more easily, but I was uncomfortable putting PII into our analytics stream. I explained the privacy and compliance risks and asked what joins they actually needed so I could understand the use case rather than just saying no. They wanted quick joins, so I proposed sending a one-way hashed identifier plus account-creation timestamp so they could link records without raw emails. I built a small helper to compute the hash consistently on the backend and added a short note to the tracking docs showing how to reproduce joins. We delivered the metrics the analyst needed, kept PII out of the pipeline, and the docs helped them onboard two more experiments without requesting sensitive data.