Project Liaison Officer (PLO)

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate like EEO, legal, application instructions, referral, etc. Must not include sections with filler like "commensurate with experience", "not specified", etc. Pay section only if posting actually states them: they gave salary range $40.87 - $57.69/hour and is commensurate with experience. The phrase "commensurate with experience" is filler? It says salary range and then "is commensurate with experience." The instruction: 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 the posting actually states them. So we can include Pay section with the salary range, but we must avoid filler text like "commensurate with experience". We could include just the range. The phrase "commensurate with experience" is considered filler; we should omit that phrase. So Pay section:

Pay

$40.87 - $57.69/hour

Schedule: posting says "This position is not eligible for remote work; on-site support is required." Also mentions work arrangement remote/hybrid subject to change. No explicit schedule like full-time, hours. Not given. So we should not create Schedule section because no specific schedule info. So omit. Benefits: they list many benefits: Medical, dental, vision, 401(k), Life/AD&D/STD/LTD insurance, Paid vacation, holiday and sick leave, Generous tuition and training assistance program, Relocation assistance, Sign-on bonuses, Employee longevity recognition, Community involvement and outreach, Team building events, Recognition program, Wellness program, Employee Assistance Program (EAP), Mobile service discount, Fitness reimbursement program. That's substantive. So Benefits section. About the role: there is a paragraph about AMEWAS, mission, etc. Also "The Position AMEWAS is seeking a highly motivated and talented Project Liaison Officer (PLO) to support Advanced Aircraft Research, Development, Test & Evaluation." That's about the role. Could be About the role section. We'll include that. Responsibilities: the list of typical day items. That's responsibilities. Requirements: Must-haves list. That's requirements. Qualifications: maybe they separate? The posting has Must-haves and Desired Skills. Could treat Must-haves as Requirements, Desired Skills as Skills or Qualifications. The instruction: use headings for Requirements, Qualifications, Skills. We need to decide what content goes where. The posting: Must-haves (list). Desired Skills (list). Also there is "Skills Crucial To Success At AMEWAS" (customer-focused mindset etc). That's also skills. So we could map: - Requirements: Must-haves (hard requirements) - Qualifications: maybe education/experience? But Must-haves already includes HS Diploma or equivalent, 10 years experience, etc. Could treat Must-haves as Requirements and Qualifications maybe not needed. But we need to avoid thin sections. Could combine Must-haves and Desired Skills into Requirements and Skills respectively. Qualifications maybe not needed if not distinct. However we have "Skills Crucial To Success At AMEWAS" which is soft skills. Could put under Skills. Thus sections: About the role, Responsibilities, Requirements (Must-haves), Skills (Desired Skills + Skills Crucial To Success), Benefits, Pay. We must not include Schedule. Check for any other sections: maybe "Work Arrangement" but that's not a standard heading; we ignore. Now need to preserve all substantive information. Must not lose any detail from Must-haves, Desired Skills, Skills Crucial To Success, Benefits, etc. We must not include boilerplate like "Refer a Friend", "Employment Eligibility and Sponsorship Disclaimer", "Security Clearance Requirement Disclaimer", "Equal employment opportunity", etc. Also remove "We’re always on the lookout for top talent..." etc. Also remove "If you are interested in applying..." etc. Also remove "AMEWAS participates in E-Verify..." etc. Also remove "Please note: AMEWAS does not accept unsolicited resumes..." etc. Also remove "Work Arrangement Remote or hybrid work arrangements are subject to business..." maybe that's not boilerplate but it's about remote work; but we already have Pay and maybe we could include a note about on-site requirement under Responsibilities or About the role? The posting says "This position is not eligible for remote work; on-site support is required." That's substantive about work arrangement. Could be included under About the role or Responsibilities? Might fit under About the role as a note. But we have no specific heading for Work Arrangement. Could we include it under About the role as a paragraph? The instruction: we can include any prose in

. So we could add a sentence about on-site requirement in About the role paragraph. But we must not invent or summarize away detail. So we need to keep that detail. Thus About the role paragraph should include: description of AMEWAS, mission, location, and that the position is not eligible for remote work; on-site support required. Also maybe mention location details: Patuxent River, MD, etc. Also mention that it's Maryland's #1 City Hiring the Most High-Tech Workers. Also include link? We should not include URLs? The instruction: preserve ALL substantive information; do not invent or summarize away detail. The URL is substantive? It's a link to learn more about surrounding area. Might be considered boilerplate? It's not navigation/legal/EEO. It's a link for area info. Might be okay to keep. But we should avoid including raw URLs? Not prohibited. Could keep as plain text. But we must not include application instructions, referral, etc. Thus About the role paragraph: combine the intro paragraph about AMEWAS, the location paragraph, and the work arrangement sentence. Now Responsibilities: list of typical day items. Must preserve all bullet points. Use

