Software Engineer

PocketHealth; Toronto; On-site; CAD 80,000 - 100,000; Full time

Job summary

PocketHealth in Toronto is looking for a Software Engineer who will collaborate with a team to deploy Conductor. You'll write code, build integrations, and help translate client needs into effective solutions. This role directly impacts healthcare by improving workflows and providing efficient automation.

Ideal candidates have 4+ years of experience, proficiency in Python or TypeScript, and hands-on knowledge of AWS. You will work in a dynamic environment aiming to improve patient care through technology.

Qualifications

• 4+ years of software engineering experience.
• Solid full-stack fundamentals including backend services and APIs.
• Hands-on experience with AWS.

Responsibilities

• Work alongside engineers to deploy Conductor efficiently.
• Support technical implementation of Conductor from kickoff to go-live.
• Document successful strategies and contribute to platform evolution.

Skills

Software engineering experience

Proficient in Python and/or TypeScript

Experience with AWS

Working with third-party APIs

Using AI tools in engineering

Strong communication skills

Tools

AWS (ECS, Lambda, API Gateway)

Workflow orchestration engines

Job description

Requirements

• 4+ years of software engineering experience
• Some exposure to client-facing or production environments is a plus, but not required
• Solid full-stack engineering fundamentals: comfortable contributing to backend services, APIs, data pipelines, and integration layers
• Proficient in Python and/or TypeScript; able to write clean, maintainable, production-quality code
• Hands-on experience with AWS (ECS, Lambda, API Gateway, or similar)
• Experience building and debugging integrations against third-party APIs and data systems
• Experience with workflow orchestration engines (Step Functions, Cadence, Temporal, Prefect, or similar) is a strong plus
• You're an engineer first - your default response to a problem is to build a solution, not escape it
• You use AI tools fluently as part of your daily engineering practice: Claude Code, Codex, Cursor, Copilot, or equivalent
• You thrive in environments where requirements are discovered through doing, not just scoping
• You communicate clearly and naturally with non-technical stakeholders, without losing engineering precision
• You hold yourself to a high bar on both code quality and client outcomes

What the job involves

• As a Software Engineer, you will work alongside a team of engineers to get Conductor live and to make it matter
• Working collaboratively and under the guidance of senior engineers, your team will take a signed contract and own everything it takes to turn it into a working deployment: writing code, building integrations, extending agentic workflows, and standing up the infrastructure to run reliably in a real provider environment
• The impact isn’t abstract. When an automation goes live, it’s dollars freed from administration and returned to care. It’s staff time given back to patients
• The software you ship, the workflows you automate, and the deployments you contribute to translate directly into care at every provider you work with. This is a rare opportunity to do work that is technically demanding, deeply human, and genuinely consequential
• Support deployments end to end: Contribute to the full technical implementation of Conductor for each client, from kickoff through go-live. Write the code, support the integration scope, and help build the trust that turns a successful go-live into a long-term relationship
• Build, integrate, and ship: Write and extend agentic workflows in Conductor's orchestration engine - building custom tools, integration adapters, and transformation logic tailored to each client's operational patterns. That means working across the full stack: backend services in Python and TypeScript, integrations against real healthcare provider environments (HL7 v2, FHIR, DICOM, RIS/PACS, EMR webhooks, scheduling software), and production-grade code you'd be proud to put in a PR
• Diagnose and resolve issues quickly: Support technical escalation during and after go-live. Use logs, workflow state, and system telemetry to diagnose problems at the code level and resolve them fast
• Shape how Conductor evolves: Translate client friction into structured product feedback. Identify patterns across deployments that should drive platform decisions. What you learn in the field shapes how Conductor is built
• Strengthen the platform as you go: Document what works. Contribute to integration libraries, shared tooling, and deployment runbooks that make future deployments faster and the platform more capable