What are the responsibilities and job description for the Healthcare .Net Tech Lead Engineer at Remote position at PropelSys Technologies LLC.?
Hope you are doing well
Please find the Job Description (JD) below.
Role: Senior Tech Lead Engineer
Location: Remote
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)
Job description:
We are hiring a Sr Tech lead to provide technical leadership across our clinical software platform - the services and applications that move clinical data through processing, review, and export, and that clinicians and staff depend on every day. The platform spans event-driven backend services, data processing pipelines, and web applications running across multiple cloud providers.
This is a hands-on, individual-contributor leadership role. You will not manage people. You will help drive and implement architecture and technical direction for systems that cross several teams, write and review code in the critical path, and be accountable for whether those systems are correct, observable, secure, and affordable in production.
Just as importantly, you will help decide what we build next. Our platform is growing - new services, new applications, and new problem domains are coming, and the right technology choices for them are open questions. We expect this engineer to be central to answering those questions: evaluating and selecting technologies, setting the patterns new systems are built on, and knowing when to standardize versus when to let a team diverge. We are hiring for engineering judgment that outlasts any particular framework, not for expertise in a fixed stack.
Because the work is clinical, correctness is not negotiable. The systems you own carry data that informs decisions about patient care and coding accuracy. Determinism, traceability, and reproducibility are engineering requirements here, not nice-to-haves.
Core Competencies
These are the capabilities the role is built on. They are deliberately technology-independent - the specific tools will change over the life of this role.
| Competency | What we mean by it |
| Systems and architecture design | Decomposing ambiguous problems into services and contracts with clear ownership. Reasoning about consistency, coupling, failure domains, and blast radius. Knowing which decisions are expensive to reverse and treating those differently from the ones that are cheap. |
| Distributed systems | Designing asynchronous, event-driven systems that behave correctly under partial failure: idempotency, retries and backoff, ordering guarantees, dead-letter handling, backpressure, and long-running or resumable workflows. |
| Taming unreliable dependencies | Building deterministic, well-behaved software around components that are slow, rate-limited, occasionally wrong, or non-deterministic - third-party APIs, external services, and machine learning inference alike. Strict schema validation at the boundary, timeouts and circuit breakers, caching, concurrency control, cost and latency budgets, and graceful degradation. |
| Data modeling and stewardship | Designing schemas and data contracts that survive years of change. Migration strategy for live systems, query performance, and versioning of the data products other teams depend on. |
| Reproducibility and auditability | Engineering systems whose behavior can be reconstructed after the fact: durable run state, versioned inputs and artifacts, lineage through multi-stage pipelines, and the ability to answer "why did this produce that" months later. |
| Reliability and operability | Building systems that can be understood in production: meaningful instrumentation, actionable alerting, service-level objectives, and incident response that produces durable fixes rather than heroics. |
| Security and compliance by design | Handling protected health information correctly by construction - least privilege, encryption, secrets management, access control, and audit trails - and working fluently inside regulatory constraints without treating them as an obstacle. |
| Technology evaluation | Assessing new languages, frameworks, platforms, and vendors on evidence: prototyping honestly, weighing total cost of ownership and operational burden, and recommending a direction that accounts for the team we actually have. |
| Technical leadership | Achieving outcomes through influence rather than authority. Mentoring senior engineers, building consensus across teams you do not lead, and writing well enough that your designs travel without you in the room. |
What You Will Do
Architecture and technical strategy
Contribute to and implement end-to-end architecture for one or more platform domains, including the contracts and integration of boundaries between them.
Minimum Qualifications
How We Define This Level
Titles vary widely across the industry, so we are explicit about the scope we are hiring for.
| Dimension | Expectation at Senior Staff |
| Scope | Multiple teams, plus at least one platform-wide concern. You are accountable for systems you do not personally write all of. |
| Time horizon | One to three years. You are expected to see around corners, not only to deliver the current quarter. |
| How impact is measured | Primarily by what you enable in others and by the durability of your technical decisions; secondarily by your own commits. |
| Autonomy |
|