Electrical Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Expertise And Functions (list of duties). That's responsibilities. Also "Other duties as assigned". So we can put Responsibilities section with bullet list. Requirements: Education/Training, Experience, Security, Physical Requirements. Those are requirements. Could be split into Requirements and Qualifications? The instruction says use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Likely: Requirements = Education/Training, Experience, Security, Physical Requirements. Qualifications maybe not separate; but we could put Qualifications as maybe none. Skills: maybe Python/C++, Zuken, SolidWorks, etc. Benefits: listed. Pay: salary range. Schedule: not mentioned, so omit. We must not include boilerplate like cookie/navigation/legal/EEO etc. There's none. We must preserve all substantive info. So we need to capture each bullet. Let's parse the posting: Expertise And Functions (list): - Support design, implementation and/or test of complex electrical/electronic equipment and systems - Interpret and implement specific design and test requirements - Analyze and support update of technical documentation for legacy aircraft systems - Perform technical analysis for subsystem components and/or software, component validation/verification, risk analyses and assessments of component supportability and design effectiveness in the context of subsystem or other derived requirements - Apply focused or specialized knowledge to resolve design issues that have an impact to subsystem or task area - Create wire diagrams, drawings and schematics to support reverse engineering projects and technical data updates; familiarity with Zuken and SolidWorks preferred - Ensure the logical and systematic derivation of component and associated interface requirements into design solutions - Lead technical reviews and meetings, both internal and external - Work through Program Managers and IPT leaders to achieve optimum program/functional cost/technical/schedule execution - Demonstrate good communication, time management skills and a willingness to learn and grow through experience - Comply with OSHA and ESD safety protocols - Maintain high ethical/professional standards of quality, performance, demeanor, and judgment always - Must be willing to collaborate, and interact professionally with supervisors and co-workers - Identify and execute required steps to bring projects to successful closure - Other duties as assigned Requirements: Education/Training: Bachelor’s Degree in a related field required; Master’s Degree in a related field preferred; Additional direct experience required without degree Experience: 5+ years of professional experience in a related field required; Background in developing, manufacturing and/or testing aircraft and/or military components preferred; Experience and proficiency with Python and/or C++ required Security: Must be a US citizen; Ability to obtain a security clearance may be required Physical Requirements: Able to occasionally reach with hands and arms; Prolonged periods of computer screen use, while sitting or standing at a desk; Adhere to safety protocols when in work areas requiring use of PPE (e.g. eyewear, gloves, masks, hearing protection, steel toed shoes, etc.); Able to safely lift and carry up to 20 pounds at a time Benefits: Health Care Plan (Medical, Dental & Vision) Retirement Plan (401k, IRA) Life Insurance (Basic, Voluntary & AD&D) Paid Time Off (Vacation, Sick & Public Holidays) Short Term & Long Term Disability Training & Development Wellness Resources Salary: The projected salary range for this position is $85,000 - $105,000. This is not a guarantee of compensation, rather actual salary will be based on experience, qualifications, and applicable certifications or degrees held. Offered salary may fall outside of this range. Schedule: none. We need to decide sections: About the role? Could be a brief paragraph summarizing role. The posting didn't have an explicit "About the role" paragraph, but we could create a short paragraph from the first line? However instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". We don't have a dedicated "About the role" paragraph; but we could treat the first bullet list as responsibilities, not about role. Could we create an About the role section using a summary of the role? That would be inventing content, not allowed. So we should omit About the role if no explicit content. Thus sections: Responsibilities, Requirements, Qualifications? We have no separate qualifications beyond requirements; but we could treat Requirements as covering education/experience/security/physical. Qualifications maybe we could put skills? But better to follow typical: Requirements = education/experience; Qualifications = preferred qualifications; Skills = technical skills. However we have both required and preferred items. We could split: Requirements: Education/Training, Experience, Security, Physical Requirements. Qualifications: Preferred qualifications (Master's degree, background in aircraft/military, etc.)? But the instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using Qualifications for preferred qualifications. We need to preserve all substantive info; we can allocate accordingly. Let's decide: - Responsibilities: bullet list of Expertise And Functions (including other duties as assigned). - Requirements: bullet list of mandatory items: Bachelor’s Degree required, 5+ years experience, US citizen, ability to obtain security clearance may be required (maybe treat as requirement?), OSHA/ESD compliance, ethical standards, collaboration, etc. But many of those are in responsibilities. Might be messy. Simplify: Use Requirements for Education/Training, Experience, Security, Physical Requirements. Use Skills for technical skills: Python/C++, Zuken, SolidWorks, wire diagrams, etc. Use Benefits as given. Use Pay as salary range. Omit Schedule. We must not invent sections like Qualifications if we don't have content. But we could put Qualifications for preferred qualifications: Master’s degree preferred, background in developing/manufacturing/testing aircraft/military components preferred. That is substantive. So we can have Qualifications section. Thus sections: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Now craft HTML. We need

