Pilot Pod Lead 6538776

Accenture•St. Louis, MO

23h•$85 - $95•Onsite

About The Position

The Pilot Pod Lead will lead a pilot pod for an application remediation project focused on critical remediation, piloting remediation for selected critical applications. The project aims to accelerate critical remediation, build sustainable currency capabilities, and establish the operating model and governance needed to sustain progress. An initial five-week mobilization sprint will establish the program operating model and enable technical delivery teams to begin work on real findings after deployment. The lead will work with application owners, engineering subject matter experts, and business and function currency leads to understand application architectures, technology stacks, and remediation constraints. They will assess vulnerability and currency findings, dependencies, potential impact, and cross-application or cross-business-unit integration risks; identify release, change authorization, and testing constraints; and document initial remediation approaches and sequencing as the basis for application-specific delivery plans. This is an Accenture Flex role involving local metro-area onsite work at the project, with reduced or eliminated travel demands. Accenture Flex describes its work as local, fixed-duration, project-based. The role requires application architecture experience, Java experience, and at least seven years of experience. A high school diploma or GED is required. The listed hourly salary range is $85 to $95, depending on role-related factors and location.

Requirements

At least 7 years of experience.
Applications architecture experience.
Java experience.
High school diploma or GED.

Responsibilities

Lead the pilot pod focused on critical remediation and pilot remediation for selected critical applications.
Engage application owners, engineering subject matter experts, and business and function currency leads to understand each application's architecture, technology stack, and known remediation constraints.
Assess application-specific vulnerability and currency findings, including component dependencies, blast radius, and cross-application or cross-business-unit integration risks.
Identify release constraints, change authorization requirements, and testing dependencies that shape each application's remediation approach.
Document the initial remediation approach and sequencing for each application as the basis for its delivery plan.