Software Engineer

• →Implement, test, and ship small to medium-sized features end to end across the Django monolith and its associated services (Care API, FHIR Facade, COBRA, Dolphins, and Health Exchange Handler).
• →Own a module or component within larger projects led by senior and staff engineers.
• →Contribute to and help maintain our document service, a TypeScript, Bun, and Hono microservice backed by PostgreSQL and S3-compatible object storage and deployed on Kubernetes.
• →Improve the admin portal and internal tooling so Support, Clinical Operations, and Implementations can handle scheduling, eligibility debugging, and billing workflows without engineering involvement.
• →Collaborate with senior engineers to clarify ambiguous requirements and surface technical risk early.

• →Diagnose and fix production bugs, moving from symptom to root cause and choosing a permanent fix over a repeat workaround.
• →Participate in the team's production support rotation, triaging incoming issues by patient impact: an issue that blocks a patient from being seen, filling a prescription, or having a claim processed correctly comes first.
• →Make careful, well-reviewed production data corrections when needed, with the discipline that patient-facing, HIPAA-regulated systems demand.
• →Identify and resolve technical debt in the systems you own before it turns into the next production issue.

• →Review your teammates' code thoroughly, with feedback that is specific, kind, and focused on what matters.
• →Write documentation and runbooks that let others resolve common issues on their own, using AI tools to draft and maintain them quickly.
• →Use AI coding tools such as GitHub Copilot, Cursor, and Claude Code in your daily workflow to speed up root-cause analysis, scaffold tests, and accelerate code review.

• You care about the mission and understand that a production bug isn't an inconvenience; it's a patient who can't get seen or a claim billed incorrectly.
• You're solidly productive in Python and Django and comfortable reading code you didn't write in a large codebase.
• You write tests as a matter of course, not as an afterthought, and your code is maintainable by the next person.
• You ask good questions when requirements are fuzzy, rather than guessing or stalling.
• You're genuinely interested in learning a second stack, and if "I've never written TypeScript, but I'd like to" describes you, that's exactly right.
• You give code reviews you'd want to receive: specific, kind, and focused on what matters.
• You've adopted AI tools into your workflow, you get real leverage from them, and you check what they produce.

• You want to work exclusively on greenfield feature work and avoid production bugs and maintenance entirely.
• You're primarily a front-end engineer without hands-on Python and Django experience.
• You're uncomfortable taking part in a production support rotation or making careful, reviewed production data changes.
• You want to stay in one language and would rather not touch a second service.
• You prefer entirely manual debugging workflows and resist AI-assisted tooling.

• 2+ years of professional software engineering experience, with a record of shipping features independently once given a clear goal.
• Hands-on Python and Django experience, including Django REST Framework APIs and the Django ORM.
• Working knowledge of relational databases (PostgreSQL and/or MySQL), including the ability to write, read, and reason about non-trivial SQL.
• Solid testing habits and experience with automated test suites and CI.
• Demonstrated debugging skill: you can work a bug from a vague report to a reproducible cause.
• Clear written communication for documentation, runbooks, and cross-functional work with Support, Clinical Operations, and Implementations.
• Openness to learning TypeScript and modern JavaScript runtime tooling on the job.
• Proficiency with AI development tools in your day-to-day engineering work, and the judgment to verify what they produce.

• Experience with TypeScript and modern JavaScript runtimes (our document service runs on Bun with the Hono HTTP framework, Bun's native SQL client for PostgreSQL, and the AWS SDK v3 S3 client).
• Familiarity with AWS, particularly S3, Secrets Manager, and IAM (our services use IRSA for credentials and read runtime config from AWS Secrets Manager through the Secrets Store CSI driver).
• Experience with containers and deployment: Docker and Docker Compose for local development, Kubernetes with Helm and Argo Rollouts for deploys, Terraform for service IAM, and GitHub Actions for CI.
• Observability experience with OpenTelemetry tracing and metrics, and comfort reading traces and dashboards to diagnose latency or error spikes.
• Experience with PHI in a HIPAA environment, or in another high-stakes, regulated, or safety-critical domain.
• Familiarity with healthcare billing and RCM concepts such as claims, eligibility verification, coverage logic, and invoice transmission.
• Exposure to healthcare interoperability, including HL7, FHIR, or health information exchange platforms like Particle Health.
• Production experience with Redis, Elasticsearch, RabbitMQ, or Celery.
• Experience with clinical integrations such as e-prescribing (Surescripts), lab integrations (Quest), or pharmacy workflows.
• Exposure to event-driven architecture, since the team is beginning to adopt a Kafka-based (AWS MSK) eventing backbone; prior Kafka experience is welcome but not expected, and this is something you would learn here, not lead.
• Prior production support, sustaining, or reliability-focused engineering experience.

The national pay range for this role is $70,000.00 – $100,000.00 CAD per year. Actual compensation will be determined by factors such as the candidate's geographic market, experience, skills, and qualifications. This role is also eligible for a target annual bonus and Fabric's Canadian employee benefits. If your compensation requirement is greater than our posted range, please still consider applying; a determination can be made based on unique qualifications. Expected compensation ranges for this role may change over time.