AI SDLC Transformation Manager

Requirements

• . Qualifications: Might be same as requirements? But we have also "Bonus points if you have..." which could be Skills or Qualifications. We'll treat "Bonus points" as Skills or Preferred Qualifications. We'll create a

  Skills

  for those bonus points. Also maybe "Qualifications" could be the degree requirement etc. But we already have requirements includes degree. We could separate: Requirements = mandatory; Qualifications = maybe education? But the instruction says use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. We have mandatory requirements (years experience, etc). We have bonus points (skills). We have degree requirement (Bachelor's or equivalent). That could go under Qualifications. Let's assign: - Requirements: the minimum years experience items (5 years SDLC, 3 years multi-agent, 3 years consulting, 3 years flow metrics, 2 years AI/ML, Bachelor's degree or equivalent). Also maybe include the degree condition. - Qualifications: maybe the degree? But we already included degree in requirements. Could treat Qualifications as education? But we have no separate qualifications beyond degree. Could skip Qualifications heading if no specific content beyond what's already in requirements. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But they ask to use headings for those if content exists. We have content for Requirements (the list). For Qualifications we could include the degree requirement if not already in Requirements. But we could also include the degree under Requirements and not have Qualifications. That's okay; we just omit Qualifications heading if no specific content. Skills: Bonus points items. Benefits: The paragraph about benefits and link. Pay: The salary ranges per location. Schedule: Travel may be required, amount varies 0-100%. We must not include filler like "commensurate with experience". Not present. We must not include duplicated lines. Ensure we preserve all substantive info. Let's extract text. About the role: Combine first two paragraphs? Actually the posting starts: "We Are Strategic Technology Effectiveness, part of Accenture's Technology Strategy & Transformation Organization. We rebuild how large enterprises define, design and govern software, and we design and implement the agentic software and processes that run it. That work changes the operating model an engineering organization runs on, the ways of working underneath it, and the tooling that makes both of those real. We start with evidence. Cycle time, flow efficiency, WIP and throughput show where delivery stalls, and that diagnosis sets the target. What we design from it is AI-native by construction. We redesign intake and prioritization, so demand meets real capacity, and rebuild the path from request to release so planning, build, review, testing and deployment connect to each other instead of handing off through spreadsheets and status meetings. Most of our build work sits upstream, where the cost of rework gets set: requirements generation, user story synthesis, design review, architecture validation. That means creator and reviewer agent patterns, tool-use orchestration, and multi-agent workflows on enterprise frameworks, with a working understanding of what each pattern costs in tokens and where it breaks. We treat the lifecycle as a system and a product itself - built to operate at a speed required for the AI era. Then we make it stick. Engineering teams move to AI-augmented work and stay there, which is what separates a delivery organization where AI is how software gets made from the working pilot. Practitioner depth in delivery operating models and AI, paired with Accenture's global platform and technology expertise, puts us in front of delivery organizations at a scale few firms reach. You Are The AI SDLC Transformation Manager guides enterprise clients on redesigning software delivery to be AI-native. You've spent real time in software delivery, not just studying it. You know what broken looks like at the process level, and you know what good looks like when AI is woven in deliberately rather than bolted on." That's about the role and the manager. We'll put that as About the role. Responsibilities: The bullet list after "Role-Specific Responsibilities". Let's capture each line: - Value stream mapping and flow metric analysis (cycle time, flow efficiency, WIP, throughput) to identify waste in existing SDLC practices - Design of AI-native to-be processes that restructure and accelerate how software is defined, designed, and governed - Change management for engineering teams transitioning to AI-augmented workflows - Strategy and design of agentic systems targeting upstream SDLC phases: requirements generation, user story synthesis, design review, and architecture validation - Know how and where to use creator and reviewer agent patterns and the token impact of doing so. - Model SDLC as a system, identifying feedback loops, bottlenecks, and second-order effects of process changes - Cross-functional perspective spanning product, engineering, QA, security, and platform - Ability to maintain fluency in the rapidly evolving AI tooling ecosystem (coding assistants, agentic platforms, evaluation frameworks, MCP/tool orchestration) - Ongoing research practice tracking capability shifts, new model releases, and emerging practitioner patterns - Expertise in what digitally native organizations are doing today and ability to translate those benchmarks into actionable roadmaps for enterprise clients - Ability to influence clients to change and modernize processes that limit the positive impact of agentic ways of working and overall SDLC - Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements. Note: The last bullet about travel could be schedule, but it's under responsibilities. We'll keep it under responsibilities? But schedule section separate. We could move travel to Schedule. However it's part of responsibilities list. The instruction: include schedule section only if posting actually states them. It does state travel may be required. So we can put travel under Schedule. But we need to not duplicate. We'll keep travel under Schedule and remove from responsibilities list. However the responsibilities list includes that line; we could keep it there but also schedule duplicate. Better to move to Schedule and remove from responsibilities to avoid duplication. The instruction: preserve ALL substantive information; do not invent or summarize away detail. If we remove it from responsibilities, we still preserve it in Schedule. That's fine. Thus responsibilities list will exclude the travel line. Requirements: List under "Here’s What You Need". Let's capture each bullet: - Minimum of 5 years working across the full SDLC, requirements through release, with demonstrated ability to map, measure, and redesign delivery processes - Minimum of 3 years of hands-on experience designing or building multi-agent or LLM-integrated systems, including prompt engineering, tool-use orchestration, or agentic application development - Minimum of 3 years in a consulting or advisory capacity working with engineering organizations, ideally at enterprise scale (5,000+ employees or $1B+ revenue) - Minimum of 3 years applying flow metrics (cycle time, WIP, throughput, flow efficiency) or value stream mapping as active diagnostic tools, not just frameworks you've presented on - Minimum of 2 years working directly with AI/ML systems, LLMs, or agentic architectures in a professional, not just experimental, context - Bachelor's degree or equivalent (minimum 12 years) work experience. (If Associate’s Degree, must have minimum 6 years work experience) We'll put these under Requirements. Qualifications: Could be none separate. We'll omit. Skills: Bonus points items: - Hands-on experience with 2+ leading AI coding assistants (GitHub Copilot, Cursor, Amazon Q Developer, Cody) in enterprise environments - Experience designing lightweight LLM evals for AI-generated SDLC artifacts( requirements docs, user stories, design reviews) - Working knowledge of Model Context Protocol (MCP) and emerging tool orchestration standards - Fluency in at least one major delivery methodology (Agile, SAFe, continuous delivery) with a clear point of view on where AI creates the most leverage - Track record of presenting AI transformation strategies to VP- or C-level stakeholders and getting buy-in We'll put under Skills. Benefits: Paragraph: "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 need to keep the link as is. Pay: The compensation paragraph and location list. We have: "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. We anticipate this job posting will be posted until 11/30/2026." Then "Benefits" section (we already handled). Then "Role Location Annual Salary Range" with list of locations and ranges. We need to preserve all that. We'll put Pay section with that paragraph and the list. We should format the list as
  • each location: "Location $low to $high". We'll keep as is. Schedule: Travel may be required for this role. The amount of travel will vary from 0 to 100% depending on business need and client requirements. We'll put under Schedule. Now we need to output only HTML fragment,