Seattle, Washington, United States
As a member of the Spark Post team, I shipped user-facing features, overhauled legacy code, built productivity tools for our content creators, and authored a general-purpose framework called `Workflow`, which ports C#-style coroutines to Objective-C and solves the "retry manager" problem (among many, many other classes of problem).
I also spearheaded a "free-range" platform stability squad commissioned to discover and battle tech debt across the organization in order to speed up developer velocity.
In that role, my mini-team interviewed dozens of Spark contributors, analyzed their knowledge, quantified their recommendations, built a report, designed a remedy program, pitched it to our stakeholders, got approval, and got to work.
We tackled issues like parsing and squashing the backlog of 600 build warnings; refactoring 10,000-line view controllers; reconciling cross-platform modal display code with platform-specific Braze popovers; and other tales too grim to tell.
At one point, I spiked the reimplementation of the Spark Post app in SwiftUI. I was able to build a feature in *seventeen minutes* that had originally taken some of my teammates two weeks to complete.
I left Adobe in excellent standing to pursue SwiftUI greenfield development opportunities.