Some languages prefix every variable with a dollar sign. Look closely at your code, and you might uncover real revenue.
Retrofitting attribution at Neighborhoods
At Neighborhoods we spent millions on paid acquisition, but the team had never intentionally connected revenue back to a user's point of entry. Working with data science on our BigQuery data and logs, I was able to retrofit attribution for over 95% of customers. We recovered campaign and keyword level ROI data where previously there was none.
Thirty wearable integrations instead of four
At Lumen we knew that fitness oriented users had the best LTV/CAC, but existing and potential users were often disappointed that we didn't have integrations with their favorite wearables such as ŌURA and WHOOP. At the time we had only four first-party integrations, and each new one required significant engineering resources. I initiated a partnership with a third-party aggregator and within a few months we had integrations with over 30 of the most desirable fitness and health trackers.
It was a true win-win-win. Users got the integration they were waiting for, and the enriched data made their Lumen service more accurate and personalized. Lumen got increased engagement and LTV, while the inflow of correlated activity data increased the research and enterprise value of Lumen's metabolism data.
Instrumentation turned latency into money
I love instrumentation and measurement. Once we got Datadog APM and tracing throughout our Lumen app it was clear that performance was affecting both SEO and ecommerce conversion rates. I saw that an old misconfiguration in the Docker container was causing the code to be run inefficiently, while traces revealed that many database queries could be safely cached in Redis. Weighing up effort vs latency gains, we systematically eliminated bottlenecks, shifting load from servers to cheaper and more flexible caching layers. We achieved 80% reductions in p50 latency, all while reducing our AWS bill.

Why you stay close to the tech
None of these high impact projects was on a roadmap, but that's why you need to stay close to the tech even as you rise in seniority. The breakthroughs only present themselves if you understand the needs of the business from first principles, yet are also close enough to the code to notice the opportunities.