Director of Talent

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes Position Summary (could be About the role). Key Responsibilities (Responsibilities). Qualifications (Required and Preferred). There's also First-Year Success Metrics (maybe could be under Requirements? but not a standard heading). There's also About Greystone Properties (company description) maybe not needed. There's no explicit Pay, Benefits, Schedule. So we should not create those sections. Also we should not repeat job title as heading. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information, but we can format as needed. Remove boilerplate like Job ID, FLSA status, DIRECT REPORTS TBD, LOCATION maybe we can include as a short paragraph? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can include location etc in a short paragraph maybe under About the role? But we need to preserve all substantive information. The location is substantive: "Greystone Properties corporate office (Columbus, GA metro), with regular travel across the portfolio". Also "PORTFOLIO Class A suburban communities across Georgia, Alabama, Tennessee, and Florida; scope grows with the portfolio". That's also substantive. We could include that in About the role paragraph. We need to avoid repeating job title as heading. So we will not have a heading for "Director of Talent". We'll start with maybe a

  containing location and portfolio info? Or we could embed in About the role section. Let's structure:

  About the role

  Location: Greystone Properties corporate office (Columbus, GA metro), with regular travel across the portfolio. Portfolio: Class A suburban communities across Georgia, Alabama, Tennessee, and Florida; scope grows with the portfolio.

  [Position Summary paragraph...]

  Then Responsibilities:

  Responsibilities

  • ... each bullet from Key Responsibilities (maybe break into sub-bullets? but we can keep as list items). We need to preserve all details. Could break into multiple list items for each major bullet: Talent Acquisition, Training & Development, Culture & Retention, HR & Benefits Partner Management, Workforce Insight. Within each we can have sub-detail maybe as separate list items or we can keep as paragraphs inside li? The instruction: Use
    • for any list of duties/requirements/benefits. So we should put each duty as a li. Could embed multiple sentences inside li. We'll need to capture all bullet points from the posting. Let's extract responsibilities: From "Key Responsibilities" section: Talent Acquisition - Build the Hiring Engine - Own hiring end to end - a standardized, portfolio-wide process for every site and corporate role: sourcing, screening, structured skills and situational assessment, HR interview, hiring manager interview, and leadership sign-off on key positions. - Hire with rigor - structured interviews, role-specific competency assessment, and layered leadership review, with every step Fair Housing, EEOC, and ADA compliant. - Equip the hiring managers - train Property Managers and Assistant Managers in structured, legally compliant interviewing and selection, so hiring quality is consistent across every community. - Build pipelines, not postings - relationships with local colleges, technical and trade schools, apartment associations, and workforce programs near each property cluster, so maintenance and leasing roles have candidates before they have vacancies. - Own the mechanics - requisitions, offers, background and drug screening, and I-9 and E-Verify compliance across Georgia, Alabama, Tennessee, and Florida, coordinated with the HR partner. Training & Development - Build the training function - Greystone's first, designed around hands-on mentorship, property-specific context, and accountability for whether the training actually worked. Documentation alone does not make someone good at the job. - Structured onboarding by role - a curriculum for Leasing Consultant, Assistant Manager, Property Manager, and Maintenance Technician that pairs formal instruction with assigned mentorship and measurably shortens ramp to competency. - A leadership development track - monthly sessions, on-demand modules, lunch and learns, and vendor-led training on the platforms the business runs on, building the internal bench the promotion pipeline depends on. - Certifications and career paths - administer the education assistance and industry certification programs that turn maintenance roles into careers with visible progression. - Compliance training - Fair Housing, safety, and systems certification, tracked to completion portfolio-wide rather than assumed. - Succession planning - with the COO and regional maintenance leadership, identify the roles that would hurt most to lose and name who is being developed for each. Culture & Retention - Make Greystone distinctive to work for - a deliberate employer brand built on selectivity in hiring, visible recognition, real mentorship, and the traditions that give people a reason to stay. This is a core deliverable, not a side initiative. - Run recognition with real cadence - monthly, quarterly, and annual recognition across every role, deliberately including maintenance and grounds, which recognition programs built around leasing tend to overlook. - Career pathing that keeps people - give high performers a defined path to grow inside Greystone rather than leaving for a larger platform's corporate track. - Measure what is actually happening - engagement surveys, stay interviews, and exit interviews, with turnover trends and root causes reported to leadership alongside recommended action, not just numbers. - Own the employee experience at transition - onboarding, communication, and the first ninety days for every employee joining the Greystone platform. HR & Benefits Partner Management - Manage the relationships, not the transactions - payroll, benefits administration, workers compensation, and employment compliance are delivered through outsourced HR and benefits partners. This role owns day-to-day management of those relationships, including escalation, performance review, and renewal. - Hold partners to standard - define service expectations and response times, monitor delivery, and resolve issues before a site team feels them. A payroll or benefits problem that reaches a Property Manager is a failure of this function. - Own benefits internally - serve as the internal owner for enrollment, open enrollment cycles, plan changes, and employee questions, working through the benefits partner and broker rather than administering plans directly. - Keep the line clear - partners own transactional execution and compliance infrastructure. Greystone owns policy, judgment, employee relations, and every decision about its own people. - Policy and documentation - maintain the employee handbook, HR policies, and job descriptions across all roles, and administer a standardized annual performance review process. - Multi-state compliance - ensure hiring, termination, leave, and wage and hour practices meet requirements in Georgia, Alabama, Tennessee, and Florida, using partner infrastructure and counsel where appropriate. Workforce Insight - Report what matters - time to fill, cost per hire, turnover by role and by property, training completion, certification attainment, and engagement, on the portfolio's regular reporting cadence. - Connect people data to operations - work with the COO to translate workforce data into staffing models for the three-tier operating model: property teams, cluster and centralized functions, and corporate. We'll put each bullet as a li. Now Requirements/Qualifications: We have "Qualifications Required" and "Preferred". Also "First-Year Success Metrics" maybe could be under Requirements? But we can treat as separate section maybe "Requirements" includes required qualifications and first-year success metrics? The instruction: Use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. There's overlap. We need to decide which sections to include based on content. We have Required qualifications (7+ years HR leadership, multifamily etc). Preferred qualifications (certifications, ATS, LMS, etc). Also First-Year Success Metrics (targets). Could be considered under Requirements? But maybe better to have a section "Requirements" for required qualifications, and another "Preferred Qualifications" maybe under Qualifications? The instruction says we can have Qualifications heading. Could combine required and preferred under Qualifications. But we also have Skills maybe separate? Not much explicit skills list besides those in qualifications. Could treat Skills as part of Qualifications. We need to avoid thin sections. Perhaps we can have:

      Requirements

      for required qualifications.

      Preferred Qualifications

      for preferred. But the instruction only lists certain headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems those are examples; we could still use other headings? 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. But we can also use other headings if needed? The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but they gave examples. Safer to stick to those headings. So we need to map our content to those headings. We have About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have no Benefits, Pay, Schedule info -> omit those sections. We have Requirements (maybe required qualifications). Qualifications (maybe preferred qualifications). Skills maybe we can include some skill-based requirements like experience with ATS, LMS, etc. But those are already in preferred qualifications. Could put them under Skills. We need to avoid thin sections; if we have little content for a heading, we should omit it. Thus: - About the role: include location, portfolio, position summary. - Responsibilities: as above. - Requirements: required qualifications (7+ years HR leadership, multifamily etc, building from ground up, etc). - Qualifications: maybe preferred qualifications (certifications, ATS/LMS, transition experience, Southeast market knowledge). - Skills: maybe specific skills like structured interview design, training curriculum design, managing outsourced HR partners, multi-state compliance, workforce analytics, etc. But those are already covered. Could combine Qualifications and Skills? But we need to decide. We could put preferred qualifications under Qualifications, and skills under Skills (like experience with ATS, LMS, etc). But we risk duplication. Better: Use Requirements for required qualifications, Qualifications for preferred qualifications, and omit Skills if no distinct skill content beyond those. But we could still include some skill statements under Skills like "Experience designing structured interview and selection processes", "Experience building training curricula for frontline teams", "Experience managing outsourced HR/PEO/benefits partner", "Working knowledge of Fair Housing, EEOC, ADA, FMLA, multi-state employment law". Those are also in qualifications. Might be okay to put them under Skills. But we need to avoid duplication? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is not prohibited but might be redundant. Better to avoid duplication. Thus we can assign: Requirements: required qualifications bullet list. Qualifications: preferred qualifications bullet list. Skills: maybe we can include specific technical skills like "Applicant tracking systems", "Learning management or training platforms", "Data analysis for workforce KPI", "Multi-state compliance management". But those are already in preferred qualifications. Could still list them under Skills as separate bullet list but that would duplicate. Might be okay but risk being considered thin? Not sure. Given the instruction to prefer a few substantive sections over many thin ones, maybe we combine Qualifications and Skills into one section called Qualifications (including both preferred qualifications and skills). But we need to follow the heading list; we can still use Qualifications heading and put both preferred qualifications and skills there. That would be one section. Thus we will have: About the role