Airworthiness Operations Specialist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer a few substantive sections over many thin ones. We need to parse the posting. Company Overview: description of Metrea. Could be "About the role"? Actually "Company Overview" is about the company, not role. The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Company Overview (maybe "About the role"? Actually "About the role" is about the position. But we have "Position Summary". Could treat that as "About the role". We'll include a section "About the role" with the Position Summary. - Responsibilities: "What You'll Do" bullet list. - Requirements: "What You Bring" bullet list (experience, etc.) - Qualifications: "Additional Eligibility Qualifications" bullet list. - Skills: maybe not separate; could combine with Requirements? But we can include a Skills section if there is explicit skill list. The posting includes "Proficiency with Microsoft Office applications" etc. Could be part of Requirements. But we can create a Skills section for those. - Benefits: list of benefits. - Pay: "Pay Range: $105,000 USD - $115,000 USD". Also mention "Base Pay Range". So we have Pay. - Schedule: "Position Type and Expected Hours of Work" includes full-time exempt, typical working hours Monday-Friday 8-5, may change, on-call. So we have schedule info. We need to remove boilerplate: EEO statement, Work Authorization / Security Clearance (maybe keep? It's eligibility but maybe considered metadata; but it's substantive? It says "Must be legally authorized to work in the United States Must be a U.S. citizen Eligible to obtain and maintain a Secret clearance". That's eligibility qualifications; could be part of Qualifications or Requirements. But the instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. This is not Job ID, it's eligibility. Might keep as part of Qualifications. Also "Work Authorization / Security Clearance" heading is not needed; we can incorporate into a paragraph. Also "Our Firmware" etc is fluff; maybe not needed? It's about company values; could be considered boilerplate? It's not standard legal but maybe not needed. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "Our Firmware" is not boilerplate but maybe not substantive for the role; could be considered company culture. Might keep as part of About the role? But we need to preserve ALL substantive information; does that include company values? It's substantive but maybe not required for role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it unless it's considered boilerplate. It's not legal/EEO; it's about company culture. Could be included in a section like "About the company" but we only have headings for certain categories. Could we add an "About the company" heading? Not in allowed list. The instruction says 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. So we need to fit content into those categories. Thus we need to decide where to put company overview, mission, etc. Could be part of "About the role" (makes sense). Or we could put in a paragraph before sections without heading? The instruction says output ONLY the HTML fragment; we can have

  elements without heading. So we can include a brief intro paragraph about company overview before sections. We must not repeat job title as heading. The job title is "Airworthiness Operations Specialist". Not to be used as heading. We must not put Job ID/requisition numbers as headings; none present. We need to remove duplicated lines. There's some duplication: "Support the Airworthiness Operations Manager in the administration, maintenance, and continuous improvement of the Computerized Maintenance Management System (CMMS), currently AMOS" appears twice? Actually first bullet and later bullet similar. We'll keep unique. Now let's extract content. Company Overview paragraph: "Metrea delivers effects-as-a-service to national security partners across five domains and more than a dozen mission areas. These include airborne ISR, electronic warfare, secure communications, aerial refueling, special air missions, aerial firefighting, and advanced simulation. We own the whole stack: designing, building, and operating turnkey capabilities that give our partners decisive, asymmetric advantage against rapidly evolving threats. Our operating model is built around three interlocking pillars. The Support Groups provide a global shared-service – spanning people, finance, platform, operations, legal, and engagement. This frees up our Core Groups, who develop and own mission capabilities end-to-end, to focus entirely on delivery. The Market Groups apply a regional lens, ensuring that our agile and adaptable capabilities remain aligned to the wicked problems that matter most to our partners across the Americas, EMEA, and Asia-Pacific. At the heart of our model is a simple but powerful idea: be a true partner with skin in the game. Our partners need effects, not just equipment. By owning the full stack – from the lab to the field – we are able to drive a continuous cycle of innovation that keeps our partners ahead. It's a fast-moving, intellectually demanding environment where talented people are given real responsibility, work on problems that matter, and contribute to an enterprise that is growing quickly and deliberately. Headquartered in Washington, DC, with facilities across the United States, the United Kingdom, as well as Continental Europe and Asia-Pacific." Group Overview: "Special Air Missions Group (SAM) is responsible for developing and delivering Metrea’s Intelligence, Surveillance, and Reconnaissance (ISR), Special Mobility, and Aerial Firefighting (AFF) capabilities. SAM oversees the integration of new mission systems, ensuring operational readiness across specialized aviation operations. It manages fleet maintenance, regulatory compliance, and strategic partnerships to enhance mission effectiveness. By consolidating expertise and infrastructure, SAM ensures Metrea’s airborne capabilities remain adaptable and mission-ready across dynamic operational environments." Position Summary: "The Airworthiness Operations Specialist supports the Airworthiness Operations Manager in the administration, maintenance, and continuous improvement of the Computerized Maintenance Management System (CMMS) and Airworthiness operational processes. This position assists in maintaining the integrity of the AMOS system architecture, supporting inspection program configuration, coordinating system administration activities, and ensuring users have the tools and training necessary to effectively utilize the system. Working closely with Airworthiness, Technical Records, Mission Systems, Maintenance, Supply Chain, and Operations. The Airworthiness Operations Specialist serves as a subject matter expert in AMOS administration and provides day-to-day system support, user training, onboarding, and process improvement. This role helps ensure AMOS remains an effective and compliant system for managing maintenance planning, technical records, airworthiness compliance, and fleet readiness. The Airworthiness Operations Specialist supports all functions of the Airworthiness Operations Manager and contributes to the successful execution of CAMO operations by promoting standardized processes, accurate system administration, and continuous improvement across the organization." We can combine Company Overview + Group Overview + Position Summary into an "About the role" section (or maybe separate "About the company" but not allowed). We'll put under

  About the role

  and include paragraphs. Responsibilities: "What You'll Do" list: - Support the Airworthiness Operations Manager in the administration, maintenance, and continuous improvement of the Computerized Maintenance Management System (CMMS), currently AMOS - Assist in maintaining the AMOS system architecture, configuration, and inspection program structure to ensure compliance with regulatory requirements, operational needs, and company standards - Serve as a Subject Matter Expert (SME) in AMOS administration, providing day-to-day system support, troubleshooting, and assisting with system enhancements and process improvements - Develop, maintain, and deliver AMOS training while supporting the onboarding of Maintenance, Technical Records, and CAMO personnel - Coordinate with Airworthiness, Technical Records, Mission Systems, Maintenance, Supply Chain, and Operations to ensure AMOS effectively supports fleet maintenance planning, technical records, and airworthiness activities - Support the development and maintenance of reports, dashboards, and performance metrics that improve fleet readiness, compliance, and operational visibility - Assist in maintaining controlled documentation, standard operating procedures, and system standards related to Airworthiness Operations and AMOS administration - Support software updates, testing, system implementations, and the introduction of new functionality within AMOS - Support the Airworthiness Operations Manager in the execution of Airworthiness Operations initiatives and provide operational support across all CAMO activities We need to ensure no duplication. The first bullet duplicates earlier sentence; but it's okay. Requirements: "What You Bring" list: - 3+ years of experience in aircraft maintenance planning, CAMO, technical records, maintenance operations, or a related aviation support function - Experience working with Computerized Maintenance Management Systems (CMMS), preferably AMOS - Strong computer literacy with the ability to quickly learn, administer, and support enterprise software applications - Strong attention to detail with experience managing, organizing, and maintaining large volumes of technical data - Excellent analytical and problem-solving skills with the ability to identify trends, improve processes, and ensure data integrity - Strong organizational and time management skills with the ability to manage multiple priorities in a fast-paced environment - Excellent written and verbal communication skills with the ability to work across multiple departments - Proficiency with Microsoft Office applications Additional Eligibility Qualifications: - Ability to prioritize and execute in a fast-paced, multi-platform operational environment - Strong communication skills with the ability to translate technical issues across teams and leadership levels - Proven ability to lead through influence in a cross-functional organization - High attention to detail with a focus on compliance, traceability, and operational impact We could merge these into Requirements and Qualifications sections. The instruction: Use headings for Requirements, Qualifications, Skills. So we need to split. We can treat "What You Bring" as Requirements (experience, skills). "Additional Eligibility Qualifications" as Qualifications (maybe more about eligibility). Skills could be separate list of specific skills like "Proficiency with Microsoft Office applications", "Strong computer literacy", etc. But we already have those in Requirements. Could create a Skills section for those. But we need to avoid thin sections. Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Qualifications into one section? But headings are specified; we could still have both but ensure they have substantive content. We have enough content for Requirements (the What You Bring list). Qualifications (Additional Eligibility Qualifications) also substantive. Skills: we could list specific skills like "Proficiency with Microsoft Office applications", "Strong computer literacy", "Ability to quickly learn, administer, and support enterprise software applications", "Strong