Principal Electrical Engineer

We need to output HTML fragment with sections using

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No placeholder like "commensurate with experience". Must preserve all substantive info, remove boilerplate, duplicated lines, application instructions, EEO, etc. We need to parse the posting. Key sections: - About the role: description of role, tasks, environment. Could be first paragraph: "i3 is seeking a Principal Electrical Engineer to support circuit board development and broader military system modernization efforts. The role will involve the research, design, development, integration, and testing of circuit boards and other electrical components, equipment, systems, and networks. Work will span software, firmware, digital, analog, mixed-signal, power, FPGA, and embedded applications, with a primary emphasis on circuit board design and system-level integration. This position provides the opportunity to contribute to a variety of technically challenging projects while working closely with engineers, project managers, technicians, fabrication partners, and external customers. Execute in a fast-paced, small-team environment throughout the product life cycle, from conceptual development and detailed design through fabrication, testing, delivery, and post-delivery support." That's about the role. - Responsibilities: list of duties: "Analyze and document existing circuit boards, electrical systems, and firmware, including their functions, components, power requirements, communication paths, and system interfaces. Develop system architecture and functional block diagrams from existing hardware and firmware designs, and use point-to-point or commercial off-the-shelf configurations to validate requirements when appropriate. Develop robust software, firmware, and hardware solutions, including circuit and PCB/PCBA design and analysis, component selection, analog and digital interface design, FPGA logic, and embedded processor or microcontroller designs. Develop replacement board architectures, schematics, PCB layouts, bills of materials, fabrication and assembly files, and supporting technical documentation. Conduct technical trade studies, evaluate technology improvements, and apply working knowledge of digital signal processing and communication protocols to system and interface design. Coordinate with fabrication and assembly vendors and support board bring-up, bench testing, aircraft and system integration, troubleshooting, flight-test or live-fire activities, root-cause analysis, corrective actions, and design revisions through final release. Partner with multidisciplinary teams and customers to develop solutions that meet technical, operational, cost, and schedule requirements. Perform other duties as assigned." We can put these as

