JW Marriott - Overnight Maintenance Attendant

We need to output HTML fragment with sections only if real specific content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. From posting: - Title: Maintenance Attendant (already shown, we don't repeat) - City, State: Atlanta, Georgia (metadata) - Location: JW Marriott Atlanta Downtown - FLSA: Non-Exempt - Status: Full-time - Reports to: Director of Engineering - Pay Range: $25 (likely per hour) - Job Summary: paragraph. - Essential Functions and Duties: list of duties. - Required Experience, Education, and Skills: list of requirements/skills. - Work Environment: description. - Other Duties: note about job description not comprehensive (boilerplate? maybe minor metadata) - Equal Employment Opportunity: boilerplate to remove. - Stonebridge offers comprehensive benefits including ... (benefits) - Also mention Massachusetts lie detector law (boilerplate/legal) remove. - Also mention "All Stonebridge openings are projected to close within 30 days..." (metadata maybe minor) - "This position will no longer be available 30 days from: 2026-09-24" (metadata) - Also "Reasonable accommodations may be made to enable qualified individuals with disabilities to perform the essential duties." (maybe part of requirements? but it's a statement about accommodation; could be included in Responsibilities? Probably not needed as separate section; we can incorporate into a short paragraph maybe under Responsibilities? But we should not invent sections. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Thus we keep: - Job Summary (maybe as About the role? The heading "About the role" could be used for job summary. We'll put Job Summary under

About the role

with a

. - Essential Functions and Duties -> Responsibilities section (

Responsibilities

) with

• each duty. - Required Experience, Education, and Skills -> could be split into Requirements, Qualifications, Skills. But we have a list that includes knowledge, ability, familiarity, problem-solving, communication, ability to work independently. Could treat as Requirements (experience/education) and Skills. However we have no explicit education requirement. Could combine into Requirements and Skills sections. But we need to avoid thin sections. Perhaps we make one section "Requirements" containing the list. Or we could split into Requirements (basic knowledge, ability to perform preventative maintenance, familiarity with safety procedures) and Skills (problem-solving, attention to detail, communication, ability to work independently). That seems reasonable. - Work Environment: maybe not a standard heading; we could put under Responsibilities? But it's about work environment; could be its own section but not in list of allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Work Environment not allowed; we could incorporate into Responsibilities or maybe omit? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, but we should likely stick to those. However we could still add other headings if needed? The instruction says use those for section headings; implies we should use those headings when appropriate. It doesn't forbid other headings, but better to stick to those. Work Environment could be placed under Responsibilities as a paragraph? Or we could create a "Requirements" section that includes work environment? Not ideal. Maybe we can treat Work Environment as part of Responsibilities (since it's about the job). But it's more about conditions. Could add a short paragraph under Responsibilities after the list. - Benefits: we have benefits description: "Stonebridge offers comprehensive benefits including medical, dental, vision, PTO, 401(k) matching, wellness support, life and disability coverage, savings accounts, tuition aid, and travel and lodging perks." That's specific; we should create Benefits section. - Pay: we have Pay Range: $25 (likely per hour). So we create Pay section with that. - Schedule: we have "Must be available to work evenings, weekends, and holidays as required, with potential on-call responsibilities for emergencies." That's schedule info. So we create Schedule section. - Other Duties: note about job description not comprehensive - could be considered boilerplate? It's a disclaimer but maybe minor metadata; we can drop. - Equal Employment Opportunity: remove. - Massachusetts lie detector law: remove. - All Stonebridge openings projected to close within 30 days: minor metadata; could drop or fold into short p. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we could include a short paragraph at the end with that info, maybe under a generic paragraph without heading? But we need to output only HTML fragment; we could include a

  with that metadata after sections. However we should avoid boilerplate; but this is not EEO, it's about posting expiration. Might be okay to include as a short p. - "Reasonable accommodations may be made to enable qualified individuals with disabilities to perform the essential duties." This is also a statement about accommodation; could be included in Responsibilities or Requirements? Might be placed as a short p under Requirements? But it's more about accommodation; we could include in Responsibilities as a note. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep the accommodation statement. Thus we need to include that statement somewhere. Potential plan: -

  About the role

  Job Summary paragraph.

  -

  Responsibilities

  • each duty from Essential Functions and Duties.

  Reasonable accommodations may be made to enable qualified individuals with disabilities to perform the essential duties.

  (maybe after list) -

  Requirements

  • Basic knowledge of maintenance systems, including refrigeration, heating, plumbing, and electrical systems.
  • Ability to perform preventative maintenance and minor repairs on equipment.
  • Familiarity with safety procedures, including lockout-tagout, is preferred.
  -

  Skills

  • Strong problem-solving skills and attention to detail.
  • Ability to communicate effectively with team members and management.
  • Ability to work independently and manage multiple tasks in a timely manner.
  -

  Benefits

  • Medical
  • Dental
  • Vision
  • PTO
  • 401(k) matching
  • Wellness support
  • Life and disability coverage
  • Savings accounts
  • Tuition aid
  • Travel and lodging perks
  (We could keep as a single sentence but better as list.) -

  Pay

  $25 per hour

  (or just "$25". The posting says Pay Range: $25. Likely per hour. We'll state "$25 per hour".) -

  Schedule

  Must be available to work evenings, weekends, and holidays as required, with potential on-call responsibilities for emergencies.

  - Then maybe a short paragraph for metadata: "All Stonebridge openings are projected to close within 30 days of the original posting date. This position will no longer be available 30 days from: 2026-09-24." We'll put as

  ...

  after sections. We must not include headings for metadata. Check for duplication: Ensure we didn't repeat any content. Now ensure we didn't include any boilerplate like EEO, Massachusetts law, etc. Check that we didn't include "Work Environment" details; we omitted them. Is that substantive? It describes indoor/outdoor, lifting, noise, etc. That's substantive. We need to preserve ALL substantive information. Omitting work environment would lose info. So we need to include it somewhere. Could add a section "Work Environment" but not in allowed headings list; but the instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That could be interpreted as we should use those headings when appropriate, but we could also use other headings if needed. However the instruction also says "Prefer a few substantive sections over many thin ones." So maybe we can incorporate work environment into Responsibilities or Requirements as a paragraph. We could add a paragraph under Responsibilities after the list: "Work involves both indoor and outdoor environments, with exposure to varying temperatures. Frequent walking, standing, and lifting of objects up to 50 lbs. Exposure to noise, vibration, and mechanical equipment during maintenance tasks." That preserves the info. Thus we keep work environment details. Now check for any other substantive info: "FLSA: Non-Exempt", "Status: Full-time", "Reports to: Director of Engineering". These are metadata; we could fold into a short p maybe under About the role? The instruction says fold minor metadata into a short

  or drop it. So we could include a short paragraph after About the role that includes those details. But we already have About the role with job summary; we could add a

  containing those metadata. However we need to avoid repeating job title as heading; fine. Thus About the role section could contain:

  The Maintenance Attendant supports the maintenance operations of the hotel, ensuring all facilities and equipment are functioning properly. This role assists with preventative maintenance tasks, repairs, and general upkeep, contributing to a safe and welcoming environment for guests and staff. FLSA: Non-Exempt. Status: Full-time. Reports to: Director of Engineering.

  But that mixes prose with metadata; still okay. Alternatively we could keep job summary separate and then a short p for metadata. But we need to avoid too many sections; we can keep About the role as job summary only, and then add a

  after it for metadata without heading. That is allowed. Thus final HTML:

  About the role

  The Maintenance Attendant supports the maintenance operations of the hotel, ensuring all facilities and equipment are functioning properly. This role assists with preventative maintenance tasks, repairs, and general upkeep, contributing to a safe and welcoming environment for guests and staff.

  FLSA: Non-Exempt. Status: Full-time. Reports to: Director of Engineering.

  Then Responsibilities list, then after list add accommodation statement as a

  . Then Requirements list. Then Skills list. Then Benefits list. Then Pay p. Then Schedule p. Then metadata p about closing date. Check that we didn't include any boilerplate like "Reasonable accommodations may be made..." we kept that as a p after Responsibilities. Now ensure we didn't include any duplicated lines. Now output only HTML fragment. Let's craft the list items precisely from the text. Essential Functions and Duties list: - Provide professional and courteous service at all times. - Assist with maintenance and preventative maintenance tasks, including refrigeration, heating, plumbing, A/C units, and hotel equipment. - Monitor electric, gas, and water consumption and report issues as needed. - Ensure all maintenance projects are completed on time and according to specifications. - Practice safety procedures, including lockout-tagout, in accordance with OSHA standards. - Perform preventative maintenance in guest rooms and public areas as scheduled. - Conduct maintenance checks of equipment and properly log findings. - Report all safety and