AI Solutions Manager

We need to output HTML fragment with sections using

for headings: 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. No Job ID etc. Remove boilerplate like EEO, accommodation, etc. Also remove application instructions. We need to preserve all substantive information. Let's parse the posting: "The Role: ..." paragraph describing role. That's about the role. Then "What You’ll Do:" with bullet list (actually sentences). That's responsibilities. Then "What We’re Looking For:" list of qualifications/requirements/skills. Also there is mention of LVCVA Ambassadors expectations (Do the Right Thing etc.) - that's maybe part of culture/values but not a specific section heading; could be part of Requirements or Skills? It's about expected behavior. Could be included under Requirements or maybe as a separate section like "Expectations". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map. We have no explicit Benefits, Pay, Schedule info. So we should not include those sections. We need to decide what goes where. "About the role": The initial paragraph describing role. "Responsibilities": The "What You’ll Do:" list. "Requirements": maybe the education/experience baseline: "A bachelor's degree ... OR a high school diploma plus four years of additional equivalent experience. 3+ years of experience ...". That's requirements. "Qualifications": maybe the demonstrated abilities etc. Could be overlapping. But we can separate: Requirements = education/experience baseline; Qualifications = demonstrated ability etc. Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one? But we have both headings allowed; we could include both if they have distinct content. Let's extract: Education/Experience: - A bachelor's degree in Business, Information Systems, Analytics, Engineering, Operations Management, Computer Science, or a related field, OR a high school diploma plus four years of additional equivalent experience. - 3+ years of experience in project management, business analysis, process improvement, or a related discipline. Demonstrated abilities: - Demonstrated ability to gather requirements from stakeholders and translate business needs into clear, actionable specifications. - Experience documenting workflows, processes, and decision logic in a form that technical teams can build from. - Practical understanding of what AI-native solutions can and cannot do. - Experience defining measurable success criteria and baselines before a project begins, and measuring realized results against them. - Experience owning a solution after launch, including user adoption, feedback, and iteration. - Excellent written and verbal communication skills, with the ability to write for both technical teams and executive audiences. - Strong facilitation and relationship-building skills at all levels of an organization. - AI tool proficiency, including hands-on use of AI assistants and agentic tools such as Claude to produce finished work, and willingness to build straightforward automations directly; training will be provided. - Microsoft Office proficiency (Word, Excel, PowerPoint). - Detail-oriented and organized, with the ability to manage multiple concurrent projects in a fast-paced environment. - All LVCVA Ambassadors are expected to demonstrate “Do the Right Thing”, “Vegas for All”, and “Be Extraordinary” by acting with integrity, fostering an inclusive and welcoming environment, and delivering exceptional service in everything they do. That last is about expected behavior; could be part of Skills or Requirements. We could put that under Skills. Thus sections:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

(education/experience)

Skills

• ...
...

(the demonstrated abilities plus maybe communication etc.) We should not include Qualifications if we already have Requirements and Skills; but we could also have Qualifications separate. However instruction: Prefer a few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one "Requirements" section, and Skills separate. But we have both headings allowed; we can decide to include Requirements and Skills only. Let's see if any content fits Qualifications better than Requirements: The list of "What We’re Looking For:" includes both education/experience and demonstrated abilities. Could treat all as qualifications. But we already have About the role and Responsibilities. Then we could have a single "Qualifications" section covering everything else. That would be fewer sections. But we also have Skills heading allowed. Could we split into Qualifications (education/experience) and Skills (abilities)? That's two sections. Given the instruction to prefer few substantive sections, maybe we should have About the role, Responsibilities, Qualifications (covering education/experience and abilities). That's three sections. But we also have Skills heading; we could omit Skills if we put everything in Qualifications. Let's decide: We'll output About the role, Responsibilities, Qualifications. Now we need to ensure we don't include filler like "commensurate with experience". Not present. We need to remove EEO boilerplate etc. The last paragraph about equal employment opportunity and accommodation should be removed. Also remove "All LVCVA Ambassadors are expected to demonstrate ..."? That's substantive about expected behavior; we should keep it. It's not boilerplate; it's part of expectations. Keep it. Now craft HTML. We need to preserve all substantive information: The role paragraph, responsibilities list, qualifications list. Let's extract role paragraph exactly: "The Role: The LVCVA's AI & Enterprise Performance team designs and builds AI-native solutions for departments across the organization, including applications, dashboards, agents, and automated workflows. Most of what determines whether AI solutions work happens before anything is built, and after it launches. The AI Solutions Manager is responsible for both ends. Reporting to the Director, AI Systems & Integration, this position is assigned projects across various departments, maps how the work is done today, sees where AI fits and where it does not, and writes the requirements the team builds from. Once a solution is live, this role stays with it to confirm it is used, accurate, and doing what it was built to do. This role requires strong organization, the ability to manage concurrent projects, and comfort working with teams at every level. It also requires a problem solver, someone curious by nature, who asks the questions that surface how a process really works, and who is comfortable with problems that do not yet have a clear answer." We should remove the leading "The Role:" maybe? It's part of the heading but we are using

