Work / Architecture in practice

Engineering knowledge,
built into the system.

Production APIs and distributed systems at ART19. Platform architecture, developer infrastructure, and operational work at Volt. Concrete contributions, with deeper case studies where the engineering decisions are documented.

ART19 / 2014–2019

From zero to production.

One of the first three engineers, I helped build ART19 from zero. I designed and built frontend and backend systems, distributed synchronization infrastructure, and APIs supporting workloads exceeding 100,000 requests per minute.

I built the pipeline that packaged the ART19 embeddable podcast player’s JavaScript and CSS assets with Node.js, published them to S3, and invalidated CloudFront caches as part of each deployment.

ART19 was later acquired by Amazon in 2021.

My path from application engineering to platform architecture

01 / Internal developer platform

Ground

Stop rebuilding the starting point.

New services required engineers to reconstruct common application plumbing. I designed and built Ground to give business logic a shared technical foundation, including generators and container-backed testing.

Used across the engineering team for all new services. Faster, more maintainable development.

Read the Ground case study

02 / Developer environments

Repeatable workstation setup

Setup should not depend on who you ask.

A polyglot environment made setup slow and troubleshooting interruptive. I automated machine configuration, tooling, databases, and development data with Ansible.

~1 week → <20 minutes for technical setup, excluding external accounts and permissions. The setup remained in use throughout my time at Volt.

Read the developer environments case study

03 / Development & build workflows

Working across services

Make switching projects easier.

Separate repositories, branches, and dependencies made cross-service work cumbersome. I led the monorepo migration, preserved project histories, and built the environments and workflows the team used.

I observed fewer version conflicts and setup questions, easier project switching, and easier cross-service changes. The dedicated build machine was retired.

Read the development and build workflows case study

Volt Labs / Production operations

Performance and visibility.

Aurora PostgreSQL performance.

I led a performance optimization initiative that reduced p99 SQL latency from multiple minutes to under two seconds.

Observability in the service foundation.

I embedded shared OpenTelemetry instrumentation, automatic HTTP request tracing, and structured logging in Ground, giving services a common starting point for understanding production behavior.

Explore the framework behind those conventions

What could make your system easier?

Start a conversation