Maintenance I
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use - for lists,
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
- Preserve ALL substantive information
- Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions)
- Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")
- Never create Pay/Schedule/Benefits sections unless posting actually states them
- Prefer few substantive sections over many thin ones
- Output ONLY HTML fragment — no /, no markdown code fences
Now, let's parse the content:
First paragraph: "Are you looking for a company that offers outstanding benefits including medical, dental, vision, short-term and long-term disability as well as tuition discounts and more than 2 ½ weeks of time off in the first year? Have you been looking for a company where you will get a consistent number of hours and competitive wages with opportunities for advancement and growth? Look no further than the Fellowship Square Christian Care Companies with 6 current locations in Arizona."
This describes benefits, hours, wages, advancement, company info. This could be "Benefits" and maybe "About the role" or "Company". But the rule says only include sections when there's real specific content. The benefits are listed specifically: medical, dental, vision, short-term and long-term disability, tuition discounts, more than 2.5 weeks time off first year. Also consistent hours, competitive wages, opportunities for advancement and growth. That's substantive. So we can have a Benefits section. Also maybe a "About the role" or "Company" section? The rule says headings like "About the role". The first paragraph is promotional but includes specific benefits. I think we can create a "Benefits" section with those details. Also maybe a "Schedule" section? It says "consistent number of hours" but not specific schedule. Could be a "Schedule" section with that phrase. But rule: never create Schedule section unless posting actually states them. It states "consistent number of hours". That's a schedule detail. Could include. But maybe better to fold into Benefits or a "Work Environment" section? The allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Benefits" and "Schedule" if they have content.
Second paragraph: "Job Description Perform routine maintenance and repair on the facility and equipment to include plumbing, plastering, electrical, carpentry, mechanical etc., as directed, in accordance with established procedures. Perform routine maintenance and repair on the facility and equipment. Respond to emergency housekeeping calls to clean spills, empty trash, or other duties as necessary. Follow all established safety procedures and precautions when performing maintenance service."
This is responsibilities. Some duplication: "Perform routine maintenance and repair on the facility and equipment" appears twice. We should deduplicate. We'll list unique duties.
Third paragraph: "Minimum of 1 year experience in plumbing, electrical, carpentry, and painting. Must be able to lift at least 50 lbs. Must be able to work well with others. Must be able to read, write, and speak the English language. Minimum of 18 years of age. Minimum of HS diploma or GED."
These are requirements/qualifications. Could be "Requirements" or "Qualifications". The rule says headings: Requirements, Qualifications. We can combine into one section "Requirements" or "Qualifications". Since they are minimum qualifications, maybe "Qualifications". But "Requirements" is also allowed. I'll use "Requirements" as it's a list of must-haves.
Now, we need to decide on sections:
1. Benefits: includes medical, dental, vision, short-term and long-term disability, tuition discounts, more than 2.5 weeks time off first year, consistent hours, competitive wages, opportunities for advancement and growth. Also company name and locations (6 locations in Arizona). That's substantive.
2. Responsibilities: list of duties.
3. Requirements: list of qualifications.
We should not include Pay section because "competitive wages" is vague, not specific pay. The rule says never create Pay section unless posting actually states them. "Competitive wages" is not specific. So no Pay section.
Schedule: "consistent number of hours" is mentioned. Could be a Schedule section with that phrase. But maybe it's better to include in Benefits or a separate Schedule section. Since the rule says include section only when real specific content. "Consistent number of hours" is a schedule detail. I'll include a Schedule section with that.
But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine schedule into Benefits? But Benefits is for benefits. Schedule is separate. I'll include Schedule.
Now, structure:
-
Benefits
- ... each benefit ...
Also include company info? The company name and locations could be in a "About the role" or "Company" section. But the rule says headings like "About the role". Could create "About the role" with a paragraph describing the company. However, the first paragraph is promotional. We can fold company info into a short paragraph under "About the role". But the rule says do NOT repeat job title as heading. The job title is not given in the text. The user didn't provide a job title. The posting starts with "Are you looking for a company...". So we don't have a job title. We can ignore.
Maybe we can have an "About the role" section with a paragraph summarizing the company and the role? But the posting doesn't have a clear "About the role" section. The first paragraph is about company benefits. The second is job description. The third is requirements.
I think we can have:
- Benefits
with list of benefits.
- Schedule
with "Consistent number of hours" (maybe also "competitive wages" but that's pay).
- Responsibilities
with list of duties.
- Requirements
with list of qualifications.
But "competitive wages" is pay-related. Could be a Pay section? But it's not specific. The rule says never create Pay section unless posting actually states them. "Competitive wages" is not a specific pay figure. So omit Pay section.
Alternatively, we could include "competitive wages" in Benefits? Not exactly a benefit. Could be in a "Compensation" but not allowed heading. So maybe drop.
Let's list benefits specifically:
- Medical, dental, vision insurance
- Short-term and long-term disability
- Tuition discounts
- More than 2½ weeks of time off in the first year
- Consistent number of hours
- Opportunities for advancement and growth
- 6 locations in Arizona (company info)
But "6 locations in Arizona" is company info, not a benefit. Could be in "About the role". I'll create an "About the role" section with a paragraph: "Fellowship Square Christian Care Companies operates 6 locations in Arizona." But the rule says include section only when real specific content. That's specific. However, the heading "About the role" might be appropriate. The rule says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" is allowed.
But the first paragraph is a promotional question. We can rephrase as a paragraph.
Let's decide on sections:
1. About the role: company description and role overview? The posting doesn't have an explicit overview. The first paragraph is about company benefits. The second is job description. The third is requirements. There's no "About the role" paragraph. But we can create a short paragraph from the first sentence: "Fellowship Square Christian Care Companies offers outstanding benefits and operates 6 locations in Arizona." That's minor metadata. The rule says fold minor metadata into a short
or drop it. So maybe we can drop the company info or include in Benefits.
I think we can have:
- Benefits section with list of benefits (including time off, insurance, tuition discounts, consistent hours, advancement opportunities).
- Responsibilities section with list of duties.
- Requirements section with list of qualifications.
That's three substantive sections. No Schedule, Pay, etc.
But "consistent number of hours" is a schedule detail. Could be a separate Schedule section with one bullet. That might be thin. The rule says prefer few substantive sections over many thin ones. So maybe include "Consistent number of hours" in Benefits list? It's not a benefit per se, but a work condition. Could be in a "Work Environment" but not allowed heading. So maybe include in Benefits as a bullet.
Similarly, "competitive wages" could be in Benefits? Not really.
I'll include "Consistent number of hours" and "Opportunities for advancement and growth" in Benefits list.
Now, let's write HTML.
We need to output only HTML fragment, no markdown fences.
We'll use
for headings, - for lists,
for prose.
We'll deduplicate responsibilities: "Perform routine maintenance and repair on the facility and equipment to include plumbing, plastering, electrical, carpentry, mechanical etc., as directed, in accordance with established procedures." and "Perform routine maintenance and repair on the facility and equipment." are duplicate. We'll keep the more detailed one.
Also "Respond to emergency housekeeping calls to clean spills, empty trash, or other duties as necessary." and "Follow all established safety procedures and precautions when performing maintenance service."
So responsibilities list:
- Perform routine maintenance and repair on the facility and equipment, including plumbing, plastering, electrical, carpentry, and mechanical systems, as directed and in accordance with established procedures.
- Respond to emergency housekeeping calls to clean spills, empty trash, or perform other duties as necessary.
- Follow all established safety procedures and precautions when performing maintenance service.
Requirements list:
- Minimum of 1 year experience in plumbing, electrical, carpentry, and painting.
- Ability to lift at least 50 lbs.
- Ability to work well with others.
- Ability to read, write, and speak English.
- Minimum age of 18 years.
- High school diploma or GED.
Benefits list:
- Medical, dental, and vision insurance
- Short-term and long-term disability coverage
- Tuition discounts
- More than 2½ weeks of paid time off in the first year
- Consistent number of hours
- Opportunities for advancement and growth
- Employment with Fellowship Square Christian Care Companies (6 locations in Arizona)
But the company name and locations might be better as a paragraph. However, the rule says use
- for any list of duties/requirements/benefits. Benefits are a list. So we can list them.
Now, we need to ensure we don't include any boilerplate. The text doesn't have EEO, etc.
Now, write HTML.
We'll order sections: Benefits, Responsibilities, Requirements. Or maybe Responsibilities first? The rule doesn't specify order. Typically job postings have Responsibilities then Requirements. But Benefits first is okay. I'll follow the order in the posting: Benefits (first paragraph), Responsibilities (Job Description), Requirements (Minimum...).
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 - Preserve ALL substantive information - Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions) - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") - Never create Pay/Schedule/Benefits sections unless posting actually states them - Prefer few substantive sections over many thin ones - Output ONLY HTML fragment — no /, no markdown code fences Now, let's parse the content: First paragraph: "Are you looking for a company that offers outstanding benefits including medical, dental, vision, short-term and long-term disability as well as tuition discounts and more than 2 ½ weeks of time off in the first year? Have you been looking for a company where you will get a consistent number of hours and competitive wages with opportunities for advancement and growth? Look no further than the Fellowship Square Christian Care Companies with 6 current locations in Arizona." This describes benefits, hours, wages, advancement, company info. This could be "Benefits" and maybe "About the role" or "Company". But the rule says only include sections when there's real specific content. The benefits are listed specifically: medical, dental, vision, short-term and long-term disability, tuition discounts, more than 2.5 weeks time off first year. Also consistent hours, competitive wages, opportunities for advancement and growth. That's substantive. So we can have a Benefits section. Also maybe a "About the role" or "Company" section? The rule says headings like "About the role". The first paragraph is promotional but includes specific benefits. I think we can create a "Benefits" section with those details. Also maybe a "Schedule" section? It says "consistent number of hours" but not specific schedule. Could be a "Schedule" section with that phrase. But rule: never create Schedule section unless posting actually states them. It states "consistent number of hours". That's a schedule detail. Could include. But maybe better to fold into Benefits or a "Work Environment" section? The allowed headings are limited: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "Benefits" and "Schedule" if they have content. Second paragraph: "Job Description Perform routine maintenance and repair on the facility and equipment to include plumbing, plastering, electrical, carpentry, mechanical etc., as directed, in accordance with established procedures. Perform routine maintenance and repair on the facility and equipment. Respond to emergency housekeeping calls to clean spills, empty trash, or other duties as necessary. Follow all established safety procedures and precautions when performing maintenance service." This is responsibilities. Some duplication: "Perform routine maintenance and repair on the facility and equipment" appears twice. We should deduplicate. We'll list unique duties. Third paragraph: "Minimum of 1 year experience in plumbing, electrical, carpentry, and painting. Must be able to lift at least 50 lbs. Must be able to work well with others. Must be able to read, write, and speak the English language. Minimum of 18 years of age. Minimum of HS diploma or GED." These are requirements/qualifications. Could be "Requirements" or "Qualifications". The rule says headings: Requirements, Qualifications. We can combine into one section "Requirements" or "Qualifications". Since they are minimum qualifications, maybe "Qualifications". But "Requirements" is also allowed. I'll use "Requirements" as it's a list of must-haves. Now, we need to decide on sections: 1. Benefits: includes medical, dental, vision, short-term and long-term disability, tuition discounts, more than 2.5 weeks time off first year, consistent hours, competitive wages, opportunities for advancement and growth. Also company name and locations (6 locations in Arizona). That's substantive. 2. Responsibilities: list of duties. 3. Requirements: list of qualifications. We should not include Pay section because "competitive wages" is vague, not specific pay. The rule says never create Pay section unless posting actually states them. "Competitive wages" is not specific. So no Pay section. Schedule: "consistent number of hours" is mentioned. Could be a Schedule section with that phrase. But maybe it's better to include in Benefits or a separate Schedule section. Since the rule says include section only when real specific content. "Consistent number of hours" is a schedule detail. I'll include a Schedule section with that. But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine schedule into Benefits? But Benefits is for benefits. Schedule is separate. I'll include Schedule. Now, structure: -
Benefits
- ... each benefit ...
Benefits
with list of benefits. -Schedule
with "Consistent number of hours" (maybe also "competitive wages" but that's pay). -Responsibilities
with list of duties. -Requirements
with list of qualifications. But "competitive wages" is pay-related. Could be a Pay section? But it's not specific. The rule says never create Pay section unless posting actually states them. "Competitive wages" is not a specific pay figure. So omit Pay section. Alternatively, we could include "competitive wages" in Benefits? Not exactly a benefit. Could be in a "Compensation" but not allowed heading. So maybe drop. Let's list benefits specifically: - Medical, dental, vision insurance - Short-term and long-term disability - Tuition discounts - More than 2½ weeks of time off in the first year - Consistent number of hours - Opportunities for advancement and growth - 6 locations in Arizona (company info) But "6 locations in Arizona" is company info, not a benefit. Could be in "About the role". I'll create an "About the role" section with a paragraph: "Fellowship Square Christian Care Companies operates 6 locations in Arizona." But the rule says include section only when real specific content. That's specific. However, the heading "About the role" might be appropriate. The rule says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So "About the role" is allowed. But the first paragraph is a promotional question. We can rephrase as a paragraph. Let's decide on sections: 1. About the role: company description and role overview? The posting doesn't have an explicit overview. The first paragraph is about company benefits. The second is job description. The third is requirements. There's no "About the role" paragraph. But we can create a short paragraph from the first sentence: "Fellowship Square Christian Care Companies offers outstanding benefits and operates 6 locations in Arizona." That's minor metadata. The rule says fold minor metadata into a short
or drop it. So maybe we can drop the company info or include in Benefits. I think we can have: - Benefits section with list of benefits (including time off, insurance, tuition discounts, consistent hours, advancement opportunities). - Responsibilities section with list of duties. - Requirements section with list of qualifications. That's three substantive sections. No Schedule, Pay, etc. But "consistent number of hours" is a schedule detail. Could be a separate Schedule section with one bullet. That might be thin. The rule says prefer few substantive sections over many thin ones. So maybe include "Consistent number of hours" in Benefits list? It's not a benefit per se, but a work condition. Could be in a "Work Environment" but not allowed heading. So maybe include in Benefits as a bullet. Similarly, "competitive wages" could be in Benefits? Not really. I'll include "Consistent number of hours" and "Opportunities for advancement and growth" in Benefits list. Now, let's write HTML. We need to output only HTML fragment, no markdown fences. We'll use
for headings, - for lists,
for prose.
We'll deduplicate responsibilities: "Perform routine maintenance and repair on the facility and equipment to include plumbing, plastering, electrical, carpentry, mechanical etc., as directed, in accordance with established procedures." and "Perform routine maintenance and repair on the facility and equipment." are duplicate. We'll keep the more detailed one.
Also "Respond to emergency housekeeping calls to clean spills, empty trash, or other duties as necessary." and "Follow all established safety procedures and precautions when performing maintenance service."
So responsibilities list:
- Perform routine maintenance and repair on the facility and equipment, including plumbing, plastering, electrical, carpentry, and mechanical systems, as directed and in accordance with established procedures.
- Respond to emergency housekeeping calls to clean spills, empty trash, or perform other duties as necessary.
- Follow all established safety procedures and precautions when performing maintenance service.
Requirements list:
- Minimum of 1 year experience in plumbing, electrical, carpentry, and painting.
- Ability to lift at least 50 lbs.
- Ability to work well with others.
- Ability to read, write, and speak English.
- Minimum age of 18 years.
- High school diploma or GED.
Benefits list:
- Medical, dental, and vision insurance
- Short-term and long-term disability coverage
- Tuition discounts
- More than 2½ weeks of paid time off in the first year
- Consistent number of hours
- Opportunities for advancement and growth
- Employment with Fellowship Square Christian Care Companies (6 locations in Arizona)
But the company name and locations might be better as a paragraph. However, the rule says use
- for any list of duties/requirements/benefits. Benefits are a list. So we can list them.
Now, we need to ensure we don't include any boilerplate. The text doesn't have EEO, etc.
Now, write HTML.
We'll order sections: Benefits, Responsibilities, Requirements. Or maybe Responsibilities first? The rule doesn't specify order. Typically job postings have Responsibilities then Requirements. But Benefits first is okay. I'll follow the order in the posting: Benefits (first paragraph), Responsibilities (Job Description), Requirements (Minimum...).
for prose. We'll deduplicate responsibilities: "Perform routine maintenance and repair on the facility and equipment to include plumbing, plastering, electrical, carpentry, mechanical etc., as directed, in accordance with established procedures." and "Perform routine maintenance and repair on the facility and equipment." are duplicate. We'll keep the more detailed one. Also "Respond to emergency housekeeping calls to clean spills, empty trash, or other duties as necessary." and "Follow all established safety procedures and precautions when performing maintenance service." So responsibilities list: - Perform routine maintenance and repair on the facility and equipment, including plumbing, plastering, electrical, carpentry, and mechanical systems, as directed and in accordance with established procedures. - Respond to emergency housekeeping calls to clean spills, empty trash, or perform other duties as necessary. - Follow all established safety procedures and precautions when performing maintenance service. Requirements list: - Minimum of 1 year experience in plumbing, electrical, carpentry, and painting. - Ability to lift at least 50 lbs. - Ability to work well with others. - Ability to read, write, and speak English. - Minimum age of 18 years. - High school diploma or GED. Benefits list: - Medical, dental, and vision insurance - Short-term and long-term disability coverage - Tuition discounts - More than 2½ weeks of paid time off in the first year - Consistent number of hours - Opportunities for advancement and growth - Employment with Fellowship Square Christian Care Companies (6 locations in Arizona) But the company name and locations might be better as a paragraph. However, the rule says use
- for any list of duties/requirements/benefits. Benefits are a list. So we can list them. Now, we need to ensure we don't include any boilerplate. The text doesn't have EEO, etc. Now, write HTML. We'll order sections: Benefits, Responsibilities, Requirements. Or maybe Responsibilities first? The rule doesn't specify order. Typically job postings have Responsibilities then Requirements. But Benefits first is okay. I'll follow the order in the posting: Benefits (first paragraph), Responsibilities (Job Description), Requirements (Minimum...).