Tell me about a time you had to convince a group of skeptics and what you did to win them over

In my first few months on a product team, I was working on a small feature that accepted uploads, and I suggested adding a lightweight validation step earlier in the flow. The two engineers reviewing my work were skeptical because they thought it would add complexity for a minor edge case. Instead of just repeating my opinion, I asked what worried them most, and I learned they were mainly concerned about introducing bugs into a part of the feature that was already close to done. I put together a small test version behind a flag and showed that the change was isolated and caught several bad inputs before they reached the later processing step. I also simplified my original version after one reviewer pointed out that I was handling more cases than we actually needed. They agreed to ship the smaller version, and after release we kept it because it reduced avoidable failures without causing issues elsewhere. That experience taught me that when people are skeptical, it's usually better to answer the actual risk they're seeing than to argue harder for the whole idea.

At my last internship, I helped on a small internal dashboard for our operations team, and I suggested changing the way we displayed late deliveries so the most urgent ones would appear first. A couple of analysts pushed back because they were used to the old layout and worried it would make the report harder to trust. Instead of arguing, I sat with them for one morning and watched how they actually used the report, then I built a simple mockup that kept the same data but reordered it by urgency and added a short explanation next to each item. I also asked one of the analysts to compare the old and new views on real cases from the previous week, which helped show that the new version made it easier to spot problems quickly without hiding anything. Once they saw they could still get to the same information and save time during their review, they were comfortable trying it. That experience taught me that people are usually more open to change when they feel heard and can see that their workflow is still respected.