Senior Software Engineer (Conductor)

Job description

### About PocketHealth Burnout, staffing shortages, chronic underfunding — healthcare is under more strain than it has ever been. A disproportionate share of available resources never reach patients; they're consumed by the administrative layer that sits between a provider and the care they deliver. PocketHealth exists to change that. Our flagship imaging platform gives patients direct, secure access to their medical images and records, trusted by hundreds of hospitals and clinics across North America. Conductor is our agentic AI automation platform — purpose-built to take the administrative weight off healthcare providers so their people and their dollars can go back into care. ### About The Role: As a **Senior Software Engineer**, you are a full-stack software engineer who works directly alongside healthcare providers to get Conductor live and to make it matter. 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. But 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. 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. This is a rare opportunity to do work that is technically demanding, deeply human, and genuinely consequential. This job posting is for an existing vacancy. The salary range for this position is $150,000 - $200,000 annually, depending on the experience and expertise you bring to the team. Salary is just one part of the story, though; this role is eligible for equity in the form of stock options and includes a comprehensive health and benefits package. We view our compensation as a total investment of your well-being, designed to support you in both your work and your life outside of it. This is a hybrid position with two days a week in our Toronto office, where we collaborate deeply; the rest is yours to work from wherever you do your best thinking. ### How We Build: Every deployment is different. Healthcare providers run similar systems but operate them in ways that diverge in the details and those details are where automations succeed or fail. We build to fit each client's actual workflows, which means you'll write purpose-built code, own the edge cases, and ship something that genuinely works rather than something that almost works. AI is a first-class part of how we work. Claude Code, Codex, and AI-assisted development are standard practice on the Conductor team — they're what let us move fast, build with precision, and keep quality high across multiple simultaneous deployments. Our engineers have the agency to advocate for the tools they need to ship with quality and pace, and we're looking for FDEs who bring that same instinct. ### What You'll Do: - **Own deployments end to end:** Lead the full technical implementation of Conductor for each client, from kickoff through go-live, as the primary point of contact for their technical and operational stakeholders. Write the code, own the integration scope, and build the trust that turns a successful go-live into a long-term relationship. - **Accelerate the sales cycle:** Partner with the GTM team to drive deals forward. You'll run technical demos, prototype automations against a prospect's real workflows, and lead the sessions that give prospective clients the confidence to commit. - **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:** Be the first line of 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. ### What We're Looking For: **Experience** - 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 **Technical Skills** - 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 **Ways of Working** - You're an engineer first — your default response to a problem is to build a solution, not escalate 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 can manage multiple active deployments without dropping threads or cutting corners - You hold yourself to a high bar on both code quality and client outcomes