Staff Software Engineer, Product
Job description
About the role
This position is responsible for defining, building, and scaling the core platform that powers autonomous AI workflows in production for global organizations. The role operates at the critical intersection of infrastructure, language tooling, and experimentation to enable mission-critical automations that support clinicians and administrators. The primary focus is on creating robust abstractions and execution patterns that allow complex workflows to run reliably at scale. Success in this role means owning the foundational systems that translate product intent into stable, high-performance software. The work directly impacts how healthcare operations teams automate intricate manual processes. You will partner closely with product and clinical stakeholders to ensure the platform meets stringent real-world requirements. Ultimately, this role shapes the architecture that determines the speed and reliability of AI-driven automation.
Key facts
What you'll do
Shape the general execution patterns for the platform through the design of language tooling and abstractions that make complex workflows understandable and maintainable.
Architect and maintain distributed computing environments to ensure reliable, scalable execution of AI workloads across heterogeneous infrastructure.
Lead core technical initiatives that establish high-quality, maintainable foundations within the primary codebase and influence long-term architectural direction.
Design and implement high-performance system components that navigate key architectural trade-offs to meet strict production requirements.
Integrate and optimize modern infrastructure stacks, including message streaming platforms like Kafka and container orchestration with Kubernetes, to support resilient workflows.
Apply deep knowledge of parallel computing concepts and distributed systems to solve bottlenecks and ensure efficient resource utilization.
Collaborate across the entire engineering stack to troubleshoot complex issues, requiring comfort with low-level debugging and high-level system strategy.
Communicate technical decisions clearly and effectively to both technical and non-technical audiences, translating product needs into engineering specifications.
Evaluate and adopt new tools and patterns that improve developer velocity, testing rigor, and overall system reliability in a fast-paced growth environment.
Mentor other engineers by setting examples in code quality, system design, and ownership of end-to-end project execution.
Ensure that all solutions adhere to security, compliance, and operational standards required for deployment in regulated healthcare environments.
Drive the implementation of observability and monitoring strategies to gain insight into workflow performance and platform health.
Champion best practices in software engineering, including rigorous code review, testing, and refactoring to sustain a high-trust engineering culture.
Partner with clinical operations teams to understand workflow constraints and translate them into robust software implementations.
Requirements
The posting states a bachelor's degree requirement. Possess a minimum of 8+ years of professional experience as a software engineer, including a demonstrated history of spearheading zero-to-one engineering projects from conception through production.
Show a proven track record of consistently shipping high-quality, reliable code on challenging projects under tight deadlines.
Bring direct experience designing, implementing, and operating high-performance systems in production environments, including navigating complex architectural trade-offs.
Demonstrate familiarity with modern infrastructure stacks and protocols, specifically message streaming systems like Kafka and container orchestration platforms like Kubernetes.
Show strong knowledge of parallel computing concepts, concurrency models, and the fundamentals of distributed systems to build resilient and scalable services.
Exhibit exceptional problem-solving abilities and the capacity to work effectively across the entire software stack, from infrastructure libraries to user-facing features.
Hold a stated bachelor's degree as required by the official application page, which verifies foundational knowledge relevant to the role.
Display strong written and verbal communication skills necessary for articulating technical trade-offs and collaborating with interdisciplinary teams.
Commit to working within the constraints of regulated industries, understanding that compliance and security are non-negotiable aspects of the development lifecycle.
Practical notes
Typical interview steps
Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.
Good to know
Roles of this type focus on platform infrastructure, distributed systems, and language tooling. Common tools include compilers, interpreters, DSLs, Kafka, and Kubernetes. Senior positions emphasize ownership of architecture and execution in high-growth environments.
Questions to ask
Useful questions for the interview: what a typical week looks like, how work is assigned, what tools the team uses, and how feedback works. Asking how the role has changed recently and what the team wishes it had known when joining is also reasonable. Questions about the manager's priorities are especially valued.
Career growth
Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.
About the company
Healthcare operations have always depended on people to bridge the gaps that technology couldn't. It relies on complex manual work to carry out critical internal processes, yet most health systems don't have enough resources to properly automate these tasks, leaving them stuck in outdated, labor-intensive SOPs.