VP of Property Operations

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Organizations" then "Position Summary", "The VP’s Responsibility for STABLE", "Direct Reports & Business Unit Ownership", "Key Responsibilities" with subheadings: Strategic Leadership, Portfolio Performance, Operations Management, Financial Performance & Compliance, Cross-Functional Collaboration, GWC + STABLE Fit, Required Qualifications. We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we must only include sections when posting has real specific content. We should map content to appropriate headings. We have: - About the organization (description). Could be "About the role"? Actually "About The Organizations" is about the company. Could map to "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. We have content about organization, position summary, responsibilities, qualifications, etc. We need to avoid repeating job title as heading. No Job ID. We need to use

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

  for prose. We must preserve all substantive information, not invent or summarize away detail. Remove boilerplate etc. We must include a section ONLY when posting has real specific content for it — never emit heading followed by filler/placeholder text. Thus we need to decide which sections to include: About the role (maybe about organization and position summary), Responsibilities (key responsibilities), Requirements (maybe required qualifications), Qualifications (maybe same as requirements?), Skills (maybe core values?), Benefits, Pay, Schedule (none present, so omit). Also maybe "GWC + STABLE Fit" could be part of Requirements or Qualifications? But we need to follow headings list; we can also create other headings if needed? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings; but also says "Prefer a few substantive sections over many thin ones." So we can use those headings only if we have content. Thus we need to map content: - About the role: could include description of organization and position summary. - Responsibilities: list of key responsibilities (Strategic Leadership, Portfolio Performance, Operations Management, Financial Performance & Compliance, Cross-Functional Collaboration). Could be bullet list. - Requirements: maybe required qualifications (minimum 10 years multifamily experience, location, leading teams, etc.) - Qualifications: maybe overlapping; but we could combine? However we need to avoid duplicate sections. Could treat Requirements as the list of required qualifications, and Qualifications as maybe "Preferred qualifications"? Not present. So maybe we only include Requirements. - Skills: maybe core values STABLE and GWC? Could be considered skills. But we have "GWC + STABLE Fit" section. Could map to Skills. - Benefits, Pay, Schedule: none, so omit. Thus we will output sections: About the role, Responsibilities, Requirements, Skills. We must ensure we don't create empty sections. Now we need to extract substantive content. About the role: combine "About The Organizations" description and "Position Summary". Must preserve all detail, not summarize away. So we need to include paragraphs describing the organization, its structure, revenue, culture, investment side, operations side, business enablement, then position summary details. We must not invent or summarize away detail; we can keep as is but maybe split into paragraphs. We need to use

  for prose. So each paragraph as

  . We need to avoid boilerplate like EEO etc. Not present. Now Responsibilities: we need to list duties. The posting has "Key Responsibilities" with subheadings: Strategic Leadership, Portfolio Performance, Operations Management, Financial Performance & Compliance, Cross-Functional Collaboration, GWC + STABLE Fit (maybe part of skills). Under each subheading there are bullet-like sentences. We need to convert to

  • . We'll need to capture each duty. Let's extract: Strategic Leadership: - Partner with the Integrator/COO to translate RAM and RCV’s V/TOs into the operational strategy for the Property Operations business unit. - Set quarterly Rocks for the business unit and ensure each direct report’s Rocks roll up to those priorities. - Drive enterprise-level initiatives that improve NOI, operational scalability, and asset value. - Lead change management as the companies grow, integrate new assets, and evolve their systems. Portfolio Performance: - Own portfolio-level performance across all assets — occupancy, retention, NOI, and resident experience. - Standardize operating procedures and implement best-in-class property management practices across the portfolio. - Monitor and improve key portfolio metrics on a weekly Scorecard cadence. Operations Management: - Hold the Director of Maintenance accountable for KPIs including work order completion time, cost per unit, and resident satisfaction. - Provide strategic oversight of planning, prioritization, and execution of all capital improvement projects. - Hold the Director of Construction accountable for delivering projects on time, on budget, and aligned with the investment thesis. - Hold the Portfolio Performance Coach accountable for rent growth, leasing performance, ancillary income generation, and the performance of the Sales/Leasing Specialist, Resident Concierge, and Tenant Financial Advocate. - Hold the Resident Experience Coach accountable for resident satisfaction, retention, and adherence to on-site operational standards. Financial Performance & Compliance: - Own business unit revenue strategy (rent growth, occupancy, ancillary income, expense optimization) in partnership with the VP of Investments on asset-level business plans and with the VP of Business Enablement (Finance) on budgeting and reporting. - Drive rent growth, ancillary income, and expense optimization to maximize NOI. - Oversee budgeting, forecasting, and variance analysis across the business unit. - Ensure full compliance with regulatory, safety, and fair housing requirements across the portfolio. Cross-Functional Collaboration: - Partner closely with the VP of Investments on acquisition diligence, asset business plans, and execution against the investment thesis. - Partner closely with the VP of Business Enablement on systems, technology, people operations, and process work that supports the business unit. - Bring clear, data-driven reporting on portfolio and business unit performance into Leadership Team meetings. - Surface issues early, IDS them at the right level, and keep the Leadership Team aligned on operational risks and opportunities. GWC + STABLE Fit: - This seat is evaluated quarterly using the People Analyzer against both GWC and the STABLE Core Values. - All four GWC criteria and all six STABLE values must be a “+” — anything less means the person is in the wrong seat. - GWC: Get it — Understands the seat, the business unit, and how RAM and RCV create value. - Want it — Genuinely wants the accountabilities of this seat, not just the title. - Capacity to do it — Has the mental, physical, emotional, and time capacity to execute at this level. We could treat GWC+STABLE Fit as part of Skills or Requirements. Since we have Skills section, we can put that there. Now Requirements: list from "Required Qualifications": - Minimum 10 years of multifamily experience. - Located in the Indianapolis, IN area or willing to relocate. - Experience leading teams of 50 or more employees. - Progressive leadership experience in property management, operations, or real estate. - Proven experience managing large, multi-site property portfolios. - Strong background across maintenance operations, CapEx/construction, and revenue optimization. - Demonstrated ability to lead through scale, change, and growth. - Deep financial acumen — budgeting, forecasting, and NOI optimization. - Experience working closely with executive leadership and ownership groups. - Working fluency in EOS — or a comparable operating system — and being able to run a healthy L10, build a Scorecard, set Rocks, and use the People Analyzer from day one. - Exceptional leadership, communication, and organizational development skills. - Data-driven mindset with strong analytical and problem-solving capabilities. We need to output as
    • . Now Skills: maybe include STABLE core values description? Could also include GWC+STABLE Fit. But we already have that content; we could put under Skills. Alternatively, we could treat GWC+STABLE Fit as part of Requirements (since it's about fit). But we already have Required Qualifications; we could add a separate section for "Core Values" but not in allowed headings. The instruction says use those headings; but we can also add other headings if needed? It says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they say "Prefer a few substantive sections over many thin ones." So we could combine GWC+STABLE Fit into Skills or Requirements. I'll put under Skills: the STABLE core values description and GWC criteria. But we need to preserve all substantive information; we must not lose any detail. So we need to include the STABLE core values explanation (the six values with descriptions) and the GWC criteria. We have that content under "Our Core Values — STABLE" and "The VP’s Responsibility for STABLE". Also "GWC + STABLE Fit". We need to include all that. Thus Skills section could contain: - STABLE core values: Show Up & Own It, Take Action, Always Growing, Be Real, Lead with Humility, Excellence in Everything, each with description. - The VP’s Responsibility for STABLE: bullet points. - GWC + STABLE Fit: evaluation criteria. We need to format as

      • for any list of duties/requirements/benefits. For prose, use

        . The core values descriptions are prose; we could put each as

      • under a
        maybe. But we need to decide: Should we treat core values as a list? Probably yes. Thus Skills section:

        Skills

        then maybe a

        intro then

        • for each value and responsibility. But we must not invent headings like "Core Values". We can just list items. Better: Provide a

          summarizing that the role requires living STABLE values and GWC criteria, then a

          • list of each. But we need to preserve all detail; we can include the descriptions as part of each
          • . Let's extract STABLE descriptions: From text: S Show Up & Own It: We take full responsibility for our commitments. We show up prepared, engaged, and ready to deliver — no excuses, no shortcuts. T Take Action: We are a bias-toward-action team. We move with urgency, make decisions with confidence, and course-correct as we learn. A Always Growing: We are curious, coachable, and committed to continuous improvement — personally and professionally. Growth is a standard, not an aspiration. B Be Real: We communicate with honesty and transparency. We say what we mean, own our mistakes, and build trust through authenticity. L Lead with Humility: We check our egos at the door. We listen first, elevate others, and recognize that the best ideas can come from anywhere. E Excellence in Everything: We hold ourselves to a high standard in everything we produce, every relationship we build, and every promise we make. Then "The VP’s Responsibility for STABLE": bullet points: - Model all six values consistently and visibly — your team will only hold the standard you hold yourself to. - Use STABLE as the first filter in every hiring, promotion, and termination decision in the business unit. - Score every direct report on STABLE quarterly via the People Analyzer; address gaps directly, not eventually. - Call out value breaches in real time, regardless of seniority or performance — silence is endorsement. - Recognize and celebrate when team members live the values well; reinforcement is part of the job. Then GWC + ST