Staff Backend Engineer / SaaS backend foundations to platform scale

Build the right backend foundation before scale makes it expensive.

I help SaaS teams build the first backend correctly, stabilize messy MVPs, and modernize platforms that have outgrown their original architecture.

16+years building software

1,500+Shopify stores supported

2M+monthly customers served

400GB+monthly outgoing API traffic

For CTOs, recruiters, and engineering leadersExperienceStaff-level backend architecture, platform modernization, migration, reliability, and engineering operating model work.For founders and Upwork clientsHow I HelpPractical help for MVP backends, messy SaaS systems, tenant isolation, integrations, and backend scale pressure.

When teams bring me in

From getting the backend right on day one to modernizing the platform after growth exposes the cracks.

You are building a SaaS MVP and want the backend right from the start

Turn product requirements into clean flows, data models, APIs, auth, permissions, background jobs, integrations, and a release path before real customers arrive.

Your MVP works, but the backend is becoming hard to change

Stabilize the system pressure points, reduce release risk, and make the next product work safer to ship.

Monolith is slowing product delivery

Find domain boundaries, reduce release risk, and move business-critical behavior through migration paths instead of rewrites.

Tenant isolation is becoming a business risk

Make data ownership, identity, permissions, and operational controls explicit before scale makes them expensive to retrofit.

Events, jobs, and webhooks are failing silently

Design workflows around idempotency, retries, observability, failure recovery, and traceable business outcomes.

APIs and integrations need stable contracts

Stabilize endpoint ownership, auth concerns, versioning, and integration behavior so teams can change the system safely.

Selected work

View case studies

RushShopify SaaS platform modernizationHelped evolve a Shopify post-purchase SaaS platform from monolith pressure toward a domain-driven service platform.NextRepAI-native B2B SaaS architectureDesigned modular MVP-to-scale architecture with Next.js, NestJS, MongoDB, Clerk, tenant-aware identity, and enrichment workflows.

What I solve

Senior backend help for the moments where architecture starts to matter.

MVP backend architecture

Turn rough SaaS requirements into reliable flows, data models, APIs, permissions, background jobs, integrations, and a release path.

Backend rescue and stabilization

Find the system pressure points, reduce release risk, improve observability, and make the next product work safer to ship.

Multi-tenant SaaS foundations

Design tenant isolation, identity boundaries, data ownership, and operational controls before growth makes them expensive to retrofit.

Legacy platform modernization

Move business-critical systems through migration paths, not rewrites, while protecting revenue and delivery speed.

Technical judgment

The Staff Engineer signal is not more tools. It is better tradeoffs.

I choose migration paths over rewrites.
I separate domain boundaries from deployment boundaries.
I design event systems around failure, retry, and idempotency.
I treat tenant isolation as a business and risk boundary.
I optimize for systems a team can operate after I leave.

Public proof

Public proof, curated for relevance.

The goal is not to list every repository. It is to show production-shaped thinking: contracts, data boundaries, tenant isolation, background workflows, and systems that are built to be operated.

GitHub profileOpen AI operations automation hubOpen NestJS backend referenceOpen