PocketHealth
Senior Software Engineer (Conductor)
At a Glance
- Location
- Greater Toronto Area, Canada
- Work Regime
- hybrid
- Employment
- Full-time
- Experience
- 5–8 years
- Department
- Engineering
- Posted
- 2026-07-27T13:57:09.686000+00:00
Key Requirements
Required Skills
Domain Knowledge
- Embedded Systems
- Engineering
Benefits & Perks
ys, extended mental health coverage, and 16 weeks of parental leave top-up.
Requirements
5-8 years of software engineering experience, with meaningful time in a forward deployed, solutions engineering, or embedded client-facing engineering role
Track record of shipping production code in client environments — not just internal products
Strong full-stack engineering fundamentals: comfortable owning backend services, APIs, data pipelines, and integration layers end to end
Proficient in Python and/or TypeScript; able to write clean, maintainable, production-quality codeHands-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
Responsibilities
You 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.
You'll sometimes enter the picture before a contract is signed — running demos, building proof-of-concept automations, and leading workflow mapping sessions that turn a prospect's skepticism into confidence.
When an automation goes live, it's dollars freed from administration and returned to care.
You'll feel that directly because you'll be the primary point of contact for the client's technical and operational stakeholders throughout, building the relationships that make hard things possible.
This role reports directly into the Co-Founder & Chief Technology Officer.
The software you ship, the workflows you automate, and the deployments you own translate directly into care at every provider you work with.