Manager, Talent Acquisition

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (EEO, E-Verify, etc). Must not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits sections unless posting actually states them. The posting includes Compensation Range: $90,000- $125,000 Annually + Benefits. So Pay section can be included with that range. Benefits are listed: 15 Days of Paid Time Off, 8 Paid Holidays, 1 Flex Holiday, 401(k) Retirement Plan with Company Match, Medical, Dental, and Eye Insurance, Employee Referral Program, Tuition Reimbursement, Employee Assistance Program (EAP), Wellness Program. So Benefits section. Schedule: posting says "based out of Milwaukee, WI (on a hybrid schedule)". So schedule info: hybrid schedule. So we can include Schedule section with that. Now sections: About the role: we have description paragraph about role. Could be "About the role". Responsibilities: list of key responsibilities. Requirements: Minimum Qualifications (list). Qualifications: Preferred Qualifications. Skills: maybe we can extract skills from requirements: leadership, communication, interpersonal, proficiency with ATS, recruiting technologies, Microsoft Office, analytical skills, ability to manage multiple priorities. Could be separate Skills section. But we must not create thin sections; prefer few substantive sections. However we have many categories; we could combine some. But instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can decide to include only those with real content. We have content for About the role, Responsibilities, Requirements (minimum qualifications), Qualifications (preferred), Benefits, Pay, Schedule. Skills maybe we can embed within Requirements or Qualifications; but we could still create Skills section if we have specific skill list. The posting includes "Strong understanding of recruitment processes, sourcing methodologies, and compliance requirements. Excellent leadership, communication, and interpersonal skills. Proficiency with ATS platforms, recruiting technologies, and Microsoft Office Suite. Strong analytical skills and ability to use data to drive decisions. Ability to manage multiple priorities in a fast-paced environment." That's skills. So we could have Skills section. We must not repeat job title as heading. So headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not include filler like "commensurate with experience". Not present. We must output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

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

  for prose. Thus each section:

  About the role

  ... prose ...

  . For responsibilities:

  Responsibilities

  • ... each bullet ...
  . Similarly for Requirements (minimum qualifications) maybe as list. Qualifications (preferred) as list. Skills as list. Benefits as list. Pay as maybe

  or list? It's a single line; could be

  . Schedule as

  . We must preserve all substantive information. Let's extract. About the role prose: from description: "We are seeking an experienced and strategic Manager, Talent Acquisition based out of Milwaukee, WI (on a hybrid schedule) to lead our recruitment efforts and develop a high-performing talent acquisition team. This role will be responsible for designing and implementing innovative recruitment strategies to attract top talent, enhancing our employer brand, strengthening workforce planning capabilities, and ensuring a positive candidate experience throughout the hiring process. The Manager, Talent Acquisition serves as a strategic partner to Human Resources and business leadership to support workforce readiness, organizational growth, and federal contracting requirements. In addition to leading talent acquisition efforts, this position will contribute to workforce planning, succession planning, talent development initiatives, and broader Human Resources priorities. The role supervises Talent Acquisition personnel and serves as a key resource regarding labor market trends, workforce forecasting, and federal contract workforce requirements, including Service Contract Act (SCA) and Davis-Bacon Act (DBA) considerations." We can keep that as prose. Responsibilities bullet list: from "Key Responsibilities" list: - Develop and implement comprehensive recruitment strategies aligned with company goals and workforce needs. - Lead, mentor, and manage Talent Acquisition staff while providing coaching and development. - Collaborate with hiring managers, HR, and leadership to define staffing needs and position requirements. - Oversee the end-to-end recruitment process and candidate experience. - Utilize data analytics to assess recruitment metrics and improve recruiting effectiveness. - Partner with leadership on workforce planning, succession planning, and talent pipeline development. - Support workforce planning efforts related to government contract proposals, transitions, mobilizations, and demobilizations. - Assist with evaluating labor availability, workforce risks, wage determinations, and staffing impacts associated with SCA and DBA contracts. - Build relationships with recruiting agencies, universities, tribal employment programs, and workforce development organizations. - Represent the organization at job fairs, industry events, and networking functions. - Conduct training for recruiting personnel on talent acquisition best practices. - Stay current on industry trends, labor market conditions, and workforce planning practices. - Support talent management, employee development, engagement, and organizational growth initiatives. - Manage budgets and resources related to recruiting activities. We need to keep all. Requirements (Minimum Qualifications): list of education/experience combos plus other requirements. Minimum Qualifications: - High School diploma or GED equivalent with 14+ years of experience; - OR Associate degree with 12+ years; - OR Bachelor’s degree with 9+ years; - OR Master’s degree with 8+ years; - OR PhD with 4+ years. - Proven success leading talent acquisition functions and recruiting teams. - Experience recruiting across engineering, construction, environmental, technical, professional services, or government contracting environments. - Strong understanding of recruitment processes, sourcing methodologies, and compliance requirements. - Excellent leadership, communication, and interpersonal skills. - Proficiency with ATS platforms, recruiting technologies, and Microsoft Office Suite. - Strong analytical skills and ability to use data to drive decisions. - Ability to manage multiple priorities in a fast-paced environment. We'll put each as

