General Maintenance | The SOMM Hotel & Spa
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. IMPORTANT: include a section ONLY when the 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 the posting actually states them. Prefer a few substantive sections over many thin ones.
Thus we need to decide which sections to include based on content.
We have:
- Perks: includes eligibility, pay range, get paid daily, PTO, holiday pay, benefits list, values based culture, culture add, referral bonus, discounted lodging/dining/spa/golf/retail, employee assistance program, Columbia Cares volunteer opportunities, committee participation opportunities, task force work opportunities, online learning platform, third party perks. This is a lot of content. Could be split into Benefits and Perks? The instruction says use headings like Benefits, Pay, Schedule. But we also have a "Perks" block at start. Could treat as "Benefits" section? However they also list Benefits - Medical, Dental, Vision, Disability, 401K HSA/FSA Plans -with employer contribution. That's benefits. The rest are perks. Could combine into a Benefits section? But they said only create Benefits section if posting actually states them. It does state benefits. So we can have a Benefits section with list of medical, dental, vision, disability, 401K, HSA/FSA with employer contribution. Also we have Pay: Hourly Pay Range: $25 to $28 DOE. Also Get Paid Daily (Make any day payday). That's pay info. So we can have Pay section.
Schedule: Not explicitly stated except "Weekend availability required." That's schedule info. Could be Schedule section.
Responsibilities: The "What Success Looks Like: Your Impact" block lists duties. That's responsibilities.
Requirements: The "What You Bring" block lists qualifications.
Also there is a "Where you'll work" description about location. Could be "About the role" or maybe not needed. Could be a short paragraph about location. The instruction says prefer a few substantive sections over many thin ones. Could include About the role (location description). But we already have many sections: Pay, Benefits, Schedule, Responsibilities, Requirements. That's 5 sections. Could be okay.
We must not include headings with filler. Ensure each heading has real content.
We need to output only HTML fragment, no /, no markdown.
We'll produce something like:
Pay
Hourly Pay Range: $25 to $28 DOE. Get Paid Daily (Make any day payday).
Benefits
- Medical
- Dental
- Vision
- Disability
- 401K
- HSA/FSA Plans – with employer contribution
But also there are many other perks like PTO, holiday pay, referral bonus, discounted lodging etc. Those could be considered benefits/perks. The instruction says use Benefits section for benefits; but we could also include a Perks section? Not in the list of allowed headings but we could use "Benefits" to capture all perks? However they said "Benefits, Pay, Schedule" as examples, not exclusive. But we should follow the examples: they gave a list of possible headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those headings. So we need to map content to those.
Thus:
- About the role: could include location description and maybe the values statement? The "Our Commitment to you:" paragraph is about culture; could be part of About the role.
- Responsibilities: the "What Success Looks Like: Your Impact" block.
- Requirements: the "What You Bring" block.
- Qualifications: maybe same as Requirements? Could combine? But we have both Requirements and Qualifications as possible headings. We could put Requirements for mandatory items, Qualifications for preferred. But we have both mandatory and preferred in same block. Could split: Requirements: Must be able to complete all types of work orders..., Must have general understanding..., Journeymen level experience or equivalent..., Ability to effectively perform painting..., Ability to perform maintenance..., Must have knowledge and ability to operate tools..., Must be flexible..., Weekend availability required. Qualifications: Hotel and/or Marriott experience highly preferred. Also maybe "Don’t meet every single requirement?" is encouraging but not a qualification.
- Skills: maybe not needed.
- Benefits: list of medical, dental, vision, disability, 401K, HSA/FSA with employer contribution, plus also PTO & holiday pay, get paid daily? Actually get paid daily is pay. PTO & holiday pay could be benefits. Also referral bonus, discounted lodging etc. Could be considered benefits/perks. But we already have Pay section for pay range and daily pay. So Benefits could include medical, dental, vision, disability, 401K, HSA/FSA, PTO & holiday pay, referral bonus, discounted lodging/dining/spa/golf/ret
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. IMPORTANT: include a section ONLY when the 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 the posting actually states them. Prefer a few substantive sections over many thin ones. Thus we need to decide which sections to include based on content. We have: - Perks: includes eligibility, pay range, get paid daily, PTO, holiday pay, benefits list, values based culture, culture add, referral bonus, discounted lodging/dining/spa/golf/retail, employee assistance program, Columbia Cares volunteer opportunities, committee participation opportunities, task force work opportunities, online learning platform, third party perks. This is a lot of content. Could be split into Benefits and Perks? The instruction says use headings like Benefits, Pay, Schedule. But we also have a "Perks" block at start. Could treat as "Benefits" section? However they also list Benefits - Medical, Dental, Vision, Disability, 401K HSA/FSA Plans -with employer contribution. That's benefits. The rest are perks. Could combine into a Benefits section? But they said only create Benefits section if posting actually states them. It does state benefits. So we can have a Benefits section with list of medical, dental, vision, disability, 401K, HSA/FSA with employer contribution. Also we have Pay: Hourly Pay Range: $25 to $28 DOE. Also Get Paid Daily (Make any day payday). That's pay info. So we can have Pay section. Schedule: Not explicitly stated except "Weekend availability required." That's schedule info. Could be Schedule section. Responsibilities: The "What Success Looks Like: Your Impact" block lists duties. That's responsibilities. Requirements: The "What You Bring" block lists qualifications. Also there is a "Where you'll work" description about location. Could be "About the role" or maybe not needed. Could be a short paragraph about location. The instruction says prefer a few substantive sections over many thin ones. Could include About the role (location description). But we already have many sections: Pay, Benefits, Schedule, Responsibilities, Requirements. That's 5 sections. Could be okay. We must not include headings with filler. Ensure each heading has real content. We need to output only HTML fragment, no /, no markdown. We'll produce something like:
Pay
Hourly Pay Range: $25 to $28 DOE. Get Paid Daily (Make any day payday).
Benefits
- Medical
- Dental
- Vision
- Disability
- 401K
- HSA/FSA Plans – with employer contribution