• . - Requirements: Education/Experience: "Required Education/Experience Bachelor's degree in Computer Engineering, Computer Science, or Electrical Engineering from an ABET-accredited institution. Additional experience may substitute for degree. 12-17 years of relevant technical experience Experience developing robust software, firmware and hardware solutions Experience performing circuit and PCB/PCBA design and analysis, FPGA designs, embedded processor/microcontroller designs. Ability to generate architectural design block diagrams from existing firmware designs. General knowledge of DSP coding and communication protocols. Experience with checkout, debug and troubleshooting of electronic printed circuit board assemblies comprising embedded hardware and firmware. Hands-on laboratory experience with instrumentation, test equipment, and debug/test methods for both software and hardware. Proficient in programming C/C++ low level algorithms Motivated self-starter and problem solver with experience executing in multi-disciplinary teams Strong written and verbal communication skills Must be able to obtain and maintain a Secret clearance U.S. citizenship required" We can list as bullet points. - Preferred Experience: "Preferred Experience Ability to design, analyze, or interpret RF signal chains and/or six-degree-of-freedom computational paths across digital, analog, and embedded system architectures. Master's degree in Computer or Electrical Engineering from an ABET-accredited institution. Familiarity with electronic safe and arm components and design for munitions. Proficiency using Altium Designer software is a plus. Interfacing to sensors and high speed mixed-signal components. Active secret clearance." We could treat as part of Requirements or separate section? The instruction says use headings for sections like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Preferred Experience could be under Requirements or Qualifications. Probably we can put under Requirements (or Qualifications). Since they have separate "Preferred Experience", we could include under Requirements as a subsection? But we must not invent headings not listed. We could include under Requirements and list both required and preferred. Or we could create a "Qualifications" section for required and preferred. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which to include. We have content for About the role, Responsibilities, Requirements (including required and preferred), Skills (knowledge/skills), Benefits (perks). Pay and Schedule: we have schedule info: "Regular i3 hours are 800 a.m. - 500 p.m. Monday-Friday, however, additional hours may be required on occasion. Regular and punctual attendance is required." That's schedule. Pay: not mentioned. So we should not create Pay section because no specific pay info. Benefits: we have perks: "Perks of being a team member owner include Long-term financial security Higher job satisfaction Greater job security Personal and professional growth Great company culture Other outstanding benefits Excellent insurance coverage 401(k) match Generous PTO Health and wellness incentives Tuition and certification reimbursement Countless opportunities to give back to the community through i3 Cares We work hard. We compete hard. We play hard." That's benefits. Skills: "Knowledge/Skills Knowledge of office administration and procedures. Exceptional judgment capabilities and relationship management skills. Excellent communication, teamwork, and client service skills; ability to clearly communicate in discussions and written documents, and to deliver feedback clearly and tactfully. Interact with a diverse array of customers and staff in a professional and courteous manner. Work independently with accountability for accurate and complete results. Be extremely organized and exceptionally detail oriented. Work well both independently and in a team environment. Be energized by a fast-paced work environment. Must be able to communicate with others effectively. Analyze information and respond appropriately. Manage time wisely and prioritize tasks. Provide superior customer service. Multi-task in a pleasant manner. Work well under pressure." Also earlier: "Motivated self-starter and problem solver with experience executing in multi-disciplinary teams Strong written and verbal communication skills". Those could be part of Skills. Physical Demands: we could maybe include under Skills? But it's not listed as a heading; we could omit because not in allowed headings. However we need to preserve ALL substantive information; we cannot drop it unless we incorporate into another section. The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to include physical demands somewhere. Could we put under Skills? It's not exactly skills but we could include as a subsection under Skills? But we must not create new headings; we can embed within a

  under Skills heading. That's acceptable: we keep the info. Similarly, "Regular i3 hours are 800 a.m. - 500 p.m. Monday-Friday, however, additional hours may be required on occasion. Regular and punctual attendance is required." That's schedule; we can put under Schedule heading. We must not include boilerplate like EEO, legal, etc. There's none obvious besides maybe "U.S. citizenship required" and "Must be able to obtain and maintain a Secret clearance". Those are substantive. We must not repeat job title as heading. Already not. We must not put Job ID/requisition numbers as headings; none present. We must output only HTML fragment. Let's structure:

  About the role

  ... (the paragraph)

  Responsibilities

  • ...
  ...

  Requirements

  • Bachelor's degree in Computer Engineering, Computer Science, or Electrical Engineering from an ABET-accredited institution (additional experience may substitute for degree).
  • 12-17 years of relevant technical experience.
  • Experience developing robust software, firmware and hardware solutions.
  • Experience performing circuit and PCB/PCBA design and analysis, FPGA designs, embedded processor/microcontroller designs.
  • Ability to generate architectural design block diagrams from existing firmware designs.
  • General knowledge of DSP coding and communication protocols.
  • Experience with checkout, debug and troubleshooting of electronic printed circuit board assemblies comprising embedded hardware and firmware.
  • Hands-on laboratory experience with instrumentation, test equipment, and debug/test methods for both software and hardware.
  • Proficient in programming C/C++ low level algorithms.
  • Motivated self-starter and problem solver with experience executing in multi-disciplinary teams.
  • Strong written and verbal communication skills.
  • Must be able to obtain and maintain a Secret clearance.
  • U.S. citizenship required.
  Maybe also include Preferred Experience as part of Requirements? Could add a note: "Preferred:" but that might be considered adding text not in original? It's okay to summarize? The instruction says do not invent or summarize away detail. Adding "Preferred:" is not inventing detail, just labeling. Might be okay. But we could also create a separate

  Qualifications

  for preferred? However Qualifications heading is allowed. We could put required under Requirements and preferred under Qualifications. That seems logical: Requirements = mandatory; Qualifications = preferred. Let's do that. Thus:

  Requirements

  (mandatory)

  Qualifications

  (preferred) Then Skills. Then Benefits. Then Schedule. We must not create Pay section. Now compile content. Mandatory requirements list as above. Preferred qualifications list: - Ability to design, analyze, or interpret RF signal chains and/or six-degree-of-freedom computational paths across digital, analog, and embedded system architectures. - Master's degree in Computer or Electrical Engineering from an ABET-accredited institution. - Familiarity with electronic safe and arm components and design for munitions. - Proficiency using Altium Designer software is a plus. - Interfacing to sensors and high speed mixed-signal components. - Active secret clearance. Note: "Active secret clearance" is also a requirement? It says "Must be able to obtain and maintain a Secret clearance" under required; also "Active secret clearance." under preferred. We'll include both. Now Skills: combine knowledge/skills and other skill-like statements. List: - Knowledge of office administration and procedures. - Exceptional judgment capabilities and relationship management skills. - Excellent communication, teamwork, and client service skills; ability to clearly communicate in discussions and written documents, and to deliver feedback clearly and tactfully. - Interact with a diverse array of customers and staff in a professional and courteous manner. - Work independently with accountability for accurate and complete results. - Be extremely organized and exceptionally detail oriented. - Work well both independently and in a team environment. - Be energized by a fast-paced work environment. - Must be able to communicate with others effectively. - Analyze information and respond appropriately. - Manage time wisely and prioritize tasks. - Provide superior customer service. - Multi-task in a pleasant manner. - Work well under pressure. - Motivated self-starter and problem solver with experience executing in multi-disciplinary teams. - Strong written and verbal communication skills. We might have duplicates; but okay. Physical demands: we need to include. Could add a

  under Skills or maybe under a separate heading? Not allowed. We'll add a

  under Skills after the list, or incorporate as a list item? Better to add a

  under Skills: "Physical demands: regularly required to talk or hear; frequently required to stand, walk, handle or feel, reach with hands and arms; occasionally required to sit, climb or balance, stoop, kneel, crouch or crawl; must be able to lift and/or move up to 10 pounds and occasionally up to 25 pounds; specific vision abilities required include close vision, distance vision, peripheral vision, depth perception and ability to adjust focus." Now Benefits: list perks. - Long-term financial security -