Lead with clarity
Bigger type, more breathing room, one clear action above the fold, and a lede that actually says what I've shipped, not what kind of engineer I "am."
Twenty years of shipping real systems: React at Disney scale, HIPAA-compliant APIs at Hoag Hospital, McKinsey client dashboards, CHOPT's checkout architecture, and two companies I run on the side. I still write the code myself. If you need someone who can pick up any stack, own the hard problems, and stay accountable through production. Let's find out if I'm the right fit.
How this page works
Each section earns its place: lead with signal, follow with proof, surface the real work, then make the ask simple. Scroll is the navigation, not a wall to fight through.
Bigger type, more breathing room, one clear action above the fold, and a lede that actually says what I've shipped, not what kind of engineer I "am."
I organized each section so you can scan fast and go deep when something catches. Role history, live previews, an interactive skill graph. Everything has its own room.
The side dots, progress bar, and nav all track where you are. I built this as a single HTML file with no framework and no build step, because I wanted the craft to be visible.
By the time you reach contact, you've seen what I've built, how I think, and what I can own. If it looks like a fit, I'd love to hear about the role.
The short version
Twenty years leaves a paper trail: enterprise data platforms at Disney, HIPAA-compliant healthcare at Hoag, McKinsey client delivery, production checkout flows, military medical systems, and two businesses I run myself. The resume is the visible layer. The real history goes deeper.
Live work previews
Live windows into public-facing work I've shipped. Some companies block iframes by policy, so every card has a direct link that always works. Enterprise systems, private repos, and healthcare integrations sit behind access controls; I can walk you through those when the conversation is real.
The public surfaces are just what I can show without an NDA. Private enterprise systems, healthcare integrations, payment flows, dashboards, automations, and more are all available to walk through when the conversation warrants it.
AI Engineering
I use AI the way a senior engineer uses a good tool: to reason faster, pressure-test architecture, generate scaffolds, surface edge cases, and move from vague business problem to production implementation without outsourcing judgment.
The real edge isn't typing prompts faster. It's knowing enough systems engineering to evaluate the output, wire it natively into products, and keep security, data quality, UX, cost, and maintainability intact. I use AI daily for architecture, solutioning, implementation, workflow automation, data validation, anomaly detection, reporting, and debugging.
Compare implementation paths, expose hidden coupling, generate option trees, and cut the time from messy requirement to workable technical plan.
Ship AI where it actually belongs: validation, internal tools, workflow automation, support surfaces, reporting dashboards, and decision engines.
Pick up unfamiliar tools quickly by pairing senior fundamentals with AI-assisted exploration, docs review, test scaffolding, and production verification.
Stay in charge: review generated code, test the edges, protect data, respect compliance, document the system, and ship maintainable software.
Interactive skill map
Hover a node to see where that language, framework, or platform shows up in my actual work. This isn't a tag cloud. It's a proof map. And the obvious subtext: whatever stack you're running, I can pick it up.
Selected capability
Move across the map or hover a node. The graph reacts to your cursor and explains where that capability shows up across enterprise, healthcare, agency, product, and military work.
Delivery history
Each card maps to a real delivery from my resume. Scan the source labels (Disney, Hoag, McKinsey, Military, Founder) and you'll see the range quickly. This is still only what's publicly visible.
Let's talk
Send the role, the stack, and the real challenge. I'll tell you straight whether I can help. If it looks like a fit, I'm happy to share repo access, architecture notes, and specifics that don't belong on a public resume.