Senior Backend Engineer
Helping founders and businesses build, scale, and modernize software products with Node.js, Go, AWS, MongoDB, PostgreSQL, and GraphQL. 3+ years of production work on APIs, serverless workflows, and event-driven architectures.
AI accelerates my workflow. Engineering judgment validates every production change.
2+ years using AI in daily engineering — for architecture, debugging, optimization, security review, documentation, tests, database design, infrastructure, and learning. I treat AI as a force multiplier, not a substitute for understanding the system.
AI Asset Management Assistant — MCP server + agent for natural-language operations.
I can also deliver modern React frontends using AI-assisted workflows (Lovable & Antigravity), allowing clients to work with one engineer for complete MVP delivery.
Backend work, end-to-end — from first commit to scaled systems.
A focused set of services that map to the problems founders actually need solved.
Building SaaS products from scratch
Backend architecture & API design
System modernization & rescue
Performance optimization
GraphQL and REST development
AWS serverless backend development
Database design & optimization
Four projects, four different shapes of hard.
Resolving a Critical SSO Security Issue
Tracked down a stubborn SSO vulnerability by rebuilding the auth flow from first principles.
Rebuilding a Struggling Platform with Go
Re-architected a messy B2C restaurant platform in Go — cleaner backend, redesigned database, calm under load.
Enterprise Financial Workflows at Scale
Backend systems for complex financial workflows, real-time updates, and enterprise-grade permissions.
Natural-language interface for asset, order, and employee operations.
MCP server + AI agent that turned multi-step internal tools into a single conversation.
A senior engineer who behaves like a partner, not a contractor.
I treat the system like it is mine until it works the way it should.
I think about maintainability, business value, and the people using the thing.
I sit with unfamiliar problems until the root cause is honest, not assumed.
Code should read like it expected to be maintained — because it will be.
Engineering, product, client, future-maintainer — all in the same head.
Direct, calm, and specific. No theatre, no jargon for its own sake.
Need help with backend, modernization, or a system that needs real ownership?
I take on a small number of engagements at a time so each one gets full attention. Tell me what you're building.