Senior Staff, Product Safety Engineer
or drop it." So we can include a short paragraph for eligibility and visa sponsorship note maybe. We need to preserve all substantive information. Let's extract sections: - About the role: The first paragraph: "Boston Dynamics is looking for a Senior Staff, Product Safety Engineer to join our product safety and compliance team. The Product Safety and Compliance team drives a systematic approach to the design, test, and manufacture of safe products at Boston Dynamics. As a Product Safety Engineer, you will provide independent safety assurance for our legged robotic systems across the full product lifecycle. The role will develop and maintain safety strategies, safety cases, safety requirements, safety assurance processes and objective evidence across hardware, software, firmware, controls, AI/ML, perception, actuation, and human-robot interaction. The role will evaluate the safety impact of product and software changes, support release and update governance , and ensure safety practices remain robust as robotic platforms, capabilities, and operational environments evolve. This role partners closely with Product, Systems Engineering/System Safety Engineering, Hardware, Software, Firmware, AI/ML, Quality, Security, and Legal, to confirm safety requirements are properly defined, implemented, verified, and validated. You will also help translate applicable standards and regulatory expectations into practical engineering and operational processes. This role is key to shaping the future of our mobile robots. We’re looking for creative, passionate product safety engineers with strong backgrounds in autonomous systems, to tackle one of the biggest challenges in the field: robot safety. You will help set the practical standards by which our robots sense, plan, and act safely, and you’ll shape how Boston Dynamics demonstrates that its systems are safe. Boston Dynamics is a world leader in mobile robots, tackling some of the toughest robotics challenges. For years, our awe-inspiring viral videos on YouTube have shown the world what remarkably capable robots can do. Now we are quickly becoming a recognized leader in automation solutions for industrial applications and warehouse logistics." That's about the role. - What You’ll Do: list of responsibilities. - What You Bring: qualifications/requirements. - Travel: Up to 10% travel. - Salary: base pay range $135,000 - $167,000. - Visa sponsorship note: not able to sponsor visas. - Eligibility: interested in every qualified candidate eligible to work in US. - Additional statements about not asking for personal financial info. We need sections: About the role (we have), Responsibilities (What You’ll Do), Requirements (maybe combine What You Bring?), Qualifications (maybe education), Skills (maybe specific skills), Benefits (none explicit), Pay (salary range), Schedule (travel maybe considered schedule? Not exactly schedule; but travel is not schedule. There's no explicit schedule like full-time, part-time, shift. So we should not create Schedule section unless present. There's no schedule info. So omit Schedule. Benefits: none explicit. So omit Benefits. Pay: we have salary range. We need to use
for section headings.
We need - for any list of duties/requirements/benefits.
We need
for prose.
We must not repeat job title as heading.
We must not include boilerplate like EEO etc. There's none.
We need to preserve all substantive information.
Let's structure:
About the role
... (the about paragraph)
Responsibilities
- Provide safety assurance across the full technical stack (hardware through AI/ML) and support readiness reviews and safety gate sign-off for new capabilities (e.g., autonomous navigation, dynamic locomotion, manipulation, human-robot interaction -HRI, AI-enabled behaviors).
- Develop and evaluate V&V strategies, acceptance criteria, test coverage, and objective safety evidence ensuring safety requirements and risk controls perform as intended.
- Prepare recommendations and evaluate safety analyses, claims, mitigations, and readiness evidence across perception, planning, controls, locomotion, actuation, and HRI to determine if claims are adequately supported.
- Evaluate safety implications of releases, firmware updates, model changes, configuration changes, and hardware revisions – including drive-by-wire actuation, fault detection, and safe-state behavior – as part of change impact assessments.
- Support incident investigations, corrective actions, post-market monitoring, and incorporation of field learning into safety assurance.
- Collaborate with engineering teams and Safety Case owners to ensure consistency in safety processes, evidence quality, rigor, maturity across products and platforms.
- Translate global and domestic regulations, standards, and certification expectations into internal safety policy and procedures and support continuous improvement of the Safety
Note: The last bullet truncated: "and support continuous improvement of the Safety". The original text: "Translate global and domestic regulations, standards, and certification expectations into internal safety policy and procedures and support continuous improvement of the Safety". It seems cut off; maybe originally "Safety program" or "Safety culture". We'll keep as is.
Requirements
Maybe combine education and experience.
But we have sections: Qualifications, Skills. The posting includes "What You Bring" which includes education, years experience, understanding, V&V expertise, systems engineering understanding, experience with safety-critical software development, familiarity with standards, experience with safety certification, ability to challenge assumptions, strong written/verbal skills, ability to influence cross-functional teams.
We could split into Qualifications (education + years experience) and Skills (technical skills). But we need to avoid thin sections. Perhaps combine into one "Qualifications and Skills" but we must use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for the core mandatory qualifications (education, experience). Then Skills for specific technical skills.
Let's decide:
Requirements: Bachelor’s or Master’s degree in EE, CE, ME, Systems Engineering, Robotics, or related discipline; 6+ years in product safety, systems safety, functional safety, safety assurance, V&V, robotics, autonomous systems, automotive, aerospace, medical devices or another safety-critical field.
Qualifications: Understanding of AI/ML safety implications and AI-enabled system V&V; Demonstrated V&V expertise, including test strategy, methodology, acceptance criteria, coverage, and objective (normative) safety evidence; Strong systems engineering understanding across hardware, software, firmware, controls, sensors, actuators, cyber-physical systems; Experience with safety-critical software development, software release processes, software quality assurance, configuration management, or safety-related change management, hazard analysis, FMEA/FMECA, STPA, STAMP, risk assessment, or equivalent methodologies; Familiarity with IEC 61508, ISO 21448/SOTIF, ISO 13849, IEC 62061, ISO 42001, ISO/IEC TS 22440, EU AI Act and/or applicable robotics safety standards; Experience with safety certification, regulatory submissions, audits or external safety assessments in the areas of autonomous, mobile, industrial, humanoid, quadruped or other robotic systems is preferred; Ability to independently challenge technical assumptions and assess residual risk; Strong written and verbal skills; Ability to influence cross-functional teams without relying on organizational authority.
Skills: maybe we could list specific skills like hazard analysis, FMEA, etc. But that overlaps.
Alternatively, we could treat "What You Bring" as Requirements and Qualifications combined, and not create Skills section. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Requirements (education+experience). We have content for Qualifications (understanding, V&V expertise, systems engineering, software dev, standards familiarity, certification experience, challenge assumptions, communication, influence). We have content for Skills? Could be the specific methodologies (FMEA, STPA, etc.) but those are already in Qualifications. Might be redundant.
We could make Skills empty? No, we must not create empty sections. So we either omit Skills or combine into Qualifications. Since we have both Requirements and Qualifications content, we can keep both and omit Skills.
Pay: we have salary range.
Schedule: we have travel up to 10% - could be considered schedule? Not exactly schedule but maybe we can treat as Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Travel is not schedule; schedule would be like full-time, part-time, shift. Not present. So omit Schedule.
Benefits: none.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay.
We also might include a short paragraph for eligibility/visa note. Could be placed under a short p after Pay or as a note. Not a heading.
Let's craft.
We need to ensure we don't duplicate lines.
Now produce HTML fragment.
Let's write:
About the role
Boston Dynamics is looking for a Senior Staff, Product Safety Engineer to join our product safety and compliance team. The Product Safety and Compliance team drives a systematic approach to the design, test, and manufacture of safe products at Boston Dynamics. As a Product Safety Engineer, you will provide independent safety assurance for our legged robotic systems across the full product lifecycle. The role will develop and maintain safety strategies, safety cases, safety requirements, safety assurance processes and objective evidence across hardware, software, firmware, controls, AI/ML, perception, actuation, and human-robot interaction. The role will evaluate the safety impact of product and software changes, support release and update governance, and ensure safety practices remain robust as robotic platforms, capabilities, and operational environments evolve. This role partners closely with Product, Systems Engineering/System Safety Engineering, Hardware, Software, Firmware, AI/ML, Quality, Security, and Legal, to confirm safety requirements are properly defined, implemented, verified, and validated. You will also help translate applicable standards and regulatory expectations into practical engineering and operational processes. This role is key to shaping the future of our mobile robots. We’re looking for creative, passionate product safety engineers with strong backgrounds in autonomous systems, to tackle one of the biggest challenges in the field: robot safety. You will help set the practical standards by which our robots sense, plan, and act safely, and you’ll shape how Boston Dynamics demonstrates that its systems are safe. Boston Dynamics is a world leader in mobile robots, tackling some of the toughest robotics challenges. For years, our awe-inspiring viral videos on YouTube have shown the world what remarkably capable robots can do. Now we are quickly becoming a recognized leader in automation solutions for industrial applications and warehouse logistics.
Responsibilities
- Provide safety assurance across the full technical stack (hardware through AI/ML) and support readiness reviews and safety gate sign-off for new capabilities (e.g., autonomous navigation, dynamic locomotion, manipulation, human-robot interaction -HRI, AI-enabled behaviors).
- Develop and evaluate V&V strategies, acceptance criteria, test coverage, and objective safety evidence ensuring safety requirements and risk controls perform as intended.
- Prepare recommendations and evaluate safety analyses, claims, mitigations, and readiness evidence across perception, planning, controls, locomotion, actuation, and HRI to determine if claims are adequately supported.
- Evaluate safety implications of releases, firmware updates, model changes, configuration changes, and hardware revisions – including drive
for prose. We must not repeat job title as heading. We must not include boilerplate like EEO etc. There's none. We need to preserve all substantive information. Let's structure:
About the role
... (the about paragraph)
Responsibilities
- Provide safety assurance across the full technical stack (hardware through AI/ML) and support readiness reviews and safety gate sign-off for new capabilities (e.g., autonomous navigation, dynamic locomotion, manipulation, human-robot interaction -HRI, AI-enabled behaviors).
- Develop and evaluate V&V strategies, acceptance criteria, test coverage, and objective safety evidence ensuring safety requirements and risk controls perform as intended.
- Prepare recommendations and evaluate safety analyses, claims, mitigations, and readiness evidence across perception, planning, controls, locomotion, actuation, and HRI to determine if claims are adequately supported.
- Evaluate safety implications of releases, firmware updates, model changes, configuration changes, and hardware revisions – including drive-by-wire actuation, fault detection, and safe-state behavior – as part of change impact assessments.
- Support incident investigations, corrective actions, post-market monitoring, and incorporation of field learning into safety assurance.
- Collaborate with engineering teams and Safety Case owners to ensure consistency in safety processes, evidence quality, rigor, maturity across products and platforms.
- Translate global and domestic regulations, standards, and certification expectations into internal safety policy and procedures and support continuous improvement of the Safety
Requirements
Maybe combine education and experience. But we have sections: Qualifications, Skills. The posting includes "What You Bring" which includes education, years experience, understanding, V&V expertise, systems engineering understanding, experience with safety-critical software development, familiarity with standards, experience with safety certification, ability to challenge assumptions, strong written/verbal skills, ability to influence cross-functional teams. We could split into Qualifications (education + years experience) and Skills (technical skills). But we need to avoid thin sections. Perhaps combine into one "Qualifications and Skills" but we must use headings from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use Requirements for the core mandatory qualifications (education, experience). Then Skills for specific technical skills. Let's decide: Requirements: Bachelor’s or Master’s degree in EE, CE, ME, Systems Engineering, Robotics, or related discipline; 6+ years in product safety, systems safety, functional safety, safety assurance, V&V, robotics, autonomous systems, automotive, aerospace, medical devices or another safety-critical field. Qualifications: Understanding of AI/ML safety implications and AI-enabled system V&V; Demonstrated V&V expertise, including test strategy, methodology, acceptance criteria, coverage, and objective (normative) safety evidence; Strong systems engineering understanding across hardware, software, firmware, controls, sensors, actuators, cyber-physical systems; Experience with safety-critical software development, software release processes, software quality assurance, configuration management, or safety-related change management, hazard analysis, FMEA/FMECA, STPA, STAMP, risk assessment, or equivalent methodologies; Familiarity with IEC 61508, ISO 21448/SOTIF, ISO 13849, IEC 62061, ISO 42001, ISO/IEC TS 22440, EU AI Act and/or applicable robotics safety standards; Experience with safety certification, regulatory submissions, audits or external safety assessments in the areas of autonomous, mobile, industrial, humanoid, quadruped or other robotic systems is preferred; Ability to independently challenge technical assumptions and assess residual risk; Strong written and verbal skills; Ability to influence cross-functional teams without relying on organizational authority. Skills: maybe we could list specific skills like hazard analysis, FMEA, etc. But that overlaps. Alternatively, we could treat "What You Bring" as Requirements and Qualifications combined, and not create Skills section. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Requirements (education+experience). We have content for Qualifications (understanding, V&V expertise, systems engineering, software dev, standards familiarity, certification experience, challenge assumptions, communication, influence). We have content for Skills? Could be the specific methodologies (FMEA, STPA, etc.) but those are already in Qualifications. Might be redundant. We could make Skills empty? No, we must not create empty sections. So we either omit Skills or combine into Qualifications. Since we have both Requirements and Qualifications content, we can keep both and omit Skills. Pay: we have salary range. Schedule: we have travel up to 10% - could be considered schedule? Not exactly schedule but maybe we can treat as Schedule section? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Travel is not schedule; schedule would be like full-time, part-time, shift. Not present. So omit Schedule. Benefits: none. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. We also might include a short paragraph for eligibility/visa note. Could be placed under a short p after Pay or as a note. Not a heading. Let's craft. We need to ensure we don't duplicate lines. Now produce HTML fragment. Let's write:About the role
Boston Dynamics is looking for a Senior Staff, Product Safety Engineer to join our product safety and compliance team. The Product Safety and Compliance team drives a systematic approach to the design, test, and manufacture of safe products at Boston Dynamics. As a Product Safety Engineer, you will provide independent safety assurance for our legged robotic systems across the full product lifecycle. The role will develop and maintain safety strategies, safety cases, safety requirements, safety assurance processes and objective evidence across hardware, software, firmware, controls, AI/ML, perception, actuation, and human-robot interaction. The role will evaluate the safety impact of product and software changes, support release and update governance, and ensure safety practices remain robust as robotic platforms, capabilities, and operational environments evolve. This role partners closely with Product, Systems Engineering/System Safety Engineering, Hardware, Software, Firmware, AI/ML, Quality, Security, and Legal, to confirm safety requirements are properly defined, implemented, verified, and validated. You will also help translate applicable standards and regulatory expectations into practical engineering and operational processes. This role is key to shaping the future of our mobile robots. We’re looking for creative, passionate product safety engineers with strong backgrounds in autonomous systems, to tackle one of the biggest challenges in the field: robot safety. You will help set the practical standards by which our robots sense, plan, and act safely, and you’ll shape how Boston Dynamics demonstrates that its systems are safe. Boston Dynamics is a world leader in mobile robots, tackling some of the toughest robotics challenges. For years, our awe-inspiring viral videos on YouTube have shown the world what remarkably capable robots can do. Now we are quickly becoming a recognized leader in automation solutions for industrial applications and warehouse logistics.
Responsibilities
- Provide safety assurance across the full technical stack (hardware through AI/ML) and support readiness reviews and safety gate sign-off for new capabilities (e.g., autonomous navigation, dynamic locomotion, manipulation, human-robot interaction -HRI, AI-enabled behaviors).
- Develop and evaluate V&V strategies, acceptance criteria, test coverage, and objective safety evidence ensuring safety requirements and risk controls perform as intended.
- Prepare recommendations and evaluate safety analyses, claims, mitigations, and readiness evidence across perception, planning, controls, locomotion, actuation, and HRI to determine if claims are adequately supported.
- Evaluate safety implications of releases, firmware updates, model changes, configuration changes, and hardware revisions – including drive