$ cat works/arc.md

Works

I started at the edge, in the room with customers at a CDN, learning what they actually needed. Then I spent twenty years moving closer to building it myself. Sales engineer, product, QA, team lead, CTO. Each step a deliberate move from understanding the problem to owning the solution. Not a ladder I climbed. A path I chose: pair knowing what to build with the ability to actually build it.

$ curl -O resume.pdf · the one-pager, generated from this page

understand what to buildbuild it

proximity to building twenty years

the arc Each step added a verb: present, define, build, scale, hire. Eventually they were all one role. Now I point a fleet at the next one. Hover a node.

Phoneware

Director of Technology · Fractional

REV A
2026 —

# the mandate

Own the technology direction for a UCaaS provider whose customizations had outgrown how they were built: portal features living in per-customer JS bundles, app backends stranded in n8n flows. Put it on rails that scale past any one person.

# what I built

Phoneware Edge: a TypeScript monorepo that replaces the pile. One global bootstrap, a manifest API that cascades reseller → domain → role, a super-admin configurator, and the feature modules it loads, plus MCP servers for the platforms underneath so the fleet can drive them.

# how I built it

AI-native from day one: agent guides in the repo, a workboard the fleet actually tracks, canary targeting so changes land safely, Terraform and GitOps under all of it. Build the tracks, then let the train run.

# stack

typescript — engineering choice monorepo — engineering choice gcp — engineering choice terraform — engineering choice gitops — engineering choice the-agent-fleet — engineering choice

The Bushido Collective

Founding Partner · Fractional Technology Leader

REV B
2022 —

# the mandate

Strategic technology leadership, AI-applied. Clients hold the destination; we hold the map: how the technology, the team, and the business fit together, why they're built that way, and where they bend. Founding-level operators for companies AI is forcing to modernize. Started nights-and-weekends in 2022; the whole job since 2026.

# what I built

The collective and the rails under it: a code (the eight virtues of bushido, rewritten for building software), open tooling like han and kasoku, and hands-on engagements like Phoneware. The map gets written down and kept current, so the knowledge never walks out the door.

# how I built it

AI-applied, not AI-theater. AI runs inside delivery as an operating model, and the judgment to direct it is the whole point. Outcomes, not hours: flat retainers, measured on what ships and what gets prevented. Twenty years of verbs (present, define, build, scale, hire) in one role, pointed at whoever needs it.

# stack

claude-code — engineering choice the-agent-fleet — engineering choice autonomy-with-guardrails — engineering choice write-it-down — engineering choice typescript — engineering choice rust — engineering choice

GigSmart

Chief Technology Officer

REV C
2018 — 2026

# the mandate

Build the platform and the team from nothing. A gig-marketplace with product vision and no engineering org. Hire, architect, and ship something that could carry real users, fast.

# what I built

An end-to-end platform: Elixir backend, two React Native apps, 0→2 apps in eight months with a team I hired and led, plus the development experience and release path underneath it.

# how I built it

Chose Elixir because a real-time marketplace is a concurrency problem: fault isolation by default, not bolted on. Invested in the dev experience and release path first, on purpose. The team only moves as fast as the rails it runs on. Kept it senior where the system was load-bearing, and pushed for process that produced velocity, not theater.

# stack

elixir — engineering choice react-native — engineering choice graphql — engineering choice terraform — engineering choice gcp — engineering choice robust-ci — engineering choice

CommercialTribe

VP of Engineering

REV D
2016 — 2018

# the mandate

Own engineering on the executive team: raise scalability, quality, and speed, and make a split onsite/remote org function as one.

# what I built

Re-laid the foundation: migrated to GCP and Kubernetes and replaced a weeks-long release cadence with automated testing and deploys that shipped in hours, across onsite engineers and a remote team in Argentina.

# how I built it

Kubernetes wasn't résumé-driven. It was the cheapest path to stability at our load. The release-time collapse mattered more than any feature: weeks-to-hours is the difference between a team that learns and one that guesses. Fix the tracks, and velocity stops being a fight.

# stack

kubernetes — engineering choice gcp — engineering choice ruby on rails — engineering choicegithubcircle-ci

Brandfolder

Chief Technology Officer

REV E
2014 — 2016

# the mandate

Rescue a product in trouble, then make it enterprise-ready. I walked in to a product crashing on a memory leak. Stability and uptime had to come before anything else could scale.

# what I built

Stopped the bleeding first: tracked down the memory leak taking the product down and got it stable. Then built the team and the product around it. Hired and trained a team of six, drove $500K+ net new revenue, and scaled to 100+ enterprise customers, migrating to Google Cloud for cost, control, and performance.

# how I built it

The one I still tell: Ruby crashed generating large zip files. Wrong tool for heavy IO. Instead of throwing hardware at it, we built the zip pipeline in Go, delivering multi-gigabyte archives at minimal cost. Right tool for the actual problem. That's the whole job in one decision.

# stack

ruby on rails — engineering choice go — engineering choice gcp — engineering choice

iTriage / Aetna

Architect & Technical Product Owner · Sr Developer & Team Lead

REV F
2012 — 2014

# the mandate

Drive architecture and delivery for a consumer health app at real scale, and grow the engineers around me while doing it.

# what I built

Led a cross-platform team that shipped several major features, making the distributed-systems calls that kept the product ahead of consumer demand as the org grew.

# how I built it

Where I learned scale is a systems-design problem before it's a code problem, and that the most durable thing a senior engineer ships is other engineers. Mentored through pairing, not lectures: teach the principle, not the patch.

# stack

ruby on rails — engineering choice distributed-systems — engineering choice

Resipsa LawFounder

Built a legal-practice SaaS on a near-zero-cost architecture; beta'd with real firms to shape requirements. First time owning the whole thing, problem to product.

2012

KickApps / KIT DigitalDirector, Product Management

Led product for a globally distributed team across NYC, Paris, and Denver. Closer to the build, specifying what got made, not just selling it.

2010 — 2012

Unicorn MediaManager, Solutions Architecture

Built web tooling to support sales and implementation, turning client feedback into product requirements. The step where I started making the thing, not just scoping it.

2009 — 2010

ViddlerProject Manager

Ran an international engineering team on Agile/Scrum; built the QA practices that kept releases stable and on schedule. First time inside the build, not outside it.

2007 — 2009

Limelight NetworksSales Engineer

The edge. Technical lead in the sales motion for a global CDN; helped land Blizzard, YouTube, Disney, Rockstar. Where I learned what customers actually need, which is where the whole path started.

2006 — 2007