Michael Gifford-Santos

Michael Gifford-Santos

AI / founding product engineer

I build AI products end to end — the agents, the infrastructure, the interface, and the brand.

Seattle — relocating to the SF Bay Area

imagine.
See the work

Built and operating

All work, including Drydock, GentlePrep, Span and E Pluribus →

100sof K-12 schools across 15+ states, served by a team that never exceeded two engineers
2systems open-sourced — agent-session infrastructure (MIT) and a distributed inference protocol (Apache-2.0)
~30services operated on k3s — blue/green deploys, runbooks, written postmortems
4apps live in the App Store and Google Play

How I work

Startup instinct, design and production engineering — three things that rarely sit in one person. Engineer #8 at one company, first hire at the next, co-founder at the last. I set the brand and the interface, build the systems underneath, and operate them after launch: nothing is lost translating between how it looks, how it works, and who gets paged when it breaks. Speed comes from orchestrating AI agents that build, test and validate, recursively. The stack is whatever the problem needs.

Product design · Brand identity · UI/UX · Full-stack & mobile · Voice interfaces · Distributed systems · AI-orchestrated development

Previously

  1. 2021–24

    Ordo — founding engineer & first hire · built and owned the payments path, six-figure weekly volume

  2. 2020–21

    Ensembl — full-stack engineer

  3. 2017–20

    Center — senior SDE, Center Expense · acquired by American Express

  4. 2012–17

    Dodecki — founder & CEO

Why

Fire, agriculture, the industrial revolution — the short list of things that changed what it costs to be human. AI belongs on it, and unlike the others it is arriving in years, not centuries. What it makes possible is the Star Trek premise: abundance, and the end of work nobody should have had to do. We get to build that, now, while it is still being invented. I have never been more excited to be an engineer.

If you are building something in this space, I would like to hear about it — roles, contract work, or an argument about how any of this should be done. Get in touch →