I move AI past the demo. Recommendation engines that lift AOV, chatbots that scale support, regression-correlation tools that tell engineers which PR broke the build, sales-intelligence dashboards that surface revenue anomalies before the next QBR. Not experiments — production systems that pay for themselves.
Engineering velocity is a system, not a vibe. I instrument it, find the bottleneck, automate the fix, and repeat. I treat developer experience as a product — measured, iterated, shipped.
Remote-first isn't a perk — it's an operating model. I've led ~40 people across multiple continents with structured onboarding, async-first communication, and the kind of documentation that turns surprise into routine.
Every server I've owned is reproducible, observable, and automated. Terraform, Ansible, Packer, CI/CD pipelines — and migrations done while the lights stay on.
I meet people where they are and give them runway to grow into roles they didn't think they could fill. The best work I've done is the team I'm not in the meeting for.
Established new engineering processes: 63% cycle time reduction, 56% lift in merge frequency. Introduced AI into the fabric of the company.
Led all software initiatives for a SaaS application on AWS.
Led developers building advertising tools for the real-estate industry on Rails 5.1.
Self-employed contract work — multiple clients
Built a first-of-its-kind clinical decision-support web service used by hospitals and oncology clinics nationwide.
First role out of school. Ruby on Rails 3.2, Redis, Riak, MySQL.
I make architectural decisions that pay interest for years — not the one that ships fastest this quarter and rots by the next.
Hiring, coaching, the calibration of expectations, the design of the SDLC — those compound harder than any framework choice.
Executives who stop reading code stop understanding their leverage. I read PRs, write spikes, and unblock people directly.
If it doesn't change a workflow or a P&L line, it's a demo. I ship the ones that do.
Measure cycle time, throughput, and developer happiness. Iterate on them with the same rigor as you'd ship a feature.