Assistant Community Manager

We need to produce HTML fragment with sections: About the role? Actually the posting includes "Why The Morgan Group?" (maybe About the company), "Morgan Core Values", "How does Morgan Group benefit you?" (Benefits), "What You'll Do" (Responsibilities), "Essential Job Functions" (list), "Non-Essential Job Functions", "Physical Requirements", "Vision Requirements", "Hearing, Speaking and Written Requirements", "Driving Requirements", "Working Environment", plus maybe "Skills" etc. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Also remove the Culture Index survey invitation? That's at top: "Want to interview with the hiring authority? Before applying, please complete our brief Culture Index survey.*** This helps us understand how you work best and ensures alignment with the role and our culture. Complete the Culture Index Survey". That's application instruction / boilerplate; remove. We need to keep substantive info: Why The Morgan Group? (company description), Morgan Core Values (list), How does Morgan Group benefit you? (benefits list), What You'll Do (Essential Job Functions description), Non-Essential Job Functions, Physical Requirements, Vision Requirements, Hearing, Speaking and Written Requirements, Driving Requirements, Working Environment. Also maybe "Advancement opportunitiesTrainingLow-cost Medical, Dental, Vision..." etc is benefits list. We must not create sections for Pay/Schedule unless present. Not present. We need to ensure we don't create sections with filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We need to use

  for each section heading. Use

  • for any list of duties/requirements/benefits. Use

    for prose. We need to decide which parts are lists: Core Values list (multiple bullet points). Benefits list (Advancement opportunities...). Essential Job Functions list (multiple bullet points). Non-Essential Job Functions (maybe just a sentence). Physical Requirements list (multiple). Vision Requirements list. Hearing, Speaking and Written Requirements list. Driving Requirements list. Working Environment list. We need to preserve all substantive info; we can't omit details. Must include all bullet points exactly as given? Probably we need to keep the content but can reformat as list items. We need to be careful not to duplicate lines. The posting includes repeated lines like "Assist the Community Manager..." etc. We'll keep them. We need to remove duplicated lines: maybe there are duplicates like "Assist the Community Manager with the service team." appears twice? Actually appears under Essential Job Functions: "Assist the Community Manager with the service team." then later "Assist the Community Manager to create and monitor the marketing for the community." Not duplicate. There's also "Assist the Community Manager in the management of the day to day operations..." etc. We'll just output as is. We need to ensure we don't include the Culture Index survey invitation. Let's extract sections: - Why The Morgan Group? (company description paragraph) - Morgan Core Values (list of values with descriptions) - How does Morgan Group benefit you? (benefits paragraph then list) - What You'll Do (maybe heading "Responsibilities" or "Essential Job Functions"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can also use other headings if they match content? The instruction: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those standard headings when appropriate. But we can also use other headings if they match? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to map sections to those headings. However the posting has sections like "Why The Morgan Group?" which is about company; could map to "About the role"? Actually "About the role" is about the job, not company. "Why The Morgan Group?" is about company culture/benefits. Could be "About the role"? Not exactly. But we could still use "About the role" heading for the company description? Might be okay. However the instruction says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests we should use those when appropriate. Safer to use those headings where they match content: we have Benefits, Responsibilities, Requirements (maybe Physical Requirements etc), Skills (maybe not explicit), Qualifications (maybe not). We have "Core Values" maybe could be under "About the role"? Not sure. Given the instruction: "Prefer a few substantive sections over many thin ones." So we could combine some. We need to include all substantive info. Could create sections: About the role (company description + core values?), Responsibilities (essential job functions), Requirements (physical, vision, hearing, driving, working environment), Benefits (benefits list). Also maybe "Skills" not present. We must not create sections with filler. Thus:

    About the role

    Why The Morgan Group? At The Morgan Group, we are more than our 70+ multifamily properties — we are a community built on people. We believe in treating everyone with respect and dignity, from our team members and partners to our residents, clients, subcontractors, and vendors. We strive to foster an inclusive environment where every idea, perspective, and contribution is valued, and where everyone feels heard and appreciated. Our Core Values are the foundation of our success — they guide how we hire, reward, and evaluate every member of the Morgan team.

    Then maybe a list for Core Values under same section? Could be a
    inside. But we could also make a separate section "Morgan Core Values" but that's not in the list. However we could treat core values as part of About the role. Better to follow instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we will produce those headings only if we have content. Thus: - About the role: includes company description and core values. - Responsibilities: essential job functions. - Requirements: includes physical, vision, hearing/speaking/written, driving, working environment (maybe also non-essential job functions? Could be part of responsibilities? but we can include non-essential under Responsibilities as well.) - Benefits: benefits list. We need to ensure we don't miss any info: Non-Essential Job Functions, Physical Requirements, Vision Requirements, Hearing, Speaking and Written Requirements, Driving Requirements, Working Environment. We'll put all those under Requirements as sub-lists? Could be separate
    with headings inside? But we cannot add extra headings besides

    . However we can include

    or inside? The instruction didn't forbid other tags, just said use

    for section headings,

    • for any list,

      for prose. It didn't forbid using or . But to be safe, we can just use

      for prose and

      • for lists. For subcategories we could use

        with bold text? Might be okay but not specified. Safer to keep each requirement category as its own

        maybe? But that would deviate from the suggested headings. However the instruction says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but it gives examples. It might be okay to use other headings as long as they are

        . The important part is to not create sections with filler. So we could create headings like "Physical Requirements", "Vision Requirements", etc. That would be more sections but each has substantive content. The instruction says "Prefer a few substantive sections over many thin ones." So we should combine where possible. Thus combine all requirements into one Requirements section with multiple

        lists each preceded by a

        describing the category? That might be okay: we can have a

        Physical Requirements:

        then
        ... but that uses

        for prose, which is allowed. So we can have:

        Requirements

        Physical Requirements:

        ...

        Vision Requirements:

        ...

        Hearing, Speaking and Written Requirements:

        ...

        Driving Requirements:

        ...

        Working Environment:

        ...
        Also include Non-Essential Job Functions maybe under Responsibilities? Could add a

        Non-Essential Job Functions:

        ... but it's just one line: "Other tasks as assigned by your supervisor, not listed as essential job functions." Could be a

        . Now Benefits: we have a paragraph then a list. Thus final HTML:

        About the role

        Why The Morgan Group? At The Morgan Group, we are more than our 70+ multifamily properties — we are a community built on people. We believe in treating everyone with respect and dignity, from our team members and partners to our residents, clients, subcontractors, and vendors. We strive to foster an inclusive environment where every idea, perspective, and contribution is valued, and where everyone feels heard and appreciated. Our Core Values are the foundation of our success — they guide how we hire, reward, and evaluate every member of the Morgan team.

        • We are Self-Starters – In it to win it – We take initiative – Be accountable
        • One Morgan – We are team players – We are inclusive – No Drama
        • We Get it Done – We are reliable – We are effective
        • Raise the Bar – We seek excellence – We learn from our mistakes – We strive to improve – Hold ourselves to high standards
        • Keep on Truckin’ – Embrace challenges & be optimistic – We are resilient – Choose positivity – We are level-headed
        • Reputation is Earned Daily – Do the right thing – We are honest and have high integrity – We make good decisions – Our future depends on it

        Responsibilities

        What You'll Do Essential Job Functions: Assist the Community Manager in the management of the day to day operations of the community to achieve the highest level of professionalism by all Team Members in the office and on the community. These duties include but are not limited to the following:

        • Adhere to MORGAN’s Leasing and Marketing, Management and Operations, Maintenance, and Emergency Procedures manuals along with the Team Member Handbook.
        • Operate the office in a professional, clean, uncluttered and well-staffed manner.
        • Maintain office and resident files (paper and online) in a confidential and secure manner using the MORGAN standard.
        • Meet with the Maintenance Supervisor and other maintenance team members concerning service requests, community maintenance and cleanliness.
        • Safeguard and assure all monies received on the community are properly deposited and entered into system per MORGAN standard.
        • Super