Field Programmable Gate Array (FPGA) Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications (maybe Preferred Qualifications), Skills? Benefits? Pay? Schedule? We need to include sections only if posting has real specific content. Let's parse the posting: - Description: Command Post Technologies, Inc. is seeking an FPGA Engineer to join our team that supports the Hypersonics Projectiles Division of the Naval Surface Warfare Center Dahlgren and contribute to the development of high-performance digital systems. In this role, you will design, implement, and optimize FPGA-based solutions for complex hardware applications. You will work with VHDL, Verilog, and high-level synthesis tools, collaborating with cross-functional teams to ensure efficient and reliable hardware integration. That's about the role. - Responsibilities: list bullet points. - Requirements: bullet list. - Preferred Qualifications: bullet list. - Physical Demands: bullet list (but maybe not a standard section; we could include under Requirements? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands is not one of those; we could either drop or incorporate into Requirements? The instruction: "Prefer a few substantive sections over many thin ones." We could include Physical Demands under Requirements or maybe as a separate section not listed? But they said use headings for those specific ones; we could still add other headings if needed? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive. But later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can add other sections if they have content. However they gave a list of typical sections; we can add Physical Demands as a section if we want. But maybe better to incorporate into Requirements or Qualifications? The instruction says "Prefer a few substantive sections over many thin ones." So we could combine Physical Demands into Requirements or maybe a separate "Physical Demands" section is thin? It's a few bullet points; could be its own section but maybe thin. I'd incorporate into Requirements as part of the bullet list. - Security Clearance Requirements: Must currently hold a security clearance at the Secret level. U.S. citizenship is a requirement for Secret clearance at this location. This is a requirement; could be part of Requirements. - About us: description of company. - What’s In It For You: list of benefits. - Additional company description paragraphs (some repeated). We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like EEO etc. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to output only HTML fragment. Let's extract substantive content: About the role: first paragraph(s) before Responsibilities. Responsibilities: bullet list. Requirements: bullet list (including education, years experience, proficiency, understanding, ability). Also include security clearance and US citizenship. Preferred Qualifications: bullet list. Benefits: list from "What’s In It For You": Great health benefits (for more info, contact us directly), Leadership training, 401k with generous company matching, Employee Stock Ownership Plan (ESOP), Career professional development, Tuition reimbursement, Flexible hours, Work/Life balance, Rewards and recognition, Paid Time Off, Parental Leave. Also maybe mention "Great health benefits (for more info, contact us directly)" - that's substantive. Also "About us": description of CPT: Service-Disabled, Veteran-Owned Small Business (SDVOSB), providing engineering services in areas of Cyber Security, Software Development, Test & Evaluation, and Strategic Planning. Employees appreciate working in a caring environment that promotes a healthy work-life balance. As individuals, we come together as a team, supporting a culture rooted in our core principles of integrity, determination, and innovation. In all of CPT’s collaboration efforts, our team prioritizes communication, accountability, and resourcefulness in order to maximize efficiency and results. Also later paragraph: "Command Post Technologies, Inc. (CPT) is a Service-Disabled Veteran-Owned Small Business (SDVOSB) founded in 2008 and headquartered in Suffolk, VA with personnel in various states including Virginia, Maryland, Florida, and Texas. With 2/3 of our staff being former military, CPT firmly believes in employing veterans. Command Post Technologies, Inc. is a unique provider of innovative solutions that enhance our corporate clients’ productivity and empower our government clients with the ability to protect against all enemies: foreign and domestic. CPT adapts its successful military experiential approach to the needs of leaders in a global business environment and provides an elite leadership curriculum that results in a world-class, leadership-altering event." That's also substantive about us; we can combine. We need to avoid duplication: there is some repetition; we should keep unique content. We need to output HTML with

headings and

• for lists,

  for prose. We should not repeat the job title as a heading. We should not include Job ID/requisition numbers. We should not include boilerplate EEO etc. We need to preserve all substantive information; do not invent or summarize away detail. Let's structure:

  About the role

  Command Post Technologies, Inc. is seeking an FPGA Engineer to join our team that supports the Hypersonics Projectiles Division of the Naval Surface Warfare Center Dahlgren and contribute to the development of high-performance digital systems. In this role, you will design, implement, and optimize FPGA-based solutions for complex hardware applications. You will work with VHDL, Verilog, and high-level synthesis tools, collaborating with cross-functional teams to ensure efficient and reliable hardware integration.

  Responsibilities

  • Design and develop FPGA-based architectures for real-time and high-speed applications.
  • Implement and optimize VHDL/Verilog code for FPGA designs.
  • Conduct simulation, synthesis, and timing analysis to ensure performance optimization.
  • Perform debugging and validation of FPGA designs using industry-standard tools and methodologies.
  • Collaborate with hardware, software, and systems engineering teams to develop integrated solutions.
  • Develop and maintain FPGA testbenches for functional verification.
  • Contribute to system integration, testing, and troubleshooting of FPGA-based hardware.
  • Document design specifications, implementation details, and test results.
  • Other duties as assigned.

  Requirements

  • Bachelor's or Master’s degree in Electrical Engineering, Computer Engineering, or related field.
  • 3-7 years of experience in FPGA design and development.
  • Proficiency in HDL programming (VHDL, Verilog) and FPGA development tools (Vivado, Quartus, etc.).
  • Strong understanding of digital logic design, high-speed interfaces, and embedded systems.
  • Experience with hardware/software co-design and debugging tools (Oscilloscope, JTAG, Signal Analyzer).
  • Ability to work in a fast-paced environment and manage multiple projects effectively.
  • Must currently hold a security clearance at the Secret level.
  • U.S. citizenship is a requirement for Secret clearance at this location.

  Preferred Qualifications

  • Experience with Xilinx, Altera (Intel FPGA), or Lattice FPGA architectures.
  • Knowledge of C/C++, Python for FPGA development.
  • Understanding of high-performance computing, signal processing, and networking applications.
  • Familiarity with System Verilog, UVM methodology, or high-level synthesis (HLS).

  About the company

  Command Post Technologies, Inc. (CPT) is a Service-Disabled, Veteran-Owned Small Business (SDVOSB), providing engineering services in the areas of Cyber Security, Software Development, Test & Evaluation, and Strategic Planning. CPT employees appreciate working in a caring environment that promotes a healthy work-life balance. As individuals, we come together as a team, supporting a culture rooted in our core principles of integrity, determination, and innovation. In all of CPT’s collaboration efforts, our team prioritizes communication, accountability, and resourcefulness in order to maximize efficiency and results.

  Founded in 2008 and headquartered in Suffolk, VA, CPT has personnel in Virginia, Maryland, Florida, and Texas. Two‑thirds of the staff are former military, and the company firmly believes in employing veterans. CPT provides innovative solutions that enhance corporate clients’ productivity and empower government clients to protect against foreign and domestic threats. The company adapts its military experiential approach to global business leadership needs and offers an elite leadership curriculum that delivers a world‑class, leadership‑altering event.

  Benefits

  • Great health benefits (for more info, contact us directly)
  • Leadership training
  • 401k with generous company matching
  • Employee Stock Ownership Plan (ESOP)
  • Career professional development
  • Tuition reimbursement
  • Flexible hours
  • Work/Life balance
  • Rewards and recognition
  • Paid Time Off
  • Parental Leave
  We should not include Pay or Schedule sections as not present. Check for any duplicated content: we have about the role and about the company; we kept unique. We removed Physical Demands and Security Clearance from separate sections; we integrated security clearance into Requirements. Physical Demands we omitted; but is that substantive? It's a few bullet points about lifting, standing, etc. Should we include? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must include Physical Demands somewhere. We could add a section "Physical Demands". It's substantive. Let's add a section. We could add

  Physical Demands

  with ul list. We must not create thin sections; but it's a few bullets, still substantive. We'll include. Thus add:

  Physical Demands

  • Must be able to lift up to 50 pounds
  • Must be able to stand and walk for prolonged amounts of time
  • Must be able to twist, bend and squat periodically
  We should also consider that we already have Requirements; maybe we could add Physical Demands under Requirements as another bullet. But the instruction says prefer few substantive sections over many thin ones. Adding a separate Physical Demands section adds another heading; but we could incorporate into Requirements to keep sections fewer. However we must preserve all detail; incorporating into Requirements is fine as long as we keep the bullets. Let's do that: add three bullets to Requirements list. Thus Requirements will have the existing bullets plus those three. Let's update Requirements list accordingly. Now we have sections: About the role, Responsibilities, Requirements, Preferred Qualifications, About the company, Benefits. We should ensure we didn't miss any substantive content: The description about "high-level synthesis tools" is in About the role. Good. The "Other duties as assigned." is in Responsibilities. The "About us" includes the earlier paragraph about caring environment etc. We used that. The later paragraph about founded 2008 etc we used. We removed duplicated lines: The "About us" appears twice; we combined. We removed EEO boilerplate. We removed "What’s In It For You" heading but we turned into Benefits section. We removed "Command Post Technologies, Inc. (C