• . Qualifications (Preferred Qualifications): list: - Broad Human Resources experience or exposure beyond recruiting preferred. - Government contracting experience strongly preferred. - Experience supporting Service Contract Act (SCA) and/or Davis-Bacon Act (DBA) environments strongly desired. - Experience interpreting wage determinations, labor classifications, and prevailing wage requirements. - Workforce planning, labor forecasting, and talent analytics experience preferred. - Experience supporting talent management, succession planning, employee development, or organizational effectiveness initiatives. - Experience supporting multi-company, federal contracting, or tribally owned organizations preferred. We'll list. Skills: Could extract from requirements but we already have many skill items; but to avoid duplication, maybe we can combine skills into Requirements or Qualifications. However instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we could have Skills separate. But we must not create thin sections; but we have enough skill items to make a section. However many of those skill items are already in Requirements; duplicating would repeat content. We should not repeat same content; we must preserve all substantive information but not duplicate? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but better to avoid redundancy. However we could move skill-specific items to Skills section and keep other qualifications in Requirements. Let's parse: Requirements includes education/experience combos plus "Proven success leading talent acquisition functions and recruiting teams." etc. Some of those are skills/experience. But we could keep Requirements as education/experience combos only, and move the skill/experience bullets to Skills. However the posting lumps them together under Minimum Qualifications. To preserve all info, we could keep them under Requirements as is, and not create Skills section (to avoid duplication). But the instruction says we can include Skills section if we have real specific content. We have skill content; but if we also keep them under Requirements, we would duplicate. Might be okay but could be considered redundant. Safer to not create Skills section and instead include skill bullets within Requirements. However they asked to prefer a few substantive sections over many thin ones. Having Skills separate might increase sections. I'd rather not include Skills section; combine skill bullets into Requirements. That reduces sections. Thus sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits, Pay, Schedule. Now Benefits list: - 15 Days of Paid Time Off - 8 Paid Holidays - 1 Flex Holiday - 401(k) Retirement Plan with Company Match - Medical, Dental, and Eye Insurance - Employee Referral Program - Tuition Reimbursement - Employee Assistance Program (EAP) - Wellness Program Pay: Compensation Range: $90,000- $125,000 Annually + Benefits. We'll put as

  Compensation Range: $90,000‑$125,000 Annually + Benefits

  . Note the dash. Schedule: based out of Milwaukee, WI (on a hybrid schedule). So

  Based out of Milwaukee, WI on a hybrid schedule.

  Now ensure we removed boilerplate: EEO, E-Verify, etc. Also removed "About Us" maybe? The "About Us" paragraph is not required as a section; but we might incorporate some of that into About the role? The "About Us" describes Oneida ESC Group. The posting already has description at start: "Description Wholly owned by the Oneida Nation of Wisconsin, Oneida ESC Group (OESC) is a holding company..." That's about the company. Should we include that? The instruction: "Preserve ALL substantive information". That description is substantive. It appears before the role description. We could include it in About the role section or maybe a separate "About the company" but not in list of headings. Since only allowed headings are those examples, we could incorporate that into About the role prose. However About the role currently focuses on role; we could prepend company description. That would still be under About the role heading. That's acceptable. Thus About the role prose: combine company description and role description. Company description: "Wholly owned by the Oneida Nation of Wisconsin, Oneida ESC Group (OESC) is a holding company that provides a consistent, cost-effective common management platform supporting our family of companies united under common ownership. Oneida ESC Group has its roots in engineering, science, and construction. We are a family of tribally-owned diversified subsidiaries. We deliver Environmental Services, Engineering and Design Services, Construction Services, and Technical and Professional Services to government agencies and commercial customers worldwide." Then role description as earlier. We'll combine into one

  maybe two paragraphs but still under same heading. Use

  for prose; can have multiple

  under same heading? Probably okay. We'll just make one

  with both paragraphs separated by a space. Now ensure we didn't include any boilerplate like "Equal Employment Opportunity", "E-Verify", etc. Now output HTML. Let's craft.

  About the role

  Wholly owned by the Oneida Nation of Wisconsin, Oneida ESC Group (OESC) is a holding company that provides a consistent, cost-effective common management platform supporting our family of companies united under common ownership. Oneida ESC Group has its roots in engineering, science, and construction. We are a family of tribally-owned diversified subsidiaries. We deliver Environmental Services, Engineering and Design Services, Construction Services, and Technical and Professional Services to