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 Provider 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 others who bring that same instinct.

How you'll make an impact:

Own the architecture, design, development, deployment, and operations of the solutions you build
Improve provider patient flow and quality of care across the full stack on the features you ship
Reduce manual effort for provider partners by building smarter workflow automation
Design and implement integrations that connect provider systems to PocketHealth, eliminating gaps in information exchange
Bring strong user empathy and a focus on quality and speed to everything you ship

What you'll need to be successful:

5+ years of software engineering experience with a full-stack skill set (our tech stack: Go, Angular, TypeScript, C#, MySQL)
Experience building and maintaining scalable, reliable integrations and customer-facing applications
Familiarity with CI/CD practices and microservices architecture
Experience with UIs that have scaled in production
Comfort owning production services end-to-end, from observability and monitoring to incident response and resolution
A collaborative mindset, strong communication skills, and a proven ability to work across teams without losing your sense of ownership
Bachelor's degree in Software Engineering, Computer Science, or equivalent experience

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