Hardware/FPGA Engineer

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "What You'll Do", "What You'll Need", "What Will Help You On The Job", salary range, benefits mention. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content accordingly. We must not repeat job title as heading. We must not include Job ID etc. Remove boilerplate: EEO statement, accommodation request, navigation, etc. Also remove "About Us" maybe? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content. We have: - About Us: mission statement. Could map to "About the role"? Actually "About Us" is company overview, not role. But we could put under "About the role"? Might be okay. However instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says e.g., not limited to those. So we can use those headings if appropriate. We have content for Responsibilities (What You'll Do), Requirements (What You'll Need), Qualifications/Skills (What Will Help You On The Job), Pay (salary range), Benefits (mention of benefits). Also maybe "About the role" could be a brief summary? Could combine About Us and role description? But we have "What You'll Do" as responsibilities. So we can have sections: Responsibilities, Requirements, Qualifications (or Skills), Pay, Benefits. We must not create sections with filler like "commensurate with experience". We have actual salary range, so Pay section is valid. Benefits: posting mentions "range of medical, financial, and/or other benefits" and link to benefits page. That's specific enough? It says "Additional cash or stock incentives may be provided as part of the compensation package, in addition to a range of medical, financial, and/or other benefits, dependent on the position offered." That's somewhat generic but still mentions benefits. We can include Benefits section with that sentence. We must not include Schedule (no info). So omit. We must not repeat job title as heading. We must not include navigation/legal/EEO etc. So remove EEO statement and accommodation request. We must preserve all substantive information. So we need to include the mission statement? Possibly under About the role? But we could include a short paragraph about the company under a heading like "About Viasat" but not in allowed headings? The instruction says use those headings for sections; but we could also add other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections, but not strictly limited? Safer to stick to those headings. So we need to map content to those headings. We have: - Responsibilities: "What You'll Do" bullet list (the day-to-day design and implement...). We'll put as

