ironquill.tech/board

$ cat jobs/staff-systems-engineer-pleasanton-ca-calyxo-3378b3e9f780.json

Staff Systems Engineer - Pleasanton, CA

Calyxo·Worldwide·Pleasanton, CA·senior
Apply on greenhouse → Get AI match score →
Calyxo, Inc. is a medical device company headquartered in Pleasanton, California, USA. The company was founded in 2016 to address the profound need for improved kidney stone treatment. Kidney stone disease is a common, painful condition that consumes vast amounts of healthcare resources each year. Our team is led by executives and investors with a proven track record of commercializing paradigm-shifting devices to meet unmet needs within urology. Are you ready to change the future of kidney stone treatment? We are seeking high achievers who want to be part of a dynamic team working in a fun, diverse atmosphere. Summary: Calyxo is seeking a Staff Systems Engineer to architect , validate , and own the system-level behavior of a complex medical device ecosystem throughout the entire product development lifecycle. You will define and own the end-to-end system architecture , translate user and business needs into robust system and subsystem requirements, validate architectural decisions through prototyping and bench testing, and proactively de ‑ risk critical technical challenges. This role carries direct accountability for system-level requirements ownership and verification . The ideal c and idate combines h and s -on medical device experience , strong systems thinking , and the technical leadership expected of a staff -level engineer operating across hardware, software, disposables, and clinical use environments. In This Role, You Will : System Architecture : Architect systems with a strong focus on technical and patient risk mitigation. Establish and control system interfaces, including fluidic, mechanical, electrical, and software-control boundaries. Drive architectural trade studies using bench testing, prototyping, and simulation to validate design decisions. Ensure architectural robustness across intended use, misuse, fault conditions, and edge cases. Requirements Ownership & Decomposition: Own creation, maintenance, and verification of system-level requirements,