Skip to content
Full Stack .NET Developer3+ years · SaaS · distributed systems

Yash Patel.

Full Stack .NET Developer | Microservices | SaaS | Angular | DevOps

Full Stack .NET Developer with 3+ years of experience building scalable SaaS applications with .NET, Angular, PostgreSQL, microservices, and DevOps. Experienced in multi-tenant platforms, distributed systems, and end-to-end product delivery.

Professional experienceAviasole Technologies · DEPPLLE Softtech
Personal flagshipMediCore Hospital Management Platform
Interactive identity deck for Yash Patel, a Full Stack .NET Developer, currently building MediCore across product interfaces, service architecture, and distributed delivery.
  • Product interfaces: Complex workflows, made clear. I shape role-focused Angular experiences with typed state, responsive interaction, and failure paths that stay understandable. Angular, TypeScript, SSR.
  • Service architecture: Boundaries that stay owned. Contract-led .NET services keep domain rules, transaction ownership, and persistence explicit as the product grows. ASP.NET Core, EF Core, PostgreSQL.
  • Distributed delivery: Reliable from event to deployment. Messaging, containers, and telemetry carry features safely across processes and into environments that remain operable. RabbitMQ, Docker, OpenTelemetry.
Identity · experience · product engineering

Career & project context

The short version, with ownership kept explicit.

Employer scale and personal-project architecture are labelled separately rather than combined into one score.

3+

Years of professional experience

Career timeline

100+

SaaS tenants supported

Employer experience · Aviasole

18

Backend service families

Personal project · MediCore

Full Stack

Frontend · Backend · DevOps

End-to-end delivery

About

Product thinking across the full stack.

I design and ship complex SaaS products end to end—from service boundaries, identity, data, and messaging to Angular workflows, observability, and containerized delivery. I care about systems that stay secure, understandable, and operable as they grow.

Delivery coverage

Frontend

01

Angular product workflows and responsive interfaces

Backend

02

.NET services, REST APIs, and domain boundaries

Databases

03

PostgreSQL, SQL Server, EF Core, and data ownership

Authentication

04

OAuth 2.0, OIDC, OpenIddict, roles, and permissions

Messaging

05

RabbitMQ, MassTransit, events, and background work

Caching

06

Redis / Valkey caching and distributed coordination

Containers

07

Docker, Kubernetes, and Helm delivery

CI/CD & infrastructure

08

Repeatable pipelines, health, and observability

Skills

Technologies I use to ship products.

Each group keeps general résumé evidence distinct from technologies verified in the current MediCore source—without percentages, rankings, or decorative proficiency scores.

/01

Backend

Service and API delivery

Résumé-backed

  • .NET
  • C#
  • ASP.NET Core
  • Web API
  • Entity Framework Core
  • ADO.NET

Project-applied

  • .NET 10
  • REST APIs
  • Service-owned EF Core
/02

Frontend

Role-focused product interfaces

Résumé-backed

  • Angular
  • TypeScript
  • JavaScript
  • jQuery

Project-applied

  • Angular 22
  • SSR
  • HTML
  • CSS
  • PrimeNG
  • Tailwind CSS
/03

Architecture

Systems with explicit ownership

Résumé-backed

  • Microservices
  • Multi-tenant SaaS
  • Clean Architecture
  • DDD
  • API Gateway
  • Event-driven design

Project-applied

  • Service-owned boundaries
  • Distributed systems
  • YARP gateway
/04

Databases & cache

Persistence and distributed state

Résumé-backed

  • PostgreSQL
  • SQL Server
  • Redis
  • Read/write replicas
  • Distributed locking

Project-applied

  • Service-owned PostgreSQL
  • Valkey
  • EF Core
/05

Messaging & workflow

Reliable work across processes

Résumé-backed

  • RabbitMQ
  • SignalR

Project-applied

  • MassTransit
  • Inbox / outbox
  • Temporal initial-owner onboarding
/06

Security

Identity and authorization boundaries

Résumé-backed

  • JWT
  • OAuth 2.0
  • OpenID Connect
  • OpenIddict
  • ASP.NET Core Identity
  • Roles & permissions

Project-applied

  • PKCE
  • Tenant-aware permissions
  • Session lifecycle controls
/07

DevOps

Repeatable delivery

Résumé-backed

  • Docker
  • Kubernetes
  • Helm
  • CI/CD
  • GitHub Actions
  • Azure DevOps

Project-applied

  • .NET Aspire
  • Containerized services
  • Helm deployment assets
/08

Observability

Systems that can be operated

Project-applied

  • OpenTelemetry
  • Prometheus
  • Grafana
  • Health checks
  • Structured logging
  • HTTP resilience
