Subject Matter Expert IV - Multi-Element Integration & Test (MEIT)

We need to output HTML fragment with sections: About Us? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "About Us" (company description) but not "About the role". We should include sections only when there is real specific content. The posting includes "Job Overview" which could be considered About the role. Also "Responsibilities" present. "Job Requirements" includes mandatory and preferred. Could map to Requirements and Qualifications. "Skills" maybe not explicit but could be derived from responsibilities? Better not to invent. We have Salary range => Pay section. Travel % is mentioned but not schedule. No explicit Benefits section (though About Us mentions competitive compensation and benefits package but not specific). We should not create Benefits unless specific. So we can include Pay section with salary range. Also maybe include Location? Not a heading per rules; we can fold minor metadata into short p. The location is given: Moorestown, NJ with 25% travel. Could be in a p. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, disclosures, privacy policy, etc. We need to preserve all substantive information: About Us description, Job Overview, Responsibilities (list), Requirements (mandatory and preferred), Working Conditions (maybe as part of Requirements?), Physical Requirements (maybe as part of Requirements). Also mention travel. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide sections: About the role (maybe Job Overview), Responsibilities, Requirements (maybe combine mandatory and preferred), Qualifications (maybe education/clearance?), Skills (maybe not), Pay, Schedule (none). We'll include About the role, Responsibilities, Requirements, Pay. We must not create sections with filler like "not specified". So only include sections with content. Let's extract content: About Us: description of CGS. That's company info, not role. Could be placed in a

  maybe under a heading? Not required. Could be just a

  before sections. Job Overview: paragraph about SME 4 – Multi-Element Integration & Test (MEIT) supporting etc. Responsibilities: list of duties (many bullet-like sentences). We need to turn into

  • . The responsibilities section includes many sentences; we can split each bullet. Requirements: Mandatory list and Preferred list. We'll make two
    maybe under Requirements heading. Qualifications: maybe we can include education/clearance as part of Requirements; but we could also have a Qualifications heading for things like U.S. Citizen, Active DoD Secret clearance, High school diploma with Military experience, etc. However the instructions say use headings for sections like Qualifications. We have content for qualifications (mandatory and preferred). Could put them under Requirements and Qualifications both? Might be redundant. Better to have Requirements for mandatory, Qualifications for preferred? But both are requirements. The instruction: "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections if we have distinct content. We could put mandatory under Requirements, preferred under Qualifications. That seems reasonable. Skills: maybe we can extract skills from responsibilities (e.g., ability to read drawings, troubleshoot, etc.) but that would be inventing? Might be considered summarizing. Better to omit Skills if not explicit. Pay: Salary range. Schedule: not specified (travel % but not schedule). So omit. Now produce HTML. We need to include location and travel info maybe in a

    after About the role. Let's craft:

    About Us: When you work at Chugach Government Solutions (CGS), you join a proud legacy ...

    Then

    About the role

    with Job Overview paragraph. Then

    Responsibilities

    with
    • each duty. Then

      Requirements

      with mandatory list. Then

      Qualifications

      with preferred list. Then

      Pay

      with salary range. We must not include boilerplate like EEO, disclosures, privacy policy. Check for any duplicated lines: we need to preserve all substantive info; we must not omit any duty etc. Let's list responsibilities sentences from the posting: From "Responsibilities Essential Job Duties:" then a long paragraph with many sentences separated by periods. We need to split each sentence into a bullet. Let's extract: - Serves as a Subject Matter Expert on US Navy and USCG Command and Control (C2) systems, providing expert-level engineering guidance to government, engineering, and operational stakeholders. - Provide engineering support for Navy and USCG Combat System elements and their interfaces, including but not limited to: IFF, SPQ-9B, SPS-75, SPS-77, NAVSSI, MK-48, C2PS, SLQ-32 and AIS. - Strong understanding of combat system interfaces and how sensor data is passed between external sensors and combat-system equipment. - Experience performing system integration, interface verification, testing, and troubleshooting of radar, electronic warfare, navigation, and weapon-system interfaces - Reviews system designs to identify gaps, risks, or shortfalls - Ability to troubleshoot sensor track data, interface communications, equipment status, and data-flow problems between interconnected systems. - Experience supporting AN/SPQ-9B radar integration, including air and surface tracking interfaces and connections to associated combat/weapon systems. - Familiarity with SEWIP electronic warfare systems, including electronic-support data and combat-system interfaces. - Knowledge of AIS data, including vessel identification, position, course, speed, and integration of AIS information into shipboard displays or combat systems. - Ability to analyze system faults, interface failures, alarms, and degraded sensor performance and determine the source of the problem. - Experience performing installation checkout, operational testing, system verification, and post-installation troubleshooting. - Ability to read and understand system drawings, interface diagrams, wiring diagrams, technical manuals, and interface-control documentation. - Experience working with shipboard networks, serial interfaces, Ethernet-based interfaces, and tactical data paths used to exchange sensor information. - Ability to work directly with engineers, technicians, ship’s force, government representatives, and equipment vendors during integration and testing - Experience supporting shipboard modernization efforts, system upgrades, and integration testing. - Demonstrated ability to lead multidisciplinary teams, mentor junior engineers, and drive technical decisions. - Technical Documentation Creation and Review Ability to document test results, discrepancies, troubleshooting actions, and corrective actions. - Comfortable working independently in lab, pier-side, and shipyard environments. - Maintains laboratory and deployed asset software configurations, ensuring alignment with approved baselines. - Works in collaboration with government, engineering, and operational stakeholders to design, integrate, test, and sustain USCG Command and Control (C2) and C4ISR systems. - Provides technical engineering support across the system lifecycle, including software development, integration, and testing of prototype and fielded systems. - Provide engineering support for installation, configuration, and integration efforts aboard USCG assets and sites. - Communicate complex concepts, lead reviews, and negotiate requirements. - Create and/or review schematics, block diagrams, and wiring diagrams - Key Responsibilities Providing accurate, timely, and authoritative technical guidance on USCG and Navy C2 systems. - Extensive knowledge of C4ISR systems, including integration, sustainment, and support. - Knowledge of test and evaluation processes. - Detailed understanding of Navy and USCG Combat System elements and their interfaces to include but not limited to; IFF, SPQ-9B, SPS-75, NAVSSI, MK-48 and C2PS - Ability to collaborate well in team environments and work independently. - Ability to meet mission and operational requirements by supporting installations, configurations, and testing aboard USCG assets and facilities. - Ability to prioritize multiple engineering tasks while maintaining a strong sense of urgency and attention to detail especially while on travel. - Maintaining high technical standards in documentation, system configuration, and engineering review activities. - Strong organizational and task-management skills, with the ability to manage competing priorities in a dynamic operational environment. - Excellent oral and written communication skills, with the ability to provide clear technical feedback to internal and external stakeholders. We need to ensure no duplication; some sentences may be similar but we keep as is. Now Requirements mandatory list: - U.S. Citizen. - Active DoD Secret security clearance. - High school diploma with Military experience. - Minimum of Seven (7) years of experience with military electronics systems. - Willingness to travel up to 25% CONUS/OCONUS. - Valid driver’s license and reliable transportation. - Ability to successfully pass a pre-employment background check and drug test. Preferred list: - BS in Computer Sciences or Engineering Field - Prior experience supporting USCG or Navy C2 or C4ISR systems. - Demonstrated experience with the Sea Commander System. - Experience supporting system integration or operational test events. - Experience developing or reviewing engineering documentation and Technical Drawings. - Confident in operating system configuration, patching, and tuning. Working Conditions and Physical Requirements: Could be included under Requirements? Might be considered part of Requirements. But we already have Requirements and Qualifications sections; we could add another section "Working Conditions" but not in allowed headings list? The allowed headings list includes those examples but not limited to; we could add but better to stick to allowed. Physical Requirements could be part of Requirements. However we might omit to avoid thin sections. But we must preserve all substantive information; we could include them as a

      under Requirements or as a separate section "Working Conditions" but not in list; risk of being considered not allowed? 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 but not exclusive? It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not add other headings. We can fold Working Conditions and Physical Requirements into a

      under Requirements or maybe under Qualifications. Let's add a paragraph after the lists. Now Pay: Salary range: $110,000.00/Yr - $145,000.00/Yr. Now About Us paragraph: we need to keep all substantive info. That includes the whole About Us block. Let's copy About Us text: "When you work at Chugach Government Solutions (CGS), you join a proud legacy of supporting missions while sustaining culture. The federal division of Chugach Alaska Corporation, CGS has been supporting critical missions as a government contractor for over 25 years. Our focus is to support facility maintenance, IT/technical services, construction and education. We are proud to have built, and continue to foster, an incredibly talented team spanning across the globe in hundreds of different fields – each team member proud to serve our country with first-class business services, while also making a difference for our Chugach shareholders. At CGS, empowering employees is a part of our core, and that focus is one of the ways we build and foster high-performing teams. We empower our employees through competitive compensation and benefits package, professional growth opportunities, truthful communication, and more! If you are looking for an opportunity to serve something bigger than yourself; if you want your day job to be one that creates meaningful value; if you are looking for an environment that highly values employees and respects individual differences – then Chugach Government Solutions may be the right fit for you!" We'll put that in a

      . Now Job Overview paragraph: "The Subject Matter Expert (SME) 4 – Multi-Element Integration & Test (MEIT) will support the Chugach Technical Program Manager and the U.S