Technical Program Manager - Enterprise Engineering

Step into a pivotal role at the heart of Enterprise Engineering, where strategy meets execution across a fast-scaling, product-led organisation. As a Technical Program Manager in Super, you’ll operate at the center of multiple high-impact initiatives—connecting four engineering tribes and cross-functional guilds to ensure seamless delivery in a year defined by transformation. Working closely with senior leadership and reporting into the CIO’s office, you will drive the day-to-day orchestration of complex programmes, turning ambitious plans into coordinated action. This is an opportunity to shape how a modern, automation-first platform enables growth, innovation, and operational excellence across an entire enterprise.

• Programme delivery for 2–4 cross-tribe initiatives at any given time. Today that means a subset of: super.xyz migration phases, Okta IDP, Workday Phase 1, Google Workspace Complex Cohorts, Identity & Zero Trust progression, the EE career architecture / Success Factors rollout, and the AI Adoption programme.
• Maintain a single source of truth for what each tribe needs from the others, when, and why.
• Surface conflicts early; drive resolution through the PMT/EM pairs and Peter Strazovec when needed.
• Cadences that produce decisions, not status. Run weekly programme syncs, biweekly steerings, and monthly leadership reviews.
• Frame trade-offs sharply, document decisions, follow up to closure.
• Risk and change management. Own change-freeze windows (e.g. World Cup blackout May–June), incident sequencing, and cross-tribe rollback plans for the protected programmes ( super.xyz , Okta, EE transformation).
• Stakeholder communication across P&T. Keep adjacent areas (Sports, Gaming, Product, Comms, Legal, Finance, HR) informed of EE's roadmap, dependencies, and disruption windows.
• Translate engineering reality into business language, and back.
• Tooling discipline. Drive Jira, Notion, and OKR hygiene across tribes. The EE bet is that internal tools are products; we hold ourselves to that standard.
• The handback discipline. Where EE has temporarily caught a ball that belongs to a functional team, you help define the path back to the right long-term owner.

• 3–5 years in technical programme management, delivery management, or a closely adjacent role (engineering programme lead, technical project manager, scrum-of-scrums lead) inside a product or engineering organisation.
• Demonstrable track record of driving at least one programme involving 3+ engineering teams to a hard deadline.
• Comfortable in the dependencies-and-sequencing layer: critical path thinking, RAID logs, change windows, blackout planning. You can build a dependency map in a day and keep it alive for a quarter.
• Strong written communication. You can produce a programme update that a CIO will read and a steering committee will act on.
• Working fluency with Jira and Notion (or equivalents).
• Comfortable in an AI-native toolchain — Claude, Cursor, scripting your own reports — or eager to get there fast.
• English, professional working proficiency.
• Base in Žilina, Zagreb, Bucharest or Warsaw