Community Inspector

We need to output HTML fragment with sections: About Us? Actually "About Us" is not a required heading per list: headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes "About Us" but that's not in allowed list; we should not create heading for it unless it's one of those. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can only use those headings. We must include a section only when posting has real specific content for it. So we need to map content. We have: - About the role: there is a section "About The Role". So we can create

About the role

with paragraph(s) describing role. - Responsibilities: there is "Essential Responsibilities". So we can create

Responsibilities

with

• list. - Requirements: there is "Required Qualifications". Could map to Requirements or Qualifications. The allowed headings include Requirements and Qualifications. We need to decide. Probably we can put Required Qualifications under

  Qualifications

  . Or we could have both Requirements and Qualifications sections. The posting includes "Required Qualifications" and "Preferred Experience". Also "Professional Appearance", "Physical And Field Requirements", "Key Competencies". Those could be part of Requirements/Qualifications/Skills. We need to preserve all substantive info. We should not invent or summarize away detail. We need to include all details. We need to decide how to split. Possible sections: - About the role: description. - Responsibilities: list of essential responsibilities. - Qualifications: required qualifications (high school diploma, driver's license, etc.) plus maybe preferred experience. - Skills: key competencies (attention to detail, consistency, etc.) maybe also professional appearance? But professional appearance is more a requirement. - Benefits: list of perks & benefits. - Pay: compensation $20-24/hour. - Schedule: schedule and work environment details. We must not create sections with filler like "commensurate with experience". We have actual content. We need to remove boilerplate: EEO, etc. We must not repeat job title as heading. We must not include Job ID. We must output only HTML fragment. Let's extract content. About Us: not needed heading; we could maybe include as a paragraph under About the role? But it's separate. However instruction: include a section only when posting has real specific content for it — never emit a heading followed by filler/placeholder text. It didn't say we cannot include other headings not in list, but they gave examples of allowed headings. Likely we should stick to those headings. So we can ignore About Us or incorporate into About the role? But About the role is separate. The About Us is company overview; maybe we can put it under About the role as part of description? But that would be mixing. However we could create a

  about the company under About the role heading? The heading is About the role, not About Us. Might be odd but acceptable? Better to keep About Us as a paragraph under About the role? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use h3 for section headings (e.g. those). Likely they expect only those headings. So we should not create About Us heading. We could drop About Us content? But we must preserve ALL substantive information. So we need to include that info somewhere. Could we put it as a paragraph under About the role? That would be mixing company overview with role description, but still preserving info. Might be acceptable. Alternatively, we could create a

  About the role

  and include both company overview and role description within that section. That would preserve all info. Let's do that. Now Responsibilities: list. We need to extract each responsibility bullet. From text: Essential Responsibilities - Conduct scheduled inspections of assigned single-family communities. - Follow established routes, schedules, and community-specific guidelines. - Perform focused inspections of landscaping, weeds, exterior paint, roof tiles, fencing, gate slats, and other visible conditions. - Apply violation standards consistently and objectively. - Document potential violations with accurate notes and photographs. - Enter findings into company software promptly and accurately. - Review governing documents and community requirements before inspections. - Observe and report visible common-area maintenance or safety concerns. - Respond to homeowner questions regarding violations through Compliance Connection or other approved channels. - Occasionally meet with homeowners on site to discuss property concerns. - Communicate professionally with homeowners, Board Members, vendors, and team members. - Coordinate with Community Managers and Assistant Community Managers regarding unusual conditions or concerns. - Maintain organized records and complete inspections within established deadlines. - Protect confidential information and follow all company policies and safety procedures. We'll put each as
• . Now Qualifications: Required Qualifications list: - High school diploma or equivalent. - Valid driver’s license with a good driving record and no DUI convictions within the past 10 years. - Reliable personal vehicle and current automobile insurance meeting company requirements. - Strong attention to detail and organizational skills. - Dependable, responsible, and able to work independently. - Strong verbal and written communication skills. - Ability to remain calm, courteous, and professional with homeowners. - Basic computer skills and the ability to learn company software. - Ability to use a smartphone or tablet to photograph and document findings. - Ability to consistently apply written rules and inspection standards. Preferred Experience: Two years of community or property management experience; or Equivalent municipal or city experience in code enforcement, property inspections, neighborhood services, or a similar compliance role. Professional Appearance: bullet list. Physical And Field Requirements: bullet list. Key Competencies: bullet list. We could combine Required Qualifications, Preferred Experience, Professional Appearance, Physical And Field Requirements, Key Competencies into Qualifications and Skills sections. But we have separate headings: Requirements, Qualifications, Skills. We could map: - Requirements: maybe Required Qualifications + Preferred Experience + Professional Appearance + Physical And Field Requirements. - Qualifications: maybe same as Requirements? Hmm. Better to use: - Requirements: Required Qualifications. - Qualifications: Preferred Experience. - Skills: Key Competencies (and maybe Professional Appearance? but appearance is more a requirement). However we need to preserve all info; we can include Professional Appearance under Requirements or Qualifications as a list. Let's decide: We'll create:

  Requirements

  with
  for Required Qualifications.

  Qualifications

  with
  for Preferred Experience.

  Skills

  with
  for Key Competencies. We also need to include Professional Appearance and Physical And Field Requirements somewhere. Could be under Requirements as additional list items? Or we could add another section like "Requirements" already used; we could add subheadings? Not allowed. Could incorporate them into Requirements list as items. Thus Requirements list will include: Required Qualifications + Professional Appearance + Physical And Field Requirements. But that may be too long but okay. Alternatively, we could create a separate section for "Requirements" and another for "Qualifications" and "Skills". Then we need to place Professional Appearance and Physical And Field Requirements somewhere; maybe under Requirements as well. Let's do that. Now Benefits: list from "Perks & Benefits". - 401(k) with company matching - Medical, dental, and vision insurance - Health savings account (HSA) - Employee assistance program - Life insurance - Paid time off - Professional development assistance - Company-sponsored CMCA certification program - Employee referral program Pay: Compensation $20 - 24 / hour. Schedule: Schedule and Work Environment details: - Full-time position - Monday–Thursday, 8:00 a.m.–5:00 p.m. - Friday, 8:00 a.m.–3:00 p.m. - Approximately 75% field-based and 25% office-based - Regular local driving with mileage reimbursement We need to put these as
  • maybe. Now About the role: we need to include company overview and role description. Company overview: "About Us City Property Management (www.cityproperty.com) is an Arizona born and raised company that is a leader in full-service HOA management with innovative technology and a stellar team to match. With more than 40 years in the business and over 150 full time employees, we pride ourselves on providing the best HOA management experience possible. We work hard for the communities we serve and it shows. With paid training and a supportive team environment, you can have confidence that your investment with us is more than a job, it is a career. Mission The mission of City Property Management is to provide the best experience in community management. Our Core Values Professionalism Engagement Knowledge Humility Client Centric Trust Flexibility Teamwork Diligent Fun, Fair & Respectful" Role description: "About The Role The Community Inspector conducts consistent, professional inspections of assigned single-family residential communities. This position identifies and documents potential violations, observes common-area conditions, and communicates professionally with homeowners and internal team members. The ideal candidate is dependable, observant, methodical, and comfortable working independently. Approximately 75% of the role involves traveling throughout assigned communities." We'll combine into paragraphs. Now we must remove boilerplate: EEO, etc. Now produce HTML. Structure:

    About the role

    ... company overview ...

    ... role description ...

    Responsibilities

    • ...
    ...

    Requirements

    • Required Qualifications items
    • Professional Appearance items
    • Physical And Field Requirements items
    But we need to separate maybe with subheadings? Not allowed. Could just list all items. Better to keep logical grouping: maybe we can have multiple
    under same heading? That's okay. We'll do:

    Requirements

    Required Qualifications

    ... but h4 not allowed? Not specified but we can use

    for headings? Might be okay but they said use

    for section headings. Using

    might be okay but could be considered extra heading. Safer to just use

    for subsection headings? But they said use

    for prose. Subsection headings could be ? Not defined. Safer to just list all items without subheadings. Thus Requirements list will be long but okay. Similarly Qualifications: Preferred Experience. Skills: Key Competencies. Now Benefits: list. Pay: maybe

    $20 - 24 / hour

    under

    Pay

    . Schedule:

    under

    Schedule

    . Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's craft text. About the role paragraph 1: combine About Us and Mission/Core Values? Might be long but okay. We'll write:

    City Property Management (www.cityproperty.com) is an Arizona born and raised company that is a leader in full-service HOA management with innovative technology and a stellar team to match. With more than 40 years in the business and over 150 full time employees, we pride ourselves on providing the best HOA management experience possible. We work hard for the communities we serve and it shows. With paid training and a supportive team environment, you can have confidence that your investment with us is more than a job, it is a career. The mission of City Property Management is to provide the best experience in community management. Our core values are Professionalism, Engagement, Knowledge, Humility, Client Centric, Trust