Technical Program Manager

Xebia is a global AI-first, digital transformation, and engineering partner. With over 25 years of experience and a team of 5,000 professionals across 16 countries, we help organizations design and build scalable products, platforms, and data-driven solutions.

We specialize in Artificial Intelligence, Data and Cloud, Intelligent Automation, and Digital Products, combining deep technical expertise with a strong focus on engineering excellence and a people-first culture.

In the CEE region, we’re a team of nearly 1,000 experts delivering modern applications, data platforms, and AI solutions for clients such as McLaren, Aviva, Deloitte, Spotify, Disney, ING, UPS, Tesco, Truecaller, All Saints, Volotea, Schmitz Cargobull, Allegro, InPost, and many, many more. We work with leading technologies including AWS, Azure, GCP, Databricks, and Snowflake, and combine strong engineering culture with a consulting mindset and a continuous focus on growth and knowledge sharing.

We are looking for a Senior Technical Project Manager to lead two connected migration work streams within a complex enterprise technology program. This is not a generic coordination role. You will provide hands‑on delivery leadership across technically complex, security‑sensitive migrations, creating clarity from partially defined requirements and driving the program through planning, dependency management, operational readiness, execution, and closure.

The role requires close coordination between business, engineering, security, identity, infrastructure, and enabling platform teams. You will be expected to challenge weak plans, surface risks early, drive decisions, and keep senior stakeholders aligned around facts, trade‑offs, and clear next actions.

The two work streams focus on reducing technology risk and modernizing access and identity capabilities. One involves migrating external users from unmanaged BYOD access toward managed devices or VDI‑based access through AWS. The second involves migrating legacy identity configurations onto a standardized Entra  within existing Active Directory environments.

• translate the migration objectives into an executable program structure with clear work streams, milestones, owners, assumptions, and success criteria,
• define clear scope and accountability across engineering, security, identity, infrastructure, O365 administration, and business stakeholders,
• create and maintain an integrated roadmap, identify the critical path, and highlight areas requiring additional staffing, technical decisions, or leadership support,
• own the integrated delivery plan from current‑state analysis through migration design, execution readiness, rollout, and closure,
• coordinate participating teams and external contributors to ensure work streams remain aligned and dependencies are actively managed,
• ensure migrations include business readiness, stakeholder communications, cutover planning, fallback considerations, and post‑migration validation,
• maintain a transparent view of risks, actions, issues, dependencies, and decisions across the migration work streams,
• identify and elevate delivery blockers early, particularly around device strategy, regional rollout constraints, identity dependencies, tenant configuration, and capacity,
• escalate issues with clear recommendations and drive them through to resolution,
• establish lightweight but rigorous governance appropriate for a security‑sensitive migration program,
• maintain the integrated plan, RAID log, dependency map, decision log, stakeholder map, and executive status reporting,
• establish migration‑readiness checkpoints and ensure teams are prepared for controlled execution,
• challenge technical plans and migration sequencing where hidden dependencies or delivery risks exist,
• facilitate productive discussions between identity, endpoint, infrastructure, security, and engineering specialists,
• translate technical constraints and dependencies into clear business and program implications,
• provide concise, fact‑based reporting to senior stakeholders, clearly distinguishing progress, risks, blockers, and required decisions,
• ensure program governance remains focused on…