Job Title: .Net Lead Developer with Healthcare

Location: Remote

Employment Type: Fulltime

Job Description:

Must or nice to have skills: .NET full-stack with Typescript/Angular/React, MS SQL but open to adopt any tech (Python, Java, Node with JS TS, AWS, RDMBS, Cloud platforms)

Minimum Qualifications

·10+ years of professional software engineering experience, with at least 3 years operating at staff level or above — defined as owning technical direction across multiple teams, not a single team or feature area. Equivalent demonstrated scope is acceptable in place of the year count.

·Depth in at least one modern backend ecosystem and real breadth beyond it. We work primarily in TypeScript/Node.js and C#/.NET; strong candidates from Java, Go, Python, or similar backgrounds are encouraged to apply, provided you have picked up unfamiliar stacks quickly before and can point to when.

·Proven ownership of distributed, event-driven systems in production — messaging and queueing, idempotency, failure handling, and workflows that run longer than a single request.

·Demonstrated skill at building reliable software on top of unreliable dependencies — you have owned an integration with a slow, rate-limited, or unpredictable external service and made the system around it behave predictably.

·Substantial hands-on experience with a major public cloud (AWS or Azure preferred) including serverless compute, containers, managed relational databases, caching, secrets management, identity and access management, and infrastructure as code.

·Strong relational data modeling and SQL, including schema and migration strategy for systems that cannot go down.

·Working depth in modern web application architecture — component-based front ends, server-side rendering, and the design and versioning of the APIs those front ends consume.

·A track record of technology decisions you made and then lived with, including at least one you would make differently today and can explain why.

·Excellent written technical communication. Design documents, RFCs, and incident write-ups are a core part of how you work, not an imposition.

·Comfort in a regulated domain — you have built software where being wrong has consequences beyond a poor user experience.

Preferred Qualifications

We do not expect any single candidate to have all of these. Strength in several is what distinguishes a strong application.

·Healthcare domain experience: FHIR, HL7v2, C-CDA, ICD-10, CPT, or risk-adjustment coding; EMR or health information exchange integration; clinical document ingestion and OCR.

·Workflow orchestration at scale — durable execution engines, checkpointing and resumability, saga or compensation patterns, and multi-stage pipelines with strict lineage requirements.

·Production experience integrating machine learning or other non-deterministic services from the application side: schema enforcement on model output, versioned prompts or configuration treated as deployable artifacts, cost and token budgeting, and reproducible runs.

·Multi-cloud or cloud-portable architecture — runtime provider abstraction for storage, queueing, caching, and databases; cross-cloud integration; avoiding lock-in without settling for a lowest-common-denominator design.

·Domain-driven design and clean or hexagonal architecture at scale, including automated enforcement of architectural boundaries.

·Observability engineering: custom metrics pipelines, dashboards and alarms as code, distributed tracing, and SLO practice.

·Identity and access: OAuth 2.0 and OIDC, a managed identity provider, token exchange, service-to-service authentication, and multi-tenant authorization models.

·Incremental modernization — strangler-pattern migrations, and integrating modern applications with legacy systems that cannot be replaced on your schedule.

·HIPAA, SOC 2, or HITRUST program experience; application security practice including static analysis and container scanning.

·Fluency with AI-assisted development tooling and a clear point of view on where it belongs in a regulated engineering workflow.

·Experience standing up greenfield services alongside an existing platform without fragmenting it.

Technical Environment

For context on what you would be walking into. This reflects the platform today; part of this role is deciding how it should change.

·Languages and frameworks: TypeScript/Node.js and C#/.NET on the backend; React with Next.js on the front end.

·Cloud: AWS and Azure in combination, plus managed application hosting — serverless functions, container services, managed Postgres, object storage, managed caching, and infrastructure as code.

·Data: PostgreSQL as the primary store, with SQL Server and Redis-compatible caching also in use.

·Messaging: managed queue and publish/subscribe services on both clouds, including cross-cloud integration.

·External services: managed machine learning inference and search services consumed behind provider-agnostic abstractions we own.

·Delivery: Azure DevOps pipelines, containerized deploys, automated security scanning, and feature flags.

“Tekshapers is an equal opportunity employer and will consider all applications without regards to race, sex, age, color, religion, national origin, veteran status, disability, sexual orientation, gender identity, genetic information or any characteristic protected by law.”