AI Adoption Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Us", "Job Description", "Responsibilities", "Qualifications", "Additional Preferred Qualifications", "Security, Salary, And Benefits", "Notice on Candidate AI Usage". We need to use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map sections accordingly. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to use those headings if content exists. We should not repeat job title as heading. We need to include sections only when posting has real, specific content. We need to preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Notice on Candidate AI Usage" maybe considered boilerplate? It's about AI usage in interview; might be considered boilerplate but it's specific to the posting. However it's about interview process; might be considered legal/EEO? Not exactly. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. The "Notice on Candidate AI Usage" is a policy about interview process; could be considered legal boilerplate. Safer to remove it. Also "See www.metassolutions.com for further details about us and careers with Metas." is navigation/link; remove. We need to include About Us? The instruction says use

for section headings (e.g. About the role...). There's no explicit "About the role" but we have "About Us". Could map to "About the role"? Probably we should use "About the role" heading for the description of role (Job Description). The "About Us" is company description; maybe we can include as a

without heading? The instruction says 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. We could include a heading "About the role" for the job description paragraph. Then "Responsibilities" heading for responsibilities list. "Qualifications" heading for qualifications (including required and preferred?). Could separate "Required Qualifications" and "Preferred Qualifications" but we only have Qualifications and Additional Preferred Qualifications. Could combine under Qualifications heading with sub-sections? But we must not invent headings not listed. Could use "Qualifications" for required, and maybe "Preferred Qualifications" as a separate heading? Not in list but could be okay? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive list. Safer to stick to those examples. So we can have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. However we have no explicit Pay or Schedule specifics besides "Market competitive salary, commensurate with experience and education." That's vague; we should not create Pay section if content is just "commensurate with experience" which is placeholder-like. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting says "Market competitive salary, commensurate with experience and education." That's basically placeholder; we should not create Pay section. Benefits: they list "Comprehensive benefits package available, Medical, Dental, Vision and Life Insurance, Paid Time Off (PTO), 401K with company match, growth, and promotion opportunities." That's specific benefits; we can create Benefits section. Schedule: not mentioned; omit. Requirements: we have qualifications (required). Could map to Requirements heading. But we also have Qualifications heading example. Use either Requirements or Qualifications. Since we have both required and preferred, we could use Requirements for required, and maybe Skills for preferred? But better to follow examples: Use Requirements for required qualifications, Qualifications for maybe both? Hmm. We need to preserve all substantive info. Let's extract: About Us: Metas Solutions excels in providing strategic consulting, program management, and data-driven analytics to federal public health agencies. Our expertise enhances health systems and delivers measurable outcomes, helping agencies achieve their mission. We collaborate with federal partners to implement agile solutions for national public health initiatives, driving impactful changes through cutting-edge programs that strengthen communities and promote well-being. Job Description: Metas Solutions has an "immediate opening" for an AI Adoption Specialist, who will support enterprise AI adoption. In this role, Specialist will work on a team to help develop strategies, roadmaps, and implementation approaches that align emerging technologies with mission priorities. Working alongside team members, technical staff, and client interest holders, Specialist will help translate AI capabilities into business recommendations, support responsible AI adoption efforts, and assist organizations through technology transformation initiatives. You'll bring project management, analytical thinking, communication skills, and a growing knowledge of AI to help support measurable mission outcomes. Responsibilities list (bullet points): - Develop and execute an AI adoption strategy, roadmap, business cases, and implementation plans aligned with agency objectives and federal priorities. - Serve as a functional SME for generative AI tools, with hands-on expertise in prompting and out-of-box capabilities across tools like ChatGPT, Claude, Gemini, NotebookLM, and Microsoft Copilot. - Lead workshops to identify business needs, assess and prioritize AI use cases, and translate AI capabilities into practical workflows. - Apply human-centered design, change management, and user experience practices to drive literacy and support responsible and sustainable AI adoption. - Design and deliver AI enablement programs, including role-based training series, demonstrations, office hours, playbooks, and self-service resources - Build and lead a network of AI champions and power users to share use cases, surface adoption barriers, and scale successful practices. - Research emerging AI technologies, generative AI capabilities, industry trends, and adoption approaches to inform strategic recommendations. - Monitor AI-related news and assess their potential impact on organizational policies and adoption. - Define and track adoption and impact measures to assess progress, identify adoption gaps, and inform ongoing priorities. Qualifications (required): - Bachelor's degree with 4+ years of experience in consulting, organizational change, or technology adoption - 2+ years of experience supporting AI adoption, generative AI initiatives, or technology transformation - Experience developing roadmaps, business cases, implementation plans, or adoption strategies - Experience applying change management and human-centered approaches techniques to increase technology adoption - Experience with generative AI tools, including prompting and applying out-of-box capabilities like custom GPTs/projects - Experience designing and facilitating workshops, peer-learning communities, training, and enablement activities for technical and non-technical audiences - Ability to translate AI capabilities and emerging technologies into practical business recommendations and use cases - Ability to manage multiple priorities in a fast-paced, client-facing environment - Ability to obtain and maintain a Public Trust or Suitability/Fitness determination based on client requirements - Must be a U.S. Citizen or Lawful Permanent Resident (Green Card Holder) Additional Preferred Qualifications: - Experience supporting federal, public health, healthcare, or other mission-driven organizations - Experience assessing emerging technologies and industry trends to inform organizational strategy - Knowledge of responsible AI, AI governance, or federal AI policies and guidance - Knowledge of cloud platforms, enterprise data ecosystems, or analytics platforms - Change management certification, such as Prosci or equivalent - Master's degree Security, Salary, And Benefits: - Must be US Citizen or Lawful Permanent Resident (Green Card Holder) with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period. - Market competitive salary, commensurate with experience and education. - Comprehensive benefits package available, Medical, Dental, Vision and Life Insurance, Paid Time Off (PTO), 401K with company match, growth, and promotion opportunities. We need to omit duplicated lines: The "Must be US Citizen or Lawful Permanent Resident (Green Card Holder)" appears twice (in Qualifications and Security section). We should keep only once? The instruction: remove duplicated lines. So we should deduplicate. Keep the requirement maybe in Qualifications; we can mention security clearance separately. We also need to remove boilerplate like "See www.metassolutions.com for further details about us and careers with Metas." and the AI usage notice and EEO statements. Now construct HTML. We'll have sections:

