Staff System Architecture and Design Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Content: - About Analog Devices (company description) – maybe not needed as a section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we only include sections if posting has real specific content for them. We have "About The Role" paragraph: "As a System Engineer, you will own the system development of high-voltage power converters — from power system architecture, power distribution box (PDBs) to intelligent power integration platforms. You will work at the intersection of power electronics, embedded firmware, and system architecture to deliver high-efficiency solutions that support the rapidly evolving power demands of AI data center." That's about the role. So we can have

About the role

with

that paragraph. Key Responsibilities: list of bullet points. So we need

Responsibilities

with

• each. We have "Required Qualifications" list. That includes qualifications like M.S. or above, 3+ years experience, etc. Also there are "Preferred" items? Actually after Required Qualifications there is a list that includes "Knowledge of datacenter power architectures — 800V distribution, rack-level power delivery, battery backup integration are preferred." and "Experience with FPGA-based control system development (VHDL/Verilog) or FPGA/MCU partitioning for power converter applications is a plus". Those could be considered Skills or Qualifications. The instruction: Use sections for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide where to put each piece. "Required Qualifications" likely maps to Requirements or Qualifications. The posting says "Required Qualifications". So we can put that under

  Requirements

  or

  Qualifications

  . Since they have both sections, we need to decide. Usually "Requirements" are mandatory, "Qualifications" could be preferred. But we have only required qualifications listed; we also have some preferred items (knowledge of datacenter power architectures, FPGA experience). Those could go under Skills or Qualifications as preferred. We could put required qualifications under Requirements, and preferred under Skills. Or we could combine all under Qualifications. The instruction says prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But they said use headings for those categories; we can include both if we have content. However we must not create thin sections. Let's see content: Required Qualifications bullet points: - M.S. or above in Electrical Engineering, Power Electronics, or a closely related field. - 3+ years of industrial experience in the project development for power converters (DC/DC, AC/DC, or inverter systems), Candidates with additional experience may be considered at the Staff Engineer level. - Understanding of power converter topologies (LLC, phase-shifted full bridge, DAB, MMC, interleaved buck/boost) and their control requirements. - Deep expertise in control design and implementation — voltage/current mode control, digital compensator design, and dynamic response optimization. - Deep expertise the design tools for simulations, such as Simetrix/Simplis, Mathcad, PLECS or PSIM. - Deep understanding of GaN/SiC device characteristics and system benefits. - Proven ability to debug and troubleshoot power electronics systems in a lab environment — oscilloscopes, power analyzers, and thermal characterization. - Excellent communication skills with the ability to clearly articulate complex technical concepts to cross-functional teams. Then after that: "Knowledge of datacenter power architectures — 800V distribution, rack-level power delivery, battery backup integration are preferred." and "Experience with FPGA-based control system development (VHDL/Verilog) or FPGA/MCU partitioning for power converter applications is a plus". Those could be Skills. Then later: "For positions requiring access to technical data, Analog Devices, Inc. may have to obtain export licensing approval..." That's legal/boilerplate; we must remove. Then: "Analog Devices is an equal opportunity employer..." Remove. Then: "Job Req Type: Experienced Required Travel: Yes, 10% of the time Shift Type: 1st Shift/Days" This includes schedule info: Shift Type: 1st Shift/Days, Required Travel: Yes, 10% of the time. So we have schedule info: shift type and travel. So we can include a Schedule section with that info. Then: "The expected wage range for a new hire into this position is $150,978 to $218,624. Actual wage offered may vary depending on work location, experience, education, training, external market data, internal pay equity, or other bona fide factors.This position qualifies for a discretionary performance-based bonus which is based on personal and company factors.This position includes medical, vision and dental coverage, 401k, paid vacation, holidays, and sick time, and other benefits." Thus we have Pay (wage range + bonus) and Benefits (medical, vision, dental, 401k, paid vacation, holidays, sick time, other benefits). So we need Pay and Benefits sections. Thus we will have sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay, Schedule. We need to decide if we need both Requirements and Qualifications. Since we have required qualifications, we could put them under Requirements. Then we could put preferred items under Skills. Or we could combine required and preferred under Qualifications and not have Skills. But we have skills like "Excellent communication skills" which is a skill but also listed under required qualifications. Might be okay to put under Requirements. Better to follow the headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (the required qualifications), Qualifications (maybe we could put the same as Requirements? but that would be duplicate). Could put the required qualifications under Requirements, and the preferred items under Qualifications (knowledge of datacenter power architectures, FPGA experience). Then Skills could be things like "Excellent communication skills" etc. But we already have communication skills in required qualifications. Might be redundant. Given the instruction to prefer few substantive sections over many thin ones, maybe we combine Requirements and Qualifications into one section called Requirements (or Qualifications). But we must follow the instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not mandatory to include all. So we can choose which to include. So we can include only those sections that have real specific content. Thus we can have: - About the role - Responsibilities - Requirements (including required qualifications and maybe also preferred? but we can separate) - Skills (maybe communication skills etc.) - Benefits - Pay - Schedule We need to ensure we don't create thin sections. Let's see if each will have substantive content. About the role: one paragraph. Responsibilities: list of ~7 bullet points. Requirements: list of required qualifications (8 bullet points). That's substantive. Skills: we could include "Excellent communication skills" (but that's already in requirements). Could also include "Knowledge of datacenter power architectures — 800V distribution, rack-level power delivery, battery backup integration are preferred." and "Experience with FPGA-based control system development (VHDL/Verilog) or FPGA/MCU partitioning for power converter applications is a plus". Those are more like preferred qualifications/skills. So we can put those under Skills. Benefits: list of medical, vision, dental, 401k, paid vacation, holidays, sick time, other benefits. Pay: wage range and bonus. Schedule: shift type and travel. Thus we have 7 sections, each substantive. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

  About the role

  As a System Engineer, you will own the system development of high-voltage power converters — from power system architecture, power distribution box (PDBs) to intelligent power integration platforms. You will work at the intersection of power electronics, embedded firmware, and system architecture to deliver high-efficiency solutions that support the rapidly evolving power demands of AI data center.

  Responsibilities

  • Design, develop, and optimize multi-kW intelligent system products including high voltage PDBs, DC/DC modules and intelligent power for AI data center.
  • Own the debug, testing, bring-up, and troubleshooting of system prototype in the lab, including hands-on measurement and root-cause analysis.
  • Perform system modeling, simulation, validation, and troubleshooting to ensure robust system performance.
  • Develop power modules and system products, including electrical, thermal, and mechanical integration of DC/DC controllers, power stages, wide-bandgap (GaN or SiC) devices, and protection solutions.
  • Design isolated power solutions and magnetic components to meet performance, safety, efficiency, and EMI requirements.
  • Implement high-voltage power management and protection functions, including hot-swap controllers, DC/DC converters, and power-stage solutions.
  • Collaborate with silicon, firmware, software, and validation teams to deliver fully integrated and tested solutions in lab.

  Requirements

  • M.S. or above in Electrical Engineering, Power Electronics, or a closely related field.
  • 3+ years of industrial experience in the project development for power converters (DC/DC, AC/DC, or inverter systems); candidates with additional experience may be considered at the Staff Engineer level.
  • Understanding of power converter topologies (LLC, phase-shifted full bridge, DAB, MMC, interleaved buck/boost) and their control requirements.
  • Deep expertise in control design and implementation — voltage/current mode control, digital compensator design, and dynamic response optimization.
  • Deep expertise with design tools for simulations, such as Simetrix/Simplis, Mathcad, PLECS or PSIM.
  • Deep understanding of GaN/SiC device characteristics and system benefits.
  • Proven ability to debug and troubleshoot power electronics systems in a lab environment — oscilloscopes, power analyzers, and thermal characterization.
  • Excellent communication skills with the ability to clearly articulate complex technical concepts to cross-functional teams.

  Skills

  • Knowledge of datacenter power architectures — 800V distribution, rack-level power delivery, battery backup integration (preferred).
  • Experience with FPGA-based control system development (VHDL/Verilog) or FPGA/MCU partitioning for power converter applications (plus).

  Benefits

  • Medical, vision, and dental coverage
  • 401(k)
  • Paid vacation
  • Holidays
  • Sick time
  • Other benefits

  Pay

  The expected wage range for a new hire into this position is $150,978 to $218,624. Actual wage offered may vary depending on work location, experience, education, training, external market