// about
About


I rebuild operational systems that break under real world pressure.
Most teams do not have a tooling problem. They have a structure problem. Bad schemas, unclear ownership, and fragile automations turn workflows into liabilities.
I fix that at the foundation. Data models, orchestration, validation, permissions, and failure handling. Systems that run reliably at scale.
Earlier in my career, I worked in clinical respiratory and anesthesia environments where process, handoff, documentation, and failure handling mattered in real time. That experience still shapes how I design operational systems: clear ownership, clean escalation paths, and no hidden failure states.
Today I apply that same thinking to operations. Events, compliance, staffing, and data infrastructure. Rebuilding automation pipelines and operational workflows to reduce man hours and friction.
// credentials
// principles
Systems over scripts
If it needs to be fixed twice, it was not designed properly.
Boring wins
Reliable systems beat clever ones. Every time.
Governance is not optional
Without ownership, access, and audit, systems decay.
Built for operators
If it fails at 2am, it is a bad system.
Sprite-sheet turntable test — 16 directional frames