Description

Responsibilities

• A member-facing self-scheduling portal in Next.js, including consent capture across SMS, email, and phone under TCPA and 10DLC constraints. The compliance requirements shape the data model, so you’ll be involved in that conversation rather than handed a spec.
• NestJS services behind clinician scheduling and dispatch, covering availability, geographic routing, priority scoring, and telehealth slots. This is the highest-leverage system we own and it’s being rebuilt.
• Migration work with teeth. Reading stored procedures to recover the business rule inside them, reimplementing that rule in application code with tests, and cutting over without breaking the operational reporting that finance and the health plans depend on.
• Python services for data pipelines, integrations, and LLM work. We run call analysis on Claude via Bedrock and are building a semantic layer over the warehouse with pgvector and an MCP server.
• Integrations with external systems: telephony, geocoding and routing, and file exchange with health plans covering eligibility, rosters, and results. Much of this is asynchronous, idempotent, and unforgiving of sloppy error handling.

Required Skills

• 5+ years shipping production software you were accountable for after launch. We care much more about systems you owned than about the number of frameworks you’ve touched.
• Strong TypeScript across the Node ecosystem. Next.js on the front end and NestJS or a comparable server framework on the back. You should have opinions about where server-side rendering helps and where it just adds a deployment problem.
• Genuine SQL depth. You can read a query plan, explain why an ORM emitted something terrible, and work in both Postgres and MySQL without treating the dialect differences as trivia. Someone who is only comfortable behind an ORM abstraction will struggle here.
• Python for services and data work. Type hints, tests, and the discipline to keep a script from quietly becoming production infrastructure.
• AWS at a working level: RDS, S3, IAM, Secrets Manager, and containerized deploys on ECS or Fargate. You should understand why a database sits in a private subnet and what a least-privilege policy actually looks like.
• Habits that hold up under review. Tests you wrote because the code needed them, migrations that are reversible, logging that helps at 2am, and pull requests someone else can follow

Key Skills

Education

Bachelor's degree