Describe a situation where you made an important business decision without consulting your manager.

In my first year, I was working on an onboarding flow when I noticed support tickets from trial users who were getting stuck at the payment step. My manager was in an all-day offsite, and the release with a new reporting feature was scheduled for that afternoon. I checked the ticket volume, confirmed with the on-call engineer that the issue was current, and realized the reporting feature was much less urgent than fixing onboarding, so I asked to hold my part of the release and spent the day on a safe fix. I sent my lead and manager a note explaining the tradeoff, the expected customer impact, and my rollback plan if the fix behaved badly. The fix reduced the ticket volume over the next two days, and my manager later told me the important part was that I acted within a clear customer-impact principle instead of waiting for permission.

At my previous role building features for a K–12 learning app, I noticed our error logs included unredacted student identifiers and the logs were being shipped to a third‑party aggregator. My manager was out at a conference and I couldn't reach them, but I knew exposing student data could violate our privacy policy and harm our users. I quickly pushed a small change to mask identifiers in the logging function and flipped the aggregator export off in our configuration, then opened a ticket describing the risk, the exact code change, and a plan to run a short audit of other loggers. I also emailed my manager and the privacy officer to explain what I did and why, and left the change behind a feature flag so we could revert it if needed. The fix prevented further sensitive data from leaving our systems and the team later used my ticket to build a permanent, automated log-redaction check.