Life Sciences - Reinvention Program Manager
Accenture · Albany, New York Metropolitan Area · 3 wk ago
Information Technology$94k–$294k/yrFull-time
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. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, accommodation, etc. Also remove duplicated lines, application instructions. Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes compensation ranges per location, benefits description, and maybe schedule? No explicit schedule (like full-time, remote). There's mention of travel willingness, but not schedule. So we can include Benefits and Pay sections. Schedule not present, so omit.
We need sections: About the role (the paragraph after "About The Role"). Responsibilities (the bullet list under "Work"). Requirements (the list of must-have qualifications). Qualifications? Might be overlapping with Requirements; but we can treat Requirements as must-have, Qualifications as preferred? The posting has "You Are An experienced practitioner..." which is more like qualifications/attributes. Then "Candidates must have at least 5 years of combined experience..." which are requirements. Then "Preferred Skills/experience" list. So we can map:
- About the role: paragraph(s) after "About The Role" up to "Work". Actually the text: "About The Role The Reinvention Program Manager is the operational backbone..." then a sentence. Then "Work Manage project communications..." seems to start responsibilities. So we can treat About the role as the first paragraph: "The Reinvention Program Manager is the operational backbone of the AI Transformation Office.This role keeps the program running with discipline, visibility, and momentum — managing communications, milestone tracking, portfolio reporting, and operating cadence across all workstreams.This is not a traditional PMO role — it is an AI-enabled program manager who uses automation to do what once required a team."
- Responsibilities: bullet list from "Work Manage project communications..." etc. Let's extract:
"Manage project communications, milestone tracking, and portfolio reporting across all transformation workstreams — giving the Portfolio Strategy & Value Lead the visibility needed to govern effectively"
"Track budget actuals against plan, surface variances early, and support governance reporting to the client's transformation leadership"
"Leverage AI-powered project management tools and automation to streamline program operations — this role is expected to be a practitioner of the tools deployed"
"Coordinate across Transformers, Workforce Architects, and AI & Data Innovators to maintain an integrated view of progress, dependencies, and risks"
"Maintain the operating cadence: cadence calls, status reports, risk logs, and action tracking across a fast-moving transformation engagement"
We'll put each as
.
- Requirements: "Candidates must have at least 5 years of combined experience in the following areas:" then bullet list:
"Program or project management at a top-tier consulting firm or in a complex enterprise delivery environment, with demonstrated experience managing multi-workstream programs from initiation through completion."
"A proven track record designing and maintaining program operating rhythms — including cadence calls, status reporting, risk logs, and budget tracking — for senior executive audiences."
"Experience leveraging AI-powered project management and automation tools to improve program visibility and reduce manual effort."
"Strong executive-ready written and verbal communication skills, including the ability to synthesize complex program status into clear, decision-ready materials."
"Experience coordinating across multidisciplinary teams including consultants, technologists, and change practitioners."
"Willingness and ability to travel domestically and internationally as client and business needs require."
- Qualifications/Skills: The "You Are An experienced practitioner..." paragraph includes attributes: analytically rigorous, structured thinking, communicate complex ideas clearly to senior stakeholders, comfortable in ambiguous environments, thrive in cross-functional delivery teams, supported business development, ready to take on more, intellectual curiosity, drive, genuine interest in how AI is transforming Life Sciences. Could be placed under Skills or Qualifications. We'll make a Skills section for those soft skills.
- Preferred Skills/experience: list:
"MBA or advanced degree in a relevant discipline."
"PMP, Agile/Scrum (CSM, SAFe), or equivalent program management certification."
"Experience managing AI-enabled transformation programs or enterprise change initiatives in Life Sciences."
"Familiarity with AI agent orchestration tools for program reporting, status automation, or backlog management."
"Track record at a top-tier consulting firm managing large-scale transformation program delivery across multiple simultaneous workstreams."
We could put these under Qualifications or Preferred Skills. Since we have a Skills section for attributes, we can put Preferred Skills under Qualifications or a separate "Preferred Qualifications". The instruction says use headings like Qualifications, Skills, Benefits, Pay, Schedule. We can decide to put "Qualifications" for the must-have requirements, and "Skills" for the preferred/experience and attributes. But we already used Requirements for must-have. So we need to map:
- About the role
- Responsibilities
- Requirements (must-have)
- Qualifications (maybe preferred? but we have Skills for attributes). Could combine preferred and attributes into Skills. Or we could have Qualifications for preferred and Skills for attributes. Let's do:
Requirements: must-have list.
Qualifications: preferred skills/experience list.
Skills: personal attributes (analytically rigorous, etc.)
But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include those headings as needed.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
We must not include Schedule.
Now Benefits: The posting says "Benefits Accenture offers a market competitive suite of benefits including medical, dental, vision, life, and long-term disability coverage, a 401(k) plan, bonus opportunities, paid holidays, and paid time off. See more information on our benefits here: U.S. Employee Benefits | Accenture". We'll keep that as a
with the description and maybe the link? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Should we keep the link? It's a link to benefits page. It's substantive. We'll include the inside the
. However we must not include navigation/legal/EEO etc. This is benefits link, okay.
Pay: The posting includes "Compensation at Accenture varies depending on a wide array of factors..." and then a list of location salary ranges. We need to preserve that. We'll include a
with the sentence about compensation varying, then maybe a
with each location and range. The instruction says use - for any list of duties/requirements/benefits. Pay is not a list of duties/requirements/benefits but it's a list of ranges; still we can use
for clarity. It's acceptable.
We must not include boilerplate like "As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below." That's part of pay description; we keep it.
Also "We anticipate this job posting will be posted until 11/01/2026." That's metadata; maybe we can drop as minor metadata? It's not job ID but could be considered minor. The instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short or drop it. This is a posting date; we could drop it or include in a short p. Safer to drop it as it's not substantive about the role. We'll drop.
Also "Role Location Annual Salary Range" heading before list; we can treat that as part of Pay section heading? We'll just list.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
Structure:
About the role
...
Responsibilities
Requirements
Qualifications
Skills
Benefits
...
Pay
Compensation at Accenture varies depending on a wide array of factors, which may include but are not limited to the specific office location, role, skill set, and level of experience. As required by local law, Accenture provides a reasonable range of compensation for roles that may be hired as set forth below.
- California: $94,400 to $293,800
...
Make sure to preserve line breaks? Not needed.
Check for any duplicated lines: we must avoid repeating. Ensure we didn't include any boilerplate like "We Are Accenture helps the world's leading enterprises..." That's introductory fluff; is that substantive? It's about the company, not the role. The instruction says preserve ALL substantive information; does that include company overview? It's not about the role but maybe considered background. However typical job posting includes that; but we might keep it as part of About the role? The instruction says "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." The company overview might be considered minor metadata? Not sure. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company overview is substantive about Accenture but not about the role. However the instruction earlier: "We Are Accenture helps the world's leading enterprises reinvent by building their digital core and unleashing the power of AI to create value at speed and scale. We are a talent- and innovation-led company with approximately 799,000 people serving clients in more than 120 countries. Accenture's Life Sciences Reinventive Enterprise practice leads AI-driven enterprise transformation at the world's leading pharmaceutical and biotechnology organizations. We deploy the Reinvention Force: a human + AI team of Transformers, Workforce Architects, and AI & Data Innovators that makes reinvention real at enterprise scale. This is a high-visibility, high-impact practice with strong momentum and a clear path to Managing Director for high performers." This is description of the practice. Could be considered part of About the role? Possibly we should include it as part of About the role section, as it gives context. The "About The Role" heading appears after that paragraph. So we could include that preceding text as part of About the role (makes sense). The instruction says "About the role" heading for section headings. So we can put that company/practice description in the About the role
. Then after that we have the specific role description. We'll combine.
Thus About the role
will contain the two paragraphs: first the company/practice overview, then the role description.
Let's extract:
First paragraph: "We Are Accenture helps the world's leading enterprises reinvent by building their digital core and unleashing the power of AI to create value at speed and scale. We are a talent- and innovation-led company with approximately 799,000 people serving clients in more than 120 countries. Accenture's Life Sciences Reinventive Enterprise practice leads AI-driven enterprise transformation at the world's leading pharmaceutical and biotechnology organizations. We deploy the Reinvention Force: a human + AI team of Transformers, Workforce Architects, and AI & Data Innovators that makes reinvention real at enterprise scale. This is a high-visibility, high-impact practice with strong momentum and a clear path to Managing Director for high performers."
Second paragraph (role): "The Reinvention Program Manager is the operational backbone of the AI Transformation Office.This role keeps the program running with discipline, visibility, and momentum — managing communications, milestone tracking, portfolio reporting, and operating cadence across all workstreams.This is not a traditional PMO role — it is an AI