Facilities Technician
` for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for lists of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat job title as heading (page already shows it)
- 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
- 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
- Output ONLY the HTML fragment — no `/`, no markdown code fences
2. **Analyze the Job Posting Content:**
Let me extract the relevant parts from the text provided:
- Company: Palm Beach Tan
- Role: Facilities Technician
- Pay: "Starting at $25/hr. - $35/hr." (This is substantive, so Pay section should exist)
- Description: "The Facilities Technician is responsible for all maintenance concerns for the stores in their assigned areas."
- Ideal candidate experience: "experience with and an understanding of the demands of building maintenance in a multi-unit setting, and a basic understanding of building maintenance systems."
- Position: full-time, requires frequent travel, no specific office location, start day from home, travel to locations
- Perks/benefits listed:
- Overtime Opportunities
- Company Car + Gas
- Free Tanning, Product and Service Discounts
- Generous Paid Time Off Plans
- Paid holidays
- Benefits Package
- 401K with company matching
- Responsibilities list:
- Providing general maintenance to store locations throughout above-mentioned area
- Repairing general items such as minor plumbing, light ballasts, doorknobs, etc.
- Maintaining tanning booths and UV free spray booths (training provided)
- General carpentry including sheetrock repair, painting
- Working with store operations staff; communicating with store management and vendors
- Requirements/Qualifications list:
- Excellent driving record (driving record check required)
- 2 years’ preferred experience with maintenance and constructions required (multi-unit experience preferred)
- Basic understanding of building maintenance systems
- Ability to manage multiple projects
- Ability to work independently
- Outstanding customer service skills
- Willingness to work nights, weekends, holidays, and some overtime based on business needs
- Ability to lift up to 50 pounds
- EEO statement at the end: "Palm Beach Tan is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, national origin, disability status, protected Veteran status, or any other characteristic protected by law." -> This should be removed per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate"
- Also remove: "Here are some of the perks we offer:" seems like intro to benefits, but benefits are listed after. I'll capture the actual benefit items.
- "Starting at $25/hr. - $35/hr." is pay info.
- "This is a full-time position that requires frequent travel. This position does not have a specific office location. You will start your day from home, and travel to locations as needed to your assigned areas." -> This is prose/context, could go in About the role or a short intro paragraph.
Now, map to allowed sections:
- Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- I need to only include sections that have real, specific content.
- Pay: "$25/hr. - $35/hr." -> include Pay section
- Benefits: The list includes "Overtime Opportunities", "Company Car + Gas", "Free Tanning, Product and Service Discounts", "Generous Paid Time Off Plans", "Paid holidays", "Benefits Package", "401K with company matching". These are specific benefits. Should I use "Benefits" heading? Yes, but only if there's real content. There is. I'll list them.
- Schedule: The posting mentions "full-time position that requires frequent travel", "Willingness to work nights, weekends, holidays, and some overtime based on business needs". There's no specific schedule structure like "9-to-5" or "shift times", but there is mention of work hours/patterns. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule is mentioned in terms of requirements ("Willingness to work nights, weekends, holidays, and some overtime"). I think I can include a Schedule section with that specific info, or fold it into Requirements/Qualifications. But the allowed headings include "Schedule". I'll check if there's actual schedule info beyond the flexibility/requirement language. It says "full-time position that requires frequent travel" and "Willingness to work nights, weekends, holidays, and some overtime based on business needs". That's more about work schedule expectations. I'll probably include a Schedule section with that specific phrasing, or maybe fold it into Requirements. To be safe, I'll see if the rule prefers "Prefer a few substantive sections over many thin ones." I'll only include Schedule if there's clear schedule info. The posting does state schedule expectations, so I'll include it briefly.
- About the role: The posting has description, pay, location-flexible nature, travel requirements. I'll create an "About the role" section with the core description, pay mention, and work arrangement.
- Responsibilities: list of duties
- Requirements/Qualifications: The posting has both "Requirements" and "Experience" sections. The rules say use headings: "Requirements, Qualifications". I'll combine or separate? The list includes "Experience Excellent driving record..." and bullet points under "Responsibilities" and then "Experience" section. I'll likely use "Requirements" for the qualifications list, or "Qualifications". The allowed headings are "Requirements, Qualifications". I'll pick one or split if there's distinct content. Looking at the text: "Responsibilities" section lists duties. Then "Experience" section lists: "Excellent driving record (driving record check required)", "2 years’ preferred experience with maintenance and constructions required (multi-unit experience preferred)", "Basic understanding of building maintenance systems", "Ability to manage multiple projects", "Ability to work independently", "Outstanding customer service skills", "Willingness to work nights, weekends, holidays, and some overtime based on business needs", "Ability to lift up to 50 pounds". These are requirements/qualifications. I'll use "Requirements" heading for these, or "Qualifications". I'll check the exact allowed list: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can use both "Requirements" and "Qualifications" if there's distinct content, but it might be redundant. I'll probably use "Requirements" for the substantive list, and maybe "Skills" if there's a separate skills section. The posting doesn't have a clear "Skills" section separate from requirements. I'll stick to "Requirements" for the qualification bullets, and maybe "Skills" if I can extract something, but I'll avoid thin sections.
Let me re-read the rules carefully: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples, not a mandate to use all. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I must only include sections that have real content.
Let's determine which sections have clear, specific content:
- About the role: Yes, has description, pay, work arrangement.
- Responsibilities: Yes, list of duties.
- Requirements or Qualifications: Yes, has specific requirements (driving record, experience, skills, physical abilities).
- Benefits: Yes, specific benefits listed.
- Pay: Yes, "$25/hr. - $35/hr."
- Schedule: Has "full-time", "frequent travel", "nights, weekends, holidays, some overtime". I'll include it with that specific phrasing, or maybe fold into Requirements. I think I'll include Schedule with the specific work schedule expectations mentioned.
- Skills: The posting has "Basic understanding of building maintenance systems", "Ability to manage multiple projects", "Ability to work independently", "Outstanding customer service skills". These could go under Skills or Requirements. I'll probably use Requirements for the hard requirements, and maybe Skills for the soft skills, but to avoid thin sections, I'll combine into one "Requirements" section, or use "Qualifications". The example headings include both "Requirements" and "Qualifications". I'll use "Requirements" for the list, and if there's extra, I'll see.
Actually, looking at the posting structure:
- "Responsibilities" heading then bullet points
- Then "Experience" heading? No, it says "Experience Excellent driving record..." etc. It's not a separate "Experience" section with dates, it's a list of requirements/experience needed. The text says: "Here are some of the perks we offer:" then benefits, then "Responsibilities Providing general maintenance..." then "Experience Excellent driving record...". So the posting has: Perks/benefits intro, Responsibilities, Experience/requirements.
I need to map this to the allowed headings while removing boilerplate (EEO statement at the end, "Palm Beach Tan is an Equal Opportunity Employer...").
Let me outline the HTML structure I'll create:
About the role
Palm Beach Tan, the industry leader in Sunbed and Spray Tanning, seeks a Facilities Technician responsible for all maintenance concerns across stores in their assigned areas. This is a full-time position requiring frequent travel; you will start your day from home and travel to locations as needed within your assigned areas. Starting pay is $25/hr. - $35/hr.
Responsibilities
- Providing general maintenance to store locations throughout the assigned area
- Repairing general items such as minor plumbing, light ballasts, doorknobs, etc.
- Maintaining tanning booths and UV-free spray booths (training provided)
- General carpentry including sheetrock repair and painting
- Working with store operations staff; communicating with store management and vendors
Requirements
- Excellent driving record (driving record check required)
- 2 years’ preferred experience with maintenance and construction (multi-unit experience preferred
` for prose - Do NOT repeat job title as heading (page already shows it) - 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 - 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 - Output ONLY the HTML fragment — no `/`, no markdown code fences 2. **Analyze the Job Posting Content:** Let me extract the relevant parts from the text provided: - Company: Palm Beach Tan - Role: Facilities Technician - Pay: "Starting at $25/hr. - $35/hr." (This is substantive, so Pay section should exist) - Description: "The Facilities Technician is responsible for all maintenance concerns for the stores in their assigned areas." - Ideal candidate experience: "experience with and an understanding of the demands of building maintenance in a multi-unit setting, and a basic understanding of building maintenance systems." - Position: full-time, requires frequent travel, no specific office location, start day from home, travel to locations - Perks/benefits listed: - Overtime Opportunities - Company Car + Gas - Free Tanning, Product and Service Discounts - Generous Paid Time Off Plans - Paid holidays - Benefits Package - 401K with company matching - Responsibilities list: - Providing general maintenance to store locations throughout above-mentioned area - Repairing general items such as minor plumbing, light ballasts, doorknobs, etc. - Maintaining tanning booths and UV free spray booths (training provided) - General carpentry including sheetrock repair, painting - Working with store operations staff; communicating with store management and vendors - Requirements/Qualifications list: - Excellent driving record (driving record check required) - 2 years’ preferred experience with maintenance and constructions required (multi-unit experience preferred) - Basic understanding of building maintenance systems - Ability to manage multiple projects - Ability to work independently - Outstanding customer service skills - Willingness to work nights, weekends, holidays, and some overtime based on business needs - Ability to lift up to 50 pounds - EEO statement at the end: "Palm Beach Tan is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, national origin, disability status, protected Veteran status, or any other characteristic protected by law." -> This should be removed per rules: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate" - Also remove: "Here are some of the perks we offer:" seems like intro to benefits, but benefits are listed after. I'll capture the actual benefit items. - "Starting at $25/hr. - $35/hr." is pay info. - "This is a full-time position that requires frequent travel. This position does not have a specific office location. You will start your day from home, and travel to locations as needed to your assigned areas." -> This is prose/context, could go in About the role or a short intro paragraph. Now, map to allowed sections: - Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - I need to only include sections that have real, specific content. - Pay: "$25/hr. - $35/hr." -> include Pay section - Benefits: The list includes "Overtime Opportunities", "Company Car + Gas", "Free Tanning, Product and Service Discounts", "Generous Paid Time Off Plans", "Paid holidays", "Benefits Package", "401K with company matching". These are specific benefits. Should I use "Benefits" heading? Yes, but only if there's real content. There is. I'll list them. - Schedule: The posting mentions "full-time position that requires frequent travel", "Willingness to work nights, weekends, holidays, and some overtime based on business needs". There's no specific schedule structure like "9-to-5" or "shift times", but there is mention of work hours/patterns. The rule says: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Schedule is mentioned in terms of requirements ("Willingness to work nights, weekends, holidays, and some overtime"). I think I can include a Schedule section with that specific info, or fold it into Requirements/Qualifications. But the allowed headings include "Schedule". I'll check if there's actual schedule info beyond the flexibility/requirement language. It says "full-time position that requires frequent travel" and "Willingness to work nights, weekends, holidays, and some overtime based on business needs". That's more about work schedule expectations. I'll probably include a Schedule section with that specific phrasing, or maybe fold it into Requirements. To be safe, I'll see if the rule prefers "Prefer a few substantive sections over many thin ones." I'll only include Schedule if there's clear schedule info. The posting does state schedule expectations, so I'll include it briefly. - About the role: The posting has description, pay, location-flexible nature, travel requirements. I'll create an "About the role" section with the core description, pay mention, and work arrangement. - Responsibilities: list of duties - Requirements/Qualifications: The posting has both "Requirements" and "Experience" sections. The rules say use headings: "Requirements, Qualifications". I'll combine or separate? The list includes "Experience Excellent driving record..." and bullet points under "Responsibilities" and then "Experience" section. I'll likely use "Requirements" for the qualifications list, or "Qualifications". The allowed headings are "Requirements, Qualifications". I'll pick one or split if there's distinct content. Looking at the text: "Responsibilities" section lists duties. Then "Experience" section lists: "Excellent driving record (driving record check required)", "2 years’ preferred experience with maintenance and constructions required (multi-unit experience preferred)", "Basic understanding of building maintenance systems", "Ability to manage multiple projects", "Ability to work independently", "Outstanding customer service skills", "Willingness to work nights, weekends, holidays, and some overtime based on business needs", "Ability to lift up to 50 pounds". These are requirements/qualifications. I'll use "Requirements" heading for these, or "Qualifications". I'll check the exact allowed list: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". I can use both "Requirements" and "Qualifications" if there's distinct content, but it might be redundant. I'll probably use "Requirements" for the substantive list, and maybe "Skills" if there's a separate skills section. The posting doesn't have a clear "Skills" section separate from requirements. I'll stick to "Requirements" for the qualification bullets, and maybe "Skills" if I can extract something, but I'll avoid thin sections. Let me re-read the rules carefully: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It lists them as examples, not a mandate to use all. "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text... and never create Pay/Schedule/Benefits sections unless the posting actually states them." So I must only include sections that have real content.
Let's determine which sections have clear, specific content:
- About the role: Yes, has description, pay, work arrangement.
- Responsibilities: Yes, list of duties.
- Requirements or Qualifications: Yes, has specific requirements (driving record, experience, skills, physical abilities).
- Benefits: Yes, specific benefits listed.
- Pay: Yes, "$25/hr. - $35/hr."
- Schedule: Has "full-time", "frequent travel", "nights, weekends, holidays, some overtime". I'll include it with that specific phrasing, or maybe fold into Requirements. I think I'll include Schedule with the specific work schedule expectations mentioned.
- Skills: The posting has "Basic understanding of building maintenance systems", "Ability to manage multiple projects", "Ability to work independently", "Outstanding customer service skills". These could go under Skills or Requirements. I'll probably use Requirements for the hard requirements, and maybe Skills for the soft skills, but to avoid thin sections, I'll combine into one "Requirements" section, or use "Qualifications". The example headings include both "Requirements" and "Qualifications". I'll use "Requirements" for the list, and if there's extra, I'll see.
Actually, looking at the posting structure:
- "Responsibilities" heading then bullet points
- Then "Experience" heading? No, it says "Experience Excellent driving record..." etc. It's not a separate "Experience" section with dates, it's a list of requirements/experience needed. The text says: "Here are some of the perks we offer:" then benefits, then "Responsibilities Providing general maintenance..." then "Experience Excellent driving record...". So the posting has: Perks/benefits intro, Responsibilities, Experience/requirements.
I need to map this to the allowed headings while removing boilerplate (EEO statement at the end, "Palm Beach Tan is an Equal Opportunity Employer...").
Let me outline the HTML structure I'll create:
About the role
Palm Beach Tan, the industry leader in Sunbed and Spray Tanning, seeks a Facilities Technician responsible for all maintenance concerns across stores in their assigned areas. This is a full-time position requiring frequent travel; you will start your day from home and travel to locations as needed within your assigned areas. Starting pay is $25/hr. - $35/hr.
Responsibilities
- Providing general maintenance to store locations throughout the assigned area
- Repairing general items such as minor plumbing, light ballasts, doorknobs, etc.
- Maintaining tanning booths and UV-free spray booths (training provided)
- General carpentry including sheetrock repair and painting
- Working with store operations staff; communicating with store management and vendors
Requirements
- Excellent driving record (driving record check required)
- 2 years’ preferred experience with maintenance and construction (multi-unit experience preferred