AI Platform Security Engineer
AMD · San Diego, CA · 3 wk ago
HybridEngineeringFull-time
We need to output HTML fragment with sections only if content present. Need to extract sections: About the role? The posting includes intro paragraph about AMD, then "The Role" paragraph, then "The Person", then "Key Responsibilities", then "Preferred Experience", then "Academic Credentials", then location line, then benefits line, then other boilerplate to remove.
We must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content to these headings appropriately.
We have:
- About the role: could be the paragraph describing the role: "AMD is looking for an AI Platform Security Engineer to join the Product Security Office (PSO) in securing the platforms that run the world’s most demanding AI workloads. Working across hardware, firmware, and software, you will implement and validate security features on internal test platforms, conduct security assessments, and drive the resolution of security issues, including those raised by customers. You will turn security requirements and designs into working, verified results on real systems, at the center of how the world’s leading AI companies build and secure their infrastructure."
That's about the role.
- Responsibilities: list of duties under "Key Responsibilities". Those are bullet points.
- Requirements / Qualifications / Skills: The posting has "The Person", "Preferred Experience", "Academic Credentials". We need to decide which sections to output. We can combine into Requirements (maybe "Qualifications") etc. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which are present.
We have content for:
- About the role: yes.
- Responsibilities: yes (list).
- Requirements: maybe combine "The Person" and "Preferred Experience" and "Academic Credentials". Could output a single "Requirements" section with paragraphs/lists.
- Qualifications: maybe not needed if we used Requirements.
- Skills: could be separate but we might not have explicit skills list besides languages etc. Could embed in Requirements.
- Benefits: there is a line: "Benefits offered are described: AMD benefits at a glance." That's vague, not specific. The instruction: never create Benefits section unless posting actually states them. This line is just a reference, not actual benefits. So we should not create Benefits section.
- Pay: not present.
- Schedule: not present.
Thus we output sections: About the role, Responsibilities, Requirements (maybe also Qualifications? but we can combine). We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, except boilerplate.
We need to format responsibilities as
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content to these headings appropriately.
We have:
- About the role: could be the paragraph describing the role: "AMD is looking for an AI Platform Security Engineer to join the Product Security Office (PSO) in securing the platforms that run the world’s most demanding AI workloads. Working across hardware, firmware, and software, you will implement and validate security features on internal test platforms, conduct security assessments, and drive the resolution of security issues, including those raised by customers. You will turn security requirements and designs into working, verified results on real systems, at the center of how the world’s leading AI companies build and secure their infrastructure."
That's about the role.
- Responsibilities: list of duties under "Key Responsibilities". Those are bullet points.
- Requirements / Qualifications / Skills: The posting has "The Person", "Preferred Experience", "Academic Credentials". We need to decide which sections to output. We can combine into Requirements (maybe "Qualifications") etc. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which are present.
We have content for:
- About the role: yes.
- Responsibilities: yes (list).
- Requirements: maybe combine "The Person" and "Preferred Experience" and "Academic Credentials". Could output a single "Requirements" section with paragraphs/lists.
- Qualifications: maybe not needed if we used Requirements.
- Skills: could be separate but we might not have explicit skills list besides languages etc. Could embed in Requirements.
- Benefits: there is a line: "Benefits offered are described: AMD benefits at a glance." That's vague, not specific. The instruction: never create Benefits section unless posting actually states them. This line is just a reference, not actual benefits. So we should not create Benefits section.
- Pay: not present.
- Schedule: not present.
Thus we output sections: About the role, Responsibilities, Requirements (maybe also Qualifications? but we can combine). We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, except boilerplate.
We need to format responsibilities as - . For responsibilities list, we have bullet points:
- Implement, configure, and validate platform security features for AI systems on internal test platforms
- Conduct security assessments of platforms, firmware, and AI systems, and clearly communicate findings and remediation
- Develop, review, and apply security fixes, and verify them on real hardware
- Analyze, reproduce, and drive resolution of security issues reported by internal teams, customers, and researchers
- Support customer security requirements and respond to customer security inquiries and findings
- Establish and maintain secure builds and AI harnesses
- Provision and manage keys, certificates, and device identities for secure boot, attestation, and platform bring-up
- Develop tooling and automation that make security testing and remediation more efficient and repeatable
- Partner with architecture, firmware, and software teams to get fixes designed, implemented, and verified
- Apply AI-assisted engineering tooling to accelerate assessment, remediation, and documentation
We need to keep them exactly.
Now "The Person": paragraph: "The ideal candidate is an experienced security engineer who is effective at implementing and validating security on real systems. You are comfortable owning a problem end to end, from analysis and reproduction through developing and verifying the fix. You communicate effectively and work optimally with customers and with different teams across AMD."
That's prose.
"Preferred Experience": list of bullet points (multiple). Need to preserve each bullet as
- . Let's extract them:
- Multiple years' experience in security engineering or platform, firmware, or software engineering with a security focus
- Experience securing and debugging systems across hardware, firmware, and software, including security assessment, vulnerability analysis, and developing and applying fixes
- Experience provisioning and managing keys, certificates, and device identities (secure boot signing, attestation, PKI), with a solid understanding of platform security concepts: secure boot, attestation, cryptography, memory safety, and isolation
- Proficient in C/C++ and at least one scripting language (Python or similar), and comfortable in Linux environments
- Demonstrated fluency with AI-assisted and agentic development tooling in real engineering work
- Strong communication skills and the ability to drive issues to resolution across teams and with customers
- Experience securing AI/ML workloads or working directly on AI training or inference infrastructure, including familiarity with confidential computing and trusted execution environments
- Familiarity with GPU and accelerator platforms, virtualization (SR-IOV, SIOV, MIG), and firmware, as well as datacenter interconnect standards (PCIe, CXL) and their security features
- Familiarity with supply-chain integrity practices, including SBOM, build provenance, and reproducible builds, and with open-source firmware projects (Caliptra, OpenBMC, coreboot, EDK II, openSIL)
- Experience supporting external security audits, red teams, or independent platform assessment, and knowledge of hardware security standards and frameworks (TCG, NIST, OCP)
We need to keep punctuation as is.
"Academic Credentials": "Bachelor’s or Master’s degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent"
Location line: "LOCATION: San Diego, CA preferred. Open to other AMD US locations for the right candidate. This role is not eligible for visa sponsorship."
We need to decide where to put location. Could be part of Requirements or a separate section? There's no heading for Location in allowed list. Could fold into Requirements as a paragraph. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Location is minor metadata, we can fold into a short
within Requirements or maybe a separate paragraph after Requirements. Probably include as a short
after Academic Credentials.
Benefits line: "Benefits offered are described: AMD benefits at a glance." This is not specific benefits, so we should not create Benefits section. Could we include as a short paragraph? The instruction: never create Benefits section unless posting actually states them. It does not state actual benefits, just a reference. So we should omit it entirely.
Other boilerplate to remove: unsolicited resumes line, EEO statement, AI screening line, Responsible AI Policy link, posting is for existing vacancy. Remove all.
Now we need to output HTML fragment with sections.
We'll have:
About the role
...
Responsibilities
- ...
...
Requirements
Maybe we need subheadings? Not allowed; only those headings. So we can put all under Requirements as paragraphs and maybe a list for Preferred Experience and Academic Credentials.
We need to preserve all substantive info. So we can include:
The ideal candidate is an experienced security engineer who is effective at implementing and validating security on real systems. You are comfortable owning a problem end to end, from analysis and reproduction through developing and verifying the fix. You communicate effectively and work optimally with customers and with different teams across AMD.
Then maybe a subheading? Not allowed. So we can just continue with paragraphs.
Then we can have a ? Not allowed. So we just list Preferred Experience as a under Requirements.
Then Academic Credentials as a .
Then Location as a
.
We need to ensure we don't create empty sections.
Thus final HTML:
About the role
AMD is looking for an AI Platform Security Engineer to join the Product Security Office (PSO) in securing the platforms that run the world’s most demanding AI workloads. Working across hardware, firmware, and software, you will implement and validate security features on internal test platforms, conduct security assessments, and drive the resolution of security issues, including those raised by customers. You will turn security requirements and designs into working, verified results on real systems, at the center of how the world’s leading AI companies build and secure their infrastructure.
Responsibilities
- Implement, configure, and validate platform security features for AI systems on internal test platforms
- Conduct security assessments of platforms, firmware, and AI systems, and clearly communicate findings and remediation
- Develop, review, and apply security fixes, and verify them on real hardware
- Analyze, reproduce, and drive resolution of security issues reported by internal teams, customers, and researchers
- Support customer security requirements and respond to customer security inquiries and findings
- Establish and maintain secure builds and AI harnesses
- Provision and manage keys, certificates, and device identities for secure boot, attestation, and platform bring-up
- Develop tooling and automation that make security testing and remediation more efficient and repeatable
- Partner with architecture, firmware, and software teams to get fixes designed, implemented, and verified
- Apply AI-assisted engineering tooling to accelerate assessment, remediation, and documentation
Requirements
The ideal candidate is an experienced security engineer who is effective at implementing and validating security on real systems. You are comfortable owning a problem end to end, from analysis and reproduction through developing and verifying the fix. You communicate effectively and work optimally with customers and with different teams across AMD.
- Multiple years' experience in security engineering or platform, firmware, or software engineering with a security focus
- Experience securing and debugging systems across hardware, firmware, and software, including security assessment, vulnerability analysis, and developing and applying fixes
- Experience provisioning and managing keys, certificates, and device identities (secure boot signing, attestation, PKI), with a solid understanding of platform security concepts: secure boot, attestation, cryptography, memory safety, and isolation
- Proficient in C/C++ and at least one scripting language (Python or similar), and comfortable in Linux environments
- Demonstrated fluency with AI-assisted and agentic development tooling in real engineering work
- Strong communication skills and the ability to drive issues to resolution across teams and with customers
- Experience securing AI/ML workloads or working directly on AI training or inference infrastructure, including familiarity with confidential computing and trusted execution environments
- Familiarity with GPU and accelerator platforms, virtualization (SR-IOV, SIOV, MIG), and firmware, as well as datacenter interconnect standards (PCIe, CXL) and their security features
- Familiarity with supply-chain integrity practices, including SBOM, build provenance, and reproducible builds, and with open-source firmware projects (Caliptra, OpenBMC, coreboot, EDK II, openSIL)
- Experience supporting external security audits, red teams, or independent platform assessment, and knowledge of hardware security standards and frameworks (TCG, NIST, OCP)
Bachelor’s or Master’s degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent
LOCATION: San Diego, CA preferred. Open to other AMD US locations for the right candidate. This role is not eligible for visa sponsorship.
We need to ensure no extra whitespace issues. Output only HTML fragment.
Check for any leftover boilerplate: we removed unsolic
or drop it. Location is minor metadata, we can fold into a short
within Requirements or maybe a separate paragraph after Requirements. Probably include as a short
after Academic Credentials. Benefits line: "Benefits offered are described: AMD benefits at a glance." This is not specific benefits, so we should not create Benefits section. Could we include as a short paragraph? The instruction: never create Benefits section unless posting actually states them. It does not state actual benefits, just a reference. So we should omit it entirely. Other boilerplate to remove: unsolicited resumes line, EEO statement, AI screening line, Responsible AI Policy link, posting is for existing vacancy. Remove all. Now we need to output HTML fragment with sections. We'll have:
About the role
...
Responsibilities
- ... ...
Requirements
Maybe we need subheadings? Not allowed; only those headings. So we can put all under Requirements as paragraphs and maybe a list for Preferred Experience and Academic Credentials. We need to preserve all substantive info. So we can include:The ideal candidate is an experienced security engineer who is effective at implementing and validating security on real systems. You are comfortable owning a problem end to end, from analysis and reproduction through developing and verifying the fix. You communicate effectively and work optimally with customers and with different teams across AMD.
Then maybe a subheading? Not allowed. So we can just continue with paragraphs. Then we can have a? Not allowed. So we just list Preferred Experience as a under Requirements.
Then Academic Credentials as a .
Then Location as a
.
We need to ensure we don't create empty sections.
Thus final HTML:
About the role
AMD is looking for an AI Platform Security Engineer to join the Product Security Office (PSO) in securing the platforms that run the world’s most demanding AI workloads. Working across hardware, firmware, and software, you will implement and validate security features on internal test platforms, conduct security assessments, and drive the resolution of security issues, including those raised by customers. You will turn security requirements and designs into working, verified results on real systems, at the center of how the world’s leading AI companies build and secure their infrastructure.
Responsibilities
- Implement, configure, and validate platform security features for AI systems on internal test platforms
- Conduct security assessments of platforms, firmware, and AI systems, and clearly communicate findings and remediation
- Develop, review, and apply security fixes, and verify them on real hardware
- Analyze, reproduce, and drive resolution of security issues reported by internal teams, customers, and researchers
- Support customer security requirements and respond to customer security inquiries and findings
- Establish and maintain secure builds and AI harnesses
- Provision and manage keys, certificates, and device identities for secure boot, attestation, and platform bring-up
- Develop tooling and automation that make security testing and remediation more efficient and repeatable
- Partner with architecture, firmware, and software teams to get fixes designed, implemented, and verified
- Apply AI-assisted engineering tooling to accelerate assessment, remediation, and documentation
Requirements
The ideal candidate is an experienced security engineer who is effective at implementing and validating security on real systems. You are comfortable owning a problem end to end, from analysis and reproduction through developing and verifying the fix. You communicate effectively and work optimally with customers and with different teams across AMD.
- Multiple years' experience in security engineering or platform, firmware, or software engineering with a security focus
- Experience securing and debugging systems across hardware, firmware, and software, including security assessment, vulnerability analysis, and developing and applying fixes
- Experience provisioning and managing keys, certificates, and device identities (secure boot signing, attestation, PKI), with a solid understanding of platform security concepts: secure boot, attestation, cryptography, memory safety, and isolation
- Proficient in C/C++ and at least one scripting language (Python or similar), and comfortable in Linux environments
- Demonstrated fluency with AI-assisted and agentic development tooling in real engineering work
- Strong communication skills and the ability to drive issues to resolution across teams and with customers
- Experience securing AI/ML workloads or working directly on AI training or inference infrastructure, including familiarity with confidential computing and trusted execution environments
- Familiarity with GPU and accelerator platforms, virtualization (SR-IOV, SIOV, MIG), and firmware, as well as datacenter interconnect standards (PCIe, CXL) and their security features
- Familiarity with supply-chain integrity practices, including SBOM, build provenance, and reproducible builds, and with open-source firmware projects (Caliptra, OpenBMC, coreboot, EDK II, openSIL)
- Experience supporting external security audits, red teams, or independent platform assessment, and knowledge of hardware security standards and frameworks (TCG, NIST, OCP)
Bachelor’s or Master’s degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent
LOCATION: San Diego, CA preferred. Open to other AMD US locations for the right candidate. This role is not eligible for visa sponsorship.
We need to ensure no extra whitespace issues. Output only HTML fragment.
Check for any leftover boilerplate: we removed unsolic
. Then Location as a
. We need to ensure we don't create empty sections. Thus final HTML:
About the role
AMD is looking for an AI Platform Security Engineer to join the Product Security Office (PSO) in securing the platforms that run the world’s most demanding AI workloads. Working across hardware, firmware, and software, you will implement and validate security features on internal test platforms, conduct security assessments, and drive the resolution of security issues, including those raised by customers. You will turn security requirements and designs into working, verified results on real systems, at the center of how the world’s leading AI companies build and secure their infrastructure.
Responsibilities
- Implement, configure, and validate platform security features for AI systems on internal test platforms
- Conduct security assessments of platforms, firmware, and AI systems, and clearly communicate findings and remediation
- Develop, review, and apply security fixes, and verify them on real hardware
- Analyze, reproduce, and drive resolution of security issues reported by internal teams, customers, and researchers
- Support customer security requirements and respond to customer security inquiries and findings
- Establish and maintain secure builds and AI harnesses
- Provision and manage keys, certificates, and device identities for secure boot, attestation, and platform bring-up
- Develop tooling and automation that make security testing and remediation more efficient and repeatable
- Partner with architecture, firmware, and software teams to get fixes designed, implemented, and verified
- Apply AI-assisted engineering tooling to accelerate assessment, remediation, and documentation
Requirements
The ideal candidate is an experienced security engineer who is effective at implementing and validating security on real systems. You are comfortable owning a problem end to end, from analysis and reproduction through developing and verifying the fix. You communicate effectively and work optimally with customers and with different teams across AMD.
- Multiple years' experience in security engineering or platform, firmware, or software engineering with a security focus
- Experience securing and debugging systems across hardware, firmware, and software, including security assessment, vulnerability analysis, and developing and applying fixes
- Experience provisioning and managing keys, certificates, and device identities (secure boot signing, attestation, PKI), with a solid understanding of platform security concepts: secure boot, attestation, cryptography, memory safety, and isolation
- Proficient in C/C++ and at least one scripting language (Python or similar), and comfortable in Linux environments
- Demonstrated fluency with AI-assisted and agentic development tooling in real engineering work
- Strong communication skills and the ability to drive issues to resolution across teams and with customers
- Experience securing AI/ML workloads or working directly on AI training or inference infrastructure, including familiarity with confidential computing and trusted execution environments
- Familiarity with GPU and accelerator platforms, virtualization (SR-IOV, SIOV, MIG), and firmware, as well as datacenter interconnect standards (PCIe, CXL) and their security features
- Familiarity with supply-chain integrity practices, including SBOM, build provenance, and reproducible builds, and with open-source firmware projects (Caliptra, OpenBMC, coreboot, EDK II, openSIL)
- Experience supporting external security audits, red teams, or independent platform assessment, and knowledge of hardware security standards and frameworks (TCG, NIST, OCP)
Bachelor’s or Master’s degree in Computer Science, Computer Engineering, Electrical Engineering, or equivalent
LOCATION: San Diego, CA preferred. Open to other AMD US locations for the right candidate. This role is not eligible for visa sponsorship.
We need to ensure no extra whitespace issues. Output only HTML fragment. Check for any leftover boilerplate: we removed unsolic