Tell me about a time you gave an unfavorable solution to solve a problem.

In my last internship, a teammate asked if we could add a few extra filters to an internal dashboard right before a demo. After looking at the code and testing it, I realized the current data source was already inconsistent in a few cases, so adding more filters would make the results look precise when they really were not. I told my mentor and then explained to the teammate that I did not think we should add the new filters yet, even though that was disappointing because they wanted to show more flexibility in the demo. Instead, I suggested we clean up one high-value filter and add a note about the others being planned, and I helped make that smaller change the same day. The demo went smoothly, and afterward we fixed the data issue properly before expanding the feature.

At a small fintech where I was a junior engineer, we found a subtle rounding bug in a new payment flow the morning a marketing campaign was scheduled to go live. The product lead wanted to push ahead to meet the deadline, but I recommended we delay the launch and roll the change back rather than risk letting incorrect charges reach customers. I walked the team through the scenarios where balances could be off and explained that a temporary delay would protect user trust and avoid complicated refunds later. The engineers and product manager agreed, I helped implement the rollback and draft a short customer notice, and we fixed the root cause in the next few days. It was disappointing to miss the campaign, but avoiding real money errors felt like the right trade-off for our users and the company’s reputation.