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."
Senior engineer. Founder. Systems builder.
I build the interfaces, APIs, AI solutions, automations, and data systems behind products that cannot afford to break.
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, including AI-native workflows, MCP servers, tool integrations, and production automation. 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.
20+
years building web and software systems
Senior
software engineer with full-stack ownership
Any stack
React, TypeScript, Node, Python, PHP, SQL, cloud, and more
Production
security, compliance, data, real uptime responsibility
Any stack means
React, TypeScript, JavaScript, Node.js, Express, Python, MCP servers, LLM APIs, AI tool integrations, agent workflows, PHP, WordPress, SQL, PostgreSQL, MySQL, MariaDB, MongoDB, AWS Lambda, S3, DynamoDB, API Gateway, Azure Functions, Snowflake, D3.js, Plotly Dash, Mapbox, Tableau, DataDog, SonarQube, Jest, Cypress, Mocha, Jenkins, GitHub Actions, Docker, Terraform, Epic, Cloverleaf, Stripe, Braintree, Twilio, Sentry, Storybook, Angular, Aurelia, LAMP, LEMP, Linux, Shell, Git, and more
Before the AI revamp
Want to see the hand-coded version that came first?
Obviously, this version of the site has been AI-revamped, but it is built on the portfolio I hand-coded before AI tooling became part of my workflow. If you want to see the original work and where this site evolved from, open my previous portfolio website.
How this page works
I built this page the same way I build products.
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.
Show the receipts
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.
Make scroll feel intentional
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.
Close with a straight ask
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. Real systems. Real ownership.
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
Open the work without leaving the page.
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
AI Forward
I build AI as an engineering capability, not a demo layer: production AI solutions, MCP servers, tool integrations, structured workflows, and application features that connect models safely to real systems and real business processes.
The real edge is knowing how to turn model capability into reliable software. I use AI daily for architecture, solutioning, implementation, workflow automation, data validation, anomaly detection, reporting, and debugging, while designing the APIs, permissions, schemas, observability, fallbacks, and human review needed to make AI useful in production.
Architecture acceleration
Compare implementation paths, expose hidden coupling, generate option trees, and cut the time from messy requirement to workable technical plan.
Native product integration
Ship AI where it actually belongs: validation, internal tools, workflow automation, support surfaces, reporting dashboards, decision engines, and model-powered product features.
Fast-ramp learning loop
Pick up unfamiliar tools quickly by pairing senior fundamentals with AI-assisted exploration, docs review, test scaffolding, and production verification.
Human-in-the-loop quality
Stay in charge: review generated code, test the edges, protect data, respect compliance, document the system, and ship maintainable software.
MCP servers & tool integrations
Build Model Context Protocol servers that expose APIs, databases, internal services, and business tools to AI clients through typed schemas, authentication, validation, and observable tool calls.
Production AI solutions
Turn business workflows into reliable AI systems with retrieval, structured outputs, tool use, approval gates, monitoring, fallback paths, cost controls, and measurable outcomes.
Interactive skill map
Move your mouse near the graph. It pushes back.
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
Full stack systems
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
The receipts speak for themselves.
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
Ready when you are.
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.