Maintenance Supervisor

We need to output HTML fragment with sections: About the role? The posting includes "Why Highmark Residential?" and "Why we need you:" and "What Highmark can do for YOU:" which are like benefits and intro. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We need to parse the posting: - Location: Spring Harbor (metadata, maybe minor, can be in a short

or drop). Not a heading. - "Why Highmark Residential? Because every position is considered critical to Highmark’s success and reputation, we take care to employ those who aspire to become the best in their field. Those who succeed at Highmark will do so because they enjoy an empowered, challenging, fulfilling, and financially rewarding workplace!" This is about the company, could be "About the role"? Actually it's about the company. Could be "About the role" or maybe "Why Highmark Residential?" but we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put that under "About the role". It's substantive. - "Why we need you: The Maintenance Supervisor is responsible for organizing, directing and managing the overall maintenance and preservation of the Community." That's also about role, could be part of About the role. - "What Highmark can do for YOU: Help you achieve your goals by continuous professional development and regular career progression sessionsCompetitive pay for the marketMonthly bonus opportunities for all site associates30% associate rent discountMedical, Dental & Vision benefits the 1 st of the month following 30 days of full-time employmentCompany-provided life insurance, short term and long term disability coverageFlexible Spending accounts401(k) eligibility after 90 days, with 4% Highmark matchProfessional Certification & Tuition reimbursementVacation, Sick and Personal Time off available to use after 90 days10 paid holidaysPaid parental leave" That's benefits. So we can have a Benefits section with list items. - Then "Responsibilities This is what you’ll do: Directs and oversees maintenance staff and ensures all areas of the community are maintainedMonitors, supports and improves team performance by assisting with skill developmentMaintains proper inventory levels and orders supplies as neededWorks hands-on to ensure market-ready, occupied and preventative maintenance is performed accurately and in a timely mannerObtains bids and interacts with contractors and is knowledgeable of competitive pricing of suppliesWorks with Property Manager in managing community budget and expenditures in all areas of maintenance" We need to format as