• . Requirements: Must-haves list. Use
  • . Skills: combine Desired Skills list and Skills Crucial To Success list. Could be two separate
    under same heading? Or we could separate into two lists but still under Skills heading. The instruction: prefer a few substantive sections over many thin ones. So we can have one Skills section with two lists maybe separated by a paragraph heading? But we cannot add extra headings inside. Could just combine all items into one list. That would lose distinction but preserve all items. That's okay. Benefits: list of benefits. Use
    • . Pay:

      $40.87 - $57.69/hour

      Now ensure we don't include any filler like "commensurate with experience". We omitted that. Check for any other filler: "The salary range of this position is $40.87 - $57.69/hour and is commensurate with experience." We only keep the range. Now check for any other sections like "Qualifications". We didn't include Qualifications heading because we didn't have distinct qualifications separate from requirements. Could we treat Must-haves as Requirements and Desired Skills as Skills, and maybe the "Skills Crucial To Success At AMEWAS" also as Skills. So we have no Qualifications section. That's okay if no specific qualifications beyond requirements. Now ensure we didn't repeat job title as heading. We didn't. Now ensure we didn't include Job ID etc. Not present. Now ensure we removed all boilerplate: EEO, Regulatory Notices, Refer a Friend, Employment Eligibility, Security Clearance Disclaimer, etc. Also removed "Physical Environment And Working Conditions" maybe that's substantive? It describes physical demands. Could be considered substantive. Should we include it? The instruction: include a section ONLY when the posting has real, specific content for it. Physical environment is specific content. But we don't have a standard heading for it; we could maybe put under Responsibilities or About the role? But it's not exactly responsibilities. Could we create a custom heading? Not allowed; only allowed headings are the listed ones. So we cannot create a new heading. We could incorporate that info into Responsibilities or About the role as a paragraph. But that might be mixing categories. However the instruction says we must preserve ALL substantive information. If we cannot add a new heading, we need to fit it into existing allowed headings. Where does physical environment fit? Could be under Responsibilities? Not really. Could be under About the role? Not really. Could be under Requirements? Not really. Could be under Skills? Not really. Could be under Benefits? No. Could be under Pay? No. Could be under Schedule? No. Thus we have a dilemma: we must preserve all substantive info, but we cannot create new headings. 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 likely they are the only allowed headings. It says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only use those headings. If we have substantive info that doesn't fit, we might need to incorporate into existing sections as prose or list items. For physical environment, we could add a list item under Responsibilities? Not appropriate. Could add a paragraph under About the role? Maybe we can add a sentence about work environment in About the role. That would preserve the info albeit not ideal but acceptable. Similarly, "Work Arrangement Remote or hybrid work arrangements are subject to business..." we already have on-site requirement note; we could incorporate that into About the role as well. Thus we will embed physical environment description into About the role paragraph. Now check for any other substantive sections: "Security Clearance Requirement Disclaimer" is substantive but it's a disclaimer about clearance. However we already have clearance requirements in Must-haves (DoD Secret Clearance). The disclaimer repeats that. We could omit as it's boilerplate? It's a disclaimer but it's substantive about clearance. However the Must-haves already lists clearance requirement. The disclaimer adds nuance about interim clearance etc. Might be considered boilerplate legal. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This is a legal disclaimer about clearance. Likely considered legal boilerplate, so remove. Similarly "Employment Eligibility and Sponsorship Disclaimer" is legal, remove. "Refer a Friend" is not boilerplate but it's a referral program encouragement; could be considered promotional but not substantive to the job. Likely remove as it's not required. "Our Excellent Benefits And Perks" we already captured benefits list; the surrounding prose about staying connected to core values etc is fluff; we can keep just the list. Now ensure we didn't miss any substantive info: The location details: "About the location: Patuxent River, MD, located in the California-Lexington Park area, is Maryland’s #1 City Hiring the Most High-Tech Workers. To learn more about the surrounding area, please visit: www.visitstmarysmd.com". We'll keep that as prose. Now we need to output only HTML fragment. Let's craft:

      About the role

      At AMEWAS, we don’t just support defense—we shape it. For over 40 years, we’ve been a trusted partner of the Department of Defense (DoD) by providing cutting-edge engineering, testing, and evaluation for U.S. Navy weapons systems. Our people are the heart of our mission. Across our headquarters in California,