Maintenance Technician
Arcan Capital · Decatur, GA · 1 mo ago
ManagementFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "Job Description" then "About Arcan Capital", "Key Responsibilities", "Qualifications & Skills", "Education & Experience (Preferred but Not Required)", "Why Join Arcan Capital?".
We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting has "About Arcan Capital" (company description). Could map to "About the role"? Actually "About the role" is generic; but we have "Job Description" paragraph describing role. Could use "About the role" heading for that paragraph. Then "Responsibilities" for Key Responsibilities. Then "Qualifications" maybe combine Qualifications & Skills and Education & Experience? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can include Qualifications and Skills separate? Probably better to have Qualifications (including Education & Experience) and Skills separate? But we have both Qualifications & Skills together. Could split: Qualifications heading for Education & Experience, Skills heading for Qualifications & Skills? However they said "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications & Skills into one section titled "Qualifications". Or we could have "Qualifications" and "Skills" as separate if content distinct. Let's see content:
Qualifications & Skills list:
- Must be at least 18 years old.
- Basic knowledge of HVAC, plumbing, electrical, carpentry, and mechanical systems.
- Strong customer service skills with a passion for assisting residents.
- Excellent communication, problem-solving, and interpersonal abilities.
- Ability to multitask, prioritize, and work efficiently in a fast-paced environment.
- Detail-oriented with strong organizational and time management skills.
- Willingness to work a flexible schedule, including on-call hours, weekends, and holidays.
Education & Experience (Preferred but Not Required):
- 1–3 years of prior maintenance experience, ideally in a similar facility.
- HVAC, EPA, and/or CPO certifications are preferred.
- A valid driver's license and reliable transportation may be required, depending on property needs.
- High school diploma or equivalent is required.
Thus we could have two sections: "Qualifications" (maybe covering the skill list) and "Education & Experience". But the instruction says use headings like Qualifications, Skills. Could do Qualifications for education/experience, Skills for skill list. That seems reasonable.
Benefits: The posting includes "Why Join Arcan Capital?" with bullet points: Supportive and people-focused culture, Opportunities for growth, Competitive compensation & benefits, including medical, dental, vision, two weeks paid vacation,5 days of PTO/Sick leave, matching 401k program and more! That's benefits info. So we can have a Benefits section.
Pay: Not specified. So we should NOT include Pay section.
Schedule: Not explicitly stated aside from willingness to work flexible schedule, on-call, weekends, holidays. That's more about schedule but not explicit schedule details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule: they mention willingness to work flexible schedule, including on-call hours, weekends, and holidays. That's somewhat schedule info but not a defined schedule. Might be considered schedule info. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule expectations (flexible schedule, on-call, weekends, holidays). So we could include a Schedule section with that info. But we already have schedule info in Skills/Willingness to work flexible schedule. Might be redundant. Better to keep schedule info under Skills or Qualifications? The instruction: prefer few substantive sections over many thin ones. So maybe we omit Schedule section and keep that info under Skills or Qualifications.
Thus sections: About the role (intro paragraph), Responsibilities (Key Responsibilities), Qualifications (Education & Experience), Skills (Qualifications & Skills), Benefits (Why Join Arcan Capital?). Also maybe About Arcan Capital could be under About the role? Actually About the role is separate from About Arcan Capital. The intro paragraph under Job Description describes role. Then there is "About Arcan Capital" separate. Could we combine both under About the role? Might be better to have About the role (role description) and About the company (maybe not required heading). But headings list does not include About the company. Could we omit About Arcan Capital? It's substantive info about company; we could include it under About the role? Or we could create a section "About Arcan Capital" but not in allowed headings list. The instruction: use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. The posting has "About Arcan Capital" (company description). Could map to "About the role"? Actually "About the role" is generic; but we have "Job Description" paragraph describing role. Could use "About the role" heading for that paragraph. Then "Responsibilities" for Key Responsibilities. Then "Qualifications" maybe combine Qualifications & Skills and Education & Experience? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We can include Qualifications and Skills separate? Probably better to have Qualifications (including Education & Experience) and Skills separate? But we have both Qualifications & Skills together. Could split: Qualifications heading for Education & Experience, Skills heading for Qualifications & Skills? However they said "Prefer a few substantive sections over many thin ones." So maybe combine Qualifications & Skills into one section titled "Qualifications". Or we could have "Qualifications" and "Skills" as separate if content distinct. Let's see content:
Qualifications & Skills list:
- Must be at least 18 years old.
- Basic knowledge of HVAC, plumbing, electrical, carpentry, and mechanical systems.
- Strong customer service skills with a passion for assisting residents.
- Excellent communication, problem-solving, and interpersonal abilities.
- Ability to multitask, prioritize, and work efficiently in a fast-paced environment.
- Detail-oriented with strong organizational and time management skills.
- Willingness to work a flexible schedule, including on-call hours, weekends, and holidays.
Education & Experience (Preferred but Not Required):
- 1–3 years of prior maintenance experience, ideally in a similar facility.
- HVAC, EPA, and/or CPO certifications are preferred.
- A valid driver's license and reliable transportation may be required, depending on property needs.
- High school diploma or equivalent is required.
Thus we could have two sections: "Qualifications" (maybe covering the skill list) and "Education & Experience". But the instruction says use headings like Qualifications, Skills. Could do Qualifications for education/experience, Skills for skill list. That seems reasonable.
Benefits: The posting includes "Why Join Arcan Capital?" with bullet points: Supportive and people-focused culture, Opportunities for growth, Competitive compensation & benefits, including medical, dental, vision, two weeks paid vacation,5 days of PTO/Sick leave, matching 401k program and more! That's benefits info. So we can have a Benefits section.
Pay: Not specified. So we should NOT include Pay section.
Schedule: Not explicitly stated aside from willingness to work flexible schedule, on-call, weekends, holidays. That's more about schedule but not explicit schedule details. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule: they mention willingness to work flexible schedule, including on-call hours, weekends, and holidays. That's somewhat schedule info but not a defined schedule. Might be considered schedule info. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state schedule expectations (flexible schedule, on-call, weekends, holidays). So we could include a Schedule section with that info. But we already have schedule info in Skills/Willingness to work flexible schedule. Might be redundant. Better to keep schedule info under Skills or Qualifications? The instruction: prefer few substantive sections over many thin ones. So maybe we omit Schedule section and keep that info under Skills or Qualifications.
Thus sections: About the role (intro paragraph), Responsibilities (Key Responsibilities), Qualifications (Education & Experience), Skills (Qualifications & Skills), Benefits (Why Join Arcan Capital?). Also maybe About Arcan Capital could be under About the role? Actually About the role is separate from About Arcan Capital. The intro paragraph under Job Description describes role. Then there is "About Arcan Capital" separate. Could we combine both under About the role? Might be better to have About the role (role description) and About the company (maybe not required heading). But headings list does not include About the company. Could we omit About Arcan Capital? It's substantive info about company; we could include it under About the role? Or we could create a section "About Arcan Capital" but not in allowed headings list. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exhaustive. So we could use other headings if appropriate, but better to stick to given examples. However we could treat About Arcan Capital as part of About the role? Might be okay.
But we need to preserve ALL substantive information. If we omit About Arcan Capital, we lose info. So we need to include it somewhere. Could use a heading like "About Arcan Capital" as . The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, just gives examples. So we can use About Arcan Capital heading.
Thus final sections:
About the role
. The instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, just gives examples. So we can use About Arcan Capital heading.
Thus final sections:
About the role
About the role
... (Job Description paragraph)
About Arcan Capital
... (company description)
Responsibilities
- ... each responsibility
Qualifications
- ... education/experience items
Skills
- ... skill items
Benefits
- ... benefits items
About the role
Arcan Capital is committed to providing an exceptional living experience for our residents by ensuring