Healthcare & regulated SaaS
Provider portals, fee schedules, onboarding, and secure multi-tenant flows with audit-minded design.
Senior Full Stack Engineer (.NET + Angular)
I design and ship production .NET + Angular systems for healthcare, SaaS, and eCommerce teams.
5+ years
Experience
Healthcare · SaaS
Domains
.NET + Angular
Core stack
Remote-ready
Availability
Who this is for
I partner with founders, CTOs, and product teams when the problem is bigger than a single screen: architecture choices, identity, performance, and delivery that survives production.
Provider portals, fee schedules, onboarding, and secure multi-tenant flows with audit-minded design.
Service boundaries, gateways, async messaging, and storefront/API foundations that can grow.
Untangle brittle .NET/Angular systems: auth debt, slow SQL, unclear modules, missing CI/CD.
How I decide
I choose modular monoliths or microservices based on change rate and team size — not fashion.
AuthZ models, token lifetimes, and audit paths are decided early — not patched after demos.
SQL, Cosmos, and cache strategy follow access patterns. Slow queries get fixed at the source.
Vertical slices with clear acceptance criteria beat big-bang rewrites and invisible progress.
Selected work
Marketplace architecture
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
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
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
Engagement model
Phase 1
Goals, constraints, risks, and success metrics. We align on what “done” means before estimating.
Phase 2
Boundaries, data, auth, and integration points for the first vertical slice — documented simply.
Phase 3
Weekly demos, clean PRs, measurable progress. Adjust the plan with evidence, not guesswork.
Next step
Share the problem, constraints, and timeline. I'll come back with a clear technical approach and next step — usually within one business day.