Property Manager at Park Lafayette Towers

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, AI disclosure, etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. Let's see if posting mentions Pay, Benefits, Schedule. It mentions "Relocation assistance is available for qualified candidates." That's a benefit? It's a benefit but not explicit benefits list. It also says "We offer competitive compensation and benefits, professional growth opportunities, and the chance to make a meaningful impact at a premier community." That's generic but mentions benefits and compensation but not specific. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "competitive compensation and benefits" but not specifics. Is that enough? Likely not; they want actual specifics like salary range, health insurance, etc. Since not provided, we should omit Pay, Benefits, Schedule sections. However we could include a Benefits section if we have something like "Relocation assistance is available". That's a specific benefit. So we could include Benefits with that item. Also "professional growth opportunities" is vague. Might still be considered benefit but not specific. The rule: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". "competitive compensation and benefits" is vague but not exactly filler? It's still generic. Safer to omit Benefits unless we have concrete like relocation assistance. We can include Benefits with relocation assistance as a list item. Also maybe "Relocation assistance is available for qualified candidates." That's a specific benefit. Also we have "About Us" paragraph at start describing ownership. That could be considered "About the role"? Actually there is an "About the Role" section later. The initial "About Us" is about companies. Could be considered part of "About the role"? Not exactly. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings matching those. The "About Us" paragraph could be placed under "About the role"? But the "About the role" heading already exists in the posting. We should keep that heading and put the description under it. The initial "About Us" paragraph is about ownership; maybe we can incorporate into About the role as context. But we must not repeat job title as heading. We can keep "About the role" heading and include both the description from "About the Role" and maybe the ownership info? However the ownership info is not part of the role description; it's about the company. Could be considered part of "About the role" but maybe better to have a separate "About the company" but not allowed headings. Since only allowed headings are those listed, we could put the ownership info under "About the role" as a preamble. Or we could drop it? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the ownership info. So we need to include it somewhere. Since we cannot add arbitrary headings, we can put it in a

before the first heading or within a heading. Probably best to put it as a

before the first heading (About the role). That's allowed because we are not adding a heading. The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. So we can start with a

containing the ownership info, then

About the role

etc. Now we need to parse the responsibilities into a list under Responsibilities heading. The responsibilities are grouped into categories: Financial & Asset Management, Operations & Property Oversight, Leasing, Marketing & Resident Experience, Team Leadership & Development, Compliance & Risk Management. Each category has bullet-like sentences. We should produce a

