We are looking for asystems engineerto own the requirements, specifications, and cross-domain integration of one or more medical devices. You will define what the system must do, ensure the specifications are clear and testable, and unblock the software, mechatronics, and cv/ml teams who are building it.key responsibilities: elicit, analyze, and document system-level requirements by collaborating with product, engineering, and clinical/scientific teams. Translate clinical and user needs into clear, structured, testable specifications (shall-statements, use cases, interface definitions) that software and mechatronics engineers can build against. Establish and maintain a traceability matrix linking clinical user needs / system requirements / software/hardware specifications / verification activities. Manage requirement specifications using tools such as jira, confluence, jama, or doors. Define and document system interfaces between subsystems: mechanical, electrical, firmware, application software, and computer vision. Contribute to architecture decisions including hardware abstraction layers, message bus design, motion control strategies, and sensor integration patterns. Create and maintain system architecture diagrams, interface control documents (icds), and timing/sequence specifications. Unblock implementation teams by clarifying requirements, resolving specification ambiguities, and making system-level decisions when trade-offs span multiple disciplines. Apply model-based systems engineering (mbse) practices using sysml. Define system-level test strategies and acceptance criteria.qualifications bachelor's degree in computer science or related field. 7+ years of experience writing structured requirements and specifications (shall-statements, use cases, icds, interface definitions). Demonstrated ability to work across mechanical, electrical, and software domains. Familiarity with requirements management and traceability tools (doors, jama, jira.) Skilled on motion control systems, robotics, or precision automation. Strong troubleshooting methodology —ability to isolate root causes across hardware/ software boundaries. Excellent written and verbal communication — you can make the complex understandable to both engineers and clinicians. English full professional proficiency.