AI Systems Security Architect

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about AMD, then "The Role", "The Person", "Key Responsibilities", "Preferred Experience", "Academic Credentials", "LOCATION". Also maybe "Benefits offered are described: AMD benefits at a glance." That's a mention but not details; we should not create Benefits section unless actual details. So we skip Benefits, Pay, Schedule. We need headings:

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting has "The Role" (description), "The Person" (ideal candidate), "Key Responsibilities", "Preferred Experience", "Academic Credentials", "LOCATION". Also maybe "About AMD" intro but not a heading. We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for the role description. "Responsibilities" for Key Responsibilities. "Requirements" could combine Preferred Experience and Academic Credentials? Or we could have separate sections: Requirements (Preferred Experience) and Qualifications (Academic Credentials). Skills maybe from Preferred Experience? But we should not create thin sections. Better to have: About the role, Responsibilities, Requirements (combining Preferred Experience and Academic Credentials), Skills (maybe from Preferred Experience?). However we must not invent content. We need to preserve all substantive info. Could create sections: About the role, Responsibilities, Requirements (Preferred Experience), Qualifications (Academic Credentials), Skills (maybe from Preferred Experience? but that duplicates). Better to follow the instruction: Use headings only when posting has real, specific content for it. So we can create sections matching the headings present in posting: "About the role" (The Role), "Responsibilities" (Key Responsibilities), "Requirements" (Preferred Experience), "Qualifications" (Academic Credentials), "Skills" maybe not needed because Preferred Experience already covers skills. But we could still include Skills if we extract skill bullet points from Preferred Experience. However that would be splitting content; still okay as long as we don't invent. But we risk creating thin sections. The instruction: Prefer a few substantive sections over many thin ones. So better to combine. Thus sections: About the role, Responsibilities, Requirements (Preferred Experience + Academic Credentials). Could also include Location as a short p. We must not repeat job title as heading. So no heading for "AI Systems Security Architect". Also no Job ID. We need to use

