Developer Experience @ impact.com · Columbus, Ohio
I work where product strategy, developer experience, and AI-native systems meet.
At impact.com, I focus on the systems around software delivery: developer tooling, platform adoption, CI/CD, and AI-assisted workflows. The goal is simple even when the systems are not — reduce cognitive load, shorten the path from idea to production, and give engineers more time for the work that requires judgment.
I am also a hands-on builder. I use Python, APIs, automation, and agentic development workflows to turn product ideas into working systems. Building keeps my product judgment honest: architecture, edge cases, observability, and maintenance all become real before they become roadmap promises.
| Project | The problem | What is interesting about it |
|---|---|---|
| HealthOS (private, in active development) | Personal health data is abundant; useful decisions are not. | A privacy-first health intelligence system designed to fuse Garmin and HealthKit data into context-aware recommendations. The Python worker is complete — sync, data fusion, recommendation rules, check-ins, training views, export, and 596 passing tests — with the native iOS experience next. |
| PM Assistant | Product work is fragmented across tools and repeated rituals. | A Claude Code-native PM operating system using commands, skills, hooks, and MCP integrations across the product lifecycle, from discovery through retrospective. |
| AI Industry Weekly | Staying current on AI news should not require reading the same story eighteen times. | A fully automated, multi-stage podcast pipeline: source ingestion, change detection, Claude-powered synthesis and script generation, text-to-speech, RSS publishing, and GitHub Actions deployment. |
- Product strategy should survive contact with the code. I prototype to expose the hard parts early.
- Good DevEx reduces cognitive load. The best platform is the paved road engineers want to take.
- AI systems need engineering discipline. Useful agents depend on clear context, deterministic seams, tests, guardrails, and honest failure modes — not just clever prompts.
- Measure outcomes, not activity. Adoption, flow, reliability, and developer sentiment matter more than tool counts.
- Build the practice, not the theater. Durable conventions and workflows outlast whichever tool is fashionable this quarter.
Before product management, I was a technology equity research analyst — studying complex markets, meeting company leaders, and turning incomplete information into an investment view. Reinventing myself as a product manager is one of the professional accomplishments I am proudest of.
That background still shapes how I operate: find the signal, understand the system, make the tradeoff explicit, and communicate a point of view that can withstand scrutiny. Today I apply that discipline to developer platforms and AI products.
Developer Experience · Internal Platforms as Products · Agentic Developer Workflows · Local-First AI · MCP · GitHub Actions · Python · Product Systems