• . - Requirements: "What You'll Need" bullet list. - Qualifications/Skills: "What Will Help You On The Job" bullet list. - Pay: salary range details. - Benefits: mention of benefits. We might also include an "About the role" section that summarises the role purpose: maybe combine "About Us" and first paragraph? But we have no explicit "About the role". Could we treat the first paragraph after "About Us" as role description? Actually after "About Us" there is "What You'll Do". So maybe we skip About the role heading entirely if no specific content. But we need to include sections only when posting has real, specific content. If we don't have a distinct "About the role" summary, we could omit that heading. The instruction: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we should not include About the role if we don't have specific content. We could maybe use the first sentence "As a Hardware Design Engineer, you will support the end-to-end development..." as role description, but that's already in Responsibilities. So we can skip About the role. Thus output sections: Responsibilities, Requirements, Qualifications (or Skills), Pay, Benefits. We need to decide which heading for the "What Will Help You On The Job": could be Qualifications or Skills. Since it's "What Will Help You On The Job" includes preferred qualifications, experience, etc. We'll use

  Qualifications

  (or Skills). The instruction list includes Qualifications and Skills as separate possible headings. We'll choose Qualifications. Now we need to preserve all substantive information: need to include the bullet points exactly as given, but we can format as
  • . Ensure we don't lose any detail. Let's extract details. Responsibilities (What You'll Do) includes: - Design and implement high-speed digital boards, including schematic capture and layout guidelines. - Develop, simulate, and verify FPGA RTL (using SystemVerilog, Verilog, or VHDL) for control, data processing, and communication functions. - Integrate and deploy firmware onto FPGA and FPGA SoC platforms. - Design high-speed interfaces (DDR4, SERDES, UART, I2C, SPI, LVDS) and perform signal/power integrity simulations using HyperLynx. - Conduct worst-case analysis (WCA) to verify electrical design margins across space environment conditions. - Lead laboratory board bring-up, hardware/firmware integration, and debug using logic analyzers, oscilloscopes, and spectrum analyzers. - Apply flight hardware and firmware design practices, working within radiation-tolerant, high-reliability component and thermal constraints. - Author and maintain comprehensive design documentation, including schematics, block diagrams, testbenches, and interface control documents. Also earlier paragraph: "As a Hardware Design Engineer, you will support the end-to-end development of advanced digital processing systems, high-speed digital boards, and FPGA-based subsystems for space-based and mission-critical communication platforms. You will serve as a key technical contributor, bridging the hardware-firmware boundary by owning the hardware lifecycle of complex board designs—including high-speed digital schematic capture, SoC integration, and mixed-signal circuit design with high-resolution ADC/DAC interfaces—while simultaneously designing, simulating, and implementing high-speed signal-processing algorithms and network protocols in FPGAs. Your responsibility will span the entire product development lifecycle from early conceptual requirements, block diagrams, and synthesizable RTL development (SystemVerilog/VHDL), through hardware-firmware co-design, board-level bring-up, and laboratory integration, all the way to worst-case analysis (WCA), power/signal integrity verification, and flight qualification in a rigorous space and flight environment." We should include that prose as

    before the list? The instruction: use

    for prose. So we can include that introductory paragraph as a

    under Responsibilities, then the list. Similarly for Requirements (What You'll Need) includes: - Bachelor’s Degree in Electrical Engineering, Computer Engineering, or a related field. - 4+ years of combined experience in high-speed digital board design and FPGA/RTL development. - Proficiency in writing synthesizable RTL in SystemVerilog, Verilog, or VHDL. - Hands-on experience with FPGA design suites and EDA tools (e.g., AMD/Xilinx Vivado, Intel/Altera Quartus, Synopsys Synplify). - Hands-on experience with schematic capture tools (e.g., Mentor Xpedition, Cadence, or Altium). - Strong laboratory debugging skills integrating firmware onto physical target boards. - US citizenship. - Ability to travel up to 10%. We'll put as

    • . Qualifications (What Will Help You On The Job) includes: - Master’s Degree in Electrical Engineering (MSEE). - Experience with space-grade FPGAs (Xilinx Radiation Tolerant, Microchip RTG4, or equivalent). - Experience with FPGA simulation and testbench development (ModelSim, Questa, etc.). - Familiarity with scripting languages (Python, TCL, or Perl) for automation. - Experience with EEE-INST-002, NASA, or ESA parts selection, screening, and derating guidelines. - Familiarity with radiation effects on electronics (TID, SEE, SEL). - Familiarity with Git, CI/CD practices, and AI development tools (Claude Code, Copilot). We'll put as
      • . Pay: Salary range $132,500.00 - $209,500.00 / annually. For specific work locations within San Jose, the San Francisco Bay area and New York City metropolitan area, the base pay range for this role is $164,500.00- $246,500.00/ annually. At Viasat, we consider many factors when it comes to compensation, including the scope of the position as well as your background and experience. Base pay may vary depending on job-related knowledge, skills, and experience. Additional cash or stock incentives may be provided as part of the compensation package, in addition to a range of medical, financial, and/or other benefits, dependent on the position offered. We need to include all that as prose under Pay section. Possibly also mention that additional cash/stock incentives may be provided. We'll put as

        . Benefits: The posting says: "Additional cash or stock incentives may be provided as part of the compensation package, in addition to a range of medical, financial, and/or other benefits, dependent on the position offered. Learn more about Viasat’s comprehensive benefit offerings that are focused on your holistic health and wellness at https://careers.viasat.com/benefits." We already included that in Pay? Actually that sentence appears in Pay paragraph. But we can also create Benefits section with that sentence and the link. However we must not duplicate content. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we put the benefits sentence in Pay, we still preserve it. But we also might create a Benefits section to follow the heading convention. However we risk duplicating the same sentence if we also include it in Pay. Better to separate: Pay section includes salary range and factors; Benefits section includes the benefits description and link. The Pay paragraph currently includes "Additional cash or stock incentives may be provided as part of the compensation package, in addition to a range of medical, financial, and/or other benefits, dependent on the position offered." That's actually about benefits. So we could move that sentence to Benefits section, leaving Pay just about salary range and factors. Let's do that. Thus Pay section: salary range statements (two ranges) and factors. Benefits section: sentence about additional cash/stock incentives and range of medical, financial, and/or other benefits, plus link. We must not include navigation/footer etc. Now produce HTML fragment:

        Responsibilities

        As a Hardware Design Engineer, you will support the end-to-end development of advanced digital processing systems, high-speed digital boards, and FPGA-based subsystems for space-based and mission-critical communication platforms. You will serve as a key technical contributor, bridging the hardware-firmware boundary by owning the hardware lifecycle of complex board designs—including high-speed digital schematic capture, SoC integration, and mixed-signal circuit design with high-resolution ADC/DAC interfaces—while simultaneously designing, simulating, and implementing high-speed signal-processing algorithms and network protocols in FPGAs. Your responsibility will span the entire product development lifecycle from early conceptual requirements, block diagrams, and synthesizable RTL development (SystemVerilog/VHDL), through hardware-firmware co-design, board-level bring-up, and laboratory integration, all the way to worst-case analysis (WCA), power/signal integrity verification, and flight qualification