Lead Software Engineer

Job Information:
Lead Software Engineer (.NET/AWS) - Healthcare (HIPAA)
Computrition - Jonas Software ()

Location: Remote (US) or Hybrid

Team: Engineering

Type: Full-time
Reports to: Senior Director of Engineering

Partners with: Lead Software Architect

About the role

Computrition is building a cloud-native platform for hospitals and health systems. You'll be the hands-on technical lead partnering with our Lead Software Architect to design and ship a secure, scalable .NET solution on AWS with a React front end, a .NET business/API layer, and PostgreSQL for persistent data. You'll own critical services, mentor engineers, raise the bar on engineering practices, and help us leverage AI safely to deliver high-quality software faster.

Attention on backend - business and API layer.

What you'll do

• Design & build: Lead development of distributed services in .NET 8 / C# (ASP.NET Core), including REST/gRPC APIs, background workers, and event-driven components.

• Cloud architecture: Implement cloud-native patterns on AWS (e.g., ECS/EKS/Lambda, API Gateway, RDS/Aurora Postgre
  
  SQL, S3, SQS/SNS/Event Bridge, Cloud Watch, KMS, Secrets Manager, Cognito/SSO).

• Data & performance: Model schemas in PostgreSQL
  , optimize queries/indices, tune performance, and design migrations and data retention strategies.

• Security & compliance: Build with HIPAA in mind-least-privilege IAM, encryption in transit/at rest, audit logging, PHI data handling, BAA considerations, and secure SDLC practices.

• Quality & delivery: Champion CI/CD (Git Hub Actions/Code Build/Code Pipeline), IaC (Terraform/CDK/Cloud Formation), automated testing (unit/integration/contract), and safe feature-flag rollouts.

• Observability: Establish metrics, logs, and traces (Open Telemetry) with actionable dashboards and alerting; lead incident response and postmortems.

• Technical leadership: Run design reviews, set coding standards, perform thoughtful code reviews, and mentor a small team of engineers.

• AI First Mentality: Safely apply AI tools (code assistants, test generation, static analysis, documentation) to accelerate delivery-respecting PHI boundaries and vendor policies.

• Collaboration: Work closely with Product, Security/Compliance, Customer Success, and clinician stakeholders to translate needs into resilient designs.

Our stack

• Backend: .NET 8 (C#), ASP.NET Core (REST/gRPC), EF Core/Dapper, Mediat
  
  R/CQRS where it fits

• Frontend: React (Type Script),
  Fluent UI
  , Vite/Webpack, Jest, React Testing Library

• Data: Postgre
  
  SQL, Redis, S3 (cold storage); potential Redshift/Athena for analytics

• Infra/Dev Ex: AWS, Docker, Terraform or CDK, Git Hub Actions, Open Telemetry, Grafana/Cloud Watch

Clean Code, Architecture & Design Patterns

We hold a high bar for clarity, maintainability, and long-term agility.

Principles we practice

• SOLID
  , DRY
  , KISS
  , YAGNI
  -favor simple, composable solutions over cleverness.

• Clean Architecture / Hexagonal boundaries: keep the domain independent of frameworks; depend on abstractions; isolate external concerns (DB, AWS, UI) behind ports/adapters.

• Secure-by-design: least-privilege IAM, safe handling of secrets, auditability, and privacy-by-default patterns appropriate for HIPAA.

Coding standards

• Small, focused classes/functions with intention-revealing names; avoid primitive obsession and Law-of-Demeter violations.

• Prefer immutability and pure functions where practical; inject dependencies; avoid shared mutable state.

• Consistent formatting (Editor Config, dotnet format) and analyzers (Roslyn/Sonar) enforced in CI.

Design patterns (used judiciously)

• Creational: Factory, Builder for complex object construction.

• Structural: Adapter, Facade, Decorator to compose behavior without inheritance.

• Behavioral: Strategy, Command, Observer,
  Mediator (e.g., Mediat
  
  R) to decouple flows.

• Architectural:
  CQRS where it adds value; domain events; anti-corruption layers between bounded contexts.

• Cloud/resilience: Circuit Breaker, Retry, Timeout, Bulkhead (e.g., Polly);
  Outbox pattern and idempotency for message-driven workflows;
  Saga/Process Manager for long-running, multi-service transactions.

• Performance: Cache-aside (Redis), pagination/streaming, back pressure for event consumers.

Testing & quality

• Pragmatic…