Data Analyst
Last spring I sent our weekly revenue dashboard to the executive team with a join that double-counted refunds. The number looked seven percent higher than it should have. Two of our VPs cited the figure in a board prep meeting before I caught the error the next morning. The mistake was mine — I had reused a query without re-reading the join logic. I sent a correction email within an hour of finding it, with the corrected number, the cause, and the impact on the prior four weeks. I asked for fifteen minutes with the CFO that afternoon. We walked through what I had changed in the new pipeline. I added a unit test on the refund row count and a second reviewer on any query that touches finance reporting. The board prep got updated cleanly. What I do differently now is, I do not reuse SQL on revenue numbers without re-reading every join from scratch.