About
I turn ambiguous operational problems into products teams can use and maintain.
Throughline
Before software, I worked in live entertainment. That made fixed launch windows, non-technical collaboration, and high-pressure operators familiar long before I wrote production code.
Across entertainment, event commerce, client work, and research tools, I kept finding the same problem: important work split across manual handoffs, generic software, and context held in people's heads. My role is to make that work explicit, then build the system around it.
My strongest work sits between product and engineering: talking with the people doing the work, choosing the right boundary for a system, shipping the implementation, and staying close enough to operations to see where the first version breaks down.
At Red Eye, that responsibility includes a guarded AI-assisted operations layer: signed evidence becomes deduplicated repair work, planning is separated from execution and review, and higher-risk changes remain behind policy, approval, rollback, exact-commit deployment, and production-verification controls.
Current focus
As the sole technical contributor, I own product direction and implementation across checkout, wallet payments, ticket delivery, producer tools, refunds, reporting, and mobile admissions. The custom platform launched in October 2025.
The work includes the unglamorous parts of production ownership: edge cases, support workflows, incident recovery, release evidence, and tools for people working a live event.
A policy-governed observation and learning architecture connects findings to proposed actions, approvals, rollback plans, verification results, measured outcomes, and reusable lessons.
Evidence standard
Production systems, scoped contributions, representative visuals, and local or pilot capabilities are labeled explicitly. Default-off, attended, pilot-scoped, and framework-only boundaries remain visible.
Next