Senior Software Engineer, Platform Engineering

Travel to Office Expectations

For Remote Roles: If this role is remote, there will be in‑office events that will require travel to and from the Mississauga and/or Salt Lake City office. These will include, but not limited to, onboarding, team events, semi‑annual and annual team meetings.

For Hybrid Roles: If this role is Hybrid, there will be an expectation to reside within commutable distance to the office/location specified in the job listing. This will include, but not limited to, weekly/bi‑weekly/monthly events in the office with your specific team. This is a requirement for this role.

Job Summary

The Platform Engineering team is a close‑knit group of highly senior engineers focused on building software products for developers — from internal APIs and services to developer tooling, CI/CD frameworks, and Kubernetes‑based abstractions. We treat our platform as a product — prioritizing usability, adoption, and developer experience as first‑class concerns. You will spend a significant portion of your time writing code — building platform services, APIs, and developer tooling used across engineering teams. This is a rare opportunity to work alongside highly experienced engineers on meaningful software problems where your ideas and expertise truly matter. The team operates in Hybrid, focusing office time for meaningful collaboration. Platform Engineering exists to empower product engineering teams to build, deploy, and operate healthcare software faster, more reliably, and more securely. We solve complex cross‑functional problems through well‑designed software systems — building APIs, services, and developer‑facing applications that reduce cognitive load so development teams can focus on delivering value to clinicians and patients. We may not own every part of the stack, but we engineer the APIs, abstractions, and interfaces that piece it together meaningfully — and we own the design, implementation, testing, and lifecycle of what we build through sound software engineering practices and SRE principles.

Key Responsibilities

• Design, build, and maintain platform services, APIs, SDKs, and internal tools used across engineering teams.
• Own platform services end‑to‑end — from design and implementation through production operation and continuous improvement, writing high‑quality, testable code throughout.
• Design and improve CI/CD workflows and developer automation with a focus on usability and efficiency.
• Apply distributed systems and backend engineering principles to design scalable, resilient services and APIs.
• Production ownership of the services and tools you build — including observability, debugging, and incident response.

Qualifications & Skills

Minimum

• Expert‑level proficiency in TypeScript and building production‑grade APIs, services, developer tools, and developer‑facing UIs (React or similar), with strong automated testing practices (unit, integration, E2E).
• Strong software engineering fundamentals — distributed systems, API design, and production backend services, with a proven ability to make pragmatic trade‑offs across scalability, reliability, and developer experience.
• Working proficiency with observability (metrics, logging, distributed tracing, SLI/SLO frameworks) and production ownership of services you build — including incident response and post‑mortems.
• Strong proficiency with Kubernetes — building software abstractions and APIs, extending capabilities through custom controllers and operators.
• Strong proficiency designing and building CI/CD pipelines optimized for security, compliance, and developer experience.
• Working proficiency with Infrastructure as Code (Terraform, Pulumi), GitOps practices, and cloud‑native environments.
• Strong communication, influence, and documentation skills — able to drive adoption of platform patterns, translate technical complexity for diverse audiences, and produce ADRs, runbooks, and developer‑facing documentation.

Preferred

• Experience building internal developer platforms or platform‑as‑a‑product initiatives, including developer portals and self‑service tooling.
• Experience with AI/ML integration: LLM APIs, intelligent automation, AI‑assisted developer tooling, and agentic patterns.
• Working proficiency with cloud security practices (IAM, secret handling, encryption), compliance tooling (HIPAA, SOC 2, HITRUST), or cloud cost optimization (FinOps).

#J-18808-Ljbffr