• for any list of duties/requirements/benefits. So we need to turn bullet points into lists. Let's extract content. Intro paragraphs: "ADVANCE YOUR CAREER. ADVANCE THE WORLD. At AMD, we believe technology has the power to solve the world’s most important challenges. From advancing healthcare and scientific discovery to powering AI and the technologies people rely on every day, innovation at AMD is shaping the future. Whether you’re designing next-gen processors, enabling AI breakthroughs, or bringing leading edge products to market, every role at AMD contributes to something bigger — technology that moves the world forward. Join us and, together, we’ll advance your career." That's prose; we can put in

  . "The Role AMD is looking for an AI Systems Security Architect to join the Product Security Office (PSO) in securing the platforms that run the world's most demanding AI workloads. Your role will be to define and drive architectures that enhance platform security. You will work at the intersection of hardware, firmware, and software, designing and implementing security features that protect AI workloads in modern data center environments." That's role description. "The Person The ideal candidate is passionate about product security for AI systems, spanning firmware, software, and hardware, and possesses leadership skills to drive sophisticated issues to resolution. You are able to communicate effectively and work optimally with different teams across AMD." That's person description. "Key Responsibilities Define and drive platform-wide security architecture across silicon, firmware, and software for AI and datacenter systems, including the platform's trust boundariesDrive the platform attestation architecture, including root of trust, measured boot, reference measurements, and remote verificationHelp drive system-wide threat modeling and security analysis across hardware, firmware, and softwareContribute to secure debug architecture and the protection of debug, test, and diagnostic interfaces on production systemsWrite system architecture specifications for platform security featuresDrive security assessment and audit readiness for AMD platforms, and close findings into the architectureApply AI-assisted engineering tooling to accelerate security analysis, review, and documentation, and help establish how the team uses it" We need to split into list items. Each sentence seems separated by no punctuation? Actually they are concatenated without spaces? Let's separate by capital letters after periods? The text: "Define and drive platform-wide security architecture across silicon, firmware, and software for AI and datacenter systems, including the platform's trust boundariesDrive the platform attestation architecture, including root of trust, measured boot, reference measurements, and remote verificationHelp drive system-wide threat modeling and security analysis across hardware, firmware, and softwareContribute to secure debug architecture and the protection of debug, test, and diagnostic interfaces on production systemsWrite system architecture specifications for platform security featuresDrive security assessment and audit readiness for AMD platforms, and close findings into the architectureApply AI-assisted engineering tooling to accelerate security analysis, review, and documentation, and help establish how the team uses it" We need to insert spaces before each capital letter that starts a new responsibility. Let's manually split: - Define and drive platform-wide security architecture across silicon, firmware, and software for AI and datacenter systems, including the platform's trust boundaries - Drive the platform attestation architecture, including root of trust, measured boot, reference measurements, and remote verification - Help drive system-wide threat modeling and security analysis across hardware, firmware, and software - Contribute to secure debug architecture and the protection of debug, test, and diagnostic interfaces on production systems - Write system architecture specifications for platform security features - Drive security assessment and audit readiness for AMD platforms, and close findings into the architecture - Apply AI-assisted engineering tooling to accelerate security analysis, review, and documentation, and help establish how the team uses it That's 7 items. "Preferred Experience Multiple years' experience in platform, system, or product security architecture, with demonstrated ownership of security architecture at system scopeDeep understanding of computer architecture and platform composition, including CPU, accelerator, and SoC systems, memory hierarchy, DMA, and I/O subsystems, as well as datacenter interconnect standards (PCIe, CXL) and their security featuresExperience with confidential computing and trusted execution environments, including memory encryption and VM isolationExpertise in root of trust, secure boot, measured boot, and boot chain architecture, including transitions between boot stages, and in attestation, including DICE, SPDM, TPM/TCG concepts, and the reference measurement lifecycleExperience with firmware security, including runtime integrity, anti-rollback, secure update, and recovery designExpertise in threat modeling, security architecture, and protocol design at platform scopeKnowledge and application of cryptographic algorithms, key hierarchies, and key management in hardware and firmware environmentsProficient in C/C++ and comfortable reading assembly, with demonstrated fluency in AI-assisted and agentic development tooling in real engineering workEffective communication and problem-solving skills, and the ability to influence across organizationsExperience securing AI/ML workloads and understanding of their security requirements at datacenter scale, with familiarity with GPU and accelerator architecture, virtualization (SR-IOV, SIOV, MIG), and firmwareExperience with secure debug, JTAG and scan chain protection, fuse and lifecycle state management, and familiarity with side-channel and fault-injection analysisFamiliarity with supply-chain integrity practices (SBOM, build provenance) and open-source firmware projects (Caliptra, OpenBMC, coreboot, EDK II, openSIL); experience supporting external security audits, red teams, or independent platform assessment; knowledge of hardware security standards and frameworks (TCG, NIST, OCP); and awareness of post-quantum cryptography migration for firmware signing and device identity" We need to split into list items. Let's parse: - Multiple years' experience in platform, system, or product security architecture, with demonstrated ownership of security architecture at system scope - Deep understanding of computer architecture and platform composition, including CPU, accelerator, and SoC systems, memory hierarchy, DMA, and I/O subsystems, as well as datacenter interconnect standards (PCIe, CXL) and their security features - Experience with confidential computing and trusted execution environments, including memory encryption and VM isolation - Expertise in root of trust, secure boot, measured boot, and boot chain architecture, including transitions between boot stages, and in attestation, including DICE, SPDM, TPM/TCG concepts, and the reference measurement lifecycle - Experience with firmware security, including runtime integrity, anti-rollback, secure update, and recovery design - Expertise in threat modeling, security architecture, and protocol design at platform scope - Knowledge and application of cryptographic algorithms, key hierarchies, and key management in hardware and firmware environments - Proficient in C/C++ and comfortable reading assembly, with demonstrated fluency in AI-assisted and agentic development tooling in real engineering work - Effective communication and problem-solving skills, and the ability to influence across organizations - Experience securing AI/ML workloads and understanding of their security requirements at datacenter scale, with familiarity with GPU and accelerator architecture, virtualization (SR-IOV, SIOV, MIG), and firmware - Experience with secure debug, JTAG and scan chain protection, fuse and lifecycle state management, and familiarity with side-channel and fault-injection analysis - Familiarity with supply-chain integrity practices (SBOM, build provenance) and open-source firmware projects (Caliptra, OpenBMC, coreboot, EDK II, openSIL); experience supporting external security audits, red teams, or independent platform assessment; knowledge of hardware security standards and frameworks (TCG, NIST, OCP); and awareness of post-quantum cryptography migration for firmware signing and device identity That's many items; we can keep as list. "Academic Credentials Bachelor's or Master's degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent" That's a single sentence; could be a

  or

  • . Since it's a single item, we can use

    . "LOCATION: San Diego, CA preferred. Open to other AMD US locations for the right candidate. This role is not eligible for visa sponsorship." We can put as

    . Now we need to omit boilerplate: The lines about benefits, EEO, etc. Remove. Now construct HTML. We'll have:

    Intro paragraph(s)

    About the role

    The Role ...

    The Person

    maybe not a standard heading but we could treat as part of About the role? The instruction only lists specific headings; but we can still use

    for any section heading we want? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those exact headings when appropriate. It doesn't forbid other headings, but says use

    for section headings (e.g. those). Probably we should stick to those headings. So we should not create a heading "The Person". Instead we could incorporate that into About the role or Requirements. The Person describes ideal candidate; could go under Requirements or Qualifications. Let's merge into Requirements section. Thus we have sections: About the role, Responsibilities, Requirements (combining Preferred Experience, Academic Credentials, and The Person). That's substantive. We need to ensure we don't create thin sections. So we will have three sections. Now we need to output only HTML fragment. Let's craft:

    ADVANCE YOUR CAREER. ADVANCE THE WORLD. At AMD, we believe technology has the power to solve the world’s most important challenges. From advancing healthcare