Server Platform Validation Engineer
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists
- Use
for prose
- Do NOT repeat job title as heading (page already shows it)
- Do NOT put Job ID/requisition numbers as headings
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's map the content:
- "The Role" section: This is the "About the role" content. I'll use
About the role
and then paragraphs.
- "The Person": This could be "Qualifications" or "Requirements". Since it describes ideal candidate traits, I'll use Qualifications
or maybe "The Person" but the rule says use standard headings like "Qualifications". I'll use "Qualifications".
- "Key Responsibilities": Responsibilities
with -
- "Preferred Experience": This is essentially requirements/skills. Could be "Requirements" or "Skills". Since it's a list of preferred experience, I'll use
Requirements
with -
- "Academic Credentials": This is education requirements. Could be part of Requirements or separate "Qualifications". I'll include as part of Requirements or separate? The rule says use headings like "Qualifications". I'll make a separate "Qualifications" section for academic credentials? But "The Person" already includes soft skills. Maybe combine: "Qualifications" for academic and "Requirements" for experience. However, the rule says "Qualifications" is a heading option. I'll do:
-
Qualifications
for academic credentials and maybe the person traits? But "The Person" is more about soft skills. The posting has "The Person" and "Preferred Experience" and "Academic Credentials". I think best to have:
- About the role
(from The Role)
- Responsibilities
(Key Responsibilities)
- Requirements
(Preferred Experience)
- Qualifications
(Academic Credentials and maybe The Person? But The Person is more about soft skills and mindset. Could be part of Qualifications. However, the rule says "Qualifications" is a heading. I'll include Academic Credentials under Qualifications, and The Person under a separate "Qualifications" or "The Person"? The rule says use standard headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "The Person" could be "Qualifications". I'll do:
- Qualifications
for The Person and Academic Credentials.
- Location: This is metadata, fold into a short maybe at the end or in a "Location" paragraph. Not a heading.
Also, there's a note about visa sponsorship: "This role is not eligible for visa sponsorship." That's important info, include in a paragraph.
Benefits: only mention "Benefits offered are described: AMD benefits at a glance." No details, so omit section.
Now, let's write HTML.
Structure:
About the role
... (The Role paragraph(s))
Responsibilities
- ...
Requirements
- ...
Qualifications
... (The Person paragraph)
... (Academic Credentials)
Location: Austin, Texas (Onsite). This role is not eligible for visa sponsorship.
But note: The Person is multiple paragraphs. I'll include as prose.
Also, the "Key Responsibilities" list is bullet points. I'll convert each bullet to - .
"Preferred Experience" list is bullet points.
"Academic Credentials" is a single line.
Now, ensure no filler. The posting has substantive content for each.
Let's extract text:
The Role: "AMD is looking for a Server Platform Validation Engineer to join a global engineering team responsible for delivering and supporting Best Known Configurations (BKCs) used across multiple server programs. This is a highly visible, hands-on role that sits at the intersection of server platform validation, system engineering, and cross-functional technical collaboration. In this role, you will serve as a key North American technical resource for BKC activities, partnering closely with engineering stakeholders in the U.S. and a broader global team. You will work directly with server platforms in the lab, troubleshoot system-level issues, execute validation and regression testing, and help ensure BKC releases are fully validated and delivered on schedule. This is an exciting opportunity for someone who enjoys understanding how complete server systems work, from x86 CPUs and operating systems to GPU integration and platform-level hardware/software interaction. You will have an opportunity to take ownership of meaningful technical work, solve complex system problems, and collaborate with engineering teams across multiple geographies and programs."
The Person: "The ideal candidate is a hands-on systems engineer who enjoys troubleshooting complex technical problems and taking ownership from investigation through resolution. This person communicates clearly, works effectively across geographically distributed teams, and is comfortable collaborating with multiple engineering disciplines and stakeholders. The successful candidate will be self-directed, organized, and able to balance hands-on technical execution with cross-functional communication. Curiosity, strong problem-solving skills, adaptability, and a continuous-improvement mindset will help this individual thrive in a fast-moving server engineering environment. Candidates who are comfortable incorporating AI into their daily workflow and interested in using emerging AI capabilities to improve or automate technical workflows will be well positioned for success. Richard specifically identified everyday AI use as valuable and agentic AI/workflow automation as a more advanced capability."
Key Responsibilities: list of 8 bullets.
Preferred Experience: list of 13 bullets.
Academic Credentials: "Bachelor’s or Master’s degree in Computer Engineering, Computer Science, Electrical Engineering, or a comparable technical discipline is preferred."
Location: "LOCATION: Austin, Texas (Onsite) This role is not eligible for visa sponsorship."
Now, produce HTML.
I'll write:
About the role
AMD is looking for a Server Platform Validation Engineer to join a global engineering team responsible for delivering and supporting Best Known Configurations (BKCs) used across multiple server programs. This is a highly visible, hands-on role that sits at the intersection of server platform validation, system engineering, and cross-functional technical collaboration. In this role, you will serve as a key North American technical resource for BKC activities, partnering closely with engineering stakeholders in the U.S. and a broader global team. You will work directly with server platforms in the lab, troubleshoot system-level issues, execute validation and regression testing, and help ensure BKC releases are fully validated and delivered on schedule. This is an exciting opportunity for someone who enjoys understanding how complete server systems work, from x86 CPUs and operating systems to GPU integration and platform-level hardware/software interaction. You will have an opportunity to take ownership of meaningful technical work, solve complex system problems, and collaborate with engineering teams across multiple geographies and programs.
Responsibilities
- Support the validation, execution, and release of Best Known Configurations (BKCs) across multiple server programs.
- Serve as a technical point of contact for North American engineering stakeholders, helping connect U.S.-based teams with the broader global BKC organization.
- Investigate, troubleshoot, and resolve system and platform issues reported by engineering users to help minimize development blockers.
- Perform hands-on server platform validation, including system setup, regression execution, testing, and analysis in a lab environment.
- Take ownership of assigned portions of the BKC release and validation process and drive activities through completion.
- Collaborate across system engineering, software, firmware, validation, and other engineering disciplines to investigate platform-level issues.
- Work with x86 server platforms and contribute to validation involving CPU, GPU/accelerator, OS, and hardware/software integration.
- Help ensure weekly BKC releases are completed on schedule, fully validated, and free of significant issues before release to engineering users.
Requirements
- Experience with server platform validation, system validation, or system engineering.
- Experience with post-silicon validation and/or platform validation programs.
- Understanding of modern x86 CPU and PC/server platform architecture, including system boot flow.
- Experience with server CPU and GPU/accelerator integration or broader hardware/software system integration.
- Working knowledge of server operating systems, particularly Linux and Windows.
- Experience developing or executing system-level validation methodologies, test plans, regression testing, or validation infrastructure.
- Experience debugging complex platform or system-level hardware/software issues.
- Familiarity with programming or scripting languages such as Python, C/C++, or Perl.
- Experience working with multiple engineering teams and stakeholders across different geographic locations.
- Experience using AI as part of day-to-day technical work. Familiarity with agentic AI or using AI agents to automate technical workflows is a plus.
- Strong written and verbal communication skills.
- Ability to independently organize and prioritize multiple technical activities.
- Experience taking technical ownership or leading activities across teams is desired.
Qualifications
The ideal candidate is a hands-on systems engineer who enjoys troubleshooting complex technical problems and taking ownership from investigation through resolution. This person communicates clearly, works effectively across geographically distributed teams, and is comfortable collaborating with multiple engineering disciplines and stakeholders. The successful candidate will be self-directed, organized, and able to balance hands-on technical execution with cross-functional communication. Curiosity, strong problem-solving skills, adaptability, and a continuous-improvement mindset will help this individual thrive in a fast-moving server engineering environment. Candidates who are comfortable incorporating AI into their daily workflow and interested in using emerging AI capabilities to improve or automate technical workflows will be well positioned for success. Richard specifically identified everyday AI use as valuable and agentic AI/workflow automation as a more advanced capability.
Bachelor’s or Master’s degree in Computer Engineering, Computer Science, Electrical Engineering, or a comparable technical discipline is preferred.
Location: Austin, Texas (Onsite). This role is not eligible
for prose - Do NOT repeat job title as heading (page already shows it) - Do NOT put Job ID/requisition numbers as headings - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's map the content: - "The Role" section: This is the "About the role" content. I'll use
About the role
and then paragraphs. - "The Person": This could be "Qualifications" or "Requirements". Since it describes ideal candidate traits, I'll useQualifications
or maybe "The Person" but the rule says use standard headings like "Qualifications". I'll use "Qualifications". - "Key Responsibilities":Responsibilities
with-
- "Preferred Experience": This is essentially requirements/skills. Could be "Requirements" or "Skills". Since it's a list of preferred experience, I'll use
Requirements
with-
- "Academic Credentials": This is education requirements. Could be part of Requirements or separate "Qualifications". I'll include as part of Requirements or separate? The rule says use headings like "Qualifications". I'll make a separate "Qualifications" section for academic credentials? But "The Person" already includes soft skills. Maybe combine: "Qualifications" for academic and "Requirements" for experience. However, the rule says "Qualifications" is a heading option. I'll do:
-
Qualifications
for academic credentials and maybe the person traits? But "The Person" is more about soft skills. The posting has "The Person" and "Preferred Experience" and "Academic Credentials". I think best to have: -About the role
(from The Role) -Responsibilities
(Key Responsibilities) -Requirements
(Preferred Experience) -Qualifications
(Academic Credentials and maybe The Person? But The Person is more about soft skills and mindset. Could be part of Qualifications. However, the rule says "Qualifications" is a heading. I'll include Academic Credentials under Qualifications, and The Person under a separate "Qualifications" or "The Person"? The rule says use standard headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So "The Person" could be "Qualifications". I'll do: -Qualifications
for The Person and Academic Credentials. - Location: This is metadata, fold into a shortmaybe at the end or in a "Location" paragraph. Not a heading. Also, there's a note about visa sponsorship: "This role is not eligible for visa sponsorship." That's important info, include in a paragraph. Benefits: only mention "Benefits offered are described: AMD benefits at a glance." No details, so omit section. Now, let's write HTML. Structure:
About the role
... (The Role paragraph(s))
Responsibilities
- ...
Requirements
- ...
Qualifications
... (The Person paragraph)
... (Academic Credentials)
Location: Austin, Texas (Onsite). This role is not eligible for visa sponsorship.
But note: The Person is multiple paragraphs. I'll include as prose. Also, the "Key Responsibilities" list is bullet points. I'll convert each bullet to - .
"Preferred Experience" list is bullet points.
"Academic Credentials" is a single line.
Now, ensure no filler. The posting has substantive content for each.
Let's extract text:
The Role: "AMD is looking for a Server Platform Validation Engineer to join a global engineering team responsible for delivering and supporting Best Known Configurations (BKCs) used across multiple server programs. This is a highly visible, hands-on role that sits at the intersection of server platform validation, system engineering, and cross-functional technical collaboration. In this role, you will serve as a key North American technical resource for BKC activities, partnering closely with engineering stakeholders in the U.S. and a broader global team. You will work directly with server platforms in the lab, troubleshoot system-level issues, execute validation and regression testing, and help ensure BKC releases are fully validated and delivered on schedule. This is an exciting opportunity for someone who enjoys understanding how complete server systems work, from x86 CPUs and operating systems to GPU integration and platform-level hardware/software interaction. You will have an opportunity to take ownership of meaningful technical work, solve complex system problems, and collaborate with engineering teams across multiple geographies and programs."
The Person: "The ideal candidate is a hands-on systems engineer who enjoys troubleshooting complex technical problems and taking ownership from investigation through resolution. This person communicates clearly, works effectively across geographically distributed teams, and is comfortable collaborating with multiple engineering disciplines and stakeholders. The successful candidate will be self-directed, organized, and able to balance hands-on technical execution with cross-functional communication. Curiosity, strong problem-solving skills, adaptability, and a continuous-improvement mindset will help this individual thrive in a fast-moving server engineering environment. Candidates who are comfortable incorporating AI into their daily workflow and interested in using emerging AI capabilities to improve or automate technical workflows will be well positioned for success. Richard specifically identified everyday AI use as valuable and agentic AI/workflow automation as a more advanced capability."
Key Responsibilities: list of 8 bullets.
Preferred Experience: list of 13 bullets.
Academic Credentials: "Bachelor’s or Master’s degree in Computer Engineering, Computer Science, Electrical Engineering, or a comparable technical discipline is preferred."
Location: "LOCATION: Austin, Texas (Onsite) This role is not eligible for visa sponsorship."
Now, produce HTML.
I'll write:
About the role
AMD is looking for a Server Platform Validation Engineer to join a global engineering team responsible for delivering and supporting Best Known Configurations (BKCs) used across multiple server programs. This is a highly visible, hands-on role that sits at the intersection of server platform validation, system engineering, and cross-functional technical collaboration. In this role, you will serve as a key North American technical resource for BKC activities, partnering closely with engineering stakeholders in the U.S. and a broader global team. You will work directly with server platforms in the lab, troubleshoot system-level issues, execute validation and regression testing, and help ensure BKC releases are fully validated and delivered on schedule. This is an exciting opportunity for someone who enjoys understanding how complete server systems work, from x86 CPUs and operating systems to GPU integration and platform-level hardware/software interaction. You will have an opportunity to take ownership of meaningful technical work, solve complex system problems, and collaborate with engineering teams across multiple geographies and programs.
Responsibilities
- Support the validation, execution, and release of Best Known Configurations (BKCs) across multiple server programs.
- Serve as a technical point of contact for North American engineering stakeholders, helping connect U.S.-based teams with the broader global BKC organization.
- Investigate, troubleshoot, and resolve system and platform issues reported by engineering users to help minimize development blockers.
- Perform hands-on server platform validation, including system setup, regression execution, testing, and analysis in a lab environment.
- Take ownership of assigned portions of the BKC release and validation process and drive activities through completion.
- Collaborate across system engineering, software, firmware, validation, and other engineering disciplines to investigate platform-level issues.
- Work with x86 server platforms and contribute to validation involving CPU, GPU/accelerator, OS, and hardware/software integration.
- Help ensure weekly BKC releases are completed on schedule, fully validated, and free of significant issues before release to engineering users.
Requirements
- Experience with server platform validation, system validation, or system engineering.
- Experience with post-silicon validation and/or platform validation programs.
- Understanding of modern x86 CPU and PC/server platform architecture, including system boot flow.
- Experience with server CPU and GPU/accelerator integration or broader hardware/software system integration.
- Working knowledge of server operating systems, particularly Linux and Windows.
- Experience developing or executing system-level validation methodologies, test plans, regression testing, or validation infrastructure.
- Experience debugging complex platform or system-level hardware/software issues.
- Familiarity with programming or scripting languages such as Python, C/C++, or Perl.
- Experience working with multiple engineering teams and stakeholders across different geographic locations.
- Experience using AI as part of day-to-day technical work. Familiarity with agentic AI or using AI agents to automate technical workflows is a plus.
- Strong written and verbal communication skills.
- Ability to independently organize and prioritize multiple technical activities.
- Experience taking technical ownership or leading activities across teams is desired.
Qualifications
The ideal candidate is a hands-on systems engineer who enjoys troubleshooting complex technical problems and taking ownership from investigation through resolution. This person communicates clearly, works effectively across geographically distributed teams, and is comfortable collaborating with multiple engineering disciplines and stakeholders. The successful candidate will be self-directed, organized, and able to balance hands-on technical execution with cross-functional communication. Curiosity, strong problem-solving skills, adaptability, and a continuous-improvement mindset will help this individual thrive in a fast-moving server engineering environment. Candidates who are comfortable incorporating AI into their daily workflow and interested in using emerging AI capabilities to improve or automate technical workflows will be well positioned for success. Richard specifically identified everyday AI use as valuable and agentic AI/workflow automation as a more advanced capability.
Bachelor’s or Master’s degree in Computer Engineering, Computer Science, Electrical Engineering, or a comparable technical discipline is preferred.
Location: Austin, Texas (Onsite). This role is not eligible
-
- "Academic Credentials": This is education requirements. Could be part of Requirements or separate "Qualifications". I'll include as part of Requirements or separate? The rule says use headings like "Qualifications". I'll make a separate "Qualifications" section for academic credentials? But "The Person" already includes soft skills. Maybe combine: "Qualifications" for academic and "Requirements" for experience. However, the rule says "Qualifications" is a heading option. I'll do:
-