Platform Architect & Engineering Consultant

Architecture,
put to work.

I’ve spent 18 years building and scaling production software. I design systems, APIs, cloud infrastructure, and the platforms engineering teams rely on—then carry the architecture into implementation.

Open to

Consulting engagements, and senior, staff, or platform architecture roles that combine system design with implementation.

Production engineering

ART19 / 2014–2019

Built from zero.

One of the first three engineers. I helped build the production platform, from application code to distributed synchronization and deployment infrastructure.

ART19 / API production scale

100,000+ requests/minute

I built APIs supporting workloads exceeding 100,000 requests per minute as the system scaled.

Volt Labs / Head of Platform

Millions of SMS messages/day

Most recently Head of Platform, working on the architecture and engineering systems behind Volt’s enterprise messaging platform.

The engineering history behind the work

Technical workstation setup

~1 week → <20 minutes

Ansible automation, observed repeatedly. External accounts and permissions excluded.

Time to first PR

~1 week → ~1 day

Through the broader platform and developer-experience effort at Volt.

Ground adoption

All new services.

A Rust application framework and CLI I designed and built within the broader internal developer platform effort. Used across the engineering team.

01 / Selected work

View all work

Better systems. Faster engineering.

Volt Labs / Ground

A shared starting point for services.

Shared capabilities, conventions, generators, and integration-test fixtures made new services faster to develop and easier to maintain.

Explore Ground

Volt Labs / Developer environments

Setup that stayed useful.

I automated workstation configuration, tooling, databases, and development data. The setup remained in use throughout my time at Volt.

Explore the environment work

Volt Labs / Development & build workflows

Work across services. Build without a dedicated machine.

I led the monorepo migration, preserved project histories, and built the project environments and release workflow the team used.

Explore the workflows

From a technical decision to a working system.

Architecture and design

System and API boundaries, cloud architecture, trade-offs, and a practical path to implementation.

Hands-on implementation

Build production capabilities and integrate them into the systems your team already operates.

Developer tools and experience

Repeatable environments, service foundations, and development and delivery workflows.

Ongoing engineering

Own a defined area of work alongside your team as the system evolves.

Problems and possible engagement outputs

Let’s talk

What do you want to build?

A new system, an API that needs to scale, or a platform that’s getting harder to change. Let’s understand the problem and decide whether there’s a useful next step.

Start a conversation