Talent Management Project - Manager - Secret - Rosslyn, VA

We need to output HTML fragment with sections: About the role? The posting includes intro paragraph about Deloitte Human Capital team, then "Work You'll Do As a Project, Senior Consultant on for our federal client, you will be responsible for:" then list of responsibilities. Then "A successful candidate would possess these skills:" list of skills. Then "The Team" paragraph about GPS practice. Then "Our Organization, Workforce, & Change offering..." maybe part of team description. Then "The Project Model..." paragraph. Then "Qualifications Required:" list. Then "Preferred:" list. Then compensation range paragraph. Then maybe benefits? Not explicit benefits except mention of benefits package competitive for project delivery-focused professionals. That's a benefit statement. Also mention discretionary annual incentive program. So we can include Benefits section with those statements. Pay section: compensation range $131,000 to $218,300. Schedule: mention co-locate at client site in Arlington, VA 50-80% of the time. That's schedule info. So we can include Schedule section. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we need to decide which sections have real content. - About the role: we have introductory paragraph describing Deloitte Human Capital team and the role purpose. That's suitable. - Responsibilities: list of duties. - Skills: list of skills (maybe combine with Requirements? But we have separate Skills heading). The posting has "A successful candidate would possess these skills:" list. So Skills section. - Requirements: maybe qualifications required? The posting has "Qualifications Required:" list. Also "Preferred:" list. Could combine under Requirements? But we have Qualifications heading as well. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have both Requirements and Qualifications. But we need to avoid duplication. Perhaps Requirements = mandatory qualifications (Bachelor's degree, 10+ years experience, etc). Qualifications = maybe preferred? Actually they have "Qualifications Required:" and "Preferred:" So we could treat Qualifications Required as Qualifications section, and Preferred as maybe also under Qualifications? But we have both headings; we could put Required under Qualifications, and Preferred under Requirements? That seems odd. Better: Use Qualifications for the required qualifications, and Requirements for the skills? But they already have Skills heading. Let's map: - About the role: intro paragraph. - Responsibilities: list of duties. - Skills: list of skills (the "A successful candidate would possess these skills:"). - Qualifications: list of required qualifications (Bachelor's degree, 10+ years experience, etc). Also maybe include "Ability to obtain and maintain a Secret security clearance", etc. - Requirements: maybe the preferred qualifications? Or we could treat Requirements as the mandatory qualifications and Qualifications as preferred? But the instruction list includes both; we need to decide. The posting has "Qualifications Required:" and "Preferred:" So we can put Required under Qualifications, Preferred under Requirements (or vice versa). However typical semantics: Qualifications are what you need; Requirements are what you need to do? But they already have Responsibilities for duties. I think we can treat Qualifications as required qualifications, and Requirements as preferred qualifications (or additional requirements). Let's do that. - Benefits: mention benefits package competitive for project delivery-focused professionals, discretionary annual incentive program. - Pay: compensation range $131,000 to $218,300. - Schedule: co-locate at client site in Arlington, VA 50-80% of the time. We must not include headings with empty/filler. Ensure we have substantive content under each. Now we need to strip boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes "#GPSHC2026" at end - that's likely a tag, we can drop. Also need to preserve all substantive information. Let's extract content. Intro paragraph: "Our Deloitte Human Capital team helps organizations create value through people performance. We work with clients to reimagine work, the workforce, and the workplace across the enterprise and to transform their HR functions with AI and emerging technology. With the rapid pace of change in today's world, you will help clients answer questions like: How do I access, develop, and motivate my workforce? What should my AI strategy be for the HR function? Do I have the right organization and culture to enable performance? Join our team to make work better for humans and humans better at work." That's About the role. Responsibilities: after "Work You'll Do As a Project, Senior Consultant on for our federal client, you will be responsible for:" then list: - Leading strategic workforce and capability planning initiatives by analyzing workforce trends, labor market dynamics, and emerging talent needs to support future organizational requirements - Developing workforce forecasts, strategic assessments, and long-term talent strategies that inform organizational planning, workforce modernization, and decision-making - Conducting workforce research and labor market analyses to identify emerging risks, opportunities, and future workforce challenges - Creating executive-level briefings, proposals, assessments, and recommendations that translate workforce insights into actionable strategies for leaders and stakeholders - Partnering with client and Deloitte stakeholders to design workforce planning approaches, build alignment around talent priorities, and support implementation of strategic workforce initiatives We'll put each as

