I'm "über" technical lead overseeing the teams responsible for Alchemy's core API product. In this role I've helped improve reliability, performance, and scale a system that serves billions of requests a day.

My time has been divided between: 1) designing and implementing architectural improvements as an individual contributor, 2) providing feedback to and mentoring other engineers, and 3) horizontal initiatives to improve overall engineering culture and process.

I spent my first couple of years at Okta building and scaling our streaming analytics infrastructure. My contributions ran the gamut of scaling our pipeline by two orders of magnitude in two years and exposing our analytics data via a new customer-facing API.

In the last 3 years I split my time on two objectives: 1) as an individual contributor, improving the resilience and scale of Okta's core Identity offering and 2) as a product owner, guiding resilience, scale, and infrastructure priorities for Workflows, Okta's no-code platform.

Stormpath was acquired by Okta a month after I joined.

I led a 5-person engineering team responsible for LinkedIn's Hadoop-based scheduled communications platform that serves hundreds of millions messages/week. Before that I was part of a 4-person team that designed and built a completely new highly-scalable real-time (Samza-based) holistic communications platform that brought more intelligence to how LinkedIn communicates with its users. In production the system processes 300+ million messages/week. Java/Scala/Samza/Spark/Hadoop/Linux.