Senior IT Project Manager-Application Transitions & Migrations
NTT DATA North America · Pittsburgh, PA · 1 mo ago
Hybrid$55–$62/hrOther
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. The posting includes many details: responsibilities (Key Responsibilities), Experience & Qualifications (qualifications), Preferred Qualifications, Key Competencies (skills). No explicit Benefits, Pay, Schedule. So we should not include those sections. Also we should not repeat job title. Provide headings for each section we include.
We need to preserve all substantive information, not invent. Remove boilerplate like equal opportunity, etc. Also remove navigation, cookie, etc. The posting includes a paragraph about NTT DATA at start, then description. We need to include that as part of About the role? Probably "About the role" section should contain the descriptive overview about the role and company. The initial paragraph: "At NTT DATA, we know that with the right people on board, anything is possible..." That's generic company fluff; but it's part of posting. We should keep it? It's substantive? It's generic but maybe we keep as part of About the role. However we should avoid boilerplate like EEO etc. The equal opportunity statement at end should be removed.
We need to format responsibilities as
for each section we include.
We need to preserve all substantive information, not invent. Remove boilerplate like equal opportunity, etc. Also remove navigation, cookie, etc. The posting includes a paragraph about NTT DATA at start, then description. We need to include that as part of About the role? Probably "About the role" section should contain the descriptive overview about the role and company. The initial paragraph: "At NTT DATA, we know that with the right people on board, anything is possible..." That's generic company fluff; but it's part of posting. We should keep it? It's substantive? It's generic but maybe we keep as part of About the role. However we should avoid boilerplate like EEO etc. The equal opportunity statement at end should be removed.
We need to format responsibilities as - . The responsibilities are listed under "Key Responsibilities" with bullet-like paragraphs. We need to extract each responsibility item. The text includes multiple paragraphs under "Key Responsibilities". We can treat each paragraph as a list item. Similarly for Knowledge Transfer & Data Request Coordination and Project & Portfolio Governance could be sub-sections under Responsibilities? But we can keep as part of Responsibilities list.
Experience & Qualifications: list of requirements. We'll put under Requirements section (maybe also Qualifications). The posting separates Experience & Qualifications and Preferred Qualifications. We could combine into Requirements (mandatory) and Qualifications (preferred). But instructions: use headings for Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide what goes where.
We have Experience & Qualifications (mandatory) and Preferred Qualifications (preferred). Also Key Competencies (skills). So we can map:
- About the role: introductory paragraphs (company description and role overview).
- Responsibilities: all responsibilities bullet points (including Knowledge Transfer & Data Request Coordination and Project & Portfolio Governance).
- Requirements: mandatory experience & qualifications (the 5+ years etc).
- Qualifications: preferred qualifications (the list after "Preferred Qualifications").
- Skills: Key Competencies list.
We must not include Benefits, Pay, Schedule.
We need to ensure we don't include filler like "commensurate with experience". Not present.
Now craft HTML.
We need to preserve all substantive information. Let's extract text.
Intro paragraph: "At NTT DATA, we know that with the right people on board, anything is possible. The quality, integrity, and commitment of our employees have been key factors in our company's growth and market presence. By hiring the best people and helping them grow both professionally and personally, we ensure a bright future for NTT DATA and for the people who work here. For more than 25 years, NTT DATA Services have focused on impacting the core of your business operations with industry-leading outsourcing services and automation. With our industry-specific platforms, we deliver continuous value addition, and innovation that will improve your business outcomes. Outsourcing is not just a method of gaining a one-time cost advantage, but an effective strategy for gaining and maintaining competitive advantages when executed as part of an overall sourcing strategy. NTT DATA's Client is seeking an experienced Senior IT Project Manager M&A to provide IT oversight, coordination, and transition leadership across a portfolio of business applications associated with a large-scale acquisition carve-out and transition program. The individual will serve as the primary IT point of accountability for assigned applications, ensuring each application has appropriate business and IT ownership, a clearly defined transition approach, accountable delivery leadership, and all required IT activities identified, coordinated, and completed. The role will also coordinate and drive Knowledge Transfer (KT) and Data Request activities necessary to support application transitions, operational readiness, and business continuity. This position extends beyond traditional project management. Individual application initiatives may be managed by a dedicated project manager, business lead, application owner, or functional stakeholder. The successful candidate will work effectively across these different delivery models, providing IT governance and oversight, assessing transition readiness, identifying gaps and dependencies, coordinating required technology activities, facilitating knowledge acquisition, and diving into application-level details when required to drive successful outcomes. The ideal candidate will combine strong project and program management discipline with hands-on experience in enterprise application delivery, business engagement, transition management, stakeholder coordination, and M&A/carve-out environments."
That's a lot; we can keep as About the role.
Now Responsibilities: Under "Key Responsibilities" heading, there are several paragraphs:
1. Application Transition Leadership & IT Oversight
- Serve as the primary IT lead and point of accountability for an assigned portfolio of application transition, separation, migration, and implementation initiatives.
- Ensure each assigned application has clearly defined business and IT ownership, an appropriate project or transition workplan, accountable delivery leadership, and a defined path to implementation, transition, and operational support.
- Assess the delivery model and level of IT involvement required for each application initiative. Some initiatives may have a dedicated IT Project Manager, while others may be business-led with IT providing specific activities, governance, and oversight.
- Partner with project managers, business leads, application owners, and technical teams to maintain visibility into milestones, risks, dependencies, decisions, issues, and outstanding IT actions without duplicating existing project management responsibilities.
- Dive into application-level details as required to identify gaps, clarify requirements, confirm dependencies, establish ownership, and drive unresolved issues to closure.
- Assess and confirm application readiness throughout the transition lifecycle, including: Business and technical requirements Solution design and architecture Infrastructure readiness Security and access requirements Interfaces and integrations Data requirements and migration Testing and validation Cutover and deployment planning Documentation Knowledge transfer Operational support and ownership
- Coordinate and drive completion of required IT activities, particularly for business-led initiatives where dedicated IT project management support may not be available.
- Coordinate cross-functional teams across business functions, IT, infrastructure, security, application teams, vendors, service providers, and third-party consultants.
- Support vendor engagement activities as required, including solution evaluations, Statement of Work (SOW) development, estimation, procurement coordination, and delivery tracking.
- Maintain portfolio-level visibility and provide concise executive-level reporting on application status, transition readiness, risks, dependencies, decisions, and areas requiring leadership intervention.
- Proactively identify and escalate applications that lack appropriate ownership, resources, transition plans, decisions, documentation, technical readiness, or delivery accountability.
- Drive issue resolution and accountability across stakeholders to ensure critical transition milestones and business continuity requirements are achieved.
2. Knowledge Transfer & Data Request Coordination
- Coordinate Knowledge Transfer (KT) activities with business stakeholders, application owners, IT teams, vendors, incumbent service providers, and external parties.
- Ensure KT requests are clearly defined, appropriately documented, submitted through established processes, tracked, and driven through completion.
- Engage with business users, application owners, SMEs, and technology teams to understand existing application knowledge and identify gaps requiring additional documentation, training, or knowledge transfer sessions.
- Facilitate discovery workshops and discussions to understand: Application functionality Supported business processes User groups and stakeholders Application ownership Interfaces and integrations Data flows Infrastructure and hosting Security requirements Upstream and downstream dependencies Operational processes Support models Technical architecture
- Translate identified knowledge gaps into structured, actionable KT requests and coordinate sessions with the appropriate subject matter experts.
- Coordinate Data Requests from business and IT stakeholders by helping define requirements, gather required information, identify data owners, and ensure requests are submitted through established channels and processes.
- Track KT and Data Requests through completion, proactively managing follow-ups, actions, dependencies, approvals, scheduling constraints, and issue resolution.
- Ensure KT outputs, technical documentation, process documentation, architecture information, operational procedures, support information, and other transition artifacts are captured and made available to the appropriate teams.
- Support knowledge retention and operational readiness to ensure receiving teams can effectively support applications following transition or separation.
3. Project & Portfolio Governance
- Establish and maintain appropriate governance across assigned applications and workstreams.
- Track key milestones, deliverables, risks, issues, assumptions, dependencies, decisions, and actions.
- Maintain RAID logs, readiness trackers, transition plans, status dashboards, and other project governance artifacts as required.
- Facilitate regular project, application, and stakeholder meetings and ensure actions and decisions are documented and followed through.
- Identify cross-application dependencies and risks that may impact broader transition timelines or business operations.
- Provide clear and timely escalation of critical issues to program leadership and senior stakeholders.
- Work collaboratively with program management, PMO, business leadership, and technology teams to ensure alignment with overall transition objectives.
We need to convert each bullet into
- . Some bullet points contain colon lists; we can keep as text inside
- .
Now Requirements (Experience & Qualifications):
- 5+ years of experience leading or coordinating complex IT application initiatives, programs, projects, transition programs, or application portfolios.
- Demonstrated success managing work across multiple concurrent applications, stakeholders, vendors, and delivery models.
- 5+ years of strong project and program management discipline, including experience assessing and managing:
- Project plans and milestones
- Risks and issues
- Dependencies
- Governance
- Ownership
- Readiness
- Resource requirements
- Decision-making and escalation
- Ability to operate effectively at both the portfolio/program level and the detailed application level.
- Strong business relationship management, stakeholder management, facilitation, communication, and presentation skills.
- Proven ability to build credibility, influence stakeholders, drive accountability, and navigate challenging cross-functional discussions.
- Working knowledge of enterprise application delivery and transition activities, including infrastructure, security, integrations, testing, deployment, cutover planning, documentation, knowledge transfer, and operational support.
- Experience gathering business and technical requirements and translating them into actionable technology plans, workstreams, decisions, and execution activities.
- Experience facilitating discovery sessions, documenting business processes and application landscapes, identifying knowledge gaps, and coordinating cross-functional information-gathering activities.
- Proven experience managing Knowledge Transfer, documentation, data collection, and transition-readiness activities involving multiple stakeholders.
- Strong analytical and problem-solving skills with the ability to identify gaps, dependencies, risks, and ownership issues and drive them to resolution.
- Ability to work effectively in complex, fast-paced transformation environments with multiple parallel initiatives and competing priorities.
We need to format as list items. Some items have sublists (like the bullet with colon). We could keep as a single
- containing a
inside? The instruction: Use - for any list of duties/requirements/benefits. It doesn't forbid nested lists. But to keep simple, we could flatten: each subpoint as separate
- . However that may lose grouping. But it's okay.
We'll produce
with - for each requirement. For the one with colon, we can make the main requirement as a
- and then nested
for subpoints. That is still a list of requirements. Acceptable.
Now Qualifications (Preferred Qualifications):
- 5+ years of experience supporting mergers, acquisitions, divestitures, separations, or carve-out programs.
- Experience with enterprise application transitions, migrations, TSA exits, application rationalization, or operational handovers.
- Experience working with geographically distributed teams, global stakeholders, vendors, and third-party service providers.
- Experience supporting application discovery, transition planning, knowledge transfer, data migration, and operational readiness activities.
- Prior experience within Life Sciences, Healthcare, Pharmaceutical, Medical Devices, or other highly regulated industries is desirable.
- PMP, PRINCE2, Agile, Scrum, or equivalent project/program management certification is preferred.
Now Skills (Key Competencies): list:
- IT Project & Program Management
- M&A / Carve-Out Transition Management
- Enterprise Application Transition
- Portfolio Governance
- Knowledge Transfer Management
- Application Discovery & Read
- inside? The instruction: Use
- for any list of duties/requirements/benefits. It doesn't forbid nested lists. But to keep simple, we could flatten: each subpoint as separate
- . However that may lose grouping. But it's okay.
We'll produce
- with
- for each requirement. For the one with colon, we can make the main requirement as a
- and then nested
- for subpoints. That is still a list of requirements. Acceptable.
Now Qualifications (Preferred Qualifications):
- 5+ years of experience supporting mergers, acquisitions, divestitures, separations, or carve-out programs.
- Experience with enterprise application transitions, migrations, TSA exits, application rationalization, or operational handovers.
- Experience working with geographically distributed teams, global stakeholders, vendors, and third-party service providers.
- Experience supporting application discovery, transition planning, knowledge transfer, data migration, and operational readiness activities.
- Prior experience within Life Sciences, Healthcare, Pharmaceutical, Medical Devices, or other highly regulated industries is desirable.
- PMP, PRINCE2, Agile, Scrum, or equivalent project/program management certification is preferred.
Now Skills (Key Competencies): list:
- IT Project & Program Management
- M&A / Carve-Out Transition Management
- Enterprise Application Transition
- Portfolio Governance
- Knowledge Transfer Management
- Application Discovery & Read