Program Manager - AI Transformation
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only if present. Also maybe "Location" etc? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to parse the posting and extract sections.
The posting includes:
- Position Type: Contract Duration: 12+ Months (Strong possibility of extension and potential conversion) Location: Charlotte, NC | Chandler, AZ | Des Moines, IA (Hybrid 3 days onsite /2 days remote)
- As a Program Manager - AI Transformation, you will: bullet list of duties.
- The ideal candidate will have: bullet list of qualifications/experience.
- Qualified candidates should APPLY NOW... (application instructions) - we should remove application instructions.
- This position is only open to applicants who can be engaged on a W-2 basis. 1099 contractors and Corp-to-Corp arrangements will not be considered... (maybe part of eligibility, but could be considered metadata; we can fold into a short
maybe under Requirements? Not sure.)
- Referral program details: referral bonus $250-$1000, contact email, phone, etc. This is maybe not core job content but could be considered "Benefits"? Actually referral bonus is not a benefit to employee; it's a referral program. Probably we should drop as it's not part of job description. The instruction says remove duplicated lines, application instructions, cookie/navigation/legal/EEO etc. Referral program maybe not needed. It's not a core job duty/requirement/benefit. Likely we should drop.
- PAY RANGE AND BENEFITS: Pay Range*: $60 -$65 per hour *Pay range offered... Benefits: Innova Solutions offers benefits( based on eligibility) that include the following: list.
- ABOUT INNOVA SOLUTIONS: description.
- EEO etc: remove.
Thus we need sections: About the role (maybe a brief description), Responsibilities (the bullet list), Requirements (maybe the ideal candidate bullet list?), Qualifications (maybe overlapping), Skills (maybe tools proficiency), Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
We have:
- About the role: could be the introductory paragraph describing role: "As a Program Manager - AI Transformation, you will: ..." Actually that's responsibilities. The "About the role" could be a short prose about the position: maybe the first paragraph: "A client of Innova Solutions is immediately hiring for a Program Manager - AI Transformation Position Type: Contract Duration: 12+ Months (Strong possibility of extension and potential conversion) Location: Charlotte, NC | Chandler, AZ | Des Moines, IA (Hybrid 3 days onsite /2 days remote)". That includes position type, duration, location, hybrid schedule. That could be considered "About the role". We'll include that as prose.
- Responsibilities: bullet list after "As a Program Manager - AI Transformation, you will:" (the bullet list). We'll put that under
Responsibilities
with - each.
- Requirements: maybe the "The ideal candidate will have:" bullet list. That's qualifications/experience. Could be split into Requirements and Qualifications. But we need to avoid thin sections. Perhaps combine into one section "Requirements" containing that list. Or we could have "Qualifications" for the bullet list and "Skills" for tools proficiency. Let's see: The ideal candidate bullet list includes experience leading complex business execution, program management, transformation, operational delivery; experience in large complex highly regulated orgs preferably financial services; proficiency with Microsoft PowerPoint, Excel, Word, Teams, enterprise project management tools; experience supporting AI, automation, digital transformation, process improvement, technology implementation; experience coordinating pilots, proof-of-concepts, testing activities, implementation readiness, deployment planning, post-launch transitions; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
We could separate: Requirements: experience leading complex business execution, program management, transformation, operational delivery; experience in large complex highly regulated orgs preferably financial services; experience partnering with cross-functional teams; domain experience preferred. Qualifications: maybe the same? Actually the bullet list is all qualifications. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content.
We have specific mention of tools proficiency: Microsoft PowerPoint, Excel, Word, Teams, enterprise project management tools. That's skills.
Thus we could have:
- Requirements: experience leading complex business execution, program management, transformation, operational delivery; experience working in large, complex, highly regulated organizations, preferably within financial services; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, and Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
- Qualifications: maybe we could treat the same as Requirements? But to avoid thin sections, maybe we combine Requirements and Qualifications into one? However instruction says prefer a few substantive sections over many thin ones. So we could have just Requirements (covering experience) and Skills (tools). Qualifications maybe not needed if we already have Requirements covering qualifications. But we need to include Qualifications only if there is real specific content. The bullet list includes qualifications; but we could treat that as Requirements. The instruction didn't forbid merging; just said use those headings for sections. It didn't say we must use all. So we can choose to include only those sections that have substantive content.
Thus we will include:
About the role
with prose about position type, duration, location, hybrid schedule.
Responsibilities
with ul of duties.
Requirements
with ul of experience/qualifications (maybe combine the ideal candidate bullet list but exclude the tools proficiency? We'll include all except tools? Actually we could include all bullet points; then Skills separate for tools proficiency.
Thus Requirements bullet list: experience leading complex business execution, program management, transformation, or operational delivery initiatives; experience working in large, complex, highly regulated organizations, preferably within financial services; experience supporting AI, automation, digital transformation, process improvement, or technology implementation initiatives; experience coordinating pilots, proof-of-concepts, testing activities, implementation readiness, deployment planning, and post-launch transitions; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, and Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
Skills bullet list: Strong proficiency with Microsoft PowerPoint, Excel, Word, Teams, and enterprise project management tools.
Benefits: list from Benefits section.
Pay: Pay range $60 - $65 per hour.
Schedule: Hybrid 3 days onsite / 2 days remote (mentioned in location line). Could be included under Schedule.
We also have Position Type: Contract Duration: 12+ Months (Strong possibility of extension and potential conversion). That could be part of About the role or maybe a separate Contract section but not required. We'll include in About the role.
Now we need to remove boilerplate: referral program, application instructions, EEO, About Innova Solutions (maybe we could keep as About the company? Not requested; we could drop as not required. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. About Innova Solutions is specific content but not requested as a heading; we could include as a paragraph under About the role? But About the role is about the role, not company. However we could add a separate section "About the company" but not in the list of allowed headings. The allowed headings are only those listed; we should not add other headings. So we should omit About Innova Solutions.
Thus final HTML fragment:
About the role
Position Type: Contract. Duration: 12+ Months (Strong possibility of extension and potential conversion). Location: Charlotte, NC | Chandler, AZ | Des Moines, IA (Hybrid 3 days onsite / 2 days remote).
Responsibilities
- Lead the business execution and operational implementation of AI-driven initiatives across Unsecured Lending Operations (ULO).
- Translate strategic AI priorities into structured work plans, milestones, deliverables, ownership models, and target timelines.
- Drive day-to-day execution across multiple initiatives, pilots, transformation programs, and operational readiness activities.
- Maintain integrated project plans, action logs, risk registers, issue trackers, dependency maps, and governance artifacts.
- Coordinate activities across Operations, Product, Technology, Risk, Compliance, Finance, Change Management, and other business partners.
- Facilitate working sessions, document key decisions, monitor action items, and ensure timely execution of commitments.
- Identify execution risks, resource constraints, delivery gaps, and competing priorities before they impact business outcomes.
- Provide clear escalation paths, impact assessments, mitigation plans, and executive recommendations.
- Coordinate business requirements, user testing, implementation readiness, training dependencies, communication plans, and operational transition activities.
- Develop executive-level presentations, status reports, dashboards, and decision-ready materials highlighting progress, risks, dependencies, and next steps.
- Establish scalable governance frameworks, reporting standards, execution routines, and best practices for future AI initiatives.
Requirements
- Experience leading complex business execution, program management, transformation, or operational delivery initiatives.
- Experience working in large, complex, highly regulated organizations, preferably within financial services.
- Experience supporting AI, automation, digital transformation, process improvement, or technology implementation initiatives.
- Experience coordinating pilots, proof-of-concepts, testing activities, implementation readiness, deployment planning, and post-launch transitions.
- Experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, and Change Management teams.
- Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
Skills
- Strong proficiency with Microsoft PowerPoint, Excel, Word, Teams, and enterprise project management tools.
Benefits
- Medical & pharmacy coverage
- Dental/vision insurance
- 401(k)
- Health saving account (HSA) and Flexible spending account (FSA)
- Life Insurance
- Pet Insurance
- Short term and Long term Dis
- for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to parse the posting and extract sections. The posting includes: - Position Type: Contract Duration: 12+ Months (Strong possibility of extension and potential conversion) Location: Charlotte, NC | Chandler, AZ | Des Moines, IA (Hybrid 3 days onsite /2 days remote) - As a Program Manager - AI Transformation, you will: bullet list of duties. - The ideal candidate will have: bullet list of qualifications/experience. - Qualified candidates should APPLY NOW... (application instructions) - we should remove application instructions. - This position is only open to applicants who can be engaged on a W-2 basis. 1099 contractors and Corp-to-Corp arrangements will not be considered... (maybe part of eligibility, but could be considered metadata; we can fold into a short
maybe under Requirements? Not sure.) - Referral program details: referral bonus $250-$1000, contact email, phone, etc. This is maybe not core job content but could be considered "Benefits"? Actually referral bonus is not a benefit to employee; it's a referral program. Probably we should drop as it's not part of job description. The instruction says remove duplicated lines, application instructions, cookie/navigation/legal/EEO etc. Referral program maybe not needed. It's not a core job duty/requirement/benefit. Likely we should drop. - PAY RANGE AND BENEFITS: Pay Range*: $60 -$65 per hour *Pay range offered... Benefits: Innova Solutions offers benefits( based on eligibility) that include the following: list. - ABOUT INNOVA SOLUTIONS: description. - EEO etc: remove. Thus we need sections: About the role (maybe a brief description), Responsibilities (the bullet list), Requirements (maybe the ideal candidate bullet list?), Qualifications (maybe overlapping), Skills (maybe tools proficiency), Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: could be the introductory paragraph describing role: "As a Program Manager - AI Transformation, you will: ..." Actually that's responsibilities. The "About the role" could be a short prose about the position: maybe the first paragraph: "A client of Innova Solutions is immediately hiring for a Program Manager - AI Transformation Position Type: Contract Duration: 12+ Months (Strong possibility of extension and potential conversion) Location: Charlotte, NC | Chandler, AZ | Des Moines, IA (Hybrid 3 days onsite /2 days remote)". That includes position type, duration, location, hybrid schedule. That could be considered "About the role". We'll include that as prose. - Responsibilities: bullet list after "As a Program Manager - AI Transformation, you will:" (the bullet list). We'll put that under
Responsibilities
with- each.
- Requirements: maybe the "The ideal candidate will have:" bullet list. That's qualifications/experience. Could be split into Requirements and Qualifications. But we need to avoid thin sections. Perhaps combine into one section "Requirements" containing that list. Or we could have "Qualifications" for the bullet list and "Skills" for tools proficiency. Let's see: The ideal candidate bullet list includes experience leading complex business execution, program management, transformation, operational delivery; experience in large complex highly regulated orgs preferably financial services; proficiency with Microsoft PowerPoint, Excel, Word, Teams, enterprise project management tools; experience supporting AI, automation, digital transformation, process improvement, technology implementation; experience coordinating pilots, proof-of-concepts, testing activities, implementation readiness, deployment planning, post-launch transitions; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
We could separate: Requirements: experience leading complex business execution, program management, transformation, operational delivery; experience in large complex highly regulated orgs preferably financial services; experience partnering with cross-functional teams; domain experience preferred. Qualifications: maybe the same? Actually the bullet list is all qualifications. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content.
We have specific mention of tools proficiency: Microsoft PowerPoint, Excel, Word, Teams, enterprise project management tools. That's skills.
Thus we could have:
- Requirements: experience leading complex business execution, program management, transformation, operational delivery; experience working in large, complex, highly regulated organizations, preferably within financial services; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, and Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
- Qualifications: maybe we could treat the same as Requirements? But to avoid thin sections, maybe we combine Requirements and Qualifications into one? However instruction says prefer a few substantive sections over many thin ones. So we could have just Requirements (covering experience) and Skills (tools). Qualifications maybe not needed if we already have Requirements covering qualifications. But we need to include Qualifications only if there is real specific content. The bullet list includes qualifications; but we could treat that as Requirements. The instruction didn't forbid merging; just said use those headings for sections. It didn't say we must use all. So we can choose to include only those sections that have substantive content.
Thus we will include:
About the role
with prose about position type, duration, location, hybrid schedule.Responsibilities
with ul of duties.Requirements
with ul of experience/qualifications (maybe combine the ideal candidate bullet list but exclude the tools proficiency? We'll include all except tools? Actually we could include all bullet points; then Skills separate for tools proficiency. Thus Requirements bullet list: experience leading complex business execution, program management, transformation, or operational delivery initiatives; experience working in large, complex, highly regulated organizations, preferably within financial services; experience supporting AI, automation, digital transformation, process improvement, or technology implementation initiatives; experience coordinating pilots, proof-of-concepts, testing activities, implementation readiness, deployment planning, and post-launch transitions; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, and Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred. Skills bullet list: Strong proficiency with Microsoft PowerPoint, Excel, Word, Teams, and enterprise project management tools. Benefits: list from Benefits section. Pay: Pay range $60 - $65 per hour. Schedule: Hybrid 3 days onsite / 2 days remote (mentioned in location line). Could be included under Schedule. We also have Position Type: Contract Duration: 12+ Months (Strong possibility of extension and potential conversion). That could be part of About the role or maybe a separate Contract section but not required. We'll include in About the role. Now we need to remove boilerplate: referral program, application instructions, EEO, About Innova Solutions (maybe we could keep as About the company? Not requested; we could drop as not required. The instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. About Innova Solutions is specific content but not requested as a heading; we could include as a paragraph under About the role? But About the role is about the role, not company. However we could add a separate section "About the company" but not in the list of allowed headings. The allowed headings are only those listed; we should not add other headings. So we should omit About Innova Solutions. Thus final HTML fragment:About the role
Position Type: Contract. Duration: 12+ Months (Strong possibility of extension and potential conversion). Location: Charlotte, NC | Chandler, AZ | Des Moines, IA (Hybrid 3 days onsite / 2 days remote).
Responsibilities
- Lead the business execution and operational implementation of AI-driven initiatives across Unsecured Lending Operations (ULO).
- Translate strategic AI priorities into structured work plans, milestones, deliverables, ownership models, and target timelines.
- Drive day-to-day execution across multiple initiatives, pilots, transformation programs, and operational readiness activities.
- Maintain integrated project plans, action logs, risk registers, issue trackers, dependency maps, and governance artifacts.
- Coordinate activities across Operations, Product, Technology, Risk, Compliance, Finance, Change Management, and other business partners.
- Facilitate working sessions, document key decisions, monitor action items, and ensure timely execution of commitments.
- Identify execution risks, resource constraints, delivery gaps, and competing priorities before they impact business outcomes.
- Provide clear escalation paths, impact assessments, mitigation plans, and executive recommendations.
- Coordinate business requirements, user testing, implementation readiness, training dependencies, communication plans, and operational transition activities.
- Develop executive-level presentations, status reports, dashboards, and decision-ready materials highlighting progress, risks, dependencies, and next steps.
- Establish scalable governance frameworks, reporting standards, execution routines, and best practices for future AI initiatives.
Requirements
- Experience leading complex business execution, program management, transformation, or operational delivery initiatives.
- Experience working in large, complex, highly regulated organizations, preferably within financial services.
- Experience supporting AI, automation, digital transformation, process improvement, or technology implementation initiatives.
- Experience coordinating pilots, proof-of-concepts, testing activities, implementation readiness, deployment planning, and post-launch transitions.
- Experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, and Change Management teams.
- Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
Skills
- Strong proficiency with Microsoft PowerPoint, Excel, Word, Teams, and enterprise project management tools.
Benefits
- Medical & pharmacy coverage
- Dental/vision insurance
- 401(k)
- Health saving account (HSA) and Flexible spending account (FSA)
- Life Insurance
- Pet Insurance
- Short term and Long term Dis
- each.
- Requirements: maybe the "The ideal candidate will have:" bullet list. That's qualifications/experience. Could be split into Requirements and Qualifications. But we need to avoid thin sections. Perhaps combine into one section "Requirements" containing that list. Or we could have "Qualifications" for the bullet list and "Skills" for tools proficiency. Let's see: The ideal candidate bullet list includes experience leading complex business execution, program management, transformation, operational delivery; experience in large complex highly regulated orgs preferably financial services; proficiency with Microsoft PowerPoint, Excel, Word, Teams, enterprise project management tools; experience supporting AI, automation, digital transformation, process improvement, technology implementation; experience coordinating pilots, proof-of-concepts, testing activities, implementation readiness, deployment planning, post-launch transitions; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
We could separate: Requirements: experience leading complex business execution, program management, transformation, operational delivery; experience in large complex highly regulated orgs preferably financial services; experience partnering with cross-functional teams; domain experience preferred. Qualifications: maybe the same? Actually the bullet list is all qualifications. The instruction says use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include based on content.
We have specific mention of tools proficiency: Microsoft PowerPoint, Excel, Word, Teams, enterprise project management tools. That's skills.
Thus we could have:
- Requirements: experience leading complex business execution, program management, transformation, operational delivery; experience working in large, complex, highly regulated organizations, preferably within financial services; experience partnering with Operations, Product, Technology, Risk, Compliance, Finance, and Change Management teams; Financial Services, Consumer Lending, Servicing, Collections, Contact Center, or Operations domain experience is highly preferred.
- Qualifications: maybe we could treat the same as Requirements? But to avoid thin sections, maybe we combine Requirements and Qualifications into one? However instruction says prefer a few substantive sections over many thin ones. So we could have just Requirements (covering experience) and Skills (tools). Qualifications maybe not needed if we already have Requirements covering qualifications. But we need to include Qualifications only if there is real specific content. The bullet list includes qualifications; but we could treat that as Requirements. The instruction didn't forbid merging; just said use those headings for sections. It didn't say we must use all. So we can choose to include only those sections that have substantive content.
Thus we will include: