Principal Motion Planning Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description: "Every minute matters..." intro, then "We're looking for a Principal Motion Planning Engineer..." then bullet list of responsibilities (As our first hire...). Then "You Will Be" bullet list of responsibilities? Actually "You Will Be our technical expert..." then list of responsibilities. Then "You Are" bullet list of qualifications/experience. Then "Bonus Points" list of bonus experience. Then some boilerplate about equal opportunity etc which we should remove. No explicit Benefits, Pay, Schedule mentioned. So we should not include those sections. Also we should not include headings with filler. So we need sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe combine You Are?), Qualifications (maybe same as Requirements?), Skills (maybe list of technical skills), Benefits (none), Pay (none), Schedule (none). We need to decide which sections to include based on content. We have: - Intro paragraph: "Every minute matters in stroke treatment..." That's about the role/company. Could be About the role. - Responsibilities: list under "You Will Be our technical expert..." includes many bullet points. - Requirements/Qualifications: "You Are 9+ years of experience..." list. - Skills: maybe the technical proficiencies: Strong math, physics, robotics fundamentals, Expert in motion planning algorithms, Good understanding of collision checking, Proven ability to build production-grade systems, Strong proficiency in C++ and/or Python, etc. Could be separate Skills section. - Bonus Points: could be included under Skills or as separate "Preferred Qualifications". But we only have headings: Skills, Qualifications, Requirements. Could put Bonus under Skills or Qualifications. Probably better to have a "Preferred Qualifications" but not allowed heading. Could incorporate into Skills or Qualifications. We must not invent sections. We'll include About the role, Responsibilities, Requirements, Skills. Possibly also Qualifications if we differentiate. But we have overlapping content. To avoid thin sections, we can combine Requirements and Qualifications into one section called Requirements (or Qualifications). The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose which to include. We'll include About the role, Responsibilities, Requirements, Skills. Bonus points can be included under Skills as additional bullet points. We must not repeat job title as heading. No Job ID. We must preserve all substantive information. So we need to include all bullet points from responsibilities, requirements, bonus points. We need to format as

for each section heading. Use