About the role

. So we can start the paragraph after that. The content after colon is the description. We'll output that as

...

. Now responsibilities: "What You’ll Do:" then list items each starting with a verb. We need to capture each as

. The list includes: - Intake and Discovery Review AI solution requests from departments and record what each one is trying to accomplish. Meet with department leadership and subject matter experts to understand the reasoning behind each request, not just the requirement. Document current processes, including steps, business rules, exceptions, and completion criteria. Create the process maps, decision trees, and data source inventories the team builds from. But the formatting is a bit messy. The original text: "What You’ll Do: Keep in mind that this list is not all-inclusive. Intake and Discovery Review AI solution requests from departments and record what each one is trying to accomplish.Meet with department leadership and subject matter experts to understand the reasoning behind each request, not just the requirement.Document current processes, including steps, business rules, exceptions, and completion criteria.Create the process maps, decision trees, and data source inventories the team builds from. Solution Design Recommend the form a solution should take, whether an application, a dashboard, an agent, or an automated workflow.Specify what each solution must do, what it must not do, the systems and data it must reach, and where a person reviews or approves its output.Set success measures, baselines, and a measurement framework before work begins. Adoption and Iteration Test each solution against its acceptance criteria, then train department staff on how to use it and what to do when output looks wrong.Follow up after launch to confirm the solution is working, and measure results against the baselines.Refine each solution over time based on how it performs in practice and what the department learns using it." We need to split into logical items. The headings within: Intake and Discovery, Solution Design, Adoption and Iteration. Each has multiple sentences. We can treat each heading as a group, but we need

items. Could make each sentence a separate

or group them. The instruction: Use

• for any list of duties/requirements/benefits. So we should break into items. Probably each bullet point is a duty. We can split by the headings and then each sentence. Let's extract duties: Intake and Discovery: - Review AI solution requests from departments and record what each one is trying to accomplish. - Meet with department leadership and subject matter experts to understand the reasoning behind each request, not just the requirement. - Document current processes, including steps, business rules, exceptions, and completion criteria. - Create the process maps, decision trees, and data source inventories the team builds from. Solution Design: - Recommend the form a solution should take, whether an application, a dashboard, an agent, or an automated workflow. - Specify what each solution must do, what it must not do, the systems and data it must reach, and where a person reviews or approves its output. - Set success measures, baselines, and a measurement framework before work begins. Adoption and Iteration: - Test each solution against its acceptance criteria, then train department staff on how to use it and what to do when output looks wrong. - Follow up after launch to confirm the solution is working, and measure results against the baselines. - Refine each solution over time based on how it performs in practice and what the department learns using it. Also there is a line "Keep in mind that this list is not all-inclusive." That's not a duty; we can ignore or include as a note? Probably we should not include as it's meta. We'll omit. Now qualifications/requirements: Education/Experience: - A bachelor's degree in Business, Information Systems, Analytics, Engineering, Operations Management, Computer Science, or a related field, OR a high school diploma plus four years of additional equivalent experience. - 3+ years of experience in project management, business analysis, process improvement, or a related discipline. Demonstrated abilities (we can treat as qualifications): - Demonstrated ability to gather requirements from stakeholders and translate business needs into clear, actionable specifications. - Experience documenting workflows, processes, and decision logic in a form that technical teams can build from. - Practical understanding of what AI-native solutions can and cannot do. - Experience defining measurable success criteria and baselines before a project begins, and measuring realized results against them. - Experience owning a solution after launch, including user adoption, feedback, and iteration. - Excellent written and verbal communication skills, with the ability to write for both technical teams and executive audiences. - Strong facilitation and relationship-building skills at all levels of an organization. - AI tool proficiency, including hands-on use of AI assistants and agentic tools such as Claude to produce finished work, and willingness to build straightforward automations directly; training will be provided. - Microsoft Office proficiency (Word, Excel, PowerPoint). - Detail-oriented and organized, with the ability to manage multiple concurrent projects in a fast-paced environment. - All LVCVA Ambassadors are expected to demonstrate “Do the Right Thing”, “Vegas for All”, and “Be Extraordinary” by acting with integrity, fostering an inclusive and welcoming environment, and delivering exceptional service in everything they do. We could also include "training will be provided" as part of AI tool proficiency bullet. Now we need to output HTML. We'll have:

  About the