Senior Technical Program Manager

Overview About the Role & Team

The Senior Technical Project Manager is the cross-workstream coordinator who owns the integrated NEXUS program plan at the execution layer. You hold workstream leads to their deadlines, manage dependencies across processes, architecture, development, data, change, and training, and surface risks early enough that they can still be decided rather than absorbed.

This is a delivery role, not an oversight role. You are expected to run the plan, not report on it.

NEXUS is IDC’s AI-integrated research production operating model. It modernizes how IDC research is created across roughly 44 document types, spanning production planning and capacity, content and workflow execution, and downstream consumption and distribution. Delivery runs in sprints, with parallel pods working document types simultaneously against fixed publication commitments.

The program combines internal teams (process design, business rules, change and communications, training and enablement, data engineering) with an external development partner and a distributed delivery model across US, Europe, and APAC time zones.

• Own and maintain the integrated NEXUS plan across all work streams
• Translate sprint scope into sequenced, owned, dated work with explicit entry and exit criteria.
• Maintain the dependency map between process design, workflow architecture, development, data provisioning, UI, testing, change, and training, and keep it current as scope evolves.
• Flag schedule conflicts and constraint collisions before they hit the critical path, with options and a recommendation.

• Run the operating rhythm: sprint planning, standups, working sessions, cross-pod syncs, and sprint close.
• Hold workstream leads accountable to committed dates and deliverables without relying on formal authority.
• Drive delivery through the external development partner — track commitments, elevate slippage, and keep build sequencing aligned to the plan.
• Coordinate handoffs between teams so no deliverable stalls waiting for an unassigned next step.

• Own the risk, issue, and dependency log end to end. Every open item has a named owner, a next step, and a date.
• Convert ambiguity into decision points: frame the choice, the options, the impact, and the recommended path for Program Office resolution.
• Maintain the decisions log so decisions stay made and are not relitigated.
• Escalate on evidence, early, and with a proposed resolution.

• Produce executive-grade status reporting for program sponsors.
• Give the Program Office a reliable, current picture of program health so their time goes to governance and strategy, not status assembly.
• Keep pod leads, product owners, and functional leads aligned on scope, sequence, and what is expected of them next.

• 8+ years in technical project or program management, including at least 3 years running multi-workstream software, platform, or workflow delivery programs.
• Demonstrated ownership of an integrated delivery plan across parallel work streams with hard, externally visible deadlines.
• Strong dependency and critical-path management across mixed technical and business teams.
• Experience managing external development vendors or partners against delivery commitments, including escalation when capacity or velocity falls short.
• Ability to hold senior stakeholders to commitments through influence rather than authority.
• Enough technical fluency to interrogate estimates, understand data and integration dependencies, and distinguish real blockers from convenient ones. You do not need to build it, but you need to understand what is being built.
• Disciplined risk, issue, dependency, and…