Principal Product Cybersecurity Assurance Engineer
for section headings
- Use - for lists
- Use
for prose
- Don't repeat job title as heading
- Don't put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/scam-warning)
- Include section ONLY when real content exists
- Never emit heading followed by filler/placeholder text
- No Pay/Schedule/Benefits sections unless explicitly stated (but "What We Offer" is benefits, so include)
- Output ONLY HTML fragment
Let me structure this:
1. About the role - there's an introductory paragraph before "About The Role" heading in the text. Actually the text starts with "Here at Humanoid..." then "About The Role" then "We are seeking...". I'll treat the first paragraph as intro, then "About the role" as a section? But the rule says don't repeat job title as heading. The job title is "Principal Product Cybersecurity Assurance Engineer". The text has "About The Role" as a heading. I'll use that as an h3.
Actually looking at the text: "About The Role" appears as a heading in the source. Then "What You'll Do" with subsections. Then "What We're Looking For". Then "Preferred". Then "What We Offer".
I'll create sections for:
- About the role (the paragraph after "About The Role")
- Responsibilities (What You'll Do) - with subsections as nested lists or separate sections? The rules say use h3 for section headings. The subsections under "What You'll Do" could be h4 but the rule only mentions h3. I'll keep them as h3 or maybe use h3 for main sections and h4 for subsections? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention h4. But the subsections are distinct. I think I'll make each subsection a separate h3 section, or combine under one Responsibilities section with sub-lists. The example shows "Responsibilities" as a heading. I'll make "Responsibilities" as h3 and then each sub-area as a sub-list with bold labels? But the rule says use ul li for lists. The subsections have prose and lists. Let me read the content.
Under "What You'll Do":
- Team Leadership & Product Security Delivery: has bullet points (Lead and develop..., Define..., Partner..., Own...)
- Security Assurance & Certification: bullet points (Drive..., Contribute..., Ensure..., Provide..., Review...)
- Incident Response & Lifecycle Security: bullet points (Establish..., Define...)
- Commercial & Bid Support: bullet points (Support..., Represent...)
Each has a bolded title and then bullet points. I could make each a separate h3 section, but that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So maybe combine under one "Responsibilities" h3 with subsections as nested lists? But the rule says use ul li for any list of duties. Could do:
Responsibilities
Team Leadership & Product Security Delivery
- ...
...
But the instruction only mentions h3. However, HTML allows h4. The instruction says "use for section headings" but doesn't forbid h4. But to be safe, I'll use h3 for main sections only. I'll make "Responsibilities" as h3 and then each sub-area as a paragraph with bold label followed by ul. Or just make each sub-area an h3? Let's see: "Team Leadership & Product Security Delivery" is a substantive area. The rule says include section ONLY when real content. Each has real content. But "Prefer a few substantive sections over many thin ones." So maybe keep as one Responsibilities section with sub-lists.
I'll do:
Responsibilities
Team Leadership & Product Security Delivery
- ...
Security Assurance & Certification
- ...
...
That seems clean.
Similarly for "What We're Looking For" - that's requirements. Could be "Requirements" h3. And "Preferred" could be "Preferred qualifications" h3. And "What We Offer" -> "Benefits" h3.
Also there's an introductory paragraph before "About The Role": "Here at Humanoid... we're growing the team..." That's about the company/role. I'll include as a paragraph under "About the role" or as a separate intro. The rule says don't repeat job title as heading. The page already shows it. So I'll start with an h3 "About the role" and include the intro paragraph and the paragraph after "About The Role".
Let's parse the text:
"Here at Humanoid, we believe in a future where robots amplify human potential. That's why we've set out on a mission to build the world's most capable, commercially-scalable, and safe humanoid robots. We're bringing that mission to life with HMND‑01 - our rapidly developed humanoid platform being deployed in real industrial environments - and we're growing the team to take it even further."
Then "About The Role" heading, then "We are seeking a Principal Product Cybersecurity Assurance Engineer with deep expertise in product security, threat modelling, and risk assurance for highly regulated electromechanical systems. In this role, you will lead the delivery of product cybersecurity across Humanoid's HMND 01 platform family — the Alpha Wheeled industrial robot and the Alpha Bipedal home robot — both powered by our KinetIQ VLM/VLA-based AI framework. Working alongside product, firmware, autonomy, and hardware teams as part of the Systems Engineering and Architecture Team, you will define and maintain the cybersecurity assurance strategy for all product security activities from first concept through post-market deployment. Security at Humanoid is an engineering discipline inseparable from functional safety and central to our mission of creating the world's most reliable, commercially scalable, and safe humanoid robots. To excel in this position, you must demonstrate the authority to influence security architecture decisions across complex, cross-functional programmes, the rigour to build defensible security cases for novel cyber-physical systems, and the leadership to grow and guide a cross team of security engineers operating at the frontier of robotics."
That's all prose. I'll put under "About the role" as paragraphs.
Then "What You'll Do" with subsections.
Then "What We're Looking For" with bullet points.
Then "Preferred" with bullet points.
Then "What We Offer" with bullet points.
No Pay, Schedule sections explicitly (though benefits include days off, healthcare, pension, etc). That's benefits.
Now, ensure no boilerplate: The text doesn't have EEO, scam warnings, application instructions. Good.
Now produce HTML fragment.
I'll write:
About the role
Here at Humanoid, we believe in a future where robots amplify human potential. That's why we've set out on a mission to build the world's most capable, commercially-scalable, and safe humanoid robots. We're bringing that mission to life with HMND‑01 - our rapidly developed humanoid platform being deployed in real industrial environments - and we're growing the team to take it even further.
We are seeking a Principal Product Cybersecurity Assurance Engineer with deep expertise in product security, threat modelling, and risk assurance for highly regulated electromechanical systems. In this role, you will lead the delivery of product cybersecurity across Humanoid's HMND 01 platform family — the Alpha Wheeled industrial robot and the Alpha Bipedal home robot — both powered by our KinetIQ VLM/VLA-based AI framework. Working alongside product, firmware, autonomy, and hardware teams as part of the Systems Engineering and Architecture Team, you will define and maintain the cybersecurity assurance strategy for all product security activities from first concept through post-market deployment. Security at Humanoid is an engineering discipline inseparable from functional safety and central to our mission of creating the world's most reliable, commercially scalable, and safe humanoid robots. To excel in this position, you must demonstrate the authority to influence security architecture decisions across complex, cross-functional programmes, the rigour to build defensible security cases for novel cyber-physical systems, and the leadership to grow and guide a cross team of security engineers operating at the frontier of robotics.
Responsibilities
Team Leadership & Product Security Delivery
- Lead and develop a cross-functional team of security engineers, maintaining accountability for the delivery of product security services within product teams throughout the HMND 01 development lifecycle.
- Define product security requirements and advise development teams on suitable implementation standards, techniques, and toolchains for embedded and AI-enabled robotic systems.
- Partner with cross-functional teams to develop security protocols, tools, and processes that keep HMND 01 technologies ahead of emerging threats — including attack surfaces specific to the KinetIQ AI inference pipeline and cloud-to-robot communication architecture.
- Own and maintain key security artefacts for audit-ready cybersecurity documentation including Security Management Plans, Threat Analysis and Risk Assessment (TARA) reports, Risk Assessments, and Remediation Action Plans across both platforms.
Security Assurance & Certification
- Drive security assurance through the full product lifecycle, ensuring every HMND 01 design is robust, compliant, and resilient. Contribute to the continual improvement of security engineering capability across the organisation.
- Ensure compliance with cybersecurity obligations under the EU Machinery Regulation 2023/1230 where cyber controls intersect with safety-critical functions and compliance to IEC 62443 (for industrial/OT product security), and the EU Cyber Resilience Act.
- Provide independent Information Assurance (IA) reviews and risk assessments on complex, high-impact projects — with particular focus on cyber-physical systems where a digital compromise could result in physical harm to operators or end users.
- Review and provide guidance on security risk assessments, risk mitigation plans, mitigation gap analysis, and security management documentation in support of system cybersecurity certification.
Incident Response & Lifecycle Security
- Establish and maintain a Product Security Incident Response (PSIR) process, encompassing coordinated vulnerability disclosure, patch deployment pipelines, and post-field incident analysis.
- Define and oversee security monitoring requirements for deployed fleets, ensuring field data feeds back into risk files and security artefacts in line with post-market surveillance obligations.
Commercial & Bid Support
- Support the production of work package descriptions and cost estimates for product bids, services, and proposals that include product security scope.
- Represent Humanoid's security posture in customer and partner engagements, including regulatory consultations and certification body interactions.
Requirements
- Proven, hands-on experience with ISO 27001/27004/27005 and the NIST Risk Management Framework (RMF), applied
for prose - Don't repeat job title as heading - Don't put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/scam-warning) - Include section ONLY when real content exists - Never emit heading followed by filler/placeholder text - No Pay/Schedule/Benefits sections unless explicitly stated (but "What We Offer" is benefits, so include) - Output ONLY HTML fragment Let me structure this: 1. About the role - there's an introductory paragraph before "About The Role" heading in the text. Actually the text starts with "Here at Humanoid..." then "About The Role" then "We are seeking...". I'll treat the first paragraph as intro, then "About the role" as a section? But the rule says don't repeat job title as heading. The job title is "Principal Product Cybersecurity Assurance Engineer". The text has "About The Role" as a heading. I'll use that as an h3. Actually looking at the text: "About The Role" appears as a heading in the source. Then "What You'll Do" with subsections. Then "What We're Looking For". Then "Preferred". Then "What We Offer". I'll create sections for: - About the role (the paragraph after "About The Role") - Responsibilities (What You'll Do) - with subsections as nested lists or separate sections? The rules say use h3 for section headings. The subsections under "What You'll Do" could be h4 but the rule only mentions h3. I'll keep them as h3 or maybe use h3 for main sections and h4 for subsections? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't mention h4. But the subsections are distinct. I think I'll make each subsection a separate h3 section, or combine under one Responsibilities section with sub-lists. The example shows "Responsibilities" as a heading. I'll make "Responsibilities" as h3 and then each sub-area as a sub-list with bold labels? But the rule says use ul li for lists. The subsections have prose and lists. Let me read the content.
Under "What You'll Do":
- Team Leadership & Product Security Delivery: has bullet points (Lead and develop..., Define..., Partner..., Own...)
- Security Assurance & Certification: bullet points (Drive..., Contribute..., Ensure..., Provide..., Review...)
- Incident Response & Lifecycle Security: bullet points (Establish..., Define...)
- Commercial & Bid Support: bullet points (Support..., Represent...)
Each has a bolded title and then bullet points. I could make each a separate h3 section, but that might be too many thin sections. The rule: "Prefer a few substantive sections over many thin ones." So maybe combine under one "Responsibilities" h3 with subsections as nested lists? But the rule says use ul li for any list of duties. Could do:
Responsibilities
Team Leadership & Product Security Delivery
- ...
...
But the instruction only mentions h3. However, HTML allows h4. The instruction says "use for section headings" but doesn't forbid h4. But to be safe, I'll use h3 for main sections only. I'll make "Responsibilities" as h3 and then each sub-area as a paragraph with bold label followed by ul. Or just make each sub-area an h3? Let's see: "Team Leadership & Product Security Delivery" is a substantive area. The rule says include section ONLY when real content. Each has real content. But "Prefer a few substantive sections over many thin ones." So maybe keep as one Responsibilities section with sub-lists.
I'll do:
Responsibilities
Responsibilities
Team Leadership & Product Security Delivery
- ...
Security Assurance & Certification
- ...
About the role
Here at Humanoid, we believe in a future where robots amplify human potential. That's why we've set out on a mission to build the world's most capable, commercially-scalable, and safe humanoid robots. We're bringing that mission to life with HMND‑01 - our rapidly developed humanoid platform being deployed in real industrial environments - and we're growing the team to take it even further.
We are seeking a Principal Product Cybersecurity Assurance Engineer with deep expertise in product security, threat modelling, and risk assurance for highly regulated electromechanical systems. In this role, you will lead the delivery of product cybersecurity across Humanoid's HMND 01 platform family — the Alpha Wheeled industrial robot and the Alpha Bipedal home robot — both powered by our KinetIQ VLM/VLA-based AI framework. Working alongside product, firmware, autonomy, and hardware teams as part of the Systems Engineering and Architecture Team, you will define and maintain the cybersecurity assurance strategy for all product security activities from first concept through post-market deployment. Security at Humanoid is an engineering discipline inseparable from functional safety and central to our mission of creating the world's most reliable, commercially scalable, and safe humanoid robots. To excel in this position, you must demonstrate the authority to influence security architecture decisions across complex, cross-functional programmes, the rigour to build defensible security cases for novel cyber-physical systems, and the leadership to grow and guide a cross team of security engineers operating at the frontier of robotics.
Responsibilities
Team Leadership & Product Security Delivery
- Lead and develop a cross-functional team of security engineers, maintaining accountability for the delivery of product security services within product teams throughout the HMND 01 development lifecycle.
- Define product security requirements and advise development teams on suitable implementation standards, techniques, and toolchains for embedded and AI-enabled robotic systems.
- Partner with cross-functional teams to develop security protocols, tools, and processes that keep HMND 01 technologies ahead of emerging threats — including attack surfaces specific to the KinetIQ AI inference pipeline and cloud-to-robot communication architecture.
- Own and maintain key security artefacts for audit-ready cybersecurity documentation including Security Management Plans, Threat Analysis and Risk Assessment (TARA) reports, Risk Assessments, and Remediation Action Plans across both platforms.
Security Assurance & Certification
- Drive security assurance through the full product lifecycle, ensuring every HMND 01 design is robust, compliant, and resilient. Contribute to the continual improvement of security engineering capability across the organisation.
- Ensure compliance with cybersecurity obligations under the EU Machinery Regulation 2023/1230 where cyber controls intersect with safety-critical functions and compliance to IEC 62443 (for industrial/OT product security), and the EU Cyber Resilience Act.
- Provide independent Information Assurance (IA) reviews and risk assessments on complex, high-impact projects — with particular focus on cyber-physical systems where a digital compromise could result in physical harm to operators or end users.
- Review and provide guidance on security risk assessments, risk mitigation plans, mitigation gap analysis, and security management documentation in support of system cybersecurity certification.
Incident Response & Lifecycle Security
- Establish and maintain a Product Security Incident Response (PSIR) process, encompassing coordinated vulnerability disclosure, patch deployment pipelines, and post-field incident analysis.
- Define and oversee security monitoring requirements for deployed fleets, ensuring field data feeds back into risk files and security artefacts in line with post-market surveillance obligations.
Commercial & Bid Support
- Support the production of work package descriptions and cost estimates for product bids, services, and proposals that include product security scope.
- Represent Humanoid's security posture in customer and partner engagements, including regulatory consultations and certification body interactions.
Requirements
- Proven, hands-on experience with ISO 27001/27004/27005 and the NIST Risk Management Framework (RMF), applied