About the role

containing the job description paragraph(s). Could combine About Us and Job Description? Actually About the role likely refers to the role description. We'll put the Job Description paragraph there. Could also include a brief About Us as a

before? But we might not have a heading for About Us. Could include About Us as a

under About the role? Might be odd. Perhaps we create a section "About the company" but not in examples. Safer to include About Us as a

before any heading? The instruction says output ONLY the HTML fragment; we can include multiple

and

sections. We'll put About Us as a

leading, then

About the role

with the job description paragraph. Then

Responsibilities

with

• ...

. Then

Requirements

with

• ...

for required qualifications. Then

Preferred Qualifications

maybe not in examples but we could use

Skills

for preferred? But better to use

Qualifications

Preferred QualificationsBenefits with

• ...

for benefits. We need to include security clearance requirement somewhere; maybe under Requirements as a line. We must not include Pay or Schedule sections. Now ensure we preserve all substantive info: About Us paragraph, Job Description paragraph, responsibilities list, required qualifications list, preferred qualifications list, security clearance line, benefits list. Check for duplicated lines: The citizenship requirement appears in both required qualifications and security section. We'll keep it only once, maybe under Required Qualifications. The security clearance line is separate: "Must be US Citizen or Lawful Permanent Resident (Green Card Holder) with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period." This includes citizenship plus clearance. Since we already have citizenship, we can keep the clearance line but note citizenship again? To avoid duplication, we could rephrase: "Ability to obtain and maintain a US Government security clearance (Public Trust 5) within a reasonable period." But we must preserve substantive info; we can't change meaning. We could keep the line as is, but then citizenship appears twice. The instruction says remove duplicated lines. So we should eliminate duplicate citizenship mention. We could keep the security line and drop the separate citizenship line from qualifications. However the qualifications list includes citizenship as a separate bullet; we could remove that bullet and keep the security line that includes citizenship. But the qualifications list also includes "Ability to obtain and maintain a Public Trust or Suitability/Fitness determination based on client requirements". That's different from security clearance. Actually there are two: "Ability to obtain and maintain a Public Trust or Suitability/Fitness determination based on client requirements" (in Qualifications) and later "Must be US Citizen or Lawful Permanent Resident (Green Card Holder) with the ability to obtain a US Government security clearance (Public Trust 5) within a reasonable period." So we have both Public Trust/Suitability/Fitness determination and security clearance. They are similar but not identical. We'll keep both. Thus