General Maintenance Worker (W23370)

We need to output HTML fragment with sections: headings

for section headings 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. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience", "not specified", etc. Do not create Pay/Schedule/Benefits sections unless posting actually states them. We need to parse the given job description. Content: "Standard Job Description This position requires a general understaning of carpentry skills, attention to detail, and the ability to be observant of others conducting work at the facility. Responsible for general maintenance of the customer infrastructure." Then "Basic Qualifications Basic carpentry skills Ability to obtain and maintain a U.S. Government SECRET or TOP SECRET clearance. Ability to lift 50lbs." Then "Desired Skills Advanced carpentry skills. Welding certification. Active SECRET or TOP SECRET clearance." Then "Pay Information This position is covered under the Service Contract Act (SCA) with an hourly wage of no less than per hour." This is weird: "no less than per hour" missing amount. It says "no less than per hour." That's placeholder? It says "no less than per hour." No amount given. That's not a specific number; it's filler. According to rule: do NOT include Pay section unless posting actually states them. Since no actual amount, we should not create Pay section. However there is later: "At Lockheed Martin, we know mission success starts with taking care of our people. Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally. The salary range for this position is as listed on the requisition. Please note that the salary information listed is a general guideline only. Lockheed Martin considers factors such as (but not limited to) scope and responsibilities of the position, candidate's work experience, education/ training, key skills as well as market(work location) and business considerations when extending an offer." That's generic, no specific numbers. So we should not include Pay section. Benefits: "Benefits offered: Medical, Dental, Vision, Flexible work arrangements and schedules (e.g., 4x10), 401(k) match, Paid time off, Holidays, Parental Leave, EAP, Flexible Spending Accounts, Education Assistance, Life Insurance, Short-Term Disability, and Long-Term Disability. Annual short-term and/or long-term incentive compensation programs may be offered depending on the position. Payments under these annual programs are not guaranteed and can vary from year to year and are tied to a range of performance metrics.For Service Contract Act (SCA) positions only. SCA employees receive a minimum of 80 hours of vacation and 88 hours of holiday paid time off. Paid sick leave is up to 56 hours annually. Paid time off is prorated based on start date during the calendar year. This is a general summary and fringe benefits are governed by the contract.For (Washington state applicants only) Non-represented full-time employees: accrue at least 10 hours per month of Paid Time Off (PTO) to be used for incidental absences and other reasons; receive at least 90 hours for holidays. Represented full time employees accrue 6.67 hours of Vacation per month; accrue up to 52 hours of sick leave annually; receive at least 96 hours for holidays. PTO, Vacation, sick leave, and holiday hours are prorated based on start date during the calendar year." That's specific benefits info. So we should include Benefits section with list. Schedule: Not explicitly mentioned except flexible work arrangements and schedules (e.g., 4x10) mentioned in benefits. That's a schedule detail. Should we create a Schedule section? The rule: include a section only when posting has real, specific content for it. The posting mentions flexible work arrangements and schedules (e.g., 4x10). That's specific enough? It's a mention of schedule. Could create Schedule section with that detail. However the rule says "Prefer a few substantive sections over many thin ones." Might combine schedule into Benefits? But schedule is separate concept. Could create Schedule section with that bullet. But we need to see if there is any other schedule info: none. Thus we could have sections: About the role (or Responsibilities), Responsibilities, Qualifications (maybe Basic Qualifications and Desired Skills combined?), Skills, Benefits, Schedule. We need to decide headings: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content exists. We have: - About the role: maybe the first paragraph describing position: "This position requires a general understanding of carpentry skills, attention to detail, and the ability to be observant of others conducting work at the facility. Responsible for general maintenance of the customer infrastructure." That's about the role. - Responsibilities: Could be same as above? Might be redundant. But we could treat that as Responsibilities. However we need to avoid duplication. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine About the role and Responsibilities into one section? But we need headings only when there is real specific content. We could have a single section "Responsibilities" covering that description. Or "About the role". Which is better? The first sentence is more about role/requirements. The second sentence is responsibility. Could combine. We also have Basic Qualifications and Desired Skills. Could combine into "Qualifications" and "Skills". Or separate: Basic Qualifications under Qualifications, Desired Skills under Skills. We need to use

  • for any list of duties/requirements/benefits. So for qualifications list we should use
    • . For skills list also. We need to preserve all substantive information. So we need to include the details: Basic carpentry skills, ability to obtain and maintain US Gov SECRET or TOP SECRET clearance, ability to lift 50lbs. Desired: Advanced carpentry skills, Welding certification, Active SECRET or TOP SECRET clearance. We need to include benefits list as
      • . Also schedule: flexible work arrangements and schedules (e.g., 4x10). Could be a
        • under Schedule. We must not include Pay section because no specific amount. We must remove boilerplate: navigation, legal, EEO, etc. The text includes some boilerplate like "At Lockheed Martin, we know mission success starts..." that's generic but still substantive? It's about Total Rewards program. Might be considered boilerplate but it's describing benefits. However we already have benefits list; the generic sentences could be omitted as they are not specific. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The Lockheed Martin paragraph is not exactly boilerplate but it's generic fluff. Might be considered boilerplate? It's not legal/EEO. It's about Total Rewards program. Could keep as part of Benefits? But we already have benefits list; the paragraph is fluff. Safer to omit it as it's not specific detail. However we need to preserve ALL substantive information. Is that paragraph substantive? It says "Our Total Rewards program is designed to attract top talent, support your well-being, and help you grow—both professionally and personally." That's vague. Might be considered boilerplate. I'd omit. Also the sentences about salary range being as listed on requisition etc are generic; omit. Now we need to output only HTML fragment, no /, no markdown. Thus produce something like:

          About the role

          This position requires a general understanding of carpentry skills, attention to detail, and the ability to be observant of others conducting work at the facility. Responsible for general maintenance of the customer infrastructure.

          Responsibilities

          General maintenance of customer infrastructure.

          (but that's duplicate). Maybe we skip Responsibilities and just have About the role. Better: Use About the role for description, and Qualifications for basic qualifications, Skills for desired skills, Benefits for benefits, Schedule for schedule. Let's craft:

          About the role

          This position requires a general understanding of carpentry skills, attention to detail, and the ability to be observant of others conducting work at the facility. Responsible for general maintenance of the customer infrastructure.

          Qualifications

          • Basic carpentry skills
          • Ability to obtain and maintain a U.S. Government SECRET or TOP SECRET clearance
          • Ability to lift 50 lbs

          Skills

          • Advanced carpentry skills
          • Welding certification
          • Active SECRET or TOP SECRET clearance

          Benefits

          • Medical
          • Dental
          • Vision
          • Flexible work arrangements and schedules (e.g., 4x10)
          • 401(k) match
          • Paid time off
          • Holidays
          • Parental Leave
          • EAP
          • Flexible Spending Accounts
          • Education Assistance
          • Life Insurance
          • Short-Term Disability
          • Long-Term Disability
          • Annual short-term and/or long-term incentive compensation programs (payments not guaranteed, vary year to year, tied to performance metrics)
          • For SCA positions: minimum 80 hours vacation and 88 hours holiday paid time off; paid sick leave up to 56 hours annually; paid time off prorated based on start date
          • Washington state applicants: Non‑represented full‑time employees accrue at least 10 hours PTO per month (≥90 hours holidays); represented full‑time employees accrue 6.67 hours vacation per month, up to 52 hours sick leave annually, ≥96 hours holidays; all prorated

          Schedule

          Flexible work arrangements and schedules (e.g., 4x10) are offered.

          But note we already included flexible work arrangements in Benefits list; might be duplication. Could move schedule detail to Schedule section and remove from Benefits to avoid duplication. However the instruction: "Preserve ALL substantive information". If we move it, we still preserve. But we need to avoid duplication? Not explicitly forbidden, but better to avoid duplicate lines. The benefits list includes "Flexible work arrangements and schedules (e.g., 4x10)" as a benefit. If we also have Schedule section repeating that, it's duplication. Better to keep it only in Benefits or Schedule, not both. Since schedule is a specific aspect, we could keep it under Schedule and remove from Benefits list. However the benefits list also includes many other items; we could keep flexible work arrangements under Benefits as it's a benefit. But then Schedule section would be redundant. The rule: "Prefer a few substantive sections over many thin ones." So maybe we should not create a separate Schedule section if the schedule info is already captured under Benefits. However the schedule info is a specific detail about flexible work arrangements; it's arguably a benefit. So we can omit Schedule section. Thus we have sections: About the role, Qualifications, Skills, Benefits. Check if any other section like Responsibilities needed: The About the