Job Description

Technical Project Manager

We are seeking an experienced Technical Project Manager to lead the end-to-end delivery of enterprise Content Management System (CMS) projects. In this role, you will work onsite with the customer, acting as the primary delivery owner and trusted point of contact between client stakeholders and our offshore engineering teams — driving projects from planning through go-live, and managing a recurring rollout cadence (approximately every 2 months) across multiple interlinked workstreams.

Key Responsibilities

Client & Stakeholder Management

• Serve as the primary onsite point of contact for the customer on all delivery matters. Build trusted relationships with client stakeholders, manage expectations, and provide regular, structured project updates and reporting.

Project Planning & Execution

• Own the project plan across the full SDLC — scope definition, work breakdown, resourcing, timeline, and budget. Track progress against milestones and proactively manage deviations.

Go-Live & Rollout Planning (Lead Role)

• Own and drive the end-to-end go-live planning process for each rollout cycle, including cutover planning, readiness checklists, rollback/contingency plans, and go/no-go decision criteria.
• Build and maintain a rolling rollout calendar (~every 2 months), sequencing releases against feature readiness, testing windows, and client business events (e.g. freeze periods, peak seasons).
• Lead go-live war rooms and cutover execution — coordinating client business teams, offshore engineering, infra/ops, and support functions in real time during deployment windows.
• Drive post-go-live stabilization: hypercare planning, defect triage, and formal sign-off/closure for each rollout.
• Maintain a rollout retrospective process to capture lessons learned and continuously tighten the cadence and reduce go-live risk over time.

Cross-Project & Dependency Coordination

• Identify and actively manage dependencies with other parallel/interlinked projects (shared environments, shared teams, shared release windows, upstream/downstream integrations).
• Maintain a cross-project dependency map and raise conflicts (resourcing, environment availability, sequencing clashes) early to the relevant PMs/leads and steering committee.
• Align this project's rollout calendar with other projects' release schedules to avoid collisions and ensure coordinated, low-risk deployment windows across the wider program.

Delivery Governance

• Coordinate closely with the offshore engineering and architecture teams to ensure requirements are clearly understood, priorities are aligned, and delivery meets agreed quality standards. Facilitate technical discussions between client and offshore teams without necessarily driving the architecture itself.

Risk & Issue Management

• Identify project and rollout risks early (technical, resourcing, dependency, or client-side); drive mitigation plans and escalate issues with clear options and recommendations.

Scope & Change Control

• Manage change requests, contract/SOW alignment, and commercial implications of scope changes in coordination with account/delivery leadership.

Reporting & Governance Cadence

• Run steering committee updates, status reports, and RAID logs; ensure transparency on progress, risks, rollout status, and financials to both client and internal leadership.

Technical Qualifications

• CMS / DXP Familiarity: Working knowledge of enterprise CMS and Digital Experience Platforms (e.g., Directus, Sitecore, Sitefinity, or Adobe Experience Manager) sufficient to understand technical constraints, estimate effort, and facilitate informed conversations — deep hands-on configuration/development experience is not required.
• Modern Web & Architecture Awareness: General understanding of headless CMS concepts, decoupled front-ends, and API-first integration patterns (REST/GraphQL), enough to translate technical risk into business impact for the client.
• Cloud & Delivery Pipelines: Familiarity with cloud environments (AWS, Azure, or GCP) and CI/CD-based delivery cycles, including deployment/release mechanics relevant to planning cutover windows.
• Release Management: Prior experience running structured release/rollout cycles — release calendars, environment/change management, cutover runbooks, and hypercare processes.
• PM Tooling & Methodology: Proficiency with project management methodologies (Agile/Scrum, Waterfall, or hybrid) and tools (Jira, MS Project, Confluence, or similar).

Core Competencies

• Communication: Excellent ability to translate technical complexity and risk into clear business language for non-technical stakeholders, and to manage sensitive conversations (delays, scope changes, escalations) onsite.
• Leadership & Ownership: Demonstrated ability to take the lead role during go-live/rollout execution — directing a cross-functional group (client, offshore, infra, support) under time pressure and owning the go/no-go call.
• Organizational Rigor: Strong planning discipline to manage a recurring, high-frequency rollout cadence without dropping quality or missing dependencies across projects.
• Commercial Acumen: Understanding of engagement models (T&M, fixed price, outcome-based), budget tracking, and margin implications of delivery decisions.
• Client-Facing Presence: Comfortable representing FPT Software independently in front of senior client stakeholders on a daily basis, including during high-pressure go-live windows.