FPGA Engineer II (ONSITE)
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, application instructions, cookie/navigation, duplicated lines. Also remove "Learn More & Apply Now!" etc. Also remove sections like "At RTX, the world's largest aerospace..." maybe that's about company; could be part of About the role? The posting includes a paragraph about RTX and Collins Aerospace. That could be considered "About the role" or maybe "About the company". We need to decide sections. We have content: - Date posted, location, etc. Probably not needed as heading; could be minor metadata folded into a short
or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So we could include a short
with location and date posted maybe. - Position Role Type: Onsite. Could be part of Schedule? Actually schedule maybe not given. There's a later section "Onsite: Employees who are working in Onsite roles will work primarily onsite." That's schedule info. So we can include a Schedule section with that description. - U.S. Person requirement: that's a requirement (citizenship/immigration). Also security clearance none. - Then description: "At RTX, the world's largest aerospace..." that's company overview; could be part of About the role. - Then "Collins Aerospace is seeking a FPGA Engineer II for the CNS (Communication, Navigation, Surveillance) Hardware Engineering Group in Melbourne, Florida." That's role intro. - Then "The primary responsibility for this position will be to support existing CNS related products as part of a team. This Engineer role is intended for an experienced Electrical Engineering professional working with a small group of other FPGA Engineers. The position will support product design along with associated requirements and test procedures. This position may encompass both new design and product sustaining support roles. This is an onsite position in Melbourne, Florida." - Then "What You Will Do:" list of duties. - Then "Qualifications You Must Have:" list. - Then "Qualifications We Prefer:" list. - Then "What we offer:" list of benefits. - Then some extra paragraphs about Avionics etc. Might be more about company; could be part of About the role. - Then "Onsite: Employees who are working in Onsite roles will work primarily onsite..." schedule. - Then salary range. - Then benefits eligibility etc (some duplication). We need to avoid duplication. We must not create sections with filler like "commensurate with experience". Pay section: we have salary range: "The salary range for this role is 68,900 USD - 131,100 USD." That's specific, so we can include Pay section. Schedule: we have Onsite description; we can include Schedule section. Benefits: we have "What we offer:" list with many items. That's benefits. Qualifications: we have both Must Have and Prefer; we could combine into Qualifications section with two sublists? But instruction: use
for section headings, - for any list of duties/requirements/benefits, and
for prose. So we can have Qualifications section with two subheadings? Not allowed to add extra headings besides
. Could embed paragraphs inside Qualifications: maybe a
summarizing must have and prefer, but we need to preserve all detail. Better to have two
lists under Qualifications, each preceded by a describing? But we cannot add extra headings; we can use
to label "Must Have:" and "Preferred:" inside the Qualifications section. That's acceptable.
Similarly Responsibilities: we have "What You Will Do:" list.
We also have Requirements: includes U.S. Person requirement, security clearance none, maybe also degree? Actually degree is in Qualifications. Requirements could be citizenship and maybe security clearance.
We also have "Skills": maybe we can extract from qualifications: experience writing RTL, using FPGA tools, Linux, scripting, C/C++, Python/Perl, etc. Could be a Skills section. But we already have Qualifications covering those. The instruction says prefer a few substantive sections over many thin ones. So we might combine Qualifications and Skills into one Qualifications section. But we have separate headings list: Skills is optional; we can omit if not needed.
We need to include sections only when posting has real specific content. So we can include:
- About the role (company overview + role intro)
- Responsibilities (What You Will Do)
- Requirements (U.S. Person, security clearance none)
- Qualifications (Must Have and Preferred)
- Benefits (What we offer)
- Pay (salary range)
- Schedule (Onsite description)
We must not include sections like Skills if we already covered in Qualifications.
Now we need to preserve all substantive information. Let's extract.
About the role: combine the paragraphs about RTX, Collins Aerospace, and the role intro.
Paragraphs:
"At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Collins Aerospace is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. With a comprehensive portfolio and deep technical expertise, we help customers meet the demands of the global market. Join us and help shape the future of aerospace and defense."
Then: "Collins Aerospace is seeking a FPGA Engineer II for the CNS (Communication, Navigation, Surveillance) Hardware Engineering Group in Melbourne, Florida. The primary responsibility for this position will be to support existing CNS related products as part of a team. This Engineer role is intended for an experienced Electrical Engineering professional working with a small group of other FPGA Engineers. The position will support product design along with associated requirements and test procedures. This position may encompass both new design and product sustaining support roles. This is an onsite position in Melbourne, Florida."
We can combine into About the role.
Responsibilities: list under "What You Will Do:":
- Requirements capture, decomposition, and traceability.
- ASIC/FPGA/MPSoC digital architecture development and design.
- Develop RTL design code and simulation in VHDL, Verilog, and/or SystemVerilog.
- Create testcases and test procedures for verification environments using SystemVerilog or VHDL
- Create placement and timing constraints.
- Perform synthesis, place and route.
- Perform static timing analysis, linting analysis, LEC, and clock-domain-crossing analysis.
- Perform ASIC/FPGA/MPSoC verification using inspection, analysis, simulation, and test methods.
- Creation of DO-254 certification artifacts for Airborne Electronic Hardware (AEH).
- Conduct and/or participate in peer reviews throughout product lifecycle.
- Communicate well with a wide variety of individuals including Engineering, Program Management, internal leadership and/or customers.
Note there is a line break missing after "Create testcases and test procedures for verification environments using SystemVerilog or VHDL". We'll keep as is.
Requirements: U.S. Person requirement (detailed definition) and Security Clearance Type: None/Not Required, Status: Not Required.
We can include a short paragraph: "This job requires a U.S. Person (U.S. citizen, national, permanent resident, refugee, or asylee). No security clearance required."
We should preserve the definition? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the definition of U.S. Person as given. That's a bit long but we can include it as a
with the definition. Also include that security clearance is none.
We could also include the link to definition? Probably not needed as it's boilerplate? It's a link to ecfr.gov; might be considered reference; we could keep it? It's not boilerplate; it's a reference. Might keep.
But we should remove duplicated lines and boilerplate like EEO etc. The link is not duplicated; it's part of the definition. We'll keep.
Qualifications: Must Have list:
- Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 2 years of prior relevant experience or an Advanced Degree in a related field
- Candidates must be U.S. Person - Job requires access to ITAR or 600/500-series EAR information or hardware (directly or indirectly) and the company will not seek an export authorization for this role.
- Experience writing RTL and testbenches using VHDL, Verilog, or SystemVerilog.
- Experience using FPGA specific tools (e.g. Questasim, Vivado, Libero, Synplify Pro, etc.).
- Experience with Linux (or Unix), scripting, C/C++, Python, and/or Perl.
Qualifications We Prefer list:
- Ability to work with supervision, as part of a team of engineers with a variety of skills and backgrounds, located throughout the world and matrixed into projects with aggressive schedules and frequent milestones.
- Experience with DO-254 processes and design assurance activities for ASIC, FPGA, and/or MPSoc developments.
- Experience with data interfaces (PCIe, DDR, I2C, Ethernet, CDN, ARINC-429, etc.)
We could combine into Qualifications section with two
headings inside: "
Must Have:
" then , then "Preferred:
" then . Using is okay inside . Not a heading.
Benefits: "What we offer:" list:
- Medical, dental, and vision insurance
- Three weeks of vacation for newly hired employees
- Generous 401(k) plan that includes employer matching funds and separate employer retirement contribution, including a Lifetime Income Strategy option
- Tuition reimbursement program
- Student Loan Repayment Program
- Life insurance and disability coverage
- Optional coverages you can buy pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection
- Birth, adoption, parental leave benefits
- Ovia Health, fertility, and family planning
- Adoption Assistance Autism Benefit
- Employee Assistance Plan, including up to 10 free counseling sessions
- Healthy You Incentives, wellness rewards program
- Doctor on Demand, virtual doctor visits
- Bright Horizons, child and elder care services
- Teladoc Medical Experts, second opinion program
- And more!
We should preserve all items. Also later there is a paragraph about benefits eligibility etc. Might be duplicate; we can ignore duplicates.
Pay: "The salary range for this role is 68,900 USD - 131,100 USD." Also later there is more about benefits eligibility etc. We'll keep the salary range.
Schedule: "Onsite: Employees who are working in Onsite roles will work primarily onsite. This includes all production and maintenance employees, as they are essential to the development of our products. Regardless of your role type, collaboration and innovation are critical to our business and all employees will have access to digital tools so they can work with colleagues around the world – and access to Collins sites when their work requires in-person meetings."
We can include that as Schedule section.
Now we need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
Date Posted: 2026-08-07 | Location: Melbourne, Florida (US-FL-MELBOURNE-313 ~ 1344 S Babcock St ~ BLDG 313)
for prose. So we can have Qualifications section with two subheadings? Not allowed to add extra headings besides
. Could embed paragraphs inside Qualifications: maybe a
summarizing must have and prefer, but we need to preserve all detail. Better to have two
- lists under Qualifications, each preceded by a
describing? But we cannot add extra headings; we can use
to label "Must Have:" and "Preferred:" inside the Qualifications section. That's acceptable. Similarly Responsibilities: we have "What You Will Do:" list. We also have Requirements: includes U.S. Person requirement, security clearance none, maybe also degree? Actually degree is in Qualifications. Requirements could be citizenship and maybe security clearance. We also have "Skills": maybe we can extract from qualifications: experience writing RTL, using FPGA tools, Linux, scripting, C/C++, Python/Perl, etc. Could be a Skills section. But we already have Qualifications covering those. The instruction says prefer a few substantive sections over many thin ones. So we might combine Qualifications and Skills into one Qualifications section. But we have separate headings list: Skills is optional; we can omit if not needed. We need to include sections only when posting has real specific content. So we can include: - About the role (company overview + role intro) - Responsibilities (What You Will Do) - Requirements (U.S. Person, security clearance none) - Qualifications (Must Have and Preferred) - Benefits (What we offer) - Pay (salary range) - Schedule (Onsite description) We must not include sections like Skills if we already covered in Qualifications. Now we need to preserve all substantive information. Let's extract. About the role: combine the paragraphs about RTX, Collins Aerospace, and the role intro. Paragraphs: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Collins Aerospace is a leader in technologically advanced, intelligent solutions that help redefine the aerospace and defense industry. With a comprehensive portfolio and deep technical expertise, we help customers meet the demands of the global market. Join us and help shape the future of aerospace and defense." Then: "Collins Aerospace is seeking a FPGA Engineer II for the CNS (Communication, Navigation, Surveillance) Hardware Engineering Group in Melbourne, Florida. The primary responsibility for this position will be to support existing CNS related products as part of a team. This Engineer role is intended for an experienced Electrical Engineering professional working with a small group of other FPGA Engineers. The position will support product design along with associated requirements and test procedures. This position may encompass both new design and product sustaining support roles. This is an onsite position in Melbourne, Florida." We can combine into About the role. Responsibilities: list under "What You Will Do:": - Requirements capture, decomposition, and traceability. - ASIC/FPGA/MPSoC digital architecture development and design. - Develop RTL design code and simulation in VHDL, Verilog, and/or SystemVerilog. - Create testcases and test procedures for verification environments using SystemVerilog or VHDL - Create placement and timing constraints. - Perform synthesis, place and route. - Perform static timing analysis, linting analysis, LEC, and clock-domain-crossing analysis. - Perform ASIC/FPGA/MPSoC verification using inspection, analysis, simulation, and test methods. - Creation of DO-254 certification artifacts for Airborne Electronic Hardware (AEH). - Conduct and/or participate in peer reviews throughout product lifecycle. - Communicate well with a wide variety of individuals including Engineering, Program Management, internal leadership and/or customers. Note there is a line break missing after "Create testcases and test procedures for verification environments using SystemVerilog or VHDL". We'll keep as is. Requirements: U.S. Person requirement (detailed definition) and Security Clearance Type: None/Not Required, Status: Not Required. We can include a short paragraph: "This job requires a U.S. Person (U.S. citizen, national, permanent resident, refugee, or asylee). No security clearance required." We should preserve the definition? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the definition of U.S. Person as given. That's a bit long but we can include it as a
with the definition. Also include that security clearance is none. We could also include the link to definition? Probably not needed as it's boilerplate? It's a link to ecfr.gov; might be considered reference; we could keep it? It's not boilerplate; it's a reference. Might keep. But we should remove duplicated lines and boilerplate like EEO etc. The link is not duplicated; it's part of the definition. We'll keep. Qualifications: Must Have list: - Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 2 years of prior relevant experience or an Advanced Degree in a related field - Candidates must be U.S. Person - Job requires access to ITAR or 600/500-series EAR information or hardware (directly or indirectly) and the company will not seek an export authorization for this role. - Experience writing RTL and testbenches using VHDL, Verilog, or SystemVerilog. - Experience using FPGA specific tools (e.g. Questasim, Vivado, Libero, Synplify Pro, etc.). - Experience with Linux (or Unix), scripting, C/C++, Python, and/or Perl. Qualifications We Prefer list: - Ability to work with supervision, as part of a team of engineers with a variety of skills and backgrounds, located throughout the world and matrixed into projects with aggressive schedules and frequent milestones. - Experience with DO-254 processes and design assurance activities for ASIC, FPGA, and/or MPSoc developments. - Experience with data interfaces (PCIe, DDR, I2C, Ethernet, CDN, ARINC-429, etc.) We could combine into Qualifications section with two
headings inside: "
Must Have:
" then- , then "
Preferred:
" then- . Using is okay inside
. Not a heading. Benefits: "What we offer:" list: - Medical, dental, and vision insurance - Three weeks of vacation for newly hired employees - Generous 401(k) plan that includes employer matching funds and separate employer retirement contribution, including a Lifetime Income Strategy option - Tuition reimbursement program - Student Loan Repayment Program - Life insurance and disability coverage - Optional coverages you can buy pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection - Birth, adoption, parental leave benefits - Ovia Health, fertility, and family planning - Adoption Assistance Autism Benefit - Employee Assistance Plan, including up to 10 free counseling sessions - Healthy You Incentives, wellness rewards program - Doctor on Demand, virtual doctor visits - Bright Horizons, child and elder care services - Teladoc Medical Experts, second opinion program - And more! We should preserve all items. Also later there is a paragraph about benefits eligibility etc. Might be duplicate; we can ignore duplicates. Pay: "The salary range for this role is 68,900 USD - 131,100 USD." Also later there is more about benefits eligibility etc. We'll keep the salary range. Schedule: "Onsite: Employees who are working in Onsite roles will work primarily onsite. This includes all production and maintenance employees, as they are essential to the development of our products. Regardless of your role type, collaboration and innovation are critical to our business and all employees will have access to digital tools so they can work with colleagues around the world – and access to Collins sites when their work requires in-person meetings." We can include that as Schedule section. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
Date Posted: 2026-08-07 | Location: Melbourne, Florida (US-FL-MELBOURNE-313 ~ 1344 S Babcock St ~ BLDG 313)