Onboarding Project Manager

Pls share profiles on below urgent requirement for Contingent workers

Role - Onboarding Project Manager

Contingent Worker

Shift Timings: 1:30 PM to 10:30 PM IST

Location: Bangalore

Hybrid Working: 3 days a week

CTC - Pls share the market range

Good communication skills

No of Roles: 1

Notice Period - Immediate

JR014432


Onboarding Project Manager

Role Overview:

We are seeking an Onboarding Project Manager with proven experience in application support transitions and managed services onboarding. The role will lead end-to-end onboarding across multiple applications, from intake and assessment through knowledge transfer, operational readiness, go-live and stabilization. Working across client stakeholders, application owners, incumbent teams and receiving support teams, the Project Manager will translate onboarding requirements into executable plans, drive dependency resolution and maintain clear application-level visibility of progress, risks, decisions and readiness. This is a hands-on delivery role requiring active ownership of transition outcomes, not only coordination and status reporting.

Key Responsibilities

1. Onboarding and Transition Delivery

• Own integrated onboarding plans covering scope, deliverables, milestones, resources, dependencies, acceptance criteria and stakeholder responsibilities.

• Manage concurrent application intakes and transition waves, aligning sequencing with business priorities, application complexity, readiness and delivery capacity.

• Coordinate intake validation and application assessments covering service catalogue alignment, supportability, criticality, operational workload and transition prerequisites.

• Establish realistic delivery baselines and manage changes to scope, effort, timelines and resource requirements through agreed change control.

• Apply Agile, Kanban or hybrid delivery practices to progress parallel workstreams while retaining formal readiness gates and approval requirements.

2. Application-Level Tracking and Backlog Management

• Maintain a single, traceable onboarding register linking each intake to its applications, workstreams, wave assignments, milestones and readiness evidence.

• Capture application-specific complexities, scope exclusions, partial onboarding, blockers, deferred activities and outstanding decisions without losing visibility in consolidated reporting.

• Convert assessment gaps and failed readiness checks into prioritized remediation items with accountable owners, target dates, dependencies and closure criteria.

• Track applications placed on hold, moved to later waves or approved with conditions, documenting the rationale, impact, approval and requirements for reassessment or re-entry.

• Keep application-level and portfolio-level views reconciled, distinguishing completed activities from accepted deliverables and approved readiness.

3. Knowledge Transfer and Operational Readiness

• Plan and drive knowledge transfer, knowledge playback, shadowing and reverse shadowing with defined coverage, deliverables and acceptance criteria.

• Coordinate validation of standard operating procedures, runbooks, knowledge articles, escalation paths and support boundaries with application owners and receiving operations teams.

• Track readiness across access provisioning and testing, ITSM workflows, assignment groups, service-level agreements, configuration records, monitoring, alert routing and reporting.

• Partner with operations leads to validate staffing, training, support coverage, workload assumptions and the effort associated with recurring non-ticketed activities.

• Coordinate security, compliance and business continuity/disaster recovery readiness reviews with the relevant control owners.

• Confirm that readiness is supported by accepted evidence and demonstrated support capability, rather than session attendance or task completion alone.

4. Governance, Risk and Stakeholder Management

• Establish a practical governance cadence covering delivery reviews, blocker resolution, readiness checkpoints and leadership escalations.

• Maintain risk, assumption, issue and dependency (RAID) logs, action trackers, decision records and auditable approval evidence.

• Drive timely resolution across client, incumbent, vendor and internal teams while retaining clear ownership of each dependency and deliverable.

• Facilitate scope clarification where support responsibilities, environment coverage, tooling dependencies or commercial implications are unresolved.

• Publish concise, evidence-based reporting on application and wave status, milestone confidence, readiness gaps, backlog aging and decisions required.

• Prepare go/no-go recommendations and escalate exceptions or residual risks to designated approvers; retain formal risk acceptance and go-live authority with the accountable governance owners.

5. Go-Live, Stabilization and Continuous Improvement

• Coordinate support cutover plans, communications, contingency arrangements and formal transfer of operational ownership.

• Manage hypercare reviews, transition-related issues and remediation through agreed stabilization and exit criteria.

• Complete steady-state handover with accepted documentation, named owners for residual actions and formal closure sign-off.

• Capture lessons learned and improve reusable onboarding templates, assessment approaches, governance controls and reporting.

• Identify recurring onboarding bottlenecks and opportunities for automation, knowledge improvement and reduced transition effort.

Required Experience and Skills

• Demonstrated experience managing end-to-end IT service transitions, application support onboarding or managed services transitions from assessment through stabilization.

• Experience delivering multiple concurrent application transitions with phased onboarding, readiness dependencies and cross-functional teams.

• Strong project management capability across planning, scheduling, resource coordination, scope control, risk management and delivery governance.

• Practical understanding of application production support and IT service management, including incident, request, change, problem, knowledge and service-level management.

• Proven experience managing knowledge transfer, SOP/runbook readiness, shadowing, reverse shadowing and evidence-based operational acceptance.

• Ability to identify support-scope ambiguity, challenge unsupported readiness claims and translate complex dependencies into clear actions and decisions.

• Working knowledge of tools such as ServiceNow, Microsoft Project, Jira, Azure DevOps, Planner, Excel and SharePoint, with proficiency in relevant planning, tracking and reporting tools.

• Strong client-facing communication, facilitation, negotiation and stakeholder management skills, including the ability to influence without direct authority.

• Ability to interpret application inventories, ticket volumes, monitoring frequency and workload data to support transition planning and capacity discussions.

Preferred Qualifications

• Bachelor s degree in information technology, computer science, business management or a related discipline, or equivalent practical experience.

• PMP, PRINCE2 or equivalent project management certification; ITIL certification and Agile/Scrum training are advantageous.

• Experience in large enterprise, regulated or multi-vendor service environments.

• Exposure to monitoring and observability, batch operations, identity and access management, CMDB and business continuity/disaster recovery practices.

• Experience building onboarding dashboards and standardized delivery frameworks that scale across application portfolios.

Success Measures

• Achievement of agreed onboarding milestones, with transparent attribution of delays and approved changes.

• Completeness and accuracy of application-level status, wave assignments, decisions and readiness evidence.

• Timely resolution or escalation of blockers, overdue actions and readiness gaps.

• Acceptance of knowledge transfer and operational readiness deliverables at the relevant gates.

• Stable support handover, measured through transition-related incidents, routing defects and agreed hypercare exit outcomes.

• Improved onboarding predictability and reduced recurring rework through lessons learned and process improvement.