Senior Software Engineer (Patient)
Confirmed on the employer's own hiring board on Nov 5, 2026. First seen by Alion on Sep 15, 2026.
About the team:
As a Senior Software Engineer on our Patient team, you will have the opportunity to apply your backend or fullstack expertise towards building the next generation of our core infrastructure that will enable thousands of hospitals and clinics - and empower millions of patients - to discover a better healthcare experience. You’ll be joining an experienced, friendly and supportive team of Engineers eager to learn, teach and ultimately make a difference.
How you’ll make an impact:
In this role on the Patient Core team, you'll build and own the backend services behind the patient experience. These are the systems that get patients their medical imaging records and let them share those records with the doctors who need them next. You will own the architecture, design, development, deployment, and operations of the solutions that you develop. Ideal candidates will possess a high degree of user empathy and a focus on the quality and speed of our product. Patient Core is where the promise of PocketHealth actually lands: a patient gets their scan in minutes instead of driving across the city for a CD. Getting that right at scale - reliably, privately, and fast - is the mandate of this team, and we need your help to bring it to life.
This job posting is for an existing vacancy. The salary range for this position is $140,000 - $170,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 at PocketHealth - 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 others who bring that same instinct.
What you'll do:
- Collaborating with cross-functional teams to understand integration requirements and design solutions that enhances functionality
- Developing and implementing solutions to connect our platform with provider applications
- Writing and testing your own code (unit/integration/functional testing), and peer testing others’
- Working closely with PMs, other devs, Customer Support & Implementation teams to get feedback & continuously improve integration features
What you'll bring:
- Bachelor’s degree in Software Engineering, Computer Science, or equivalent/similar
- 4+ years of experience as a Software Engineer, with a Backend focussed or broad Full Stack skill set
- Experience building/maintaining scalable, reliable integrations and building customer-facing applications
- Understanding of CI/CD
- Experience building and maintaining microservices/experience
- Some experience working with user interfaces that have scaled
- A collaborative mindset, strong communication skills and a proven ability to partner with teams across an organization while maintaining a strong sense of ownership
Technologies we use:
Go, MySQL, TypeScript, Angular
We currently use the following in our tech stack, but experience with each of these specific tools isn’t necessary. We know languages and tools are portable, and familiarity with something similar is ok!