I make products for the web, as well as the teams and practices that effectively deliver them.
I've gained a reputation for Design Systems, with a passion for delivering unique and consistent product experiences across devices and surfaces. This extends to both the technical and organizational needs inherent to that level of cohesion.
Most recently, I've been leading the Google Cloud Design System Teams on a mission to completely revamp the console's Design System strategy, technically and organizationally.
I am currently seeking Engineering Leadership roles across companies of all sizes. Take a look at some of my past work, and reach out if you might have a good fit.
TL;DR - Led a multi-year mission to reinvent Cloud Console's frontend strategy by overhauling its Design System approach and surrounding tooling ecosystem.
The Google Cloud Web Console is likely one of the largest enterprise Angular applications in the world, if not the largest, and I led its Design System team, responsible for delivering the right tools for thousands of downstream Google engineers to build feature pages.
The Design System team had taken on an extremely centralized role in frontend development, something that was hurting product-wide velocity, as well as the team itself. Additionally, there was a strong business need to update the styling of the platform to the new, updated guidelines of Google Material, but the platfrom had been unable to do so for years due to millions of lines of existing frontend code.
As the strategic and technical lead for the Design System team, I drove change to reinvent the team and ecosystem, decentralizing UI development for the product in the process.
When I came on the team, it was consistently underwater, with work planning largely being an exercise in largest fire, and a number of efforts underway to try and stem the bleeding.
As TLM, I largely rebuilt the practices and rituals of the cross-functional Design System teams into something that provided stability, value, and reasonable expectations, rather than constant fire drills.
As part of the overall strategy of updating the Design System across the Console to the latest Google Material specifications, I proposed, advocated for, and then drove execution on an overhaul-level Design System migration.
Whereas previous attempts to update the Console depended on brute force solutions and/or manual migrations, this strategy enabled the console to be updated with minimal changes to feature team code, something previously thought impractical.
TL;DR - Managed and drove alongside multiple teams to accomplish cross-functional business goals as the Technical Product Owner for Bandwidth Dashboard's frontend strategy.
The Bandwidth Dashboard is a developer console for Bandwidth CPaaS customers to manage their telephony services and products. I helped to drive this primary frontend touchpoint by unblocking a messy and protracted migration, and then drove our Frontend, Developer Exerience, and Auth teams to accomplish a number of cross-functional goals.
Bandwidth had a centralized frontend team, and that team had been working to incrementally deliver an overhaul of the Dashboard from GWT to React, but architectural issues with co-delivery, as well as a propensity to redesign pages in the process, was killing velocity. Upon joining the team, I successfully lobbied for a pivot to a lift-and-shift style model that enabled us to unblock the work and deliver a full overhaul of the product, after over a year of stalled progress.
Expanding my role into a full Technical Product Owner for the dashboard, I worked with product to deliver a number of meaningful, cross-functional objectives across my three teams.
Bandwidth had historically been utilizing their Java feature developers to code the UI for the dashboard utilizing GWT, but had decided they wanted a more modern frontend stack.
The project to accomplish this had been stalled for some time, as there was an insistence that the new application be incrementally delivered, while the GWT pages continued to run the page chrome and crucial services. I successfully advocated for a more practical approach that enabled a React-only experience, and unblocked the project as a result.
As Technical Product Owner for the console frontend, and a manager of three important cross-functional teams (Frontend, identity/auth, and developer experience), I was able to plan, enable, and execute far-reaching strategic change to the product, including:
TL;DR - Cofounded a B2B Web Infographics product for college/pro sports teams. Drove most aspects of the 10-15 person startup until profitability.
ScoreShots is a sports infographics tool designed to enable Sports Information Directors and other untrained staff to post and schedule templated infographics to social media with live and easy to customize data.
I was the primary architect for the MVP, initial release, and overhauled product that is in use today. During this time I operated as both a lead engineer and CTO, coding many of the crucial features alongside generally running operations, as well as preparing business plans and pitch decks.
In 2021, ScoreShots was sold to athletics conglomerate PrestoSports, and is now their key Infographics product.
ScoreShots Next was a revamp to our existing product that I largely designed and architected. It rebuilt the shaky backend of the product to use GraphQL microservices, as well as redesigning the brand into a consistent look and feel via a Design System.
ScoreShots Video was a cloud rendering pipeleine that enabled web-based video editing from any device. By compiling and utilizing custom ffmpeg binaries in serverless environments, I was able to cheaply and effectively offer on-demand rendering and editing of video graphics, including ones driven by statistics and After Effects motion.