Community Manager-HM
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings.
We have:
- About YES (company description) could be "About the role"? Actually "About the role" is generic; but we have company overview. Could use "About the role" heading for overview of role? But we also have Position Overview. Maybe we can use "About the role" for Position Overview, and "About the company" not a standard heading; but we could incorporate into Position Overview or maybe omit. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. So we can use those headings if appropriate. We have content for: About the role (Position Overview), Responsibilities (Essential Functions), Requirements (Required Skills), Qualifications (Education And Experience), Benefits (The YES Difference). Pay and Schedule not present, so omit.
We must not repeat job title as heading. So no heading "Community Manager". Good.
We need to preserve all substantive information. So we need to include company overview text (Founded in 2008...). That is substantive; we need to place it somewhere. Could be under "About the role" or maybe a separate heading like "About the company". Since not in list, but we can still use for any heading; the instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to use "About the role" for position overview and maybe include company description within that paragraph? Could combine.
Better: Use "About the role" heading for Position Overview (which includes description of role). Then we could add a preceding paragraph about company before that heading? But headings must be used for sections; we could have a paragraph before first heading (company overview) without heading? That's allowed? The instruction: use for section headings (e.g. About the role, Responsibilities...). It doesn't say you must have a heading for every block, but we should use headings for sections. Could have a leading paragraph without heading? Might be okay but better to include a heading like "About the company". However not in examples but likely acceptable. I'll include "About the company" as .
But to be safe, maybe use "About the role" for company overview and then separate "Position Overview" as another heading? That seems redundant.
Let's decide: We'll have sections:
- About the company (h3) with company description.
- About the role (h3) with Position Overview paragraph.
- Responsibilities (h3) with Essential Functions list.
- Requirements (h3) with Required Skills list.
- Qualifications (h3) with Education And Experience list.
- Benefits (h3) with benefits list.
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: "Your safety matters..." and equal opportunity line, also "YES I can help * YES We are a team * YES We add value * YES We build community" maybe considered tagline but not boilerplate; could keep as paragraph? It's not essential but maybe keep as part of culture. However it's repetitive and maybe not needed. I'd remove it as it's not substantive info about job. It's more marketing. I'd drop.
Also remove "Community Manager Reports To: Regional Manager" maybe metadata; we can fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for any heading; the instruction says use for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but suggests using those. Safer to use "About the role" for position overview and maybe include company description within that paragraph? Could combine.
Better: Use "About the role" heading for Position Overview (which includes description of role). Then we could add a preceding paragraph about company before that heading? But headings must be used for sections; we could have a paragraph before first heading (company overview) without heading? That's allowed? The instruction: use for section headings (e.g. About the role, Responsibilities...). It doesn't say you must have a heading for every block, but we should use headings for sections. Could have a leading paragraph without heading? Might be okay but better to include a heading like "About the company". However not in examples but likely acceptable. I'll include "About the company" as .
But to be safe, maybe use "About the role" for company overview and then separate "Position Overview" as another heading? That seems redundant.
Let's decide: We'll have sections:
- About the company (h3) with company description.
- About the role (h3) with Position Overview paragraph.
- Responsibilities (h3) with Essential Functions list.
- Requirements (h3) with Required Skills list.
- Qualifications (h3) with Education And Experience list.
- Benefits (h3) with benefits list.
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: "Your safety matters..." and equal opportunity line, also "YES I can help * YES We are a team * YES We add value * YES We build community" maybe considered tagline but not boilerplate; could keep as paragraph? It's not essential but maybe keep as part of culture. However it's repetitive and maybe not needed. I'd remove it as it's not substantive info about job. It's more marketing. I'd drop.
Also remove "Community Manager Reports To: Regional Manager" maybe metadata; we can fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
for section headings (e.g. About the role, Responsibilities...). It doesn't say you must have a heading for every block, but we should use headings for sections. Could have a leading paragraph without heading? Might be okay but better to include a heading like "About the company". However not in examples but likely acceptable. I'll include "About the company" as .
But to be safe, maybe use "About the role" for company overview and then separate "Position Overview" as another heading? That seems redundant.
Let's decide: We'll have sections:
- About the company (h3) with company description.
- About the role (h3) with Position Overview paragraph.
- Responsibilities (h3) with Essential Functions list.
- Requirements (h3) with Required Skills list.
- Qualifications (h3) with Education And Experience list.
- Benefits (h3) with benefits list.
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: "Your safety matters..." and equal opportunity line, also "YES I can help * YES We are a team * YES We add value * YES We build community" maybe considered tagline but not boilerplate; could keep as paragraph? It's not essential but maybe keep as part of culture. However it's repetitive and maybe not needed. I'd remove it as it's not substantive info about job. It's more marketing. I'd drop.
Also remove "Community Manager Reports To: Regional Manager" maybe metadata; we can fold into short p or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. So "Reports To: Regional Manager" is minor metadata; we can include in a short p under About the role maybe. Also "Community Manager Position Overview" heading we will not use as heading because we use h3 for About the role. We'll keep the paragraph. Now craft HTML. We need to preserve all substantive information: Let's extract. Company overview: "Founded in 2008, YES Communities has established itself as a leader in the manufactured housing space. YES is the largest privately held manufactured housing REIT in the country. Our commitment to improving communities and enhancing the lives of our residents is evident in our long-standing industry presence and the experience of our leadership team. This dedication and expertise have earned YES recognition and respect in the field, underscoring our significant role in shaping the manufactured housing landscape." Position Overview paragraph: "As a Community Manager, you play a very important leadership role not only with existing team members but with the residents of our communities as well. You will perform regular operational tasks such as collecting rent, managing supplies and marketing materials, developing the team, and protecting all company assets. In addition to this, you are also the main source of communication for the residents and will be the point person when it comes to resolving all complaints that come through your office. You must be able to make executive decisions when it comes to financial success and the overall safety and conditions of your community. Your commitment to communicating community successes and challenges with your immediate supervisor and your team members will ensure your team’s alignment with company goals and objectives." Essential Functions list (bullet points): - Manage daily community operations, including but not limited to: evictions, collections, resident relations, maintain community budget, and protect all company assets - Recruit, train, manage, and develop team members. Conduct consistent team meetings to reinforce expectations and facilitate employee growth - Manage the marketing, sale, leasing, and turn of all new, used, foreclosed, and broker homes to ensure ongoing success and high occupancy of the community - Develop and maintain positive relationships with vendors, cities, municipalities, and counties - Plan and oversee community events to help maintain a positive community environment - Coordinate with residents to uphold property standards - Travel to/attend company meetings, trainings, and conferences as requested by management. Coordinate new home delivery and set-up, and request any warranty or follow-up work with manufacturers - Additional duties as assigned by management subject to change Required Skills list: - Excellent oral and written communication skills - Strong conflict resolution skills - Strong leadership and decision-making skills, including management of team member performance - Proficiency in Microsoft Office and industry specific software products - Proven ability to adapt to new or unforeseen situations - Must obtain or transfer state-specific licensing within 90 days of employment (in applicable states) Education And Experience list: - A valid in-state driver’s license is required - High School Diploma or equivalent is preferred - Property management or equivalent experience is preferred Benefits list (from The YES Difference): - Competitive salary - Comprehensive health benefits - Life, long and short-term disability insurance - 401(k) with company match We might also include "YES I can help ..."? I'll drop. Now produce HTML fragment:
About the company
Founded in 2008, YES Communities has established itself as a leader in the manufactured housing space. YES is the largest privately held manufactured housing REIT in the country. Our commitment to improving communities and enhancing the lives of our residents is evident in our long-standing industry presence and the experience of our leadership team. This dedication and expertise have earned YES recognition and respect in the field, underscoring our significant role in shaping the manufactured housing landscape.
About the role
As a Community Manager, you play a very important leadership role not only with existing team members but with the residents of our communities as well. You will perform regular operational tasks such as collecting rent, managing supplies and marketing materials, developing the team, and protecting all company assets. In addition to this, you are also the main source of communication for the residents and will be the point person when it comes to resolving all complaints that come through your office. You must be able to make executive decisions when it comes to financial success and the overall safety and conditions of your community. Your commitment to communicating community successes and challenges with your immediate supervisor and your team members will ensure your team’s alignment with company goals and objectives.
Reports To: Regional Manager
Responsibilities
- Manage daily community operations, including but not limited to: evictions, collections, resident relations, maintain community budget, and protect all company assets
- Recruit, train, manage, and develop team members. Conduct consistent team meetings to reinforce expectations and facilitate employee growth
- Manage the marketing, sale, leasing, and turn of all new, used, foreclosed, and broker homes to ensure ongoing success and high occupancy of the community
- Develop and maintain positive relationships with vendors, cities, municipalities, and counties
- Plan and oversee community events to help maintain a positive community environment
- Coordinate with residents to uphold property standards
- Travel to/attend company meetings, trainings, and conferences as requested by management. Coordinate new home delivery and set-up, and request any warranty or follow-up work with manufacturers
- Additional duties as assigned by management subject to change
Requirements
- Excellent oral and written communication skills
- Strong conflict resolution skills
- Strong leadership and decision-making skills, including management of team member performance
- Proficiency in Microsoft Office and industry specific software products
- Proven ability to adapt to new or unforeseen situations
- Must obtain or transfer state-specific licensing within 90 days of employment (in applicable states)
Qualifications
- A valid in-state driver’s license is required
- High School Diploma or equivalent is preferred
- Property management or equivalent experience is preferred
Benefits
- Competitive salary
- Comprehensive health benefits
- Life, long and short-term disability insurance
- 401(k) with company match