work with me00

Drag to turn · arrow keys to inspect

Different threads. One continuous system.

Memory, authority, and execution are separate concerns. The green thread is what must survive their handoff.

Your study / 1200 × 1200
Download image
For founders / recruiters / ambitious teams

Systems depth. Product taste. Room to build across disciplines.

I bring production ownership across healthcare, fintech data, and backend systems, alongside founder-led work in AI infrastructure, learning products, research tools, and interactive 3D. I connect the architecture to the experience people actually use.

Start a conversation Book 30 minutes

Don't take the claims. Take the receipts — every one scored against six proof criteria, failures included. Open the ledger

01

What changes when I join the problem

Depth without tunnel vision. Range without hand-waving.

I can move from a failing background workflow to a product hierarchy, a trust model, or a founder decision without losing the connective tissue between them.

01

I see the whole system

Architecture, product surface, rollout, evidence, and adoption remain one problem until the user can trust the result.

02

I work AI-natively

Agents expand my execution surface across code, research, quality, and distribution; judgment and accountability stay authored.

03

I stay calm near consequence

Healthcare and regulated data systems trained me to make failure modes smaller, rollouts reversible, and decisions legible.

04

I finish the product

Install paths, operator hierarchy, interaction details, and proof are not polish after the engineering. They complete it.

Capabilities / the full range

Different disciplines. Useful together.

  • Product & interactionProduct architecture · Interface design · Accessible interaction
  • Backend, cloud & dataAPI architecture · Distributed workflows · Data pipelines & governance
  • AI & agent systemsAgent orchestration · MCP & identity · Evaluation & observability
  • Research & machine learningScientific computing · Model architecture · Experiment design
  • 3D & game developmentReal-time rendering · Materials & lighting · Gameplay & worldbuilding
  • Native & developer toolsSystems programming · CLI & runtime design · Testing & distribution
  • Creative direction & communityVisual storytelling · Motion composition · Collaborative facilitation
Explore skills, tools, and the work behind them
02

Three ways to inspect the claim

Founder proof / OrgX

I designed the continuity and proof layer I believed agent work was missing.

Product thesis, shared work graph, client ecosystem, trust boundaries, quality bars, receipts, distribution, and the operator surfaces that connect them.

Inspect the flagship →
OrgX receipt-first artifact viewer
Production proof / Alma

Regulated workflows that earned adoption and stayed observable.

HIPAA production · reassessments · reversible rollout · measurable reliability.

Inspect Alma →Product-culture proof / Config

I turn collaboration into a making environment—not a meeting.

Figma and Chill · global BIPOC design community · play, iteration, and action.

Watch the talk ↗
03

Where the fit is strongest

Give me the consequential system, not the isolated ticket.

Founder collaborations, senior/staff IC roles, and small high-agency teams building agent platforms, developer tools, data-intensive products, learning experiences, or operational software where architecture and interaction need equal care.

  • Houston-based and remote-friendly
  • Comfortable across backend, product surface, and system narrative
  • Best with ownership, candid collaboration, and an evidence-driven bar
A good first conversation is concrete.

Show me the system, the pressure, and what has resisted becoming clear.