Entry Level- FPGA Engineer (Onsite- Aberdeen, Maryland)
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID etc.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the "How To Apply" section? That's application instructions. According to rule: remove application instructions. So we should not include the "How To Apply" paragraph. Also drop "Compensation- Salary ..."? That's compensation info but we decided not to create Pay section; but we still need to preserve substantive information. The compensation paragraph includes info about base pay may vary, additional incentives, range of benefits. That's substantive. We could include that in Benefits section maybe. But we need to avoid creating Pay section. So we can put compensation details in Benefits section? Or maybe a "Compensation" section? But rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation info (though vague). But we could treat it as "Compensation" section? The rule mentions Pay specifically; but "Compensation" might be considered similar to Pay. Safer to not create a Compensation section. Instead we could incorporate that info into Benefits section (since benefits mentioned). But the paragraph also mentions base pay may vary, additional incentives. That's pay info. If we put it in Benefits, we might be mixing pay with benefits, but still preserving info. The rule only prohibits creating Pay/Schedule/Benefits sections unless posting actually states them. It doesn't say we cannot include pay info inside another section. So we can include compensation details in Benefits section or maybe in a "Compensation and Benefits" section? That might be considered a Pay section. Safer to put in Benefits.
Schedule: we have "Position Type/Expected Hours of Work This is a full time, exempt position." That's schedule info. We can create a Schedule section with that line.
Now we need to ensure we don't include any filler like "commensurate with experience". Not present.
Now we need to extract content:
About The Opportunity: paragraph(s) after "About The Opportunity". We'll combine into a section
About the role
maybe? The heading could be "About the role". Use that.
Responsibilities: "What You Will Do" list. We'll make Responsibilities
then - each bullet.
Requirements: "Minimum Qualifications" list. We'll make
Requirements
then - each bullet.
Preferred Qualifications: "Preferred, Not Required" list. We'll make
Preferred Qualifications
then - each bullet.
Benefits: include compensation paragraph and benefits mention. We'll make
Benefits
then containing the compensation paragraph (maybe split into sentences). Also include "range of medical, financial, and/or other benefits." Actually that's part of same paragraph. We'll keep as is.
Schedule:
Schedule
This is a full time, exempt position.
We also need to include "Technology and mission areas" paragraph maybe incorporate into About the role or as separate section? Could add to About the role after the initial paragraph. Let's include it in About the role as additional paragraphs.
We must not include "How To Apply", "Work Authorization/Security Clearance", "AAP/EEO Statement", "EVERGREEN RECRUITING NOTICE". Also drop "Position Type/Expected Hours of Work" we used for Schedule.
Now let's craft HTML.
We need to preserve all substantive information: ensure we don't lose any details.
Let's copy the About The Opportunity paragraph:
"Fairwinds Technologies is continuously looking for curious, hands-on early-career engineers who want to turn digital design concepts into working hardware for radios, RF systems, embedded platforms, and operationally relevant test environments. In this role, you may support either our xG or Mixed Signal product development team, or technical-services contracts aligned with those product areas. You will work alongside experienced FPGA, DSP, RF, embedded software, systems, and test engineers to design, simulate, implement, integrate, and verify programmable-logic solutions. Assignments may span internal product development and customer-funded research, integration, test, demonstration, and field-support activities. The position is designed to build practical engineering depth while giving an early-career engineer exposure to the full lifecycle from requirements and architecture through hardware verification and measured system performance."
Then "Technology and mission areas Depending on assignment, you may contribute in one or more of the following areas: xG wireless systems, including 5G, non-terrestrial networking, software-defined radio, tactical communications, radio integration, and networked edge systems.Mixed Signal products, including Global Link and EchoPhase-related capabilities, channel emulation, coherent combining, wideband signal processing, and high-speed data-converter interfaces.Digital upconversion and downconversion, filtering, channelization, synchronization, buffering, timing, control, calibration, and real-time data paths.Ruggedized mission modules and RF systems that combine FPGA logic, embedded compute, networking, radio, and mixed-signal hardware.Government-funded R&D and technical-services contracts involving architecture, implementation, integration, verification, demonstrations, documentation, and field support."
We need to keep that as prose.
Now Responsibilities bullets: list each sentence starting with "Design, implement, simulate, and verify FPGA logic using VHDL, Verilog, or SystemVerilog under the guidance of experienced engineers." etc. We'll extract each.
Let's list them:
- Design, implement, simulate, and verify FPGA logic using VHDL, Verilog, or SystemVerilog under the guidance of experienced engineers.
- Develop reusable modules for data movement, control, timing, digital interfaces, buffering, signal processing, monitoring, and system integration.
- Create testbenches, test vectors, assertions, and repeatable verification procedures to demonstrate functional and timing performance.
- Use FPGA vendor development tools to synthesize, place and route, analyze timing, program devices, and debug designs in laboratory hardware.
- Support device and board bring-up involving FPGAs, data converters, processors, memory, clocks, radios, RF front ends, and high-speed digital interfaces.
- Collaborate with DSP engineers to translate algorithms and reference models into fixed-point, pipelined, resource-aware hardware implementations.
- Collaborate with embedded software engineers on register maps, control interfaces, drivers, configuration, telemetry, and embedded Linux integration.
- Use simulation, on-chip debug tools, laboratory instruments, and captured data to identify root causes and validate corrective actions.
- Participate in code reviews, configuration management, issue tracking, design reviews, and continuous integration practices.
- Prepare clear design descriptions, interface documentation, verification results, test reports, and configuration records for product and customer-funded activities.
Now Minimum Qualifications bullets:
- Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, or a closely related technical field, completed or expected before start date.
- Coursework, laboratory, internship, capstone, research, or personal-project experience with FPGA development, digital logic, computer architecture, or embedded systems.
- Foundational understanding of synchronous digital design, finite-state machines, registers, counters, memories, clocking, reset strategies, and timing concepts.
- Academic or project experience using VHDL, Verilog, SystemVerilog, or another hardware description language.
- Basic familiarity with simulation, synthesis, testbenches, and debugging digital hardware.
- Ability to apply structured problem solving, learn unfamiliar devices and interfaces, communicate assumptions, and document results clearly.
- Ability to collaborate in a multidisciplinary engineering environment and satisfy customer, site-access, export-control, and security requirements associated with assigned work.
Now Preferred, Not Required bullets:
- Hands-on experience with an AMD/Xilinx, Intel/Altera, Microchip, Lattice, or comparable FPGA development board and toolchain.
- Exposure to high-speed interfaces, data converters, DDR memory, Ethernet, PCIe, JESD204, SPI, I2C, UART, AXI, or similar buses and protocols.
- Familiarity with fixed-point arithmetic, digital signal processing, software-defined radio, clock-domain crossing, timing closure, or hardware-in-the-loop testing.
- Experience using Python, MATLAB, Simulink, cocotb, C or C++, Linux, Git, scripting, or automated build and verification workflows.
- Coursework or project experience in wireless communications, RF systems, signal processing, 5G/LTE, non-terrestrial networks, radar, satellite communications, or test and measurement.
Now Benefits/compensation paragraph: "Compensation- Salary At Fairwinds, 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, location and experience. Additional incentives may be provided as part of the compensation package, in addition to a range of medical, financial, and/or other benefits."
We need to keep that as is. Might want to fix the hyphen: "Compensation- Salary" maybe it's a typo; we keep as is.
Now Schedule: "Position Type/Expected Hours of Work This is a full time, exempt position."
We'll output as This is a full time, exempt position.
Now ensure we don't include any extra whitespace or markdown.
Let
for prose. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to drop the "How To Apply" section? That's application instructions. According to rule: remove application instructions. So we should not include the "How To Apply" paragraph. Also drop "Compensation- Salary ..."? That's compensation info but we decided not to create Pay section; but we still need to preserve substantive information. The compensation paragraph includes info about base pay may vary, additional incentives, range of benefits. That's substantive. We could include that in Benefits section maybe. But we need to avoid creating Pay section. So we can put compensation details in Benefits section? Or maybe a "Compensation" section? But rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state compensation info (though vague). But we could treat it as "Compensation" section? The rule mentions Pay specifically; but "Compensation" might be considered similar to Pay. Safer to not create a Compensation section. Instead we could incorporate that info into Benefits section (since benefits mentioned). But the paragraph also mentions base pay may vary, additional incentives. That's pay info. If we put it in Benefits, we might be mixing pay with benefits, but still preserving info. The rule only prohibits creating Pay/Schedule/Benefits sections unless posting actually states them. It doesn't say we cannot include pay info inside another section. So we can include compensation details in Benefits section or maybe in a "Compensation and Benefits" section? That might be considered a Pay section. Safer to put in Benefits. Schedule: we have "Position Type/Expected Hours of Work This is a full time, exempt position." That's schedule info. We can create a Schedule section with that line. Now we need to ensure we don't include any filler like "commensurate with experience". Not present. Now we need to extract content: About The Opportunity: paragraph(s) after "About The Opportunity". We'll combine into a section
About the role
maybe? The heading could be "About the role". Use that. Responsibilities: "What You Will Do" list. We'll makeResponsibilities
then- each bullet.
Requirements: "Minimum Qualifications" list. We'll make
Requirements
then- each bullet.
Preferred Qualifications: "Preferred, Not Required" list. We'll make
Preferred Qualifications
then- each bullet.
Benefits: include compensation paragraph and benefits mention. We'll make
Benefits
thencontaining the compensation paragraph (maybe split into sentences). Also include "range of medical, financial, and/or other benefits." Actually that's part of same paragraph. We'll keep as is. Schedule:
Schedule
This is a full time, exempt position.
We also need to include "Technology and mission areas" paragraph maybe incorporate into About the role or as separate section? Could add to About the role after the initial paragraph. Let's include it in About the role as additional paragraphs. We must not include "How To Apply", "Work Authorization/Security Clearance", "AAP/EEO Statement", "EVERGREEN RECRUITING NOTICE". Also drop "Position Type/Expected Hours of Work" we used for Schedule. Now let's craft HTML. We need to preserve all substantive information: ensure we don't lose any details. Let's copy the About The Opportunity paragraph: "Fairwinds Technologies is continuously looking for curious, hands-on early-career engineers who want to turn digital design concepts into working hardware for radios, RF systems, embedded platforms, and operationally relevant test environments. In this role, you may support either our xG or Mixed Signal product development team, or technical-services contracts aligned with those product areas. You will work alongside experienced FPGA, DSP, RF, embedded software, systems, and test engineers to design, simulate, implement, integrate, and verify programmable-logic solutions. Assignments may span internal product development and customer-funded research, integration, test, demonstration, and field-support activities. The position is designed to build practical engineering depth while giving an early-career engineer exposure to the full lifecycle from requirements and architecture through hardware verification and measured system performance." Then "Technology and mission areas Depending on assignment, you may contribute in one or more of the following areas: xG wireless systems, including 5G, non-terrestrial networking, software-defined radio, tactical communications, radio integration, and networked edge systems.Mixed Signal products, including Global Link and EchoPhase-related capabilities, channel emulation, coherent combining, wideband signal processing, and high-speed data-converter interfaces.Digital upconversion and downconversion, filtering, channelization, synchronization, buffering, timing, control, calibration, and real-time data paths.Ruggedized mission modules and RF systems that combine FPGA logic, embedded compute, networking, radio, and mixed-signal hardware.Government-funded R&D and technical-services contracts involving architecture, implementation, integration, verification, demonstrations, documentation, and field support." We need to keep that as prose. Now Responsibilities bullets: list each sentence starting with "Design, implement, simulate, and verify FPGA logic using VHDL, Verilog, or SystemVerilog under the guidance of experienced engineers." etc. We'll extract each. Let's list them: - Design, implement, simulate, and verify FPGA logic using VHDL, Verilog, or SystemVerilog under the guidance of experienced engineers. - Develop reusable modules for data movement, control, timing, digital interfaces, buffering, signal processing, monitoring, and system integration. - Create testbenches, test vectors, assertions, and repeatable verification procedures to demonstrate functional and timing performance. - Use FPGA vendor development tools to synthesize, place and route, analyze timing, program devices, and debug designs in laboratory hardware. - Support device and board bring-up involving FPGAs, data converters, processors, memory, clocks, radios, RF front ends, and high-speed digital interfaces. - Collaborate with DSP engineers to translate algorithms and reference models into fixed-point, pipelined, resource-aware hardware implementations. - Collaborate with embedded software engineers on register maps, control interfaces, drivers, configuration, telemetry, and embedded Linux integration. - Use simulation, on-chip debug tools, laboratory instruments, and captured data to identify root causes and validate corrective actions. - Participate in code reviews, configuration management, issue tracking, design reviews, and continuous integration practices. - Prepare clear design descriptions, interface documentation, verification results, test reports, and configuration records for product and customer-funded activities. Now Minimum Qualifications bullets: - Bachelor's degree in Electrical Engineering, Computer Engineering, Computer Science, or a closely related technical field, completed or expected before start date. - Coursework, laboratory, internship, capstone, research, or personal-project experience with FPGA development, digital logic, computer architecture, or embedded systems. - Foundational understanding of synchronous digital design, finite-state machines, registers, counters, memories, clocking, reset strategies, and timing concepts. - Academic or project experience using VHDL, Verilog, SystemVerilog, or another hardware description language. - Basic familiarity with simulation, synthesis, testbenches, and debugging digital hardware. - Ability to apply structured problem solving, learn unfamiliar devices and interfaces, communicate assumptions, and document results clearly. - Ability to collaborate in a multidisciplinary engineering environment and satisfy customer, site-access, export-control, and security requirements associated with assigned work. Now Preferred, Not Required bullets: - Hands-on experience with an AMD/Xilinx, Intel/Altera, Microchip, Lattice, or comparable FPGA development board and toolchain. - Exposure to high-speed interfaces, data converters, DDR memory, Ethernet, PCIe, JESD204, SPI, I2C, UART, AXI, or similar buses and protocols. - Familiarity with fixed-point arithmetic, digital signal processing, software-defined radio, clock-domain crossing, timing closure, or hardware-in-the-loop testing. - Experience using Python, MATLAB, Simulink, cocotb, C or C++, Linux, Git, scripting, or automated build and verification workflows. - Coursework or project experience in wireless communications, RF systems, signal processing, 5G/LTE, non-terrestrial networks, radar, satellite communications, or test and measurement. Now Benefits/compensation paragraph: "Compensation- Salary At Fairwinds, 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, location and experience. Additional incentives may be provided as part of the compensation package, in addition to a range of medical, financial, and/or other benefits." We need to keep that as is. Might want to fix the hyphen: "Compensation- Salary" maybe it's a typo; we keep as is. Now Schedule: "Position Type/Expected Hours of Work This is a full time, exempt position." We'll output asThis is a full time, exempt position.
Now ensure we don't include any extra whitespace or markdown. Let
- each bullet.
Benefits: include compensation paragraph and benefits mention. We'll make
- each bullet.
Preferred Qualifications: "Preferred, Not Required" list. We'll make