• for lists. Use

  for prose. We must remove boilerplate: equal opportunity, E-Verify, etc. Let's extract content. Intro paragraph: "Every minute matters in stroke treatment. Magnendo is developing robotic technology to make life-saving endovascular procedures faster, safer, and more accessible. By combining advanced robotics, magnetic navigation, and intelligent software, we are tackling one of the most technically demanding challenges in healthcare while aiming to expand access to advanced stroke care for patients around the world. Join us in shaping the future of endovascular intervention." That's About the role. Responsibilities: after "We're looking for a Principal Motion Planning Engineer to lead the architecture, design, and development of collision-aware motion planning software for a medical grade robot arm operating in a complex and highly variable clinical environment. As our first hire in this domain, you will be a critical part of the small, dedicated team we are building to bring our breakthrough technology from prototype to FDA-approved product." Then bullet list starting with "You Will Be our technical expert for all things relating to collision-aware motion planning". Actually that's a heading then bullet list. Let's capture bullet points: - Own the architecture, implementation, and system documentation of our motion planning subsystem - Implement custom software that achieves high performance across key metrics for our application - Evolve and troubleshoot our motion planning software to address complex real-world circumstances as our system moves from prototype to production - Evaluate and select applicable 3rd party libraries and tools - Write clean, testable code that can be maintained and extended; document your designs clearly for cross-functional audiences - Help define and document coding styles, standards, and software development process and that reflects best practices for modern high reliability software development - Collaborate with Systems Engineers to define and review requirements, test plans, and acceptance criteria; support risk analysis, design reviews, and root-cause investigations - Provide technical leadership and guidance to other engineers in your domain That's responsibilities. Requirements/Qualifications: "You Are 9+ years of experience and demonstrated ability to deliver on the responsibilities described above (can be a combination of deep graduate research and industry experience) Strong math, physics, and robotics fundamentals (forward/inverse kinematics and dynamics, computational geometry) Expert in motion planning algorithms, including sampling-based methods (e.g., RRT, PRM), and trajectory optimization techniques (e.g., CHOMP, STOMP, TrajOpt) Good understanding of collision checking methods and collision model representations Proven ability to build production-grade systems that achieve highly reliable performance in real-world applications Strong proficiency in C++ and/or Python, with a firm grasp of real-time performance considerations, memory management, and software design patterns A good collaborator who understands the importance of clear communication and humility Able to clearly convey complex tradeoffs to cross-functional teams and external partners" That's qualifications. Bonus Points: list: - Experience with 3rd party motion planning libraries such as Drake and cuRobo - Experienced with scientific/high-performance edge compute platforms, able to benchmark and optimize CPU/GPU pipelines, memory access and alignment, caching, latency etc. - Experience in the medical device industry, ideally with interventional or robotic systems, working knowledge of medical device software requirements - Experience with autonomous systems, exposure to sensor integration and perception, including RGB, depth cameras, and point cloud processing, SLAM, or object detection as it pertains to reactive and perception-driven motion planning - Experience developing software under a regulatory framework such as medical device (e.g., IEC 62304, IEC 60601), functional safety (IEC 61508, ISO 13849), or automotive (ISO 26262) - Experience developing software under a regulatory framework such as medical device (IEC 60601), functional safety (IEC TBD), or automotive (IEC TBD) (some duplication but keep) We can include bonus points under Skills or as part of Requirements. Probably better to have Skills section that includes technical proficiencies and bonus points. Thus Skills section bullet list: - Strong math, physics, and robotics fundamentals (forward/inverse kinematics and dynamics, computational geometry) - Expert in motion planning algorithms, including sampling-based methods (e.g., RRT, PRM), and trajectory optimization techniques (e.g., CHOMP, STOMP, TrajOpt) - Good understanding of collision checking methods and collision model representations - Proven ability to build production-grade systems that achieve highly reliable performance in real-world applications - Strong proficiency in C++ and/or Python, with a firm grasp of real-time performance considerations, memory management, and software design patterns - Experience with 3rd party motion planning libraries such as Drake and cuRobo - Experienced with scientific/high-performance edge compute platforms, able to benchmark and optimize CPU/GPU pipelines, memory access and alignment, caching, latency etc. - Experience in the medical device industry, ideally with interventional or robotic systems, working knowledge of medical device software requirements - Experience with autonomous systems, exposure to sensor integration and perception, including RGB, depth cameras, and point cloud processing, SLAM, or object detection as it pertains to reactive and perception-driven motion planning - Experience developing software under a regulatory framework such as medical device (e.g., IEC 62304, IEC 60601), functional safety (IEC 61508, ISO 13849), or automotive (ISO 26262) - Experience developing software under a regulatory framework such as medical device (IEC 60601), functional safety (IEC TBD), or automotive (IEC TBD) - A good collaborator who understands the importance of clear communication and humility - Able to clearly convey complex tradeoffs to cross-functional teams and external partners But some of these overlap with Requirements. To avoid duplication, we could keep Requirements as the experience and soft skills, and Skills as technical proficiencies + bonus. However the instruction says preserve ALL substantive information; duplication is okay if it's in original? The original had both "You Are" list (which includes technical fundamentals etc.) and then Bonus Points list. There's some overlap but we can keep both sections: Requirements (the "You Are" list) and Skills (the technical fundamentals + bonus). However there is overlap between Requirements and Skills (e.g., strong math etc appears in both). To avoid duplication we could split: Requirements: experience, collaboration, communication. Skills: technical fundamentals, motion planning expertise, C++/Python, bonus points. That seems reasonable. Thus: About the role: paragraph. Responsibilities: list of 8 bullet points. Requirements: list: - 9+ years of experience and demonstrated ability to deliver on the responsibilities described above (can be a combination of deep graduate research and industry experience) - A good collaborator who understands the importance of clear communication and humility - Able to clearly convey complex tradeoffs to cross-functional teams and external partners Skills: list: - Strong math, physics, and robotics fundamentals (forward/inverse kinematics and dynamics, computational geometry) - Expert in motion planning algorithms, including sampling-based methods (e.g., RRT, PRM), and trajectory optimization techniques (e.g., CHOMP, STOMP, TrajOpt) - Good understanding of collision checking methods and collision model representations - Proven ability to build production-grade systems that achieve highly reliable performance in real-world applications - Strong proficiency in C++ and/or Python, with a firm grasp of real-time performance considerations, memory management, and software design patterns - Experience with 3rd party motion planning libraries such as Drake and cuRobo - Experienced with scientific/high-performance edge compute platforms, able to benchmark and optimize CPU/GPU pipelines, memory access and alignment, caching, latency etc. - Experience in the medical device industry, ideally with interventional or robotic systems, working knowledge of medical device software requirements - Experience with autonomous systems, exposure to sensor integration and perception, including RGB, depth cameras, and point cloud processing, SLAM, or object detection as it pertains to reactive and perception-driven motion planning - Experience developing software under a regulatory framework such as medical device (e.g., IEC 62304, IEC 60601), functional safety (IEC 61508, ISO 13849), or automotive (ISO 26262) - Experience developing software under a regulatory framework such as medical device (IEC 60601), functional safety (IEC TBD), or automotive (IEC TBD) We should not include Benefits, Pay, Schedule sections. Now produce HTML fragment:

  About the role

  Every minute matters in stroke treatment. Magnendo is developing robotic technology to make life-saving endovascular procedures faster, safer, and more accessible. By combining advanced robotics, magnetic navigation, and intelligent software, we are tackling one of the most technically demanding challenges in healthcare while aiming to expand access to advanced stroke care for patients around the world. Join us in shaping the future of endovascular intervention.

  Responsibilities

  • Own the architecture, implementation, and system documentation of our motion planning subsystem
  • Implement custom software that achieves high performance across key metrics for our application
  • Evolve and troubleshoot our motion planning software to address complex real-world circumstances