FPGA Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We have content: Job Description (prose), Responsibilities (list), Essential Skills (list), Additional Skills & Qualifications (list), Work Environment (prose), Job Type & Location (prose), Pay And Benefits (pay range and benefits list), Workplace Type (prose), Application Deadline (date), About Actalent (boilerplate? maybe not needed but it's about company; but it's likely considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Actalent is not exactly those, but it's company description; might be considered boilerplate but not explicitly prohibited. However we should preserve substantive information; but it's not essential to the role. Might be okay to keep? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The About Actalent is substantive about the company but not about the role. Might be considered boilerplate but not listed. Safer to keep? However they said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. About Actalent is not those. I'd keep it as a section maybe "About the company" but we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's no "About the company". So we might not create a heading for it; we could embed it in a

  under maybe "About the role"? But that's not accurate. Better to omit it because we don't have a heading for it and we shouldn't invent headings. 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; we could also use other headings if needed? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we should map content to those headings. If a section doesn't have substantive content, we omit it. Thus we need to decide which headings to include: - About the role: could be the Job Description paragraph. - Responsibilities: list of responsibilities. - Requirements: maybe Essential Skills? Or Requirements could be essential skills? Qualifications could be Additional Skills & Qualifications? Skills could be maybe combine? But we need to avoid thin sections. We could combine Requirements and Qualifications into one? But they said prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements (including essential skills and additional skills), Benefits, Pay, Schedule? Schedule maybe from Work Environment (hybrid, onsite as needed). Pay And Benefits includes pay range and benefits. So we could have Pay and Benefits combined? But they said use headings Pay and Benefits separately if they exist. The posting has both Pay And Benefits section. So we can have

  Pay

  with pay range, and

  Benefits

  with benefits list. Or we could combine but they said prefer few sections; but we have both present, so we should include both. Schedule: The posting mentions hybrid work environment, onsite as needed, but not a specific schedule like hours. Could be considered schedule info. We could include Schedule section with that info. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Qualifications and Skills maybe omitted to avoid thin sections; we can incorporate qualifications into Requirements. We must not repeat job title as heading. Good. We must not include Job ID etc. We must remove boilerplate: equal opportunity, accommodation, etc. Also remove "Application Deadline" maybe? That's not in headings list; but we could include it under About the role? Might be considered metadata; but we could drop it as it's not in headings list and not required. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." Application deadline is minor metadata; we could drop it or fold into a short p. Probably drop it. About Actalent is company description; could be folded into About the role? Might be considered minor metadata; but it's not about the role. Might drop. We need to preserve all substantive information about the role: responsibilities, essential skills, additional skills, work environment, job type & location, pay, benefits, workplace type. Thus we will produce:

  About the role

  The FPGA Engineer designs, implements, and verifies FPGA-based solutions that support advanced Navy torpedo testing systems. This role focuses on developing HDL code in AMD/Xilinx environments, creating robust verification plans and testbenches, and supporting hardware integration and laboratory testing. The engineer collaborates closely with cross-functional technical teams, produces clear engineering documentation, and contributes to the modernization of critical government systems.

  Responsibilities

  • Design, modify, integrate, and verify FPGA implementations that support Navy torpedo testing systems.
  • Develop high-quality HDL code using Verilog, SystemVerilog, and VHDL within AMD/Xilinx FPGA development environments.
  • Create comprehensive FPGA verification plans and develop testbenches to validate functionality and performance.
  • Execute verification activities, analyze results, and refine designs based on test outcomes and system requirements.
  • Support FPGA integration efforts as designs transition from development to hardware implementation.
  • Troubleshoot FPGA and hardware-related issues during laboratory testing and integration activities.
  • Utilize laboratory equipment, including oscilloscopes, digital multimeters (DMMs), and other debugging tools, to validate and debug FPGA designs.
  • Generate and maintain detailed technical documentation, including design descriptions, implementation plans, verification reports, and other engineering artifacts.
  • Collaborate closely with firmware engineers, systems engineers, and technical leads throughout the entire development lifecycle.
  • Participate in design reviews, present technical findings, and incorporate feedback to improve design quality and reliability.
  • Contribute innovative technical solutions while operating within established engineering processes and standards.
  • Support system integration activities as the program progresses toward full hardware implementation and testing.
  • Work onsite as needed to support integration phases and hands-on laboratory testing.

  Requirements

  • Bachelor's degree in Electrical Engineering, Computer Engineering, or a related technical discipline.
  • Practical experience developing FPGA designs using Verilog, SystemVerilog, and VHDL.
  • Hands-on experience with AMD/Xilinx FPGA devices and the Vivado design tool suite.
  • Experience creating and executing FPGA verification plans and developing testbenches.
  • Experience supporting FPGA integration and hardware testing activities in a lab environment.
  • Strong technical documentation skills, including the ability to write clear design descriptions, implementation plans, and engineering reports.
  • Hands-on experience using laboratory test equipment such as oscilloscopes and digital multimeters (DMMs) for debugging and validation.
  • Ability to work onsite in Middletown, RI as required by project and integration activities.
  • Ability to obtain and maintain a Secret Security Clearance.
  • Proficiency in HDL design and verification, including testbench development and validation workflows.
  • Ability to collaborate effectively with cross-functional engineering teams and participate in structured design reviews.
  • Experience with Ethernet interfaces for FPGA-based systems.
  • Experience with SPI communication protocols and their implementation in FPGA designs.
  • Experience working on defense, aerospace, or Navy programs and familiarity with their engineering processes.
  • Experience supporting system-level integration efforts and resolving hardware–firmware interaction issues.
  • Familiarity with embedded hardware development environments and workflows.
  • Interest in modernizing and improving legacy government systems and test infrastructures.
  • Ability to contribute innovative ideas within established engineering frameworks and processes.

  Work Environment

  This role operates in a hybrid work environment, combining remote work with onsite collaboration in Middletown, RI. During critical integration phases, the FPGA Engineer works onsite full time to support hands-on hardware implementation and laboratory testing. The work involves regular use of engineering and lab equipment such as AMD/Xilinx FPGA development tools (Vivado), oscilloscopes, digital multimeters (DMMs), and other debugging instruments. The environment is highly technical and collaborative, with close interaction among firmware, systems, and hardware engineers focused on modernizing and improving government test systems.

  But we said we prefer few sections; we have About the role, Responsibilities, Requirements, Work Environment, Pay, Benefits, Schedule maybe. That's many sections. Could we combine Work Environment into About the role? But About the role already has description; we could add work environment there. However the instruction: "Prefer a few substantive sections over many thin ones." We have many sections but each is substantive. Could we merge Requirements and Work Environment? Not really. Could we merge Pay and Benefits? They are separate headings but we could combine into one "Compensation and Benefits"? But they gave examples of Pay and Benefits as separate headings; but we could still combine if we think it's thin? However they have substantive content for both pay range and benefits list, so each is substantive. So it's okay. Schedule: we haven't added a Schedule section; we could add schedule info from Work Environment (hybrid, onsite as needed). But we already have Work Environment covering that. So we could drop Schedule. Thus final sections: About the role, Responsibilities, Requirements, Work Environment, Pay, Benefits. We need to ensure we don't include any boilerplate like equal opportunity, accommodation, etc. We removed those. Check for any duplicated lines: we have not duplicated. Now output HTML fragment only. Let's craft. Be careful to escape any HTML special characters? Not needed. We'll output:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Work Environment

  ...

  Pay

  The pay range for this position is $100000.00 - $130000.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors.

  Benefits

  • Medical, dental & vision
  • Critical Illness, Accident, and Hospital
  • 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available
  • Life Insurance (Volunt