About
Engineering as ownership.
I don't hand off tickets. I own the outcome — from the architecture whiteboard to the production deploy, and everything that breaks in between.
How I work
Most engineering problems are not technical problems — they're delivery problems. The wrong abstraction chosen too early. The integration left for "later". The infrastructure decision delegated to someone who doesn't know the business constraints.
I solve this by staying in the problem end-to-end. I've designed Cloudflare BFF architectures and written the Vue components that consume them. I've modelled federated GraphQL schemas and owned the migrations that keep them consistent with production data. I've set up the AWS resources and been on call when they misbehave.
This is what senior delivery looks like — not "I did my part", but "it's running and I know why".
Background
I've built and shipped production systems across B2B and platform contexts — working across the full delivery stack as the person who makes sure the thing actually works in production, not just in the demo.
My expertise runs deepest at the intersection of frontend architecture (Vue 3, TypeScript), edge computing (Cloudflare Workers, BFF patterns), and API design (GraphQL, Federation). I'm comfortable in AWS and DevOps territory when the job requires it.
Currently
Exploring AI-assisted engineering — specifically how autonomous agent fleets can own the full software delivery cycle. This portfolio was built by one.
Open to senior engineering roles and consulting engagements where full-stack ownership and delivery speed matter.