Sr. Platform Hardware Design Engineer

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to parse the posting. First, the posting includes a paragraph about AMD mission, then "The Role" description. That could be "About the role". Then "Key Responsibilities" list. Then "Preferred Experience" list. Then "Academic Credentials". Then location line repeated. Then "Benefits offered are described: AMD benefits at a glance." That's a mention of benefits but not details. It says "Benefits offered are described: AMD benefits at a glance." That's not specific content; it's a reference. According to rules: never create Benefits section unless posting actually states them. It only says benefits are described elsewhere, not listing them. So we should not include Benefits section. Pay and Schedule: not mentioned. So we omit those. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly combine Preferred Experience as Requirements or Skills. Academic Credentials as Qualifications. Preferred Experience includes many items; could be Requirements or Skills. We'll decide. We need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate: EEO, visa sponsorship lines, AI screening, etc. Also remove duplicated lines: "This role is not eligible for visa sponsorship." appears twice; we should keep only one? The instruction: remove duplicated lines. So we should keep only one instance, but maybe we can drop it entirely as it's boilerplate? It's not substantive? It's a condition; maybe it's substantive? It's about visa sponsorship eligibility. Could be considered metadata. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." Visa sponsorship is minor metadata; we could drop it. Safer to drop it. Also "LOCATION: Austin, TX or Denver, CO" is location; could be minor metadata; we could drop or include in a short p. The instruction: fold minor metadata into a short

or drop it. So we could include a short p for location. But we need to preserve ALL substantive information; location is substantive? Might be considered metadata but still relevant. We'll include a short p. We also have "This role is not eligible for visa sponsorship." repeated; we can drop. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we remove the EEO paragraph, the AI policy line, etc. Now construct sections. About the role: The paragraph after "The Role As a Senior Platform Hardware Design Engineer, you will lead and be part of the design team developing state-of-the-art systems. This is a dynamic and fast-paced engineering environment where you will lead and participate in a wide variety of challenging product development projects. Your responsibilities include leading the development of system and board hardware from inception to full-volume production. This position requires the capability to closely work with power supply designs, mechanical and thermal teams, firmware development and validation teams, PCB layout engineers, and internal and external design stakeholders to create high-quality products and smooth volume production within a tight schedule. This position will focus on product development for the data center AI acceleration markets, one of the fastest-growing segments within AMD. Additionally, experience with switches and their board design, specifically using Broadcom or Cisco switches, is essential. This is a hybrid work opportunity based at our labs in Austin TX or Longmont CO, and relocation assistance may be available." We need to keep that as prose in

. Possibly split into multiple paragraphs but one is fine. Responsibilities: The "Key Responsibilities" block is a list of duties. We'll convert each sentence into

. The block currently is a long paragraph with sentences separated by periods. We need to split into list items. Let's extract each responsibility: - Technically lead cross-functional engineering teams responsible for system and hardware development of AI acceleration-based systems from product definition to production. This includes the physical design of multilevel boards, DFM (Design for Manufacturing), power regulation, board bring-up qualification and debug, thermal, signal integrity, and EMI (Electro-Magnetic Interference). - Provide cross-functional technical leadership and communication within the hardware engineering, architecture, customer, and program management teams. - Actively drive technical definition/architecture and program execution/issue resolution in a dynamic development environment with programs in various development phases ranging from concept, feasibility, execution, production, or sustaining. - Work with SOC silicon architects and the business unit to define and develop product requirements, specifications, and cost targets. - Drive innovation in system architecture, system management, circuit implementations, and security down to the level of component selections. - Define and manage validation and assist with hardware bring-up, troubleshooting, design verification, optimizations, and fine-tuning for an optimum balance of cost and performance at the board and system level. - Provide implementation guidelines and feedback to silicon, package, and system design groups. - Create and publish design technical documentation for internal and external stakeholders. We'll keep each as

