Portland, Oregon · open to new work

I lead the product.
I write the code.

For nine and a half years I was the only product lead on one platform, and I held product through adoption, through its infrastructure, and through the company built around it. Since AI made it reachable I have written the code too. I have built a national data pipeline of 176 scrapers with an LLM extraction layer across 18 AWS CDK stacks, an app in both stores, and a generation platform in about sixteen days, all of it solo.

Covered by

I see the whole machine

I can hold a system in my head and watch it run. That part has never changed job titles.

What changed is that I write the code now, and I do it with models in the loop and say so. 84% of the commits on the data pipeline carry an AI co-author trailer. I was early to it and I have not stopped.

The product half

  • Nine and a half years as its only product lead across three surfaces, from a three-site pilot to fifteen states: roadmap, go-to-market, and the regulatory posture underneath both
  • 290-issue backlog authored personally, median 35 days to close, RICE scoring automated into GitHub Projects
  • Built the in-house engineering function after an eight-year agency relationship wound down

The technical half

  • Ran a school’s whole network at 16 Exchange, the website, and 200 endpoints (on payroll, with master keys). Then sysadmin, then a decade-old homelab
  • SQL reads like English I built the platform’s first Athena data lake and Metabase reporting layer
  • Writing production code since AI and early to it: 473 merged pull requests on the platform, 18 CDK stacks operated solo, 72 releases of a mobile app across two stores

Three titles,
one system

Product was in my hands for all three titles. Running the infrastructure in the middle is why the cost of a decision is not something I have to go ask about.

  1. Adoption 2017

    Learn what it has to be

    First full-time employee on a product nobody had adopted yet. Client Adoption Lead, which meant standing in the room, watching what people actually did, and finding out what the software had to be.

  2. Infrastructure 2018

    Then run the machine

    Director of DevOps for three and a half years: the unit economics of every message, the vendor relationships, and one roadmap keeping three government entities and two of the city’s largest food nonprofits aligned, while product never left my hands. That is why the software held without a rewrite when 2020 turned a booking tool for three sites into how New York City ran its emergency food lines and message volume rose 474%.

  3. Product 2022

    Then own the whole thing

    Co-Founder and Product Director through 2026: strategy, the federally regulated eligibility rules in five states, and a 290-issue backlog authored personally at a median 35 days to close. Somewhere in there the tooling caught up and I started shipping the code myself.

Selected work

All work

Plentiful · 2017–2026

1.3 million people book a grocery pickup instead of standing in a line.

The Plentiful directory: a map of the United States covered in pantry pins, beside a list of pantries showing their next reservation and line times.
The public directory. 3,000+ provider locations, nine languages.

For people getting food

The Plentiful app listing nearby pantries with their reservation times. The Plentiful app's Pick visit time sheet, with selectable appointment slots.

Find a pantry, book a time, walk in at that time. Web, iOS and Android — and the whole flow over plain SMS for everyone without a data plan.

For people handing it out

The pantry app checking a visitor in by scanning their Plenti-Pass QR code.

Check people in by Plenti-Pass, run the schedule, and complete federally regulated eligibility paperwork. Web, tablet, and a self-service kiosk on roughly $150 of POS hardware.

21M+ visits · 1.3M+ people · 15 states · nine languages

See how it works
  • For The Greater Good

    It has no screen. 176 scrapers across 42 states, an LLM extraction layer, and 63,351 verified locations at the far end.

  • The ClaySmasher analytics screen, charting hit rate across recent sessions.

    ClaySmasher

    No account, no backend, no telemetry. Ten disciplines scored stand by stand, and every session stays on the phone.

  • imagen

    419 commits in about sixteen days, on a GPU in my house. The dog is the demo.

Plentiful and Plenti-Pass are trademarks of Plentiful, Inc. Screenshots are from its public App Store listing and plentiful.org, shown to illustrate work performed 2017–2026. This site is not affiliated with or endorsed by Plentiful, Inc.