Community Relations Director

We need to output HTML fragment with sections: About the role? Actually we have description: THE COMPANY, What We Offer, Position Summary, Key Responsibilities, Requirements, Salary Description. We must use

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

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

  for prose. Do NOT repeat the job title as a heading. 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. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to decide which sections to include: About the role? Could be "About the company" maybe? The headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings based on content. We have: THE COMPANY (company overview) - could be "About the role"? Actually "About the role" is about the position, but we have Position Summary. Could use "About the role" for Position Summary. Or we could use "About the company" but not in list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? Likely we should stick to those headings. So we can use: About the role (position summary), Responsibilities (key responsibilities), Requirements (education, experience, competencies), Qualifications (maybe combine with Requirements?), Skills (maybe separate), Benefits (What We Offer), Pay (Salary Description). Schedule not present, so omit. We must not create sections with filler. So we need to ensure each section has substantive content. We'll produce:

  About the role

  Position Summary ...

  Responsibilities

  • ...
  ...

  Requirements

  Maybe include Education and Experience, Competencies, And Skills. Could split into Requirements and Qualifications and Skills but we have limited headings. Could do Requirements (education + experience) and Skills (competencies). But we also have Qualifications heading available. Could do Requirements for education, Qualifications for experience/skills? Let's think. The posting has sections: Education, Experience, Competencies, And Skills. We could map: - Requirements: Education (High School diploma required, bachelor's preferred) - Qualifications: Experience (3-5 years relational sales, etc.) - Skills: Competencies, And Skills (list of abilities) But we also have Benefits and Pay. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Check each for substantive content. About the role: Position Summary paragraph. Responsibilities: list of duties. Requirements: Education bullet list? Could be
  • High school diploma required.
  • Bachelor's degree in marketing, business, or related field preferred (or equivalent combination).
  Qualifications: Experience bullet list: At least 3-5 years of experience in relational sales, preferably in assisted living and/or independent living, hospitality, or healthcare settings. Positive team player mentality and passion for serving seniors. Proven track record in achieving and exceeding sales goals. Ability to manage time effectively, high initiative, and good judgment. Ability to work in a fast-paced environment and capacity to work evenings and/or weekends if needed. Professional ethics with a positive attitude, exceptional verbal and written communication skills, and the ability to motivate others and work within a team environment. Proficient in Microsoft Excel, Word, Outlook, and CRM software. A valid driver’s license. But note some of those are skills/competencies. However we have Skills heading separate. Could split: Qualifications for experience, Skills for competencies. Thus Qualifications: Experience bullet list (3-5 years experience, etc.) maybe also include positive team player mentality etc. But those are more like competencies. Might be okay. Skills: list of abilities: Ability to manage time effectively, high initiative, good judgment; ability to work fast-paced, evenings/weekends; professional ethics, positive attitude, exceptional verbal/written communication, ability to motivate others, team work; proficient in MS Office, CRM; valid driver's license. But there is overlap. To avoid duplication, we need to preserve all info but not duplicate. We can split logically: Qualifications: Experience (years, preferred sectors). Skills: Competencies and abilities (communication, teamwork, technical, driver's license). Also include positive team player mentality etc. Might be okay. Let's extract: Experience: At least 3-5 years of experience in relational sales, preferably in assisted living and/or independent living, hospitality, or healthcare settings. Positive team player mentality and passion for serving seniors. (Could be skill/competency) Proven track record in achieving and exceeding sales goals. (skill) Ability to manage time effectively, high initiative, and good judgment. (skill) Ability to work in a fast-paced environment and capacity to work evenings and/or weekends if needed. (skill) Professional ethics with a positive attitude, exceptional verbal and written communication skills, and the ability to motivate others and work within a team environment. (skill) Proficient in Microsoft Excel, Word, Outlook, and CRM software. (skill) A valid driver’s license. (skill/requirement) Thus we could put all under Skills. But we also have Qualifications heading; maybe we can use Qualifications for education and experience combined? Actually we have Requirements for education, Qualifications for experience, Skills for competencies. That seems fine. Thus: Requirements: Education bullet list. Qualifications: Experience bullet list (3-5 years experience, preferred sectors). Also maybe include positive team player mentality? But that's more skill. We'll keep just experience. Skills: list of competencies (team player mentality, track record, time management, fast-paced, evenings/weekends, professional ethics, communication, motivation, teamwork, MS Office, CRM, driver's license). Benefits: What We Offer list. Pay: Salary Description. Now ensure we don't include any boilerplate like "THE COMPANY" etc. We need to include company overview? The instruction says preserve ALL substantive information. The company overview is substantive. Should we include it? It could be part of About the role? Or we could add a section "About the company" but not in allowed headings. However we could incorporate company overview into About the role paragraph? The About the role currently is Position Summary only. We could expand About the role to include company overview as well. But the heading "About the role" is about the role, not company. However we could add a separate section "About the company" but not in list; maybe we should not create a heading not in list. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we need to fit company overview somewhere. Could be part of About the role? Might be okay to include a brief sentence about the company in About the role paragraph. But we must preserve all substantive information; we can include company overview in a

  under About the role before the position summary. That would be okay. Thus About the role:

  Cogir Senior Living, based in Scottsdale, Arizona, proudly oversees a network of senior living communities spanning 11 states nationwide. As a trusted leader in senior housing, we are dedicated to growth while maintaining our commitment to exceptional care for our residents and a supportive, growth-focused environment for our team members. At Cogir, our culture is rooted in the core values of human focus, creativity, and excellence, which inspire us to continuously improve and achieve excellence in all we do. Join us in our mission to enrich the lives of our residents while building a meaningful and fulfilling career!

  then maybe also position summary? Actually Position Summary is separate. Could combine both. But we need to avoid duplication. We'll put company overview then position summary as separate paragraphs under same heading? That's okay. Thus About the role will have two paragraphs: company overview and position summary. Now Responsibilities: list each duty as

  . We need to ensure we don't include any filler like "commensurate with experience". Not present. Now Benefits: list each benefit from "What We Offer": Compensation includes a base salary and a generous, accelerating commission structure. Health, Dental, Vision, and Life Insurance. 401K with company match. Paid Vacation, Holidays, and Sick Leave. Employee Assistance Program, Generous Employee Referral Program and more. We need to turn into list items. However note "Compensation includes a base salary and a generous, accelerating commission structure." That's about pay, but we also have Pay section for salary range. Might duplicate. But we should preserve all info. Could include compensation description in Benefits? But we also have Pay section for salary range. The instruction says prefer a few substantive sections over many thin ones. Could combine compensation description into Pay section? But Pay section is for salary range; we could include both base salary+commission and the range. However the Benefits list includes compensation description; we could keep it as a benefit item. But then Pay section would be redundant. However we must not create Pay section unless posting actually states them; it does state salary range. So we need Pay section. The compensation description (base salary + commission) is also substantive; we could include it in Pay section as well, or we could keep it in Benefits but then Pay section would only have range. The instruction says prefer few substantive sections over many thin ones. Having both Benefits and Pay is okay. We'll keep compensation description in Benefits as a bullet, and Pay section will have the salary range. Thus Benefits list items: - Base salary and a generous, accelerating commission structure - Health, Dental, Vision, and Life Insurance - 401K with company match - Paid Vacation, Holidays, and Sick Leave - Employee Assistance Program - Generous Employee Referral Program - and more (maybe we keep "and more" as item? Could be vague but it's substantive? It's filler? Might be okay to keep as "and more".) Now Pay: Salary Description: $70,000 - $75,000 a year. Now we need to ensure we don't include any duplicated lines. Check for duplicates: The responsibilities list includes many items; ensure we capture all. Let's list responsibilities from posting: - Develop and implement all sales and marketing strategies and tactics for the community, consistent with the company's objectives. - Design, implement, and facilitate the community's annual marketing plan with input and support from the Executive Director, corporate marketing, and operations teams. - Develop and manage the lead base, responding to telephone inquiries remotely and in real-time. - Maintain and/or improve community occupancy level and revenue production according to business and marketing plans. - Conduct walk-in and scheduled tours with prospective residents or interested parties. - Provide sales activity reports with documented lead status, closing needs, and next steps. - Follow up with all potential residents, referral sources, or interested parties. - Maintain the community's Customer Relationship Management software (Yardi) accurately and promptly. - Supervise, direct, and motivate