Electrical Systems Engineer- Philadelphia, PA (OCONUS Travel)

We need to output HTML fragment with sections: About the role? The description includes intro about organization, mission, etc. We need to decide sections: maybe "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We must only include sections that have real specific content. We have salary range: posted salary range USD $78,900 - $123,300 /Yr. Also later Salary Range $75,000-$100,000 (maybe duplicate). We need to include Pay section only if posting actually states them. It does, so include Pay. Schedule: travel component 20-30% etc. That's schedule/travel. So include Schedule. Benefits: not mentioned explicitly. No benefits listed. So omit Benefits. Skills: we have many desired qualifications, knowledge, proficiencies. Could be Skills section. Qualifications: Minimum Education Required, Experience Required, etc. Could be Qualifications. Responsibilities: list. About the role: we have introductory paragraph describing Noblis, mission, etc. Could be About the role. We must not repeat job title as heading. No Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. Must not omit details. Must include all content. We need to format using

for section headings,

• for any list of duties/requirements/benefits, and

  for prose. We need to decide what constitutes a list. Responsibilities are a list; we can put each as

• . Requirements/Qualifications maybe also list. We must not create sections with filler like "commensurate with experience". Not present. We need to include Pay section with salary range. Should we include both ranges? There's two: posted salary range $78,900-$123,300 and later Salary Range $75,000-$100,000. Both are substantive; we should include both? Might be contradictory but we must preserve all info. Could combine as two sentences. Schedule: travel component 20-30%; typical locations Yokosuka Japan, Rota Spain, Bahrain, Pearl Harbor; trips 2-3 weeks; emergent trips shorter. Now we need to extract all details. Let's parse the job description text: "ATTENTION MILITARY AFFILIATED JOB SEEKERS - Our organization works with partner companies to source qualified talent for their open roles. The following position is available to Veterans, Transitioning Military, National Guard and Reserve Members, Military Spouses, Wounded Warriors, and their Caregivers. If you have the required skill set, education requirements, and experience, please click the submit button and follow the next steps. Noblis is hiring an Electrical Systems Engineer to provide engineering, technical, logistics, and obsolescence support to U.S. Navy ships and vessels related to the following systems and equipment: Hull, Mechanical, and Electrical (HM&E) Propulsion Systems for U.S. Navy Surface Ships – both in-service and new construction, as well as provide equipment support. Noblis MSD’s mission is to support the Naval Sea Systems Command (NAVSEA) and, Naval Surface Warfare Center (NSWCPD) and their missions’ to enable research, development, test and evaluation, acquisition, engineering, systems integration, in-service and fleet engineering with cybersecurity, comprehensive logistics, and life-cycle savings." That's introductory. "Posted Salary RangeUSD $78,900.00 - USD $123,300.00 /Yr." "This role will be based out of Philadelphia, PA and will also have a travel component (About 20-30%; Typical locations are Yokosuka Japan, Rota Spain, Bahrain, or Pearl Harbor. Planned trips are 2-3 weeks in length, emergent trips do come up and are typically a bit shorter.)" "Responsibilities Include Provide design support for integration of equipment in an industrial/shipboard environmentProvide technical input to the design of future MCS systemsDevelop, derive, and refine system and software requirements for future fielded systemsTroubleshoot complex problems of fielded systemsReview technical documentation related to fielded and future systems Provide test support at Land Based Engineering Site (LBES)Provide shipboard SW & HW installation support to ships in the fleetDevelop test procedures to exercise requirements of fielded and future systemsDesign, develop, test, install, and maintain MCS software and supporting software productsIdentify and document software and system related problemsResolve software problems through debugging, research, and investigationWrite, review, and maintain technical documentation such as user manuals and product specification" Then "Auto req ID 484361BR Minimum Education Required High School/GED Required Experience Required Qualifications Bachelor’s level Degree in an Engineering Discipline. Computer Science, Electrical Engineering, and Computer Engineering degrees preferred, others will be considered based on experience.3+ years of professional experienceExperience with software testing and hardware troubleshootingActive DoD Secret clearance and US citizenshipMust have a valid US passport or ability to obtain one upon position acceptanceAbility to travel 20-30% of the timePhysical Requirements Employees working in naval industrial environments, whether shipboard or pierside, must meet certain physical requirements to safely perform essential job functions. Individuals must be capable of standing and walking for extended periods, often on uneven, wet, or slippery surfaces, and must be able to climb vertical ladders, stairs, and steep inclines while carrying tools or equipment. The position requires the ability to work in confined spaces with limited ventilation and restricted movement, including crawling through narrow passageways and working in overhead or below-deck areas. Workers must possess sufficient manual dexterity and grip strength to operate hand and power tools, manipulate controls, and handle materials weighing up to fifty pounds on a regular basis, with occasional lifting of heavier objects with assistance. The role demands the physical ability to bend, stoop, kneel, crouch, and reach overhead repeatedly throughout the workday. Adequate vision is necessary to read technical manuals, identify color-coded systems, and detect safety hazards, while hearing capability must be sufficient to perceive warning signals, alarms, and verbal communications in noisy environments, with or without hearing protection. Employees must be able to work in varying environmental conditions including extreme temperatures, high humidity, direct sunlight, and exposure to weather elements. The position requires the stamina to work extended shifts and the balance and coordination necessary to maintain stability on moving vessels. Workers must be capable of responding quickly to emergency situations, including evacuating confined spaces and moving to emergency stations. Reasonable accommodations may be available for qualified individuals with disabilities who can perform the essential functions of the position with or without such accommodation." "Preferred Experience Desired Qualifications Knowledge of fundamental concepts, practices, and procedures associated with industrial control systemsDemonstrated desire and ability to mentor junior personnel in systems engineering fundamentals, troubleshooting techniques, and shipboard installation/maintenance practicesAbility to provide technical recommendations on team workflows, engineering methodologies, and process efficienciesProficiency in reading electrical diagramsProficiency in the use of test tools associated with industrial control systemsProficiency in the use of diagnostic tools associated with industrial control system troubleshootingBasic knowledge of network troubleshooting toolsBasic technical writing abilitySelf-motivated and ability to complete tasks efficientlyAbility to communicate effectively within an integrated team environmentExperience upgrading hardware platforms of Legacy Embedded SystemsExperience with Versa Module Eurocard (VME) systemsKnowledge of network protocols such as TCP/IP and UDPExperience supporting and troubleshooting networked, IP-based systems" "City* Philadelphia State* Pennsylvania Job_Category Engineering Job Code Electrical_Engineer Electrical_Engineer Affiliate Sponsor Noblis Salary Range $75,000-$100,000" We need to preserve all substantive info. So we need to include: - Intro paragraph about organization, mission, military affiliated note. - Salary range (both maybe). Could combine: "Posted Salary Range: USD $78,900.00 - USD $123,300.00 /Yr. Additionally, the posting lists a Salary Range of $75,000-$100,000." - Location: Philadelphia, PA. - Travel component details. - Responsibilities list. - Minimum Education Required: High School/GED? Actually says "Minimum Education Required High School/GED Required Experience Required Qualifications Bachelor’s level Degree in an Engineering Discipline." This is confusing: It says Minimum Education Required High School/GED Required Experience Required Qualifications Bachelor’s level Degree... Probably means minimum education is High School/GED, but qualifications prefer Bachelor's. We'll capture both. - Experience Required: 3+ years professional experience, experience with software testing and hardware troubleshooting. - Active DoD Secret clearance and US citizenship. - Must have valid US passport or ability to obtain. - Ability to travel 20-30% of the time (already in schedule). - Physical Requirements: detailed list. - Preferred Experience/Desired Qualifications: list of knowledge/skills. - Job Category: Engineering. - Job Code: Electrical_Engineer (maybe duplicate). - Affiliate Sponsor: Noblis. We must not include boilerplate like EEO etc. Not present. We must not include navigation, cookie, legal, scam-warning. We must not include duplicated lines. There's duplication of "Electrical_Engineer". We'll keep once. We must not include Job ID/Auto req ID? The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include the Auto req ID in a short paragraph, maybe as metadata. It's minor; we can include in a

  at end or beginning. But we should not create a heading for it. We'll include it in a

  maybe under About the role or separate small paragraph. We need to output only HTML fragment, no /, no markdown. We'll structure:

  About the role

  Intro paragraph(s) including military affiliated note, Noblis hiring, mission, location, salary ranges, etc.

  But we also have separate sections for Responsibilities, Requirements (maybe combine Education/Experience/Clearance etc), Qualifications (maybe preferred), Skills (maybe desired qualifications), Pay, Schedule. We need to avoid thin sections. Let's decide: - About the role: includes intro, mission, location, salary ranges, maybe job code, affiliate sponsor. - Responsibilities: list. - Requirements: includes Minimum Education (HS/GED), Experience (3+ years, software testing/hardware troubleshooting), Clearance, Citizenship, Passport, Ability to travel (maybe also schedule but we have schedule separate). Could also include Physical Requirements? Might be better as its own section? But we have no specific heading for Physical Requirements; we could include under Requirements or a separate section like "Physical Requirements". The instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Requirements not listed; but we could treat it as part of Requirements or Qualifications. However we must preserve all info; we can include Physical Requirements under Requirements as a list. - Qualifications: maybe Bachelor's degree preferred etc. But we already have education in Requirements. Could combine. - Skills: includes desired qualifications list (knowledge of industrial control systems, mentoring, technical recommendations, reading electrical diagrams, test tools, diagnostic tools, network troubleshooting, technical writing, self-motivated, communication, upgrading hardware platforms, VME systems, TCP/IP/UDP, networked IP-based systems). - Pay: salary ranges. - Schedule: travel component details. We must not create Benefits section. We must not create empty sections. Now we need to ensure we don't repeat info unnecessarily but preserve all. Some info may appear in multiple places (travel appears in schedule and also in Requirements ability to travel). We'll keep both but maybe mention in schedule only and note ability to travel in Requirements as well (it's required). We'll keep. Now craft HTML. We'll need to escape any special characters? Not needed. We'll