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 of role, responsibilities, requirements, qualifications, maybe skills. No explicit Benefits, Pay, Schedule. So we should include About the role (maybe intro), Responsibilities (the bullet list of duties), Requirements (maybe years of experience?), Qualifications (the "You Are" list), Skills (maybe the bullet list of abilities). We need to parse the posting.
Let's extract:
Intro: "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. We're looking for a Technical Fellow to serve as a top technical authority across three critical areas of our system: the hardware infrastructure for our robotic platform, the procedural workflow and usability requirements that shape our UI/UX, and the design of our steerable guidewire itself. This is a special role for someone who can move fluidly between systems-level hardware architecture, clinical workflow, and medical device design."
That's about the role.
Responsibilities: The bullet list after "You Will Own" etc. Let's capture each line:
- Own systems engineering for the hardware components of our platform, including the carts that house our robot and sensors and the advancer unit that drives the magnetic guidewire and other devices, all in the context of relevant medical device safety standards (e.g., IEC 60601, ISO 14971)
- Define and drive the requirements, architecture, and interfaces across these hardware subsystems, balancing mechanical, electrical, magnetic, and controls considerations
- Partner with external (contract/vendor) hardware design teams to define, review, and validate mechanical and electromechanical requirements
- Define requirements around procedural workflows and usability that drive our UI/UX design, applying human factors and usability engineering practices consistent with IEC 62366-1, and working closely with clinical, software, and human factors partners
- Lead guidewire design, from concept through prototyping and iteration, in close partnership with our contract manufacturer
- Partner with and provide technical guidance to a process engineer supporting guidewire manufacturing and process development
- Serve as a top technical authority across systems, hardware, and guidewire design, providing technical oversight to internal engineers and external contractors and partners
- Drive design decisions using first-principles engineering analysis, simulation, and hands-on prototyping and testing
- Define and review requirements, test plans, and acceptance criteria across the hardware and guidewire subsystems you own
- Collaborate closely with systems, software, robotics, and clinical teams to integrate your designs into the broader system
- Support risk analysis, design reviews, and root-cause investigations across your areas of ownership, consistent with ISO 14971 risk management practices
- Help mature design and quality processes appropriate for a regulatory V-model framework as the company scales toward clinical and commercial products (e.g., ISO 13485, ISO 14971)
That's responsibilities.
Requirements: maybe the "You Are" list includes experience requirements: "13 + years of experience (BS) / 11+ years (MS) / 8+ years (PhD) with hands-on experience in both medical device engineering and robotics across hardware systems, workflow/UX, and minimally invasive medical device design". That's a requirement. Also "Demonstrated experience owning systems-level hardware architecture and requirements across mechanical, electrical, and controls disciplines, with designs that have met medical device standards such as IEC 60601". Also "Experience defining procedural workflow and usability requirements that inform UI/UX design, shaped by usability engineering standards such as IEC 62366-1, in a clinical or procedural setting". Also "Background in guidewire, catheter, or related interventional device design under ISO 13485 design controls, including work with contract manufacturers and awareness of biocompatibility requirements (ISO 10993)". Also "Comfortable serving as a top technical authority - providing design guidance and review to internal engineers, external contractors, and future direct reports alike". Also "Proven track record of innovative technical problem-solving, backed by a portfolio of patents or other tangible evidence of novel contributions to the field". Also "Able to operate with the judgment and independence expected of a Technical Fellow, setting technical direction with limited oversight across multiple disciplines, while holding the line on rigor where it matters most". Also "Excellent communicator, able to clearly convey complex technical tradeoffs across hardware, workflow, and device design to cross-functional teams and external partners". Also "An adept, fast learner who is comfortable in a fast-paced environment". Those could be qualifications or skills.
We need to decide sections: About the role (intro), Responsibilities (list), Qualifications (the "You Are" list maybe), Skills (maybe the bullet list of abilities like communication, fast learner, etc). But we must not create sections with filler. We need to ensure each section has substantive content.
We could combine Qualifications and Skills into one section "Qualifications" that includes experience, background, etc. Or we could split: Requirements (experience years) and Qualifications (background, etc). But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only those with real content.
Let's map:
- About the role: intro paragraph(s).
- Responsibilities: the bullet list under "You Will Own".
- Requirements: maybe the years of experience requirement (13+ years BS etc). That's a specific requirement.
- Qualifications: the list of demonstrated experience, background, etc (the "You Are" items after the years line). Could be considered qualifications.
- Skills: maybe the abilities like communication, fast learner, etc. Could be considered skills.
But we need to ensure we don't repeat content. Let's extract distinct blocks.
Block A: Intro (About the role).
Block B: Responsibilities (You Will Own ... list).
Block C: Requirements: "You Are 13 + years of experience (BS) / 11+ years (MS) / 8+ years (PhD) with hands-on experience in both medical device engineering and robotics across hardware systems, workflow/UX, and minimally invasive medical device design". That's a requirement.
Block D: Qualifications: The rest of the "You Are" list after that line? Actually the "You Are" heading includes years line then bullet points? The posting shows:
You Are 13 + years of experience (BS) / 11+ years (MS) / 8+ years (PhD) with hands-on experience in both medical device engineering and robotics across hardware systems, workflow/UX, and minimally invasive medical device designDemonstrated experience owning systems-level hardware architecture and requirements across mechanical, electrical, and controls disciplines, with designs that have met medical device standards such as IEC 60601Experience defining procedural workflow and usability requirements that inform UI/UX design, shaped by usability engineering standards such as IEC 62366-1, in a clinical or procedural settingBackground in guidewire, catheter, or related interventional device design under ISO 13485 design controls, including work with contract manufacturers and awareness of biocompatibility requirements (ISO 10993)Comfortable serving as a top technical authority - providing design guidance and review to internal engineers, external contractors, and future direct reports alikeProven track record of innovative technical problem-solving, backed by a portfolio of patents or other tangible evidence of novel contributions to the fieldAble to operate with the judgment and independence expected of a Technical Fellow, setting technical direction with limited oversight across multiple disciplines, while holding the line on rigor where it matters mostExcellent communicator, able to clearly convey complex technical tradeoffs across hardware, workflow, and device design to cross-functional teams and external partnersAn adept, fast learner who is comfortable in a fast-paced environment Bonus Points Experience with design considerations for systems operating in the presence of a strong magnetic fieldPrior experience managing or partnering closely with a process engineer or manufacturing engineering functionTrack record of patents, publications, or industry recognition reflecting deep technical expertise
So after the years line, there is a series of statements without clear bullet separation. We can treat each sentence as a qualification/skill.
We could split: Qualifications: the demonstrated experience, background, comfort as authority, proven track record, ability to operate with judgment, etc. Skills: excellent communicator, fast learner, bonus points items.
But we need to avoid thin sections. Perhaps we can combine all after years into a single "Qualifications" section that includes both experience and skills. That would be substantive.
Thus sections: About the role, Responsibilities, Requirements (years), Qualifications (the rest). No Benefits, Pay, Schedule.
Let's craft HTML:
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. We're looking for a Technical Fellow to serve as a top technical authority across three critical areas of our system: the hardware infrastructure for our robotic platform, the procedural workflow and usability requirements that shape our UI/UX, and the design of our steerable guidewire itself. This is a special role for someone who can move fluidly between systems-level hardware architecture, clinical workflow, and medical device design.
Responsibilities
Own systems engineering for the hardware components of our platform, including the carts that house our robot and sensors and the advancer unit that drives the magnetic guidewire and other devices, all in the context of relevant medical device safety standards (e.g., IEC 60601, ISO 14971)
Define and drive the requirements, architecture, and interfaces across these hardware subsystems, balancing mechanical, electrical, magnetic, and controls considerations
Partner with external (contract/vendor) hardware design teams to define, review, and validate mechanical and electromechanical requirements
Define requirements around procedural workflows and usability that drive our UI/UX design, applying human factors and usability engineering practices consistent with IEC 62366-1, and working closely with clinical, software, and human factors partners
Lead guidewire design, from concept through prototyping and iteration, in close partnership with our contract manufacturer
Partner with and provide technical guidance to a process engineer supporting guidewire manufacturing and process development
Serve as a top technical authority across systems, hardware, and guidewire design, providing technical oversight to internal engineers and external contractors and partners
Drive design decisions using first-principles engineering analysis, simulation, and hands-on prototyping and testing
Define and review requirements, test plans, and acceptance criteria across the hardware and guidewire subsystems you own
Collaborate closely with systems, software, robotics, and clinical teams to integrate your designs into the broader system
Support risk analysis, design reviews, and root-cause investigations across your areas of ownership, consistent with ISO 14971 risk management practices
Help mature design and quality processes appropriate for a regulatory V-model framework as the company scales toward clinical and commercial products (e.g., ISO 13485, ISO 14971)
Requirements
13+ years of experience (BS) / 11+ years (MS) / 8+ years (PhD) with hands-on experience in both medical device engineering and robotics across hardware systems, workflow/UX, and minimally invasive medical device design.