Regional Service Technician

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Use

for headings. Use

• for lists. Use

  for prose. We need to extract content. Job description includes: - Overview: "We are a dynamic Property Management company dedicated to serving our tenants and managing a diverse portfolio of properties. We focus on creating value to Property management and maintenance through innovative strategies, operational excellence, and strong tenant relationships." That's about company. - Position Overview: "We are seeking dependable and skilled Multifamily Maintenance Service Technicians I and II to join our growing regional maintenance team. These positions complete resident service requests, prepare vacant apartments for new residents, perform preventive maintenance, care for property grounds, and help keep our apartment communities safe, clean, and fully operational. Applicants will be considered for either the Service Technician I or Service Technician II position based on experience, technical skills, certifications, and ability to work independently. We are a growing housing provider working toward becoming the largest provider of quality workforce housing in Indiana. This is an opportunity to join during an important stage of growth, help shape a high-performing maintenance operation, and build a long-term career with training, increased responsibility, and advancement potential." - How Our Regional Maintenance Team Works: description of hub model, meeting location, travel, driver's license, etc. - Our S T A B L E Core Values: list of values with explanations. - Service Technician Levels: description of I and II. - Primary Responsibilities: bullet list. - Required Qualifications: bullet list. - Preferred Qualifications: bullet list. - Physical Requirements: bullet list. - Compensation & Benefits: "Competitive pay based on experience and qualifications, along with an employee rent discount and a generous Paid Time Off policy." We need to decide sections. We have content for About the role (company overview + position overview). Could be "About the role". Could also include "How Our Regional Maintenance Team Works" maybe part of role. Responsibilities: we have Primary Responsibilities list. Requirements: maybe Required Qualifications. Qualifications: maybe Preferred Qualifications. Skills: maybe combine required/preferred? But we can have Skills section for things like "Ability to use smartphone", "Professional communication", etc. However we already have Required Qualifications includes many skill-like items. Could split. Benefits: we have Compensation & Benefits includes pay and benefits. Pay: "Competitive pay based on experience and qualifications". Benefits: employee rent discount, generous PTO. Schedule: maybe mention on-call rotation, some evenings, weekends, holidays. Also mention rotating on-call schedule. So we can have Schedule section. We must not create sections with filler like "commensurate with experience". Pay section: we have "Competitive pay based on experience and qualifications". That's specific enough? It's not a number but it's a statement. The instruction says: 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. "Competitive pay based on experience and qualifications" is not a placeholder like "commensurate with experience"? It's similar but maybe acceptable as it's actual statement. It's not a specific number but it's a statement. I'd include Pay section with that sentence. Benefits: we have employee rent discount and generous Paid Time Off policy. That's specific. Schedule: we have rotating on-call schedule, including some evenings, weekends, and holidays. Also mention must be able to report reliably to designated daily meeting location. That's schedule-related. So we can include Schedule. Now we need to avoid duplication. Also we must not include boilerplate like EEO etc. Not present. We need to output only HTML fragment. Let's craft sections:

  About the role

  We are a dynamic Property Management company dedicated to serving our tenants and managing a diverse portfolio of properties. We focus on creating value to property management and maintenance through innovative strategies, operational excellence, and strong tenant relationships. We are seeking dependable and skilled Multifamily Maintenance Service Technicians I and II to join our growing regional maintenance team. These positions complete resident service requests, prepare vacant apartments for new residents, perform preventive maintenance, care for property grounds, and help keep our apartment communities safe, clean, and fully operational. Applicants will be considered for either the Service Technician I or Service Technician II position based on experience, technical skills, certifications, and ability to work independently. We are a growing housing provider working toward becoming the largest provider of quality workforce housing in Indiana. This is an opportunity to join during an important stage of growth, help shape a high-performing maintenance operation, and build a long-term career with training, increased responsibility, and advancement potential.

  Maybe also include how team works: Could be part of About the role or separate section "How the team works". But we only have allowed headings list; we could add a section like "How the team works" but not in list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It implies we should use those headings only. So we should not create other headings. So we must fit all content under those headings. Thus we need to incorporate "How Our Regional Maintenance Team Works" and core values etc into those sections. We could put team work description under About the role or Responsibilities? Probably About the role includes overview of role and work environment. Core values could be part of About the role as well. Service Technician Levels could be part of Requirements or Qualifications. Let's structure: About the role: company overview, position overview, team work model, core values, service technician levels. Responsibilities: Primary Responsibilities list. Requirements: Required Qualifications list. Qualifications: Preferred Qualifications list. Skills: maybe we can extract skill-specific items from required/preferred like "Ability to use a smartphone or mobile device", "Professional communication and respectful resident-service skills", "Ability to work independently while also contributing as part of a team", "Dependable attendance". But those are already in Required Qualifications. Could still list them under Skills. But we must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication but better to avoid duplication. However we can split. Maybe better: Use Required Qualifications as Requirements, Preferred Qualifications as Qualifications, and Skills for things like "Ability to use smartphone", "Professional communication", "Ability to work independently", "Dependable attendance". But those are already in Required Qualifications; splitting may cause duplication but still preserves all info. Might be okay. Alternatively, we could omit Skills section if no distinct skill content beyond what's in Requirements/Qualifications. But we have some skill-like items: "Ability to use a smartphone or mobile device to receive assignments, update work orders, enter notes, and upload photographs." That's a skill. "Professional communication and respectful resident-service skills." That's skill. "Ability to work independently while also contributing as part of a team." That's skill. "Dependable attendance and the ability to report to work on time and prepared." That's skill. Could put those under Skills. But then Required Qualifications would lose those items; we need to keep them somewhere. If we move them to Skills, we must remove from Requirements to avoid duplication. But the instruction says preserve ALL substantive information; we can relocate. It's okay as long as not lost. Thus we can define: Requirements: Previous experience in multifamily, apartment, residential, facilities, construction, or building maintenance. Working knowledge of common residential maintenance repairs. Reliable transportation to report to the designated daily meeting location. Valid driver's license and an acceptable driving record. Ability and willingness to work at multiple apartment communities and travel between assigned properties during the workday. Ownership of the basic hand tools and power tools needed to perform maintenance work. Specialty tools and specialized equipment will be provided as needed. Willingness and ability to participate in an on-call rotation. Ability to pass all employment-related screening requirements applicable to the position. Qualifications: Preferred Qualifications: EPA Section 608 certification, with Universal certification strongly preferred. Multifamily or apartment-maintenance experience. Experience diagnosing and repairing residential HVAC systems. Experience completing apartment turns and make-ready work. Familiarity with mobile work-order or property-management software. Additional trade certifications or formal maintenance training. Skills: Ability to use a smartphone or mobile device to receive assignments, update work orders, enter notes, and upload photographs. Professional communication and respectful resident-service skills. Ability to work independently while also contributing as part of a team. Dependable attendance and the ability to report to work on time and prepared. Physical Requirements maybe could be part of Requirements or Qualifications? But we have no heading for Physical Requirements. Could we include under Requirements? It's substantive. Could add a subsection under Requirements? But we only allowed headings list; we could still include a

  or

  under Requirements for physical requirements. That's fine. Thus Requirements will include both qualifications and physical requirements. But we already have Requirements list; we can add physical requirements as another
  under same heading. Similarly, Benefits: employee rent discount and generous Paid Time Off policy. Pay: Competitive pay based on experience and qualifications. Schedule: Participate in a rotating on-call schedule, including some evenings, weekends, and holidays. Also must be able to report reliably to the designated daily meeting location each morning for a brief team huddle, daily priorities, and work assignments. That's schedule. Now we need to ensure we don't create sections with filler. All have content. Now produce HTML. We'll need to wrap each section:

  Heading

  then content. For lists:
  • ...
  For prose:

  ...

  We must not include any extra text outside HTML. Let's craft. About the role: combine company overview, position overview, team work model, core values, service technician levels. We need to be careful not to make it too long but preserve all specifics. Let's draft:

  We are a dynamic Property Management company dedicated to serving our tenants and managing a diverse portfolio of properties. We focus on creating value to property management and maintenance through innovative strategies, operational excellence, and strong tenant relationships. We are seeking dependable and skilled Multifamily Maintenance Service Technicians I and II to join our growing regional maintenance team. These positions complete resident service requests, prepare vacant apartments for new residents, perform preventive maintenance, care for property grounds, and help keep our apartment communities safe, clean, and fully operational. Applicants will be considered for either the Service Technician I or Service Technician II position based on experience, technical skills, certifications, and ability to work independently. We are a growing housing provider working toward becoming the largest provider of quality workforce housing in Indiana. This is an opportunity to join during an important stage of growth, help shape a high-performing maintenance operation, and build a long-term career with training, increased responsibility, and advancement potential.

  Our regional maintenance team operates a centralized, hub‑style model. Team members report to a designated meeting location each morning for a brief team huddle, daily priorities, and work assignments, then travel to multiple apartment communities throughout the region to complete service requests, apartment turns, preventive maintenance, grounds work, and other assigned priorities. Because assignments may change based on resident needs and operational priorities, technicians must be comfortable working at multiple properties and moving between communities during the workday. Transportation arrangements may vary by assignment and available company vehicles. All technicians must be able to report reliably to the designated daily meeting location and must hold a valid driver's license with an acceptable driving record.

  Our S T A B L E Core Values guide how we serve residents, protect our properties, and support one another:

  • S – Show Up and Own It: