Senior Community Leasing Manager

We need to produce HTML fragment with sections: About the role? Actually we have sections: Who We Are, What We Do, Benefits That Matter, Position Overview, What You Will Do (with sub-bullets), Ideally You'll Have, You'll Crush It If You Have, Organizational Structure, Additional Compensation (Sign-on Bonus). Also maybe "Benefits That Matter" is a benefits section. Also "Additional Compensation" maybe part of Benefits or separate. We must use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use other headings if they match content? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate, but we can also use other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect we use those exact headings where applicable. However the posting has sections like "Who We Are", "What We Do", "Benefits That Matter", "Position Overview", "What You Will Do", "Ideally, You'll Have", "You'll Crush It If You Have", "Organizational Structure", "Additional Compensation". We need to map to allowed headings? Possibly we can rename to match: "About the role" could cover Position Overview and What You Will Do? But we need to preserve all substantive info. We could create sections: About the role (Position Overview + What You Will Do), Responsibilities (maybe part of What You Will Do), Requirements (Ideally You'll Have), Qualifications/Skills (You'll Crush It If You Have), Benefits (Benefits That Matter + Additional Compensation), Pay (maybe not present except sign-on bonus?), Schedule (maybe not present). However we must not create sections with filler like "Pay" if not stated. The posting mentions Competitive pay, but not specific numbers. It says "Competitive pay that values your contributions" under Benefits That Matter. That is a benefit, not a specific pay figure. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It says "Competitive pay" is stated, so we could include a Pay section? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state "Competitive pay that values your contributions". That's a statement about pay, albeit vague. So we could include a Pay section with that statement. However they also said "Prefer a few substantive sections over many thin ones." So maybe combine Benefits and Pay. We also have Schedule: not mentioned besides "Must be available for additional hours including evenings and weekends as needed". That's schedule info. So we could include Schedule section. We need to avoid boilerplate like EEO etc. Remove disclaimer lines etc. We must preserve all substantive information. So we need to include all details: Who We Are, What We Do, Benefits That Matter (list), Position Overview, What You Will Do (with bullet list of duties), Ideally You'll Have (list), You'll Crush It If You Have (list), Organizational Structure (reports to, direct reports, functional oversight), Additional Compensation (sign-on bonus). Also maybe "Portfolio and pipeline numbers as of Q2 2026" is part of What We Do. We need to output only HTML fragment, no markdown fences. We'll structure:

About the Company

maybe not allowed but we can use

for section headings; they gave examples but not exclusive. Safer to use those exact headings where possible. Let's map: - About the role: could combine Position Overview and What You Will Do? But we also have Who We Are and What We Do which are about company. Could be "About the role" not appropriate for company info. Maybe we can still use

for any heading; they just gave examples. I think it's okay to use other headings as long as they are

. 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 suggests using those for typical sections. I'll use those headings where applicable, and for company info maybe use "About the role"? Not ideal. Could use "About the role" for Position Overview and What You Will Do, and then separate sections for "Who We Are" and "What We Do" maybe as

as well but not in list. Might be okay. Better to follow instruction: Use

for section headings. So any heading we output must be

. We'll decide headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll try to fit content into these. Let's map: - About the role: Position Overview + maybe brief summary of role. - Responsibilities: What You Will Do (list of duties). - Requirements: Ideally You'll Have (list). - Qualifications/Skills: You'll Crush It If You Have (list) maybe combine with Requirements? But we need both. - Benefits: Benefits That Matter + Additional Compensation (sign-on bonus) maybe also Competitive pay. - Pay: Competitive pay statement. - Schedule: Must be available for additional hours including evenings and weekends as needed. We also need to include Who We Are and What We Do somewhere. Could be part of About the role? Not ideal but we could include a short paragraph under About the role describing company. Or we could add a separate

like "About the Company" but not in list. Might violate instruction but maybe okay. Safer to incorporate into About the role: include a paragraph about Core Spaces (Who We Are, What We Do). That preserves info. Thus:

About the role