. Skills: after "A successful candidate would possess these skills:" list: - Ability to work independently and collaborate as part of a team - Effective written and verbal communication skills - Meticulous attention to detail and quality of work product - Ability to build and sustain professional relationships - Ability to lead projects or workstreams - Ability to manage and prioritize multiple tasks in a fast-paced and dynamic environment - Strong interpersonal skills and professional demeanor - Ability to meet deadlines - Ability to mentor and provide clear guidance to others Qualifications Required: list: - Bachelor's degree - 10+ years of professional experience - 5+ years of experience in strategic workforce planning, human capital strategy, organizational transformation, or consulting/advisory work that includes workforce forecasting, labor market analysis, and development of executive-level workforce strategies and recommendations - Ability to obtain and maintain a Secret security clearance - Ability to co-locate at the client site in Arlington, VA 50-80% of the time - Must be legally authorized to work in the United States without the need for employer sponsorship, now or at any time in the future Preferred: - Active Secret security clearance - Experience supporting workforce planning and talent management initiatives within large federal agencies Also note: For individuals assigned and/or hired to work in Virginia, Deloitte is required by law to include a reasonable estimate of the compensation range for this role. This compensation range is specific to Virginia and takes into account the wide range of factors that are considered in making compensation decisions including but not limited to skill sets; experience and training; licensure and certifications; and other business and organizational needs. At Deloitte, it is not typical for an individual to be hired at or near the top of the range for their role and compensation decisions are dependent on the facts and circumstances of each case. A reasonable estimate of the current range is $131,000 to $218,300. You may also be eligible to participate in a discretionary annual incentive program, subject to the rules governing the program, whereby an award, if any, depends on various factors, including, without limitation, individual and organizational performance. Also earlier: "The Project Model is designed for professionals with specialized skills that align to a current client need. Team members focus on delivering services to clients, without additional expectations related to business development or promotion. Their employment is tied to their role on a project, and they are eligible for a benefits package that is competitive for project delivery-focused professionals." That's benefits. Also "The Team Deloitte's Government & Public Services (GPS) practice - our people, ideas, technology and outcomes - is designed for impact. Serving federal, state, & local government clients as well as public higher education institutions, our team of professionals brings fresh perspective to help clients anticipate disruption, reimagine the possible, and fulfill their mission promise. Our Organization, Workforce, & Change offering shapes market-leading organizational strategies, delivers impactful change, and generates client value through the workforce, while leveraging data-driven insights and exceptional delivery execution." That could be part of About the role or maybe a separate section like "About the Team". But we only have headings list; we could incorporate into About the role or maybe we could add a section "About the Team" but not in allowed headings. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, not exclusive? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings. We can embed team description within About the role or maybe under Responsibilities? Probably About the role can include the team description as part of role context. We'll keep About the role as the introductory paragraph plus maybe the team description? But we must not invent content; we can include the team description as part of About the role because it's about the team/organization. That seems okay. Thus About the role will contain: - Intro paragraph about Deloitte Human Capital team. - Then maybe a paragraph about The Team (GPS practice) and Organization, Workforce, & Change offering. - Then maybe The Project Model paragraph. We need to preserve all substantive information; we can include them as paragraphs under About the role. Now Benefits: we have "eligible for a benefits package that is competitive for project delivery-focused professionals." and "You may also be eligible to participate in a discretionary annual incentive program". We'll put those as

• items. Pay: compensation range. Schedule: co-locate at client site in Arlington, VA 50-80% of the time. Now ensure we don't include headings with empty content. All sections have content. Now produce HTML fragment: no or . Use

  for each heading, then content. Structure:

  About the role

  ... intro ...

  ... team description ...

  ... project model ...

  Responsibilities

  • ...
  ...

  Skills

  ...

  Qualifications

  ...

  Requirements

  ...
  (for preferred)

  Benefits

  ...

  Pay

  $131,000 to $218,300

  Schedule

  Co‑locate at the client site in Arlington, VA 50‑80% of the time.

  Check for any duplicated lines: ensure we didn't repeat. Now verify we haven't missed any substantive info: The posting also mentions "The Project Model is designed for professionals with specialized skills that align to a current client need. Team members focus on delivering services to clients, without additional expectations related to business development or promotion. Their employment is tied to their role on a project, and they are eligible for a benefits package that is competitive for project delivery-focused professionals." We included that in About the role. Also "For individuals assigned and/or hired to work in Virginia, Deloitte is required by law to include a reasonable estimate of the compensation range for this role." That's part of Pay section context; we could include a sentence before the range. But we can incorporate that into Pay paragraph: "For individuals assigned and/or hired to work in Virginia, Deloitte is required by law to include