Tactical UI/UX and Operator Decision Support Lead

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to parse the job posting. The posting includes: - Intro: "Opportunity PeopleTec is currently seeking a Tactical UI/UX and Operator Decision Support Lead to support our Huntsville, AL location. The candidate will serve as a Tactical UI/UX and Operator Decision Support Lead within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Product Manager. The candidate will design low-cognitive-load C2 map interfaces and decision-support tools for high-stress tactical operators across the system lifecycle (design, development, acquisition, integration, testing, fielding, and sustainment). The candidate will prepare and present UI/UX findings, reports, and improvement plans to senior management and stakeholders. Will work within and/or lead a multidisciplinary team to achieve program goals. Perform other tasks as assigned by the Chief Engineer and/or Product Manager. The candidate will be required to interface with internal PMs across PAE Fires and external organizations to include HQDA, ASA(ALT), JIATF 401, ATEC, AMCOM, and others for coordination and synchronization of UI/UX technical and programmatic objectives." Then "Duties" list: bullet points. Then "Qualifications" with "Required Skills/Experience:" list. Then "Travel: 25%" and "Must be a U.S. Citizen" and "An active DoD Secret clearance is required..." etc. Then "Education Requirements Bachelor's degree in Engineering (or related technical discipline); advanced degree preferred." Then "Desired Skills Top Secret clearance preferred" Then "Overview People First..." etc. That's company overview, not needed? It's not a section heading we need to include unless we have content for About the role? Actually "About the role" could be the introductory paragraph describing role. We can put that under

About the role

with