. Requirements: Could be the "Preferred Experience" list? But that's more like preferred qualifications. We could treat "Preferred Experience" as Requirements. However we also have Academic Credentials separate. We'll make Requirements from Preferred Experience items (maybe split into bullet list). But we need to avoid thin sections; we could combine Preferred Experience and Academic Credentials into Qualifications and Skills? Let's think. We have sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to decide what goes where. Academic Credentials: "Bachelor’s or Master's degree in Computer or Electrical Engineering preferred". That's a qualification. Preferred Experience list includes many items: Strong board hardware and system design experience, Proven ability to drive product development from concept to mass production, Ability to write product specifications, BOM management skills, Solid experience in high-speed mixed-signal design techniques, Strong experience in Cadence tools, such as Concept Capture and Allegro PCB, Solid experience in LDOs and Multiphase DC-DC switching power supply Power Integrity for high-power ASIC products, Experience with power conversion and delivery for high-performance processors or GPUs is a plus, Experience with hardware lab tools, digital oscilloscopes, and other common lab equipment, Experience with firmware, APIs, applications, OSes, and their interactions within Windows, Linux, Data Accelerators, compute, and virtualization environments, Understanding of industrial standards: high-speed/digital interfaces (USB, PCI Express), memory interface, I2C/SMBus/PMBus, SPI, JTAG, Experience with scripting to assist with daily tasks (Python, BASH, Perl, etc), Must be self-driven, collaborative, and a strong team player with technical leadership skills to support optimal performance, Excellent teamwork, communication, and organization skills, Experience with high-speed serial interfaces, PCI Express and USB is a plus, Specific experience with switches, CPUs, FPGAs, and their board design including SI and PI knowledge. We could split these into Requirements (hard requirements) and Skills (preferred). But the posting labels them "Preferred Experience". So they are not strict requirements but preferred. However we still need to include them somewhere. We could put them under Requirements (since they are experience) or Skills. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Preferred Experience and Academic Credentials into a single "Qualifications" section. Or we could have Requirements (the core responsibilities) and Qualifications (education + preferred experience). But we already have Responsibilities separate. Let's do: - About the role (p) - Responsibilities (ul) - Qualifications (ul) combining Academic Credentials and Preferred Experience. We could also add Skills if needed, but we can avoid thin sections. The instruction says include a section ONLY when posting has real, specific content for it. So we can have just About the role, Responsibilities, Qualifications. That's three sections. That's acceptable. We must not create Benefits, Pay, Schedule sections. Now we need to output HTML fragment only, no /. Use

for each section heading. We need to include location maybe as a short p after About the role? Could fold minor metadata into a short p. We could add a

for location: "Location: Austin, TX or Longmont CO (hybrid). Relocation assistance may be available." But the posting says Austin TX or Longmont CO, and relocation assistance may be available. Also later says LOCATION: Austin, TX or Denver, CO (conflict). Actually there is inconsistency: earlier says Austin TX or Longmont CO; later says Austin, TX or Denver, CO. We need to preserve ALL substantive information; we must not invent or summarize away detail. So we need to include both location mentions? The posting has two location statements: "This is a hybrid work opportunity based at our labs in Austin TX or Longmont CO, and relocation assistance may be available." and later "LOCATION: Austin, TX or Denver, CO". This is duplicated/conflicting. We need to preserve all substantive information, but also remove duplicated lines. The duplicated lines refer to identical lines; these are not identical but similar. We could combine them into a single statement that captures both? But that would be summarizing. Better to include both as separate sentences? Might be considered duplicated? Not exactly same. We could include both as separate sentences in a p. That preserves info. We also have "This role is not eligible for visa sponsorship." repeated twice; we should drop duplicates. We could drop it entirely as minor metadata. But maybe it's substantive? It's a condition. The instruction says fold minor metadata into a short p or drop it. So we can drop it. Now construct HTML. We'll have:

About the role

The Role As a Senior Platform Hardware Design Engineer, you will lead and be part of the design team developing state-of-the-art systems. This is a dynamic and fast-paced engineering environment where you will lead and participate in a wide variety of challenging product development projects. Your responsibilities include leading the development of system and board hardware from inception to full-volume production. This position requires the capability to closely work with power supply designs, mechanical and thermal teams, firmware development and validation teams, PCB layout engineers, and internal and external design stakeholders to create high-quality products and smooth volume production within a tight schedule. This position will focus on product development for the data center AI acceleration markets, one of the fastest-growing segments within AMD. Additionally, experience with switches and their board design, specifically using Broadcom or Cisco switches, is essential. This is a hybrid work opportunity based at our labs in Austin TX or Longmont CO, and relocation assistance may be available. LOCATION: Austin, TX or Denver, CO

But we need to avoid repeating "The Role" as heading? Already we have heading. The paragraph starts with "The Role As a Senior..." which repeats the heading; but we must preserve ALL substantive information; we cannot remove that phrase because it's part of the posting. It's okay. Now Responsibilities:

Responsibilities

• Technically lead cross-functional engineering teams responsible for system and hardware development of AI acceleration-based systems from product definition to production. This includes the physical design of multilevel boards, DFM (Design for Manufacturing), power regulation, board bring-up qualification and debug, thermal, signal integrity, and EMI (Electro-Magnetic Interference).
• Provide cross-functional technical leadership and communication within the hardware engineering, architecture, customer, and program management teams.
• Actively drive technical definition/architecture and program execution/issue resolution in a dynamic development environment with programs in various development phases ranging from concept, feasibility, execution, production, or sustaining.
• Work with SOC silicon architects and the business unit to define and develop product requirements, specifications, and cost targets.
• Drive innovation in system architecture, system management, circuit implementations, and security down to the level of component selections.
• Define and manage validation and assist with hardware bring-up, troubleshooting, design verification, optimizations,