Principal FPGA Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
First, remove boilerplate: Date Posted, Country, Location line, Position Role Type, etc. Also remove security clearance details? Those are part of Requirements. Keep them.
We need to produce sections:
- About the role: maybe a paragraph summarizing the role description: The Multi-Product Power & Digital (MPD) department designs FPGAs... We are currently seeking a Principal Electrical Engineer... This position is an onsite role, located in McKinney, TX.
- Responsibilities: list of duties from "What You Will Do". Use - .
- Requirements: includes citizenship, security clearance, etc. Also "Qualifications You Must Have" maybe part of Requirements? The posting has "Qualifications You Must Have" and "Qualifications We Value". Those are qualifications. So we can have Requirements section for mandatory: U.S. citizenship, ability to obtain/maintain security clearance, active existing clearance required after day 1. Also maybe "Typically requires a degree in STEM and a minimum of 8 years of prior relevant experience." That's a qualification but could be in Requirements. We'll decide.
- Qualifications: could combine both "Qualifications You Must Have" and "Qualifications We Value". But we need to avoid duplication. Perhaps separate sections: Requirements (mandatory) and Qualifications (preferred). The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements and Qualifications separate.
- Skills: maybe list specific technical skills: FPGA/ASIC design (VHDL/Verilog), tools, timing closure, etc. Could be extracted from qualifications.
- Benefits: from "What We Offer": relocation based on candidate eligibility, benefits list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also annual short-term/long-term incentive compensation programs. We'll include.
- Pay: salary range: 107,500 USD - 204,500 USD.
- Schedule: maybe not explicitly given; only mention onsite role. No schedule details like full-time, etc. Not given. So we should not create Schedule section if no specific content.
We must not include boilerplate like EEO, legal, privacy policy, application instructions, etc.
We must preserve all substantive information; do not invent or summarize away detail. Must not repeat job title as heading.
We need to output only HTML fragment.
Let's craft.
First, maybe a short paragraph for metadata? Not needed as heading.
We'll start with
About the role
then ...
.
Then Responsibilities
with each duty.
We need to extract duties from "What You Will Do". Let's list them:
- Provide full lifecycle support of production quality FPGA designs for all major vendors and device families including AMD (Xilinx), Altera, and Microchip (Microsemi) using tools such as AMD Vivado, Altera Quartus Prime Pro or Libero.
- Generate FPGA designs for the following applications: gigabit and multigigabit transceiver (MGT) serial interfaces, Radio Frequency (RF) DSP, controls, data links, embedded processing and processor interfaces.
- Translate system level requirements into FPGA requirements
- Architect FPGA-based systems to determine parts, interfaces, and Concept of Operations (CONOPS)
- Lead small teams of FPGA engineers and code in VHDL for reliability and maintainability
- Verify designs utilizing self-checking techniques with directed and constrained random tests, while tracking functional and code coverage
- Define schedules for FPGA tasking and drive execution to the planned budget and schedule.
- Identify and manage project risks and opportunities.
- Create complete documentation including requirements, verification plan, and user’s guides
- Lead medium sized teams to success.
- Coach, review, and delegate work to junior engineers.
- Serve as a subject-matter expert within discipline.
- Lead internal and external technical reviews.
- Support customer interactions and relations.
- Contribute to product and technology roadmaps
- Make improvements to processes, systems or products to enhance overall performance
- Engage in personal technical growth and facilitate technical growth in peers and junior engineers.
We'll put each as - .
Now Requirements: include:
- U.S. citizenship required (as only U.S. citizens are eligible for a security clearance)
- Ability to obtain and maintain a U.S. government issued security clearance is required.
- Security clearance type: DoD Clearance: Secret
- Security clearance status: Active and existing security clearance required after day 1.
Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements" but we already captured.
We could also include "Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and a minimum of 8 years of prior relevant experience." That's a qualification but could be in Requirements. However we have a Qualifications section for both must-have and valued. To avoid duplication, we could put the degree/experience in Qualifications (must-have). But the instruction says we can have Requirements and Qualifications sections. Let's decide: Requirements: citizenship, security clearance. Qualifications: education/experience, technical skills, etc. That seems logical.
Thus Requirements section will contain only citizenship and clearance details.
Now Qualifications section: include both "Qualifications You Must Have" and "Qualifications We Value". We'll combine into a list maybe separate subheadings? But we only allowed headings for sections; we could still have
with items, maybe separate with headings inside? Not needed. We'll just list all qualifications as bullet points.
But we must not invent or summarize away detail; we need to preserve all substantive information. So we need to include each bullet from both sections.
Let's extract Qualifications You Must Have:
- Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and a minimum of 8 years of prior relevant experience.
- Experience to include one or more of the following:
* FPGA/ASIC design (VHDL and/or Verilog coding) or FPGA/ASIC verification (System Verilog coding)
* Experience with AMD (Xilinx), Altera and/or Microchip (Microsemi) devices and with tools such as AMD Vivado, Altera Quartus Prime Pro or Libero.
* Hands on experience with integration and debug of FPGA/ASIC in a lab environment
* Experience with timing closure, clock domain crossing and reset domain crossing analysis, and constraint development.
* Experience with source code management, design reviews, and code release in a team development environment.
Qualifications We Value:
- One or more advanced degrees in Electrical Engineering or a related STEM major. A suitable degree may be counted as 2 years of work experience.
- FPGA/ASIC design experience in one or more of the following areas:
* Radar processing techniques
* Image processing techniques for visual and infrared sensors
* Embedded systems design using ARM, Microblaze, or NIOS processors
* Gigabit serial interfaces and multi-gigabit transceivers (MGTs)
* Constrained random verification in UVM using System Verilog
* Verification utilizing emulation platforms, such as Veloce
* Experience with High Level Synthesis (HLS)
* Experience with vector processors and/or GPUs
* Using AI to improve FPGA workflows (verification automation, log triage, regression analytics)
* AI/ML inference on FPGA (Vitis AI, FINN, custom accelerators)
- Demonstrated ability to lead successful teams.
- Experience managing technical, cost, and schedule risks and opportunities.
- Experience with project management tools such as Earned Value and/or Agile Execution.
- Experience communicating and documenting technical topics and presenting to customers and management.
- Experience leading a program transition from development to production.
- Proposal development experience.
- Experience with intellectual property generation (patents & publications).
- Demonstrated mentorship of junior engineers.
We'll list each as
- . For sub-bullets we can just flatten.
Now Skills section: maybe we can extract specific technical skills from qualifications: FPGA/ASIC design (VHDL/Verilog), tools (Vivado, Quartus Prime Pro, Libero), timing closure, clock domain crossing, reset domain crossing, constraint development, source code management, design reviews, code release, integration/debug in lab, etc. Also radar processing, image processing, embedded systems design, gigabit serial interfaces, MGTs, constrained random verification UVM System Verilog, emulation platforms Veloce, HLS, vector processors/GPUs, AI/ML inference, etc. Also leadership skills, project management, communication, proposal development, IP generation, mentorship.
We could create a Skills section with bullet list of these skills. However we already have Qualifications covering many of these; but the instruction allows Skills section. To avoid duplication, we could still include Skills but ensure we don't repeat same content verbatim? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections, but better to avoid redundancy. However we could still include Skills as a concise list of technical skills distinct from qualifications. But many of those are also qualifications. Might be okay to have both sections; but we risk being considered redundant but not violating rules. However the instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Perhaps we can combine Skills into Qualifications, and not create a separate Skills section. Since we already have Qualifications covering skills, we can omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have any Schedule info: none. So omit.
Now Benefits: from "What We Offer": relocation based on candidate eligibility. Benefits list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also annual short-term and/or long-term incentive compensation programs depending on level and collective bargaining; payments not guaranteed. We'll include those as bullet points.
Pay: salary range: 107,500 USD - 204,500 USD.
Now we need to ensure we don't include boilerplate like "Learn More & Apply Now!", "This position requires a security clearance." (we already have). Also remove links, etc.
Now produce HTML.
Let's craft.
We'll start with
About the role
...
About the role paragraph: combine sentences: "The Multi-Product Power & Digital (MPD) department designs FPGAs, circuit cards, and electronics subassemblies for a range of products including missiles/effectors, radars, and electronic warfare systems. The team leverages digital, analog, and power design skills to provide support throughout the product lifecycle from architecture and design through production and sustainment. We are currently seeking a Principal Electrical Engineer, with strong technical leadership ability, to function as the Field Programmable Gate Array Lead. This position is an onsite role located in McKinney, TX."
Now Responsibilities with each duty.
Now Requirements with items: U.S. citizenship required; Ability to obtain and maintain a U.S. government issued security clearance required; Security clearance type: DoD Secret; Active and existing security clearance required after day 1.
Now Qualifications with all qualifications items.
We need to ensure we preserve the nuance: "Typically requires a degree in STEM and a minimum of 8 years of prior relevant experience." We'll keep as bullet.
For the "Experience to include one
About the role
then...
. ThenResponsibilities
- with each duty.
We need to extract duties from "What You Will Do". Let's list them:
- Provide full lifecycle support of production quality FPGA designs for all major vendors and device families including AMD (Xilinx), Altera, and Microchip (Microsemi) using tools such as AMD Vivado, Altera Quartus Prime Pro or Libero.
- Generate FPGA designs for the following applications: gigabit and multigigabit transceiver (MGT) serial interfaces, Radio Frequency (RF) DSP, controls, data links, embedded processing and processor interfaces.
- Translate system level requirements into FPGA requirements
- Architect FPGA-based systems to determine parts, interfaces, and Concept of Operations (CONOPS)
- Lead small teams of FPGA engineers and code in VHDL for reliability and maintainability
- Verify designs utilizing self-checking techniques with directed and constrained random tests, while tracking functional and code coverage
- Define schedules for FPGA tasking and drive execution to the planned budget and schedule.
- Identify and manage project risks and opportunities.
- Create complete documentation including requirements, verification plan, and user’s guides
- Lead medium sized teams to success.
- Coach, review, and delegate work to junior engineers.
- Serve as a subject-matter expert within discipline.
- Lead internal and external technical reviews.
- Support customer interactions and relations.
- Contribute to product and technology roadmaps
- Make improvements to processes, systems or products to enhance overall performance
- Engage in personal technical growth and facilitate technical growth in peers and junior engineers.
We'll put each as
- .
Now Requirements: include:
- U.S. citizenship required (as only U.S. citizens are eligible for a security clearance)
- Ability to obtain and maintain a U.S. government issued security clearance is required.
- Security clearance type: DoD Clearance: Secret
- Security clearance status: Active and existing security clearance required after day 1.
Also maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements" but we already captured.
We could also include "Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and a minimum of 8 years of prior relevant experience." That's a qualification but could be in Requirements. However we have a Qualifications section for both must-have and valued. To avoid duplication, we could put the degree/experience in Qualifications (must-have). But the instruction says we can have Requirements and Qualifications sections. Let's decide: Requirements: citizenship, security clearance. Qualifications: education/experience, technical skills, etc. That seems logical.
Thus Requirements section will contain only citizenship and clearance details.
Now Qualifications section: include both "Qualifications You Must Have" and "Qualifications We Value". We'll combine into a list maybe separate subheadings? But we only allowed headings for sections; we could still have
- with items, maybe separate with
- . For sub-bullets we can just flatten.
Now Skills section: maybe we can extract specific technical skills from qualifications: FPGA/ASIC design (VHDL/Verilog), tools (Vivado, Quartus Prime Pro, Libero), timing closure, clock domain crossing, reset domain crossing, constraint development, source code management, design reviews, code release, integration/debug in lab, etc. Also radar processing, image processing, embedded systems design, gigabit serial interfaces, MGTs, constrained random verification UVM System Verilog, emulation platforms Veloce, HLS, vector processors/GPUs, AI/ML inference, etc. Also leadership skills, project management, communication, proposal development, IP generation, mentorship.
We could create a Skills section with bullet list of these skills. However we already have Qualifications covering many of these; but the instruction allows Skills section. To avoid duplication, we could still include Skills but ensure we don't repeat same content verbatim? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections, but better to avoid redundancy. However we could still include Skills as a concise list of technical skills distinct from qualifications. But many of those are also qualifications. Might be okay to have both sections; but we risk being considered redundant but not violating rules. However the instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Perhaps we can combine Skills into Qualifications, and not create a separate Skills section. Since we already have Qualifications covering skills, we can omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have any Schedule info: none. So omit.
Now Benefits: from "What We Offer": relocation based on candidate eligibility. Benefits list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also annual short-term and/or long-term incentive compensation programs depending on level and collective bargaining; payments not guaranteed. We'll include those as bullet points.
Pay: salary range: 107,500 USD - 204,500 USD.
Now we need to ensure we don't include boilerplate like "Learn More & Apply Now!", "This position requires a security clearance." (we already have). Also remove links, etc.
Now produce HTML.
Let's craft.
We'll start with
About the role
...
About the role paragraph: combine sentences: "The Multi-Product Power & Digital (MPD) department designs FPGAs, circuit cards, and electronics subassemblies for a range of products including missiles/effectors, radars, and electronic warfare systems. The team leverages digital, analog, and power design skills to provide support throughout the product lifecycle from architecture and design through production and sustainment. We are currently seeking a Principal Electrical Engineer, with strong technical leadership ability, to function as the Field Programmable Gate Array Lead. This position is an onsite role located in McKinney, TX." Now Responsibilities- with each duty.
Now Requirements
- with items: U.S. citizenship required; Ability to obtain and maintain a U.S. government issued security clearance required; Security clearance type: DoD Secret; Active and existing security clearance required after day 1.
Now Qualifications
- with all qualifications items.
We need to ensure we preserve the nuance: "Typically requires a degree in STEM and a minimum of 8 years of prior relevant experience." We'll keep as bullet.
For the "Experience to include one
headings inside? Not needed. We'll just list all qualifications as bullet points. But we must not invent or summarize away detail; we need to preserve all substantive information. So we need to include each bullet from both sections. Let's extract Qualifications You Must Have: - Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and a minimum of 8 years of prior relevant experience. - Experience to include one or more of the following: * FPGA/ASIC design (VHDL and/or Verilog coding) or FPGA/ASIC verification (System Verilog coding) * Experience with AMD (Xilinx), Altera and/or Microchip (Microsemi) devices and with tools such as AMD Vivado, Altera Quartus Prime Pro or Libero. * Hands on experience with integration and debug of FPGA/ASIC in a lab environment * Experience with timing closure, clock domain crossing and reset domain crossing analysis, and constraint development. * Experience with source code management, design reviews, and code release in a team development environment. Qualifications We Value: - One or more advanced degrees in Electrical Engineering or a related STEM major. A suitable degree may be counted as 2 years of work experience. - FPGA/ASIC design experience in one or more of the following areas: * Radar processing techniques * Image processing techniques for visual and infrared sensors * Embedded systems design using ARM, Microblaze, or NIOS processors * Gigabit serial interfaces and multi-gigabit transceivers (MGTs) * Constrained random verification in UVM using System Verilog * Verification utilizing emulation platforms, such as Veloce * Experience with High Level Synthesis (HLS) * Experience with vector processors and/or GPUs * Using AI to improve FPGA workflows (verification automation, log triage, regression analytics) * AI/ML inference on FPGA (Vitis AI, FINN, custom accelerators) - Demonstrated ability to lead successful teams. - Experience managing technical, cost, and schedule risks and opportunities. - Experience with project management tools such as Earned Value and/or Agile Execution. - Experience communicating and documenting technical topics and presenting to customers and management. - Experience leading a program transition from development to production. - Proposal development experience. - Experience with intellectual property generation (patents & publications). - Demonstrated mentorship of junior engineers. We'll list each as
- . For sub-bullets we can just flatten.
Now Skills section: maybe we can extract specific technical skills from qualifications: FPGA/ASIC design (VHDL/Verilog), tools (Vivado, Quartus Prime Pro, Libero), timing closure, clock domain crossing, reset domain crossing, constraint development, source code management, design reviews, code release, integration/debug in lab, etc. Also radar processing, image processing, embedded systems design, gigabit serial interfaces, MGTs, constrained random verification UVM System Verilog, emulation platforms Veloce, HLS, vector processors/GPUs, AI/ML inference, etc. Also leadership skills, project management, communication, proposal development, IP generation, mentorship.
We could create a Skills section with bullet list of these skills. However we already have Qualifications covering many of these; but the instruction allows Skills section. To avoid duplication, we could still include Skills but ensure we don't repeat same content verbatim? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections, but better to avoid redundancy. However we could still include Skills as a concise list of technical skills distinct from qualifications. But many of those are also qualifications. Might be okay to have both sections; but we risk being considered redundant but not violating rules. However the instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. Perhaps we can combine Skills into Qualifications, and not create a separate Skills section. Since we already have Qualifications covering skills, we can omit Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have any Schedule info: none. So omit.
Now Benefits: from "What We Offer": relocation based on candidate eligibility. Benefits list: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also annual short-term and/or long-term incentive compensation programs depending on level and collective bargaining; payments not guaranteed. We'll include those as bullet points.
Pay: salary range: 107,500 USD - 204,500 USD.
Now we need to ensure we don't include boilerplate like "Learn More & Apply Now!", "This position requires a security clearance." (we already have). Also remove links, etc.
Now produce HTML.
Let's craft.
We'll start with