Senior FPGA Verification Engineer
for section headings (e.g. 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 (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include. The posting includes:
- About The Team (description)
- About The Job (description)
- What You’ll Do (list of duties)
- Required Qualifications (list)
- Preferred Qualifications (list)
- US Salary Range (Pay)
- Benefits (list)
We should map to headings: "About the role" maybe for About The Job? But we have both About The Team and About The Job. Could combine? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: could be About The Job description (maybe also include About The Team? Might be separate but we can include as part of About the role? Probably better to have "About the team" as separate? Not in list but we can still use heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings if appropriate, but better to stick to those. However we need to preserve all substantive info. We could have:
About the team
(though not in examples but allowed). The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to use those exact headings where applicable.
We have:
- About the role: could be "About The Job" description.
- Responsibilities: "What You’ll Do"
- Requirements: "Required Qualifications"
- Qualifications: maybe "Preferred Qualifications" (or Skills)
- Skills: maybe "Preferred Qualifications" includes skills.
- Benefits: "Benefits"
- Pay: "US Salary Range"
- Schedule: not present, so omit.
We also have "About The Team" which could be placed under "About the role" or separate heading like "About the team". Since not in examples but we can still use About the team. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could incorporate About The Team into About the role section (maybe as a paragraph). That would preserve info.
Thus sections:
About the role
Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years.
The Anduril Imaging team develops state-of-the-art imaging systems across both hardware and software, deployed to tackle the most significant security challenges of America and its allies. The team is heavily involved in utilizing computer vision, perception, electro-optical, infrared, and sensor data to give our war fighters and allies an advantage.
The Imaging team is seeking a Senior FPGA Verification Engineer to help design a new product lines. In this role, you will work closely with an interdisciplinary technical team to define, complete the design and analysis, build prototypes leading to ground and flight testing, and mature the prototypes into products.
Then Responsibilities:
Responsibilities
- Verification environment architecture and design using tools like SystemVerilog or OVM/UVM
- Creation of written test plan, testcases, code coverage tracking, and functional coverage tracking
- Testbench development for the verification of RTL blocks using VHDL or SystemVerilog
- Recommend new tools and practices for continuous improvement in the group's ASIC / FPGA verification flow
- Contribute to engineering estimates for new program pursuits.
- Provide technical leadership for project verification teams by breaking down work, planning activities, and reporting status
Requirements (Required Qualifications):
Requirements
- A Bachelor's in Electrical Engineering, Computer Engineering, or a related technical field is typically required.
- 8+ years of experience developing HDL firmware for FPGA devices
- Demonstrated experience developing and simulating RTL designs using VHDL and/or Verilog in a professional FPGA or ASIC development environment.
- Proven ability to design, implement, and execute verification testbenches for RTL blocks using VHDL and/or SystemVerilog.
- Experience applying chip-level verification methodologies, including constrained-random testing, functional coverage analysis, and assertion-based verification (SystemVerilog)
- Experience using revision control systems such as Git or Subversion to manage source code, collaborate across engineering teams, and maintain configuration integrity.
Note there is a duplicated line in original: "experience developing and simulating RTL designs using VHDL and/or Verilog in a professional FPGA or ASIC development environment." appears twice. We should keep only one instance (preserve all substantive info but not duplicate). We'll include once.
Preferred Qualifications:
Qualifications
(or Skills). Let's use "Qualifications" for preferred.
- Experience with ASIC/FPGA lab validation and debug using standard lab equipment, along with familiarity with DFT, manufacturability, and production test concepts.
- Proficiency with Unix/Linux environments, scripting or software development (C, C++, Python, Perl, or shell), and industry-standard ASIC/FPGA simulation and synthesis tools such as QuestaSim, Synplify, Quartus, or Vivado.
Pay:
Pay
US Salary Range $165,000—$218,000 USD
Benefits:
Benefits
- Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package.
- Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next.
But the benefits text includes a sentence that is prose; we could split: first bullet about equity grants, second paragraph about benefits. The instruction: use - for any list of duties/requirements/benefits, and
for prose. So we need to decide if benefits are a list. The posting says: "Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next. For more information, Explore Our Benefits."
We could treat as two paragraphs: one about equity grants, one about benefits package. Or we could make a list with two items: equity grants and benefits package. The benefits package description is prose; but we can still put in
- as it's a list item. Probably better to make a list:
- Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package.
- Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next.
We should also include the line "For more information, Explore Our Benefits." That's like a link; but it's application instruction? It's not essential; we could drop as it's like a call to action. Might be considered boilerplate? It's not legal/EEO but it's a navigation. Safer to drop.
We also need to remove duplicated lines, scam warning boilerplate, EEO, etc. Already removed.
Now ensure we didn't include any placeholder like "commensurate with experience". Not present.
Now output only HTML fragment.
Let's craft final HTML:
About the role
Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years.
The Anduril Imaging team develops state-of-the-art imaging systems across both hardware and software, deployed to tackle the most significant security challenges of America and its allies. The team is heavily involved in utilizing computer vision, perception, electro-optical, infrared, and sensor data to give our war fighters and allies an advantage.
The Imaging team is seeking a Senior FPGA Verification Engineer to help design a new product lines. In this role, you will work closely with an interdisciplinary technical team to define, complete the design and analysis, build prototypes leading to ground and flight testing, and mature the prototypes into products.
Responsibilities
- Verification environment architecture and design using tools like SystemVerilog or OVM/UVM
- Creation of written test plan
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - About The Team (description) - About The Job (description) - What You’ll Do (list of duties) - Required Qualifications (list) - Preferred Qualifications (list) - US Salary Range (Pay) - Benefits (list) We should map to headings: "About the role" maybe for About The Job? But we have both About The Team and About The Job. Could combine? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: could be About The Job description (maybe also include About The Team? Might be separate but we can include as part of About the role? Probably better to have "About the team" as separate? Not in list but we can still use heading? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we can use other headings if appropriate, but better to stick to those. However we need to preserve all substantive info. We could have:
About the team
(though not in examples but allowed). The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to use those exact headings where applicable.
We have:
- About the role: could be "About The Job" description.
- Responsibilities: "What You’ll Do"
- Requirements: "Required Qualifications"
- Qualifications: maybe "Preferred Qualifications" (or Skills)
- Skills: maybe "Preferred Qualifications" includes skills.
- Benefits: "Benefits"
- Pay: "US Salary Range"
- Schedule: not present, so omit.
We also have "About The Team" which could be placed under "About the role" or separate heading like "About the team". Since not in examples but we can still use About the team. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could incorporate About The Team into About the role section (maybe as a paragraph). That would preserve info.
Thus sections:
About the role
About the team. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we cannot use other headings, but to be safe we could incorporate About The Team into About the role section (maybe as a paragraph). That would preserve info.
Thus sections:
About the role
About the role
Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years.
The Anduril Imaging team develops state-of-the-art imaging systems across both hardware and software, deployed to tackle the most significant security challenges of America and its allies. The team is heavily involved in utilizing computer vision, perception, electro-optical, infrared, and sensor data to give our war fighters and allies an advantage.
The Imaging team is seeking a Senior FPGA Verification Engineer to help design a new product lines. In this role, you will work closely with an interdisciplinary technical team to define, complete the design and analysis, build prototypes leading to ground and flight testing, and mature the prototypes into products.
Then Responsibilities:Responsibilities
- Verification environment architecture and design using tools like SystemVerilog or OVM/UVM
- Creation of written test plan, testcases, code coverage tracking, and functional coverage tracking
- Testbench development for the verification of RTL blocks using VHDL or SystemVerilog
- Recommend new tools and practices for continuous improvement in the group's ASIC / FPGA verification flow
- Contribute to engineering estimates for new program pursuits.
- Provide technical leadership for project verification teams by breaking down work, planning activities, and reporting status
Requirements
- A Bachelor's in Electrical Engineering, Computer Engineering, or a related technical field is typically required.
- 8+ years of experience developing HDL firmware for FPGA devices
- Demonstrated experience developing and simulating RTL designs using VHDL and/or Verilog in a professional FPGA or ASIC development environment.
- Proven ability to design, implement, and execute verification testbenches for RTL blocks using VHDL and/or SystemVerilog.
- Experience applying chip-level verification methodologies, including constrained-random testing, functional coverage analysis, and assertion-based verification (SystemVerilog)
- Experience using revision control systems such as Git or Subversion to manage source code, collaborate across engineering teams, and maintain configuration integrity.
Qualifications
(or Skills). Let's use "Qualifications" for preferred.- Experience with ASIC/FPGA lab validation and debug using standard lab equipment, along with familiarity with DFT, manufacturability, and production test concepts.
- Proficiency with Unix/Linux environments, scripting or software development (C, C++, Python, Perl, or shell), and industry-standard ASIC/FPGA simulation and synthesis tools such as QuestaSim, Synplify, Quartus, or Vivado.
Pay
US Salary Range $165,000—$218,000 USD
Benefits:Benefits
- Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package.
- Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next.
- for any list of duties/requirements/benefits, and
for prose. So we need to decide if benefits are a list. The posting says: "Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package. Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next. For more information, Explore Our Benefits." We could treat as two paragraphs: one about equity grants, one about benefits package. Or we could make a list with two items: equity grants and benefits package. The benefits package description is prose; but we can still put in
- as it's a list item. Probably better to make a list:
- Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package.
- Additionally, Anduril offers top-tier benefits for full-time employees, including: At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next.
About the role
Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years.
The Anduril Imaging team develops state-of-the-art imaging systems across both hardware and software, deployed to tackle the most significant security challenges of America and its allies. The team is heavily involved in utilizing computer vision, perception, electro-optical, infrared, and sensor data to give our war fighters and allies an advantage.
The Imaging team is seeking a Senior FPGA Verification Engineer to help design a new product lines. In this role, you will work closely with an interdisciplinary technical team to define, complete the design and analysis, build prototypes leading to ground and flight testing, and mature the prototypes into products.
Responsibilities
- Verification environment architecture and design using tools like SystemVerilog or OVM/UVM
- Creation of written test plan