> Markdown version of [/jobs/ext/2677131-senior-technical-program-manager](https://www.wearedevelopers.com/jobs/ext/2677131-senior-technical-program-manager). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Technical Program Manager - **Company:** Idc Inc - **Location:** Boston, MA, United States (Remote available) - **Experience:** Expert - **Salary:** $187,200.0 - $249,600.0 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, JIRA, Information Engineering, Data Infrastructure, Cisco Nexus Switches, Scrum Methodology, Smartsheet, Snowflake, Coda - **Published:** September 2, 2026 - **Apply:** https://www.jofdav.com/jobs/59505435-senior-technical-program-manager ## About the Role * 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 workstreams 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 decision log practice, with evidence of keeping logs decision-ready rather than decorative. * Executive-grade written communication: short, direct, accurate, and traceable to source. * Comfort operating with incomplete information in a program where the operating model is still being defined., * Experience in research, publishing, editorial, or content production operations. * Experience delivering AI enablement, automation, or workflow modernization programs in a professional services or knowledge business. * Hands-on use of workflow and program management platforms such as Coda, Smartsheet, Jira, or equivalent. * Experience coordinating distributed and offshore delivery teams across multiple time zones. * Familiarity with data platform concepts sufficient to coordinate data provisioning dependencies (for example, Snowflake-based sources). ## Description 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. What You'll Do Integrated program plan * Own and maintain the integrated NEXUS plan across all workstreams * 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. Execution and cadence * 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, escalate slippage, and keep build sequencing aligned to the plan. * Coordinate handoffs between teams so no deliverable stalls waiting for an unassigned next step. Risk, issue, and decision management * 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. Reporting and stakeholder communication * 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. ## Related Videos - [Improving quality with Agentic AI with Rovo Dev and Xray](https://www.wearedevelopers.com/videos/2005-improving-quality-with-agentic-ai-with-rovo-dev-and-xray) - [Beyond the 9–5: Designing Work Around Humans](https://www.wearedevelopers.com/videos/1321-beyond-the-9-5-designing-work-around-humans) - [How Cisco embraced a DevOps culture within its network engineering team](https://www.wearedevelopers.com/videos/99-how-cisco-embraced-a-devops-culture-within-its-network-engineering-team) - [The Software Engineer 2030: From Coder To AI Orchestrator? - Patrick Schnell](https://www.wearedevelopers.com/videos/1825-the-software-engineer-2030-from-coder-to-ai-orchestrator-patrick-schnell) - [Collaboration Quantified: Lessons from Open Source Developer Networks](https://www.wearedevelopers.com/videos/1422-collaboration-quantified-lessons-from-open-source-developer-networks) - [Grappling With Clunky Old Software? Start by Understanding What’s Inside!](https://www.wearedevelopers.com/videos/1189-grappling-with-clunky-old-software-start-by-understanding-what-s-inside) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Should Tech Managers Be Developers First? Pros and Cons](https://www.wearedevelopers.com/magazine/327-should-tech-managers-be-developers-first-pros-and-cons) - [From developer to manager – what does it take to become an engineering manager?](https://www.wearedevelopers.com/magazine/42-from-developer-to-manager-what-does-it-take-to-become-an-engineering-manager) - [Best US AI Conferences for CTOs in 2026: Build vs. Buy, Vendor Evaluation, and Peer Intelligence](https://www.wearedevelopers.com/magazine/736-best-us-ai-conferences-for-ctos-in-2026-build-vs-buy-vendor-evaluation-and-peer-intelligence) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [What is Agentic Programming and Why Should Developers Care?](https://www.wearedevelopers.com/magazine/625-what-is-agentic-programming-and-why-should-developers-care)