• for list of duties. - Then "Qualifications We’re looking for you if: Interested in the aboveYou have leadership and team-building skillsExperience in apartment maintenanceYou strive for excellence Some things we can’t live without are: Five years of apartment management and supervisor experienceMust be able to direct, motivate, train and develop subordinatesType II A/C Certification or UniversalHigh school diploma or equivalentValid driver’s license #SE2M Req ID: 2026-10064" We need to separate Qualifications and maybe Requirements? The posting lumps qualifications. We could treat "Qualifications" as a heading and list items. We also have "Skills" maybe not explicit; we could omit if no specific. Pay: The posting mentions "Competitive pay for the market" but that's vague; we should not create Pay section unless posting actually states them. It says "Competitive pay for the market" which is vague but still states pay? It says competitive pay for the market - not a specific number. According to rule: 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 for the market" is somewhat vague but still states that pay is competitive. Is that considered filler? It's not a specific number, but it's a statement about pay. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive pay for the market". That is a statement about pay, albeit vague. Should we include Pay section? The rule also says "Prefer a few substantive sections over many thin ones." Might be better to include Pay as part of Benefits? But Benefits already includes many items; pay could be separate. However the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay, so we could include Pay section with that statement. But we need to avoid filler like "commensurate with experience". "Competitive pay for the market" is somewhat generic but still a statement. I'd include Pay section with a

  stating that. Schedule: Not mentioned, so omit. Skills: Not explicitly listed; we could omit. Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay. We need to use

  for each heading. We need to use

  • for any list of duties/requirements/benefits. We need to use

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading; we won't. We need to not put Job ID/requisition numbers as headings; we can fold minor metadata into a short

    or drop it. The location and Req ID can be in a short

    maybe at top. We need to output only HTML fragment. Let's craft:

    Location: Spring Harbor

    Req ID: 2026-10064

    Then

    About the role

    with paragraphs combining the why highmark and why we need you. We need to preserve all substantive information: The why highmark text: "Because every position is considered critical to Highmark’s success and reputation, we take care to employ those who aspire to become the best in their field. Those who succeed at Highmark will do so because they enjoy an empowered, challenging, fulfilling, and financially rewarding workplace!" plus the introductory sentence "Why Highmark Residential?". We also have "Why we need you: The Maintenance Supervisor is responsible for organizing, directing and managing the overall maintenance and preservation of the Community." We'll combine into maybe two

    elements. Then

    Responsibilities

    with
    • each duty. Duties list: - Directs and oversees maintenance staff and ensures all areas of the community are maintained - Monitors, supports and improves team performance by assisting with skill development - Maintains proper inventory levels and orders supplies as needed - Works hands-on to ensure market-ready, occupied and preventative maintenance is performed accurately and in a timely manner - Obtains bids and interacts with contractors and is knowledgeable of competitive pricing of supplies - Works with Property Manager in managing community budget and expenditures in all areas of maintenance We need to preserve the exact phrasing; ensure no missing punctuation. Then

      Qualifications

      with list. Qualifications text: "We’re looking for you if: Interested in the aboveYou have leadership and team-building skillsExperience in apartment maintenanceYou strive for excellence Some things we can’t live without are: Five years of apartment management and supervisor experienceMust be able to direct, motivate, train and develop subordinatesType II A/C Certification or UniversalHigh school diploma or equivalentValid driver’s license" We need to split into items. The posting seems to have two parts: "We’re looking for you if:" then bullet-like items: Interested in the above, You have leadership and team-building skills, Experience in apartment maintenance, You strive for excellence. Then "Some things we can’t live without are:" then items: Five years of apartment management and supervisor experience, Must be able to direct, motivate, train and develop subordinates, Type II A/C Certification or Universal, High school diploma or equivalent, Valid driver’s license. We'll combine all into a list. Then

      Benefits

      with list. Benefits text: "Help you achieve your goals by continuous professional development and regular career progression sessionsCompetitive pay for the marketMonthly bonus opportunities for all site associates30% associate rent discountMedical, Dental & Vision benefits the 1 st of the month following 30 days of full-time employmentCompany-provided life insurance, short term and long term disability coverageFlexible Spending accounts401(k) eligibility after 90 days, with 4% Highmark matchProfessional Certification & Tuition reimbursementVacation, Sick and Personal Time off available to use after 90 days10 paid holidaysPaid parental leave" We need to split into items. The text seems to be concatenated without spaces. We need to parse logically: - Help you achieve your goals by continuous professional development and regular career progression sessions - Competitive pay for the market - Monthly bonus opportunities for all site associates - 30% associate rent discount - Medical, Dental & Vision benefits the 1st of the month following 30 days of full-time employment - Company-provided life insurance, short term and long term disability coverage - Flexible Spending accounts - 401(k) eligibility after 90 days, with 4% Highmark match - Professional Certification & Tuition reimbursement - Vacation, Sick and Personal Time off available to use after 90 days - 10 paid holidays - Paid parental leave We'll make each a
    • . Then

      Pay

      with

      Competitive pay for the market

      (maybe we already included that in benefits; but we have it as separate Pay section. However we already listed "Competitive pay for the market" as a benefit item. To avoid duplication, we could either keep it only in Benefits or only in Pay. The rule says preserve ALL substantive information; we must not lose info. If we put it in Benefits list, we still have the info. If we also make a Pay section, we would duplicate. Better to keep it only once. Since Benefits section already includes many items, we could keep Competitive pay for the market as part of Benefits list. Then we would not need a separate Pay section. The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state competitive pay, but we already have it in Benefits. However the instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we could have a Pay section. But we also must not create thin sections. If we put pay in Benefits, we avoid a thin Pay section. The rule: "Prefer a few substantive sections over many thin ones." So better to not create a Pay section if we can incorporate pay into Benefits. However the rule also says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't forbid putting pay info in Benefits section. So we can omit Pay section. Thus sections: About the role, Responsibilities, Qualifications, Benefits. We need to ensure we include all info: location and req ID as short p. Now craft HTML. Check for any missing info: The posting also had "Why Highmark Residential? Because every position is considered critical to Highmark’s success and reputation, we take care to employ those who aspire to become the best in their field. Those who succeed at Highmark will do so because they enjoy an empowered, challenging, fulfilling, and financially rewarding workplace!" We need to keep that exactly. Also "Why we need you: The Maintenance Supervisor is responsible for organizing, directing and managing the overall maintenance and preservation of the Community." We'll put those as two paragraphs under