Applied depthHow these skills work together

Frontend product engineering

Interfaces for real operations

I turn complex administration and day-to-day workflows into role-focused Angular experiences with typed state, responsive interaction, and clear failure handling.

Backend & API engineering

Services with owned boundaries

I build contract-driven APIs and domain services with explicit transaction ownership, maintainable application layers, and data access designed for long-lived products.

Distributed SaaS architecture

Systems that grow without blurring ownership

I decompose platforms around tenant-safe domains, service-owned data, asynchronous events, and durable workflows instead of allowing a shared monolith to emerge.

Identity & authorization

Trust designed into every boundary

I implement browser and service authentication, token and session lifecycles, and role- and permission-based authorization that fails closed when context is uncertain.

Data, messaging & concurrency

Correctness across distributed work

I design persistence, caching, real-time communication, and messaging paths around retries, idempotency, locking, read scale, and partial failure.

Platform delivery & operations

From local orchestration to production

I carry systems through gateways, containerization, repeatable delivery, health and telemetry so deployed software remains observable and supportable.

Experience

Professional work, before architecture depth.

Employer-owned delivery is kept separate from the personal MediCore project. The most relevant achievements stay visible; additional verified details remain one disclosure away.

01Employer experience

Feb 2024 - 31 Jul 2026

Aviasole Technologies

Full Stack .NET Developer / Software Engineer

  • Architected and delivered a multi-tenant SaaS insurance platform serving 100+ tenants across multiple insurance lines.
  • Worked across Auth, Core (agent agencies), CRM, Lead Management & Distribution, Notification, and Gateway microservices.
  • Built public lead-capture flows for insurance plan pages, storing prospect data for agent assignment and follow-up.
  • Implemented configurable lead routing by LOB, state, language, and agent criteria, using round-robin to fairly distribute matching leads among eligible agents.
More verified role details
  • Integrated CRM with the US CMS Government ACA API for plan listing, enrollment workflows, and multi-provider insurance support.
  • Configured OpenIddict-based OAuth 2.0 / OIDC authorization with role- and permission-based access across microservices.
  • Supported event-driven notifications across WebSocket, email, and push channels using RabbitMQ.
  • Separated background job processing into a dedicated Console App with read/write replicas and Redis distributed locking for scale and concurrency control.
  • Containerized services with Docker, deployed with Helm, and established CI/CD using Azure DevOps and GitHub Actions.
02Employer experience

Aug 2023 - Feb 2024

DEPPLLE Softtech

DotNet Full Stack Developer

Himatnagar

Featured personal project

PersonalIn ProgressSource-backed
Featured project / 01

MediCore.

MediCore Hospital Management Platform

A multi-tenant hospital management SaaS platform covering patient registration, appointments, clinical workflows, inpatient operations, billing, reporting, and hospital administration.

Current source-backed stack

  • .NET 10
  • ASP.NET Core
  • Angular 22
  • PostgreSQL
  • EF Core
  • OpenIddict
  • YARP
  • RabbitMQ / MassTransit

18

Backend service families

Personal project · current topology

4

Angular SSR workspaces

Role-specific product surfaces

Full stack

Product-to-platform delivery

Interfaces · services · operations

Architecture

One product. Explicit boundaries.

This responsive delivery path is derived from the current MediCore source. It shows how role-specific interfaces, trust boundaries, service-owned domains, distributed infrastructure, and operations fit together.

  1. 01Layer

    Role-specific product surfaces

    Four Angular 22 SSR workspaces keep platform operations, tenant administration, care delivery, and reporting in separately governed product boundaries.

    • Super Admin
    • Tenant Admin
    • Care Workspace
    • Reporting Workspace
  2. 02Layer

    Edge, identity & trust

    A YARP gateway fronts the service estate while OpenIddict OAuth 2.0 / OIDC, tenant context, and permission policies protect browser and service-to-service paths.

    • YARP
    • OpenIddict
    • OAuth 2.0 / OIDC
    • Tenant-aware permissions
  3. 03Layer

    Service-owned healthcare domains

    18 service families own their contracts, application behavior, domain rules, and persistence instead of sharing one database-shaped application core.

    • Contracts
    • Application
    • Domain
    • EF Core persistence
  4. 04Layer

    Distributed platform backbone

    PostgreSQL and EF Core hold service data; RabbitMQ and MassTransit carry reliable events; Valkey supports caching and locks; Temporal coordinates the initial-owner onboarding workflow.

    • PostgreSQL
    • RabbitMQ / MassTransit
    • Valkey
    • Temporal onboarding
  5. 05Layer

    Delivery & operational visibility

    Aspire composes local services, while containers, Helm, health checks, HTTP resilience, and OpenTelemetry make deployment and diagnosis part of the design.

    • .NET Aspire
    • Docker
    • Kubernetes / Helm
    • OpenTelemetry

Progressive case study

Scan first. Open the depth you need.

The overview stays concise for recruiters. Technical interviewers can expand the source-backed architecture, authentication, messaging, tenancy, DevOps, observability, product-surface, domain, and engineering decisions below.

OverviewOne product, separated into role-specific interfaces and service-owned healthcare domains.
  • Four Angular 22 SSR workspaces
  • 18 backend service families
  • Tenant-aware boundaries
  • Current source-backed topology
ArchitectureContracts, application behavior, domain rules, and persistence remain owned by the service family responsible for them.
  • YARP edge boundary
  • Layered .NET services
  • Service-owned EF Core contexts
  • PostgreSQL persistence
AuthenticationOpenIddict OAuth 2.0 / OIDC protects browser and service paths alongside tenant context and permission policies.
  • OpenIddict
  • OAuth 2.0 / OIDC
  • Tenant context
  • Role and permission policies
Messaging & workflowRabbitMQ and MassTransit carry reliable events; Temporal coordinates the initial-owner onboarding workflow.
  • RabbitMQ / MassTransit
  • Inbox / outbox
  • Idempotency and retries
  • Temporal initial-owner onboarding
Multi-tenancyTenant scope and authorization are enforced across API, data, cache, event, and background-work boundaries.
  • Tenant-scoped APIs
  • Tenant-aware persistence
  • Cache and event isolation
  • Fail-closed authorization
DevOpsLocal orchestration and deployment assets make delivery repeatable across service and frontend boundaries.
  • .NET Aspire
  • Docker
  • Kubernetes
  • Helm
ObservabilityHealth checks, traces, metrics, structured logs, and HTTP resilience are part of the implementation foundation.
  • OpenTelemetry
  • Prometheus
  • Grafana
  • Health and resilience
Product surfacesFour workspaces keep distinct users and workflows in separately governed interfaces.

Platform operations

Super Admin

Tenant lifecycle, identity, permissions, audit, billing, terminology, consent, and platform governance.

Hospital administration

Tenant Admin

Facilities, practitioners, scheduling configuration, clinical setup, privacy, consent, and billing governance.

Clinical & front-desk teams

Care Workspace

Patient registry, appointments, clinical care, inpatient operations, consent, and patient financial workflows.

Authorized decision-makers

Reporting Workspace

A separately permission-gated surface for operational reporting and governed analytical access.

Domain map18 service families grouped by care, trust, finance, intelligence, and coordination.

Care delivery

  • Patients
  • Providers
  • Facilities
  • Scheduling
  • Clinical Care
  • Inpatient

Trust & governance

  • Identity
  • Tenant
  • Permissions
  • Consent Authority
  • Privacy
  • Audit Logs

Finance & engagement

  • Patient Billing
  • Tenant Billing
  • Notifications

Intelligence & coordination

  • Terminology
  • Reporting
  • Workflows
Engineering foundationsThe design principles used to protect isolation, ownership, reliability, and operability.

Isolation before convenience

Tenant scope and authorization are enforced at API, data, cache, event, and background-work boundaries rather than treated as UI concerns.

Ownership over coupling

Each domain owns its model, contracts, persistence, and lifecycle; cross-service behavior travels through deliberate APIs and events.

Failure is part of the design

Inbox/outbox messaging, idempotency, distributed locks, durable workflows, retries, and cancellation shape paths that cross process boundaries.

Operability is product work

Health checks, traces, metrics, structured logs, resilience policies, and repeatable deployment assets are built alongside features.

Current implementation stackThe source-backed technologies currently represented across the MediCore repositories.
  • .NET 10
  • ASP.NET Core
  • Angular 22
  • PostgreSQL
  • EF Core
  • OpenIddict
  • YARP
  • RabbitMQ / MassTransit
  • Valkey
  • Temporal
  • OpenTelemetry
  • .NET Aspire
  • Docker
  • Kubernetes / Helm
  • Nx
  • PrimeNG
  • Tailwind CSS

Education

The academic foundation.

Computer Science Engineering

B.Tech in Computer Science Engineering

Parul University, Vadodara

May 2019 - Apr 2023CGPA: 6.77/10

Résumé

Read it online. Keep the original.

The web résumé preserves the supplied summary, skills, experience, MediCore project details, and education. Open the accessible web layout or download the checked-in PDF.

Contact

Let's Build Something Great.

If you are hiring a Full Stack .NET Developer to help build secure, scalable SaaS products across backend, frontend, and delivery, I would be glad to discuss the work.

patelyash9157@gmail.com