. Responsibilities: The duties list. Requirements: Could combine qualifications? But we have separate sections: Requirements and Qualifications. The posting has "Qualifications" with required skills/experience, education, etc. Could treat that as Qualifications. Requirements maybe not separate; but we could put "Requirements" for required skills/experience and "Qualifications" for education? However instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). So we need to decide which sections have content. We have: - About the role: intro paragraph. - Responsibilities: duties list. - Requirements: maybe the required skills/experience (10+ years, etc.)? Or could be "Required Skills/Experience". We'll put under Requirements. - Qualifications: education requirements and desired skills? Actually they have "Education Requirements" and "Desired Skills". Could be Qualifications. - Skills: maybe list of specific technical skills (React, TypeScript, WebGL/CesiumJS, OpenLayers, Human Factors Engineering). Could be under Skills. - Benefits: Not mentioned explicitly; there is "People First" benefits package in overview but not specific. Should not create Benefits unless posting actually states them. It mentions "People First" benefits package but not details. That's vague; better not to create Benefits. - Pay: Not mentioned. - Schedule: Not mentioned (maybe travel 25% but that's not schedule). So omit. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. We need to preserve all substantive information, not invent or summarize away detail. Use

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

  for prose. We must not repeat job title as heading. Do not put Job ID/requisition numbers as headings (none present). Remove boilerplate: EEO statement, navigation, etc. Also remove "Overview People First..." etc? That's company overview; not required but could be considered boilerplate? It's not EEO/legal but it's generic marketing. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The overview is not explicitly listed but could be considered boilerplate? It's not required to keep; but it's substantive about company culture. Might be considered not required; but we can keep if we want but not required. Safer to omit as it's not directly about the role. The instruction says preserve ALL substantive information; but overview is substantive about company but not about the role. However it's not boilerplate like EEO. It's still part of posting. But we can decide to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Overview is not those. So we could keep it under maybe a section "About the company"? But we don't have a heading for that. We could incorporate into About the role? Might be stray. Safer to omit because not requested headings. The instruction says "include a section ONLY when the posting has real, specific content for it". The overview is specific content but we don't have a heading for it; we could create a heading like "About the company" but not in allowed list. So better to omit. Thus we will output:

  About the role

  ... intro paragraph ...

  Responsibilities

  • ... each duty ...

  Requirements

  • ... required skills/experience ...

  Qualifications

  • ... education requirements ...
  • ... desired skills ...

  Skills

  • ... specific technical skills ...
  We need to ensure we preserve all substantive information from the posting. Let's extract details. Intro paragraph: "Opportunity PeopleTec is currently seeking a Tactical UI/UX and Operator Decision Support Lead to support our Huntsville, AL location. The candidate will serve as a Tactical UI/UX and Operator Decision Support Lead within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Product Manager. The candidate will design low-cognitive-load C2 map interfaces and decision-support tools for high-stress tactical operators across the system lifecycle (design, development, acquisition, integration, testing, fielding, and sustainment). The candidate will prepare and present UI/UX findings, reports, and improvement plans to senior management and stakeholders. Will work within and/or lead a multidisciplinary team to achieve program goals. Perform other tasks as assigned by the Chief Engineer and/or Product Manager. The candidate will be required to interface with internal PMs across PAE Fires and external organizations to include HQDA, ASA(ALT), JIATF 401, ATEC, AMCOM, and others for coordination and synchronization of UI/UX technical and programmatic objectives." That's the About the role. Now Duties list (under "Duties"): - Provide technical support and leadership in UI/UX across the system lifecycle (design, development, acquisition, integration, testing, fielding, and sustainment). - Define HMI requirements for, and evaluate, decluttered and responsive map displays supporting simultaneous multi-target engagements. - Define and assess automated target prioritization workflows and weapon assignment recommendations. - Lead operator-in-the-loop (OITL) feedback sessions with air defense units. - Develop and maintain the Micro-Frontend UI Suite, the Human-Machine Interface (HMI) Design Spec, and Operator Usability Evaluation Reports. - Ensure compliance with defense and industry standards by managing UI/UX processes effectively. - Interface with internal teams and external organizations to coordinate UI/UX objectives and strategies. - Prepare and present UI/UX findings, reports, and improvement plans to senior management and stakeholders. - Conduct strategic planning and coordination to support program objectives. - Provide technical guidance and leadership to peer and subordinate engineers within the UI/UX team. - Use digital tools and methodologies to manage cost, schedule, and performance for assigned activities. - Perform other tasks as assigned by the Chief Engineer and/or Product Manager. Note some duplicates: "Prepare and present UI/UX findings, reports, and improvement plans to senior management and stakeholders." appears also in intro; but we keep as part of duties. Now Required Skills/Experience (under Qualifications): - 10+ years of relevant experience. - Additional education may be substituted for years of experience. - Extensive experience in UI/UX, particularly within defense or aerospace industries. - Knowledge of React, TypeScript, WebGL/CesiumJS, OpenLayers, and Human Factors Engineering (MIL-STD-1472). - Strong knowledge of industry standards and defense requirements. - Excellent communication and presentation skills. - Ability to lead and work within a multidisciplinary team. - Previous experience working in a U.S. Government Program Office (required). - Travel: 25% - Must be a U.S. Citizen - An active DoD Secret clearance is required to perform this work. Candidates are required to have an active Secret clearance upon hire, and the ability to maintain this level of clearance during their employment. Now Education Requirements: - Bachelor's degree in Engineering (or related technical discipline); advanced degree preferred. Desired Skills: - Top Secret clearance preferred. Now we also have "Overview People First..." but we omit. Now we need to map to sections. About the role: intro paragraph. Responsibilities: duties list. Requirements: required skills/experience (including travel, citizenship, clearance). Could also include "Previous experience working in a U.S. Government Program Office (required)". That's a requirement. Qualifications: education requirements and desired skills (Top Secret clearance preferred). Could also include "Additional education may be substituted for years of experience" but that's more about experience substitution; could go under Requirements or Qualifications. We'll keep under Requirements maybe. Skills: specific technical skills: Knowledge of React, TypeScript, WebGL/CesiumJS, OpenLayers, and Human Factors Engineering (MIL-STD-1472). Also maybe "Strong knowledge of industry standards and defense requirements" but that's more knowledge; could be under Skills as well. But we already have that in Requirements. To avoid duplication, we could put the technical stack under Skills, and keep other experience under Requirements. Thus: Skills: Knowledge of React, TypeScript, WebGL/CesiumJS, OpenLayers, and Human Factors Engineering (MIL-STD-1472). Also maybe "Strong knowledge of industry standards and defense requirements" but that is also a skill. We'll include. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now output HTML fragment. We must not include markdown fences. Let's craft.

  About the role

  Opportunity PeopleTec is currently seeking a Tactical UI/UX and Operator Decision Support Lead to support our Huntsville, AL location. The candidate will serve as a Tactical UI/UX and Operator Decision Support Lead within a Project Management Office (PMO) within PAE Fires and will be responsible for providing technical support to the program's Chief Engineer and the Product Manager. The candidate will design low-cognitive-load C2 map interfaces and decision-support tools for high-stress tactical operators across the system lifecycle (design, development, acquisition, integration, testing, fielding, and sustainment). The candidate will prepare and present UI/UX findings, reports, and improvement plans to senior management and stakeholders. Will work within and/or lead a multidisciplinary team to achieve program goals. Perform other tasks as assigned by the Chief Engineer and/or Product Manager. The candidate will be required to interface with internal PMs across PAE Fires and external organizations to include HQDA, ASA(ALT), JIATF 401, ATEC, AMCOM, and others for coordination and synchronization