im·a·cto

$ 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.

understand what to buildbuild it
sales eng Limelight 2006 pm / qa Viddler 2007 solutions arch Unicorn 2009 director, pm KIT 2010 founder Resipsa 2011 team lead iTriage 2012 cto Brandfolder 2014 vp eng Comm.Tribe 2016 cto GigSmart 2018–26 fractional · caio now 2026→
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.

GigSmart

Chief Technology Officer
REV A
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

elixirreact-nativegraphqlterraformgcprobust-ci

CommercialTribe

VP, Engineering
REV B
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

kubernetesgcpruby on railsgithubcircle-ci

Brandfolder

Chief Technology Officer
REV C
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 railsgogcp

iTriage / Aetna

Technical Product Owner · Team Lead · Sr Developer
REV D
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 railsdistributed-systems
Resipsa LawFounder, Developer

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.

2011 — 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 — 2011
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 / QA 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
© 2026 — written by a human, with help, and said so canonical jasonwaldrip.com · delivered through The Bushido Collective