Who We Are Core Spaces (Core) is more than a real estate company, it’s a people company. Where building relationships is just as important as building properties. From researchers and architects to designers and operators, Core is made up of risk takers and dreamers who are on a mission to invent the future of living. Our six cultural values guide us every day and we strive to live them in everything we do: PUSH (Invent Better Places to Live), GRIT (We Got This), LIFT (Help Each Other Win), SHINE (Bring Your Full Self), UPHOLD (Never Break Trust), GROW (Always Get Better). Everything Core does stems from this culture of collaboration and innovation, and the drive to constantly improve the resident experience. This unique approach has led to creating spaces and services that are redefining the way people live. What We Do Founded in 2010, Core is a vertically integrated real estate investment manager focused on acquiring, developing and managing across the student housing and build-to-rent (“BTR”) sectors. Its residential communities feature world-class amenities, progressive design, and hospitality-driven service. Core’s student housing portfolio includes over 74,440 beds currently owned or managed, with a pipeline of over 53,860 beds in various stages of development. Core’s BTR division has over 3,000 homes under development, now leasing or in its pipeline in high-growth metros nationwide. For more information, visit www.corespaces.com. Portfolio and pipeline numbers as of Q2 2026

Then Position Overview maybe we need to include as part of About the role? Could add a paragraph after that: "Position Overview The Senior Community Leasing Manager is responsible..." We'll include that as a paragraph. Then Responsibilities:

Responsibilities

• ... list items from What You Will Do (leadership and staff management, leasing strategy, marketing & execution oversight, operations & compliance, collaboration & special projects, other). We'll need to break down each bullet. We must preserve all substantive info; we can keep the sub-bullets as separate
• items. Then Requirements:

  Requirements

  • Ideally, You'll Have list items.
  Then Qualifications/Skills: maybe

  Qualifications

  for You'll Crush It If You Have list. Then Benefits:

  Benefits

  • list from Benefits That Matter.
  Then Pay:

  Pay

  Competitive pay that values your contributions.

  Then Schedule:

  Schedule

  Must be available for additional hours including evenings and weekends as needed based on business needs.

  We also need to include Additional Compensation (sign-on bonus). Could be part of Benefits or Pay. Since we already have Pay section for competitive pay, we could add sign-on bonus under Benefits or Pay. Perhaps add to Benefits list: "Sign‑on Bonus of $2,500". Or add to Pay: "Competitive pay that values your contributions; Sign‑on Bonus of $2,500". We'll include in Benefits. Also need to include Organizational Structure: Reports to, Direct Reports, Functional Oversight. Where to put? Could be under About the role or Responsibilities? Maybe under About the role as a paragraph. But we need to preserve it. Could add a separate

  maybe "Organizational Structure" but not in list. Might be okay but risk. Perhaps we can incorporate into About the role after Position Overview: a paragraph about reporting lines. Let's add after Position Overview: a paragraph: "Organizational Structure: Reports to: Community Manager; Direct Reports: N/A; Functional Oversight: Leasing Associates and Community Concierges." Now ensure we removed boilerplate: Disclaimer, EEO, etc. Also removed "Additional Compensation Sign -on Bonus of $2,500" we incorporated. Check for any other boilerplate: "Disclaimer Disclaimer: Please note that job responsibilities, reporting lines, and duties outlined in this job description are subject to change..." remove. Also "As an Equal Opportunity Employer..." remove. Now ensure we didn't miss any substantive info: Who We Are, What We Do, Benefits list (including culture belonging, competitive pay, generous PTO, paid 14+ holidays including birthday, paid parental leave after 90 days, paid volunteer time off, robust health plan options begin within at least 30 days, yearly subscription to meditation app, environment that provides voice, EAP, company retirement options including 401(k)+matching & Roth). Also sign-on bonus. Also "Other Must be available for additional hours including evenings and weekends as needed based on business needs." Already in Schedule. Also "Provides oversight for leasing operations during peak periods, ensuring smooth execution of move-ins, move-outs, and turnover activities are executed by the team." That's part of Responsibilities maybe under Operations & Compliance or Other. We'll include as a bullet under Responsibilities. Also "Must be able to occasionally lift and move objects up to 50 pounds as situations may require.This may include bending, stooping, and lifting throughout the workday." Include as bullet under Responsibilities maybe under Operations & Compliance. Now we need to ensure we didn't duplicate lines. Let's craft the HTML. We'll need to escape any special characters? Not needed. We'll produce:

  About the role

  Who We Are Core Spaces (Core) is more than a real estate company, it’s a people company. Where building relationships is just as important as building properties. From researchers and architects to designers and operators, Core is made up of risk takers and dreamers who are on a mission to invent the future of living. Our six cultural values guide us every day and we strive to live them in everything we do: