Senior Full Stack Engineer (.NET + Angular)

I design and ship production systems on .NET + Angular.

I design and ship production .NET + Angular systems for healthcare, SaaS, and eCommerce teams.

Start a project inquiry See selected work

Prefer WhatsApp? Message me · Read the blog

5+ years

Shipping

Healthcare · SaaS

Domains

1 business day

Reply time

Contract · remote

Availability

Clean ArchitectureASP.NET CoreAngularAzureSQL ServerCosmos DBRedisIdentityServerDockerRabbitMQSignalRCI/CD

Selected work

Production systems with clear boundaries.

Full case notes →

Marketplace architecture

CarBazaar

Microservices marketplace for vehicle auctions — designed around independent deployability and secure identity.

A reference architecture clients can extend into real marketplaces — clear boundaries, event-driven flow, and production-grade auth patterns.

.NET · Angular · IdentityServer · RabbitMQ · Docker · JWT / OAuth 2.0

eCommerce platform

Ecom_NET10

Clean Architecture eCommerce stack — ASP.NET Core APIs + Angular SPA with maintainable domain boundaries.

A foundation teams can extend into real merchandising and checkout without rewriting the core — patterns proven in .NET 10 solutions.

ASP.NET Core · .NET 10 · Angular · EF Core · SQL Server · JWT

Healthcare / SaaS

Healthcare & SaaS delivery

NDA — architecture patterns only

Enterprise healthcare modules for providers, fees, and onboarding — shipped in production with cross-functional teams.

Operational features that improved enrollment and provider workflows — delivered with product, design, and QA partners on production systems.

.NET Core · Angular · SQL Server · Azure · Cosmos DB · AWS

How we work

From discovery to production — without foggy retainers.

For founders, CTOs, and product teams who need senior ownership on healthcare, SaaS, or marketplace systems — architecture, identity, and delivery that survives production.

Phase 1

Discover & frame

Goals, constraints, risks, and success metrics. We align on what “done” means before estimating.

Phase 2

Architect the slice

Boundaries, data, auth, and integration points for the first vertical slice — documented simply.

Phase 3

Build, review, ship

Weekly demos, clean PRs, measurable progress. Adjust the plan with evidence, not guesswork.

Boundaries before buzzwords

I choose modular monoliths or microservices based on change rate and team size — not fashion.

Security is a design input

AuthZ models, token lifetimes, and audit paths are decided early — not patched after demos.

Data shapes the product

SQL, Cosmos, and cache strategy follow access patterns. Slow queries get fixed at the source.

Ship in thin slices

Vertical slices with clear acceptance criteria beat big-bang rewrites and invisible progress.

Next step

Need a senior .NET + Angular partner for the next release?

Share the problem, constraints, and timeline. I'll come back with a clear technical approach and next step — usually within one business day.

Start a project inquiry WhatsApp