for each section heading. Then

• for lists. Use

  for prose if any. We'll output only HTML fragment. Let's draft:

  Responsibilities

  • Support design, implementation and/or test of complex electrical/electronic equipment and systems
  • Interpret and implement specific design and test requirements
  • Analyze and support update of technical documentation for legacy aircraft systems
  • Perform technical analysis for subsystem components and/or software, component validation/verification, risk analyses and assessments of component supportability and design effectiveness in the context of subsystem or other derived requirements
  • Apply focused or specialized knowledge to resolve design issues that have an impact to subsystem or task area
  • Create wire diagrams, drawings and schematics to support reverse engineering projects and technical data updates; familiarity with Zuken and SolidWorks preferred
  • Ensure the logical and systematic derivation of component and associated interface requirements into design solutions
  • Lead technical reviews and meetings, both internal and external
  • Work through Program Managers and IPT leaders to achieve optimum program/functional cost/technical/schedule execution
  • Demonstrate good communication, time management skills and a willingness to learn and grow through experience
  • Comply with OSHA and ESD safety protocols
  • Maintain high ethical/professional standards of quality, performance, demeanor, and judgment always
  • Must be willing to collaborate, and interact professionally with supervisors and co-workers
  • Identify and execute required steps to bring projects to successful closure
  • Other duties as assigned

  Requirements

  • Bachelor’s Degree in a related field required
  • Master’s Degree in a related field preferred
  • Additional direct experience required without degree
  • 5+ years of professional experience in a related field required
  • Must be a US citizen
  • Ability to obtain a security clearance may be required
  • Able to occasionally reach with hands and arms
  • Prolonged periods of computer screen use, while sitting or standing at a desk
  • Adhere to safety protocols when in work areas requiring use of PPE (e.g. eyewear, gloves, masks, hearing protection, steel toed shoes, etc.)
  • Able to safely lift and carry up to 20 pounds at a time
  But note we duplicated Master's degree preferred; maybe move to Qualifications. Let's adjust: Requirements only mandatory: Bachelor's degree required, 5+ years experience, US citizen, ability to obtain security clearance may be required, physical requirements. We'll keep Master's degree preferred in Qualifications. Thus: Requirements: - Bachelor’s Degree in a related field required - Additional direct experience required without degree - 5+ years of professional experience in a related field required - Must be a US citizen - Ability to obtain a security clearance may be required - Able to occasionally reach with hands and arms - Prolonged periods of computer screen use, while sitting or standing at a desk - Adhere to safety protocols when in work areas requiring use of PPE (e.g. eyewear, gloves, masks, hearing protection, steel toed shoes, etc.) - Able to safely lift and carry up to 20 pounds at a time Qualifications: - Master’s Degree in a related field preferred - Background in developing, manufacturing and/or testing aircraft and/or military components preferred Skills: - Experience and proficiency with Python and/or C++ required - Familiarity with Zuken and SolidWorks preferred - Ability to create wire diagrams, drawings and schematics - Technical analysis for subsystem components and/or software, component validation/verification, risk analyses and assessments - Apply focused or specialized knowledge to resolve design issues - Ensure logical and systematic derivation of component and associated interface requirements into design solutions - Lead technical reviews and meetings - Work through Program Managers and IPT leaders to achieve optimum program/functional cost/technical/schedule execution - Demonstrate good communication, time management skills and a willingness to learn and grow through experience - Comply with OSHA and ESD safety protocols - Maintain high ethical/professional standards of quality, performance, demeanor, and judgment - Must be willing to collaborate, and interact professionally with supervisors and co-workers - Identify and execute required steps to bring projects to successful closure But many of these overlap with responsibilities. However we need to preserve all substantive info; we can keep them in Skills but might duplicate. Better to keep Skills limited to technical/proficiency items: Python/C++, Zuken, SolidWorks, wire diagrams, etc. The rest are responsibilities. Thus Skills: - Experience and proficiency with Python and/or C++ required - Familiarity with Zuken and SolidWorks preferred - Ability to create wire diagrams, drawings and schematics But we also have "Create wire diagrams, drawings and schematics to support reverse engineering projects and technical data updates; familiarity with Zuken and SolidWorks preferred" already in responsibilities. So we could keep that in responsibilities and not duplicate in Skills. However we need to capture the skill of Python/C++ which is not in responsibilities. So Skills section will contain Python/C++ and maybe Zuken/SolidWorks (though already mentioned). It's okay to have some overlap but we should avoid duplication? The instruction didn't forbid duplication, but we should preserve all info; duplication is okay but maybe better to avoid. We'll keep Skills: Python/C++ required; Zuken and SolidWorks preferred. Now Benefits section as given. Pay section: salary range. Now produce HTML. Check for any placeholder text like "commensurate with experience" etc. Not present. Make sure not to include any