Community Manager

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: 1. Company Overview - this is prose about the company 2. Job Title: Community Manager - but the rule says NOT to repeat the job title as a heading since the page already shows it 3. About the role / Responsibilities - there's a description of the role and then "Essential Duties & Responsibilities" with subsections 4. Requirements / Qualifications - "Education/experience", "Physical Requirements", "License/equipment" 5. Benefits - mentioned in the compensation paragraph 6. Pay - "Salary Range: $24 per hour to $26 per hour" 7. Schedule - not explicitly stated but mentions overtime, weekends, night hours, on-call Rules: - Use

for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for lists - Use

  for prose - Do NOT repeat job title as heading - Do NOT put Job ID/requisition numbers as headings - 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 - never emit heading followed by filler/placeholder text - 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 Let me structure this: 1. Company Overview - prose, can be a

  or maybe a section with heading "About the company" but the rules say use specific headings like "About the role". The company overview is not one of the listed heading types. But it's substantive content. I could include it as a section with heading "About the company" but the rules only list specific headings. However, the rules say "e.g." so maybe other headings are allowed? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. But to be safe, I'll use the suggested ones where they fit. The posting has: - Company overview (prose) - Role description (prose) - Essential Duties & Responsibilities (with subsections: Personnel Management, Financial Management, Strategic Leasing Management, Administrative & Maintenance Management) - these are lists - Education/experience (list) - Physical Requirements (list) - License/equipment (list) - Compensation/benefits info (prose with salary range) I'll create sections: - About the role (for the initial description of Community Manager) - Responsibilities (for the Essential Duties & Responsibilities) - Requirements (for Education/experience, Physical Requirements, License/equipment) - Benefits (for the benefits mentioned) - Pay (for salary range) - Schedule (for the hours/on-call info) But note: The rules say "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state benefits, pay, and schedule (overtime, weekends, night hours, on-call). So I can include them. I need to fold minor metadata into a short

  or drop it. There's no Job ID. Now, let's write the HTML. I'll start with a

  for company overview? Or maybe a section "About the company" with

  ? The rules don't forbid other headings, but they give examples. I think it's okay to have a heading for company overview. But the instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say "only these". I'll include a heading "About the company" for the company overview. But the user might expect only those headings. However, the company overview is substantive. I'll include it as a section with heading "About the company". Alternatively, I could put the company overview in a

  without a heading. But it's a distinct section. I'll use

  About the company

  . Now, for the role description: "The Community Manager is responsible for overseeing the entire operations..." That's "About the role". Then "Essential Duties & Responsibilities" -> "Responsibilities". Then "Education/experience", "Physical Requirements", "License/equipment" -> "Requirements" (or "Qualifications"). The rules list both "Requirements" and "Qualifications". I'll use "Requirements". Then compensation paragraph includes benefits, pay, and schedule info. I'll split into Benefits, Pay, Schedule. Let's extract the benefits: "comprehensive total rewards package, which includes benefits (medical, dental, vision, life, accidental, and disability insurance), 401K with employer matching, and commission and performance bonuses, when applicable. Full-time employees also receive paid sick days and company holidays." Pay: "Salary Range: $24 per hour to $26 per hour" Schedule: "work overtime, weekends, and night hours (emergencies)" and "Must have reliable transportation due to the emergency on-call requirement." Also physical requirements mention schedule aspects. I'll create sections accordingly. Now, for lists: The duties are grouped under subheadings (Personnel Management, Financial Management, etc.). I could make each a sub-list with a heading? But the rules say use
  • for any list of duties/requirements/benefits. The subheadings are not in the allowed headings list. I could either make them

    or incorporate into list items. Since the rules only specify

    for section headings, I can use

    for subsections? But the output should be clean. I think I'll keep the subheadings as bold text within list items or as separate

    ? The instruction doesn't forbid other tags. But to keep it simple, I'll make each duty area a list item with a strong label, and then sub-items as nested lists? That might be too complex. The original has bullet points under each subheading. I'll create a list for each subheading, but the rules say use

    • for any list. I can have multiple
      under the Responsibilities section, each preceded by a

      or . However, the rules only mention

      for section headings. I'll use

      for sub-sections within Responsibilities. That should be fine. But the instruction: "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say not to use other heading levels. I'll use

      for the duty categories. Alternatively, I could make a single list with all duties, but they are categorized. I'll keep categories as

      and then

      for each. Now, for Education/experience: it's a list of bullet points. I'll make a
      under Requirements. Physical Requirements: also a list. License/equipment: a list. Benefits: list. Pay: just a sentence. Schedule: list or prose. Let's write. I'll output only the HTML fragment. Start with company overview:

      About the company

      Asset Living is a third-party management firm and a proven partner in fostering thriving communities nationwide. Founded in 1986, Asset Living has decades of experience delivering exceptional value to our partners. Since the beginning, our undeniable passion has driven our organic growth from a small property management firm to one of the most trusted allies in real estate. Asset Living's growing portfolio includes a multitude of properties across the country that span the multifamily, single-family home rentals, affordable housing, build-to-rent, active adult, and student housing divisions. Asset Living is a fast-growing company made up of talented individuals from diverse backgrounds that differentiate us and help us drive innovation and results for our clients and communities across the US. At Asset Living, we wholeheartedly believe 'Together We Lead, Together We Succeed'. We empower each other to lead by example, collaborate, and evolve – inspired by our belief that we can continually improve as individuals and as an organization. Together, we create an environment where every voice is heard, every idea is valued, and every individual experiences opportunities to grow as our company grows. When you join Asset Living, you become part of a dynamic team that thrives on unity, unique talents, and a universal culture of winning. Recognized as one of the nation's Best and Brightest Places to Work and ranked in the NMHC top 50 professionals, join Asset Living because of its reputation as the most trusted partner in real estate, workplace culture, and growth opportunities. Asset Living is a member of The Institute of Real Estate Management (IREM) and is recognized as an Accredited Management Organization (AMO). Together, we lead the way, and together, we achieve excellence in all that we do. Join a workplace where success is a collective journey and leadership is a shared responsibility.

      Then About the role:

      About the role

      The Community Manager is responsible for overseeing the entire operations of a housing community under the supervision of the Regional Manager. As a Community Manager, you will manage all phases of the operations, including personnel, leasing, maintenance, financial, administration & risk management. As an on-site leader, you will supervise all aspects of the property and staff to ensure compliance with Asset's policies and procedures, safety and fair housing guidelines, and liability concerns.

      Responsibilities:

      Responsibilities

      Personnel Management

      • Regular/daily onsite attendance is required
      • Use consistent techniques & company directives to screen, hire, train, coach, and develop on-site staff
      • Ensure the effectiveness of staff through ongoing training, coaching, counseling, and guidance in compliance with Asset training benchmarks
      • Complete weekly/daily office & maintenance staff schedules and assignments
      • Deal effectively and consistently with performance problems; document adequately, communicate with direct supervisor and HR, and terminate appropriately when necessary
      • Promote harmony and quality job performance of staff through support and effective leadership
      • Ensure staff compliance and consistency with Company policies and procedures

      Financial Management

      • Achieve the highest possible net operating income through the implementation of effective cost control and revenue & leasing improvement; identify trends and recommend strategies and adjustments
      • Develop yearly operating budgets/forecasts
      • Monitor the timely receipt and reconciliation of deposits, rent collections, and charges to ensure they are submitted on a timely basis
      • Monitor the timely receipt, reconciliation, and coding of all vendor invoices
      • Ensure property closeout is completed on time and ownership financial reports are accurate

      Strategic Leasing Management

      • Develop yearly marketing plan and utilize marketing strategies & systems
      • Ensure staff leasing techniques are effective in obtaining closure, follow-up procedures met, signing/documentation of leases, and reporting systems are accurate and up to date
      • Deal with resident complaints, concerns, and requests to ensure resident satisfaction
      • Develop and implement resident retention programs (i.e., resident functions, special promotions, monthly newsletter, etc.)
      • Effectively show, lease, and move in prospective residents

      Administrative & Maintenance Management

      • Ensure all administrative &