• for each duty. Could keep categories as part of list items or we could have subheadings? Not allowed; only headings are the predefined ones. So we just list all responsibilities as list items. Similarly, "What You Bring" includes qualifications, requirements, skills. We need to split into Requirements, Qualifications, Skills sections if there is specific content. The posting includes: "High school diploma or GED required; college degree preferred", "Professional designations such as CAM, ARM, or CCRM preferred", "3+ years of experience in multifamily property management", "3+ years of experience leading, developing, and managing on-site teams", "Strong financial acumen, including budgeting, reporting, and expense management", "Solid understanding of leasing, marketing strategies, and resident retention", "Excellent communication, leadership, and interpersonal skills", "Strong organizational skills with attention to detail and ability to manage multiple priorities", "Effective problem-solving skills with the ability to make sound decisions in a fast-paced environment", "Proficiency in Microsoft Office Suite", "Experience with Entrata, REBA, or similar systems", "Self-starter with strong initiative, accountability, and a results-driven mindset", "Flexibility to work extended hours, including time prior to office opening", "Ability to walk the property, stand for extended periods, and work both indoors and outdoors as needed". Also there is a separate "Physical Requirements" section with details. We need to decide what goes into Requirements vs Qualifications vs Skills. Typically Requirements: education, experience, certifications. Qualifications: maybe similar. Skills: abilities. But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. We can create three sections if we can split content meaningfully. Let's map: Requirements (maybe education, experience, certifications): - High school diploma or GED required; college degree preferred - Professional designations such as CAM, ARM, or CCRM preferred - 3+ years of experience in multifamily property management - 3+ years of experience leading, developing, and managing on-site teams Qualifications (maybe knowledge/abilities): - Strong financial acumen, including budgeting, reporting, and expense management - Solid understanding of leasing, marketing strategies, and resident retention - Proficiency in Microsoft Office Suite - Experience with Entrata, REBA, or similar systems Skills (maybe soft skills): - Excellent communication, leadership, and interpersonal skills - Strong organizational skills with attention to detail and ability to manage multiple priorities - Effective problem-solving skills with the ability to make sound decisions in a fast-paced environment - Self-starter with strong initiative, accountability, and a results-driven mindset - Flexibility to work extended hours, including time prior to office opening - Ability to walk the property, stand for extended periods, and work both indoors and outdoors as needed Physical Requirements could be its own section? Not in allowed headings. Could be part of Requirements or Qualifications? Might be better to include under Requirements as a list item. But we have a separate "Physical Requirements" heading in the posting. Since we cannot create arbitrary headings, we could incorporate those details into Requirements or Qualifications. Probably under Requirements as they are requirements. We'll add them as list items. Now Benefits: we have "Relocation assistance is available for qualified candidates." Also "We offer competitive compensation and benefits, professional growth opportunities, and the chance to make a meaningful impact at a premier community." The latter is vague; we could include "professional growth opportunities" as a benefit but it's vague. Might be okay but risk of filler. The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "professional growth opportunities" is not exactly those but still vague. Safer to only include concrete benefit: relocation assistance. Also maybe "competitive compensation" is vague; we should not create Pay section. So Benefits section with relocation assistance. Now we need to ensure we don't include boilerplate: EEO, AI disclosure, etc. Remove those paragraphs. Now produce HTML:

  Owned by Cottonwood Residential and managed by Mandel Group. Together, our two organizations are partnering to hire an exceptional Property Manager for Park Lafayette. Cottonwood Residential, based in Salt Lake City, Utah, and Mandel Group, headquartered in Milwaukee, Wisconsin, bring decades of multifamily experience and a shared commitment to creating exceptional communities and delivering outstanding resident experiences. We are excited to bring together the strengths and expertise of both organizations as we search for the next leader of the Park Lafayette community.

  About the role

  The Property Manager is responsible for the overall performance, operations, and financial success of a multifamily community. This role leads all on-site functions, including leasing, resident experience, financial management, and property maintenance, while ensuring alignment with Cottonwood Residential’s standards and objectives. The Property Manager drives a culture of service excellence, accountability, and collaboration. This role is ideal for a results-driven professional who can balance financial performance, team leadership, and resident satisfaction to maximize asset value and deliver strong operational outcomes. Relocation assistance is available for qualified candidates.

  But we already used relocation assistance in Benefits; we might duplicate. Better to keep relocation assistance only in Benefits, not in About the role. The About the role paragraph originally didn't include relocation assistance; that was a separate sentence after the role description? Actually the posting: "Relocation assistance is available for qualified candidates." appears after the About the role paragraph? Let's check: In the text, after "About the Role" paragraph, there is a line "Relocation assistance is available for qualified candidates." then "Key Responsibilities". So we should place that under Benefits, not About the role. Thus About the role paragraph ends before that line. Now Responsibilities heading with ul list of all responsibilities. We need to capture each bullet. Let's extract: Financial & Asset Management - Manage the financial performance of the community, including operating within budget and achieving revenue and expense targets - Oversee rent collection, delinquency management, and bad debt recovery, including participation in legal proceedings as necessary - Review and approve invoices to ensure accuracy, proper coding, and budget alignment - Assist the Regional Manager in developing and managing the annual operating budget - Analyze financial reports, occupancy trends, and market data to drive informed decision-making Operations & Property Oversight - Oversee the daily operations of the community, ensuring efficiency, organization, and compliance with company policies - Conduct regular property inspections to identify maintenance needs, safety concerns, and opportunities for improvement - Oversee Self-Guided Tour operations, including unit readiness, signage, and daily inspections - Coordinate with maintenance teams and external vendors to ensure timely completion of repairs and capital needs - Maintain accurate and complete records, including resident files, vendor contracts, property inventory, and compliance documentation - Ensure all administrative systems and property management data are accurate and up to date Leasing, Marketing & Resident Experience - Develop and execute marketing and leasing strategies to achieve occupancy and revenue goals - Conduct regular market surveys and competitive analysis to inform pricing and positioning - Oversee leasing performance, ensuring effective use of sales techniques and marketing tools - Implement resident retention programs to drive renewals and satisfaction - Ensure a high level of responsiveness to resident requests and service needs - Plan and support resident engagement initiatives and community events Team Leadership & Development - Lead, coach, and develop all on-site office and maintenance team members - Oversee hiring, onboarding, training, scheduling, and performance management for the community team - Foster a strong team culture focused on accountability, collaboration, and service excellence - Provide ongoing feedback, coaching, and development opportunities to support team success - Set clear expectations and monitor performance against property and company goals Compliance & Risk Management - Ensure compliance with company policies, safety standards, and all applicable local, state, and federal regulations - Promote safety awareness and ensure adherence to OSHA standards across the community - Identify and address potential risks, safety hazards, and operational