Senior Backend Engineer · Financial Systems & Multi-Tenant Platforms
I architect the backend systems that companies trust to move money, protect data, and scale without breaking — across fintech, healthcare, logistics, and SaaS.
I build the systems that power products people depend on. Over five years of building in the trenches of production backend engineering, I've shipped 15+ APIs serving real users across fintech, healthcare, logistics, and hospitality.
My work lives at the intersection of domain complexity and engineering discipline — designing state machines, decomposing monoliths into microservices, and architecting event-driven systems that remain coherent under pressure.
I've been the sole engineer who ships, the team lead who unblocks, and the architect who thinks three steps ahead. Whether it's a multi-tenant SaaS platform, a government logistics system, or a healthcare payments engine — I take ownership of outcomes, not just tasks.
Good backend engineering is invisible. Users never think about the API, the queue, or the state machine — they just trust the product.
Production-proven tools from API design to deployment infrastructure.
A track record of ownership, promotion, and shipping in fully remote, distributed teams.
End-to-end platforms built from schema to deployment — sole engineer to production.
Designed and built the entire backend for a two-sided space marketplace from zero — hosts listing spaces, tenants booking them, and payments flowing between both with full financial integrity.
Multi-tenant employee background verification platform with Livewire-powered admin interfaces, RBAC enforcement, and asynchronous batch processing pipelines.
Full-featured alumni association platform supporting membership management, event organization, job postings, career advice, and social features with per-association data scoping.
Writing about backend systems, engineering judgment, and production lessons learned the hard way.
The interesting problems aren't in the UI. They're in the edge cases: concurrent inventory, partial checkout failures, and notification idempotency. A production-grade cart built in 14 hours to explore the real backend decisions.
A couple of minutes after 8am standup, the CEO joined and said the words developers dread. The server had crashed hours earlier and we'd missed every warning. A practical guide to production-ready engineering.
I wasn't always this disciplined. When I first started using AI, I treated it like a magic wand and paid dearly for it. This is the framework I built moving from "AI-generated" to "AI-assisted" — from passive user to active architect.
I work full-time, lead a team, and have personal projects in flight. I didn't have 40 hours of open air — I had nights, weekends, and stolen moments. Here's the exact workflow that shipped a production Laravel MVP in ~50 hours over 6 weeks.
Measurable outcomes from production systems, across years of engineering ownership.
Hiring for a backend role? Let's talk about your team and what you're building. Have a specific problem — payments, multi-tenancy, architecture, performance? Bring it.
30 minutes. No small talk.
Come with context — what you're building, what's broken, or what role you're hiring for.