Saving a Multi-Team Program at Risk
You are a newly hired Senior Program Manager at a mid-size travel technology company. The company was formed through the merger of three legacy travel brands, each with its own booking engine, partner integration layer, and data model.…
Create a free account to upload your work. Your progress saves as a draft until you submit.
What You'll Be Doing
You are a newly hired Senior Program Manager at a mid-size travel technology company. The company was formed through the merger of three legacy travel brands, each with its own booking engine, partner integration layer, and data model.
Leadership has approved a six-month initiative to consolidate all three platforms onto a single unified partner API. The program spans four engineering teams (Platform, Integrations, Data, QA/Release), two product teams, and three external vendor partners.
There is no formal program management practice today — no cross-team dependency tracking, no stage-gate reviews, no unified reporting to leadership. Engineering teams run two-week sprints with scrum masters, but nobody owns the orchestration layer. You’re building this from scratch.
The Complicating Factors
- Two engineering teams are in different time zones (US West Coast and South America) with only a 3-hour overlapping work window.
- The Data team has a hard dependency: Platform cannot build unified API endpoints until schema mapping is done. But Data is also split across a separate regulatory compliance initiative.
- One external vendor partner may sunset their current API in 4 months — faster than your phased rollout plan.
- The QA/Release team has never tested a multi-platform migration at this scale.
YOUR TASK
Produce a Governance One-Pager, Video Walk Through, and AI Usage Log that demonstrates how you would structure this program. This is intentionally open-ended — we want to see how you think, not how thoroughly you can fill a template. See below questions that should be answered in the one-pager, video and AI Usage Log.
CONSTRAINTS
- No greenfield. The three legacy platforms are running live production traffic 24/7. Partner SLAs guarantee booking availability. Your approach must account for zero-downtime migration.
- Time zone reality. A daily standup at 9 AM Pacific does not work for a team in South America with a 3-hour overlap window. Account for asynchronous collaboration.
- Competing priorities are real. The Data team is split. Do not assume they’re fully dedicated to your program.
- Budget for your time, not a textbook. This is a 30-minute exercise. Judgment and structure over exhaustive detail. A focused one-pager with clear thinking is more valuable than a 10-page template.
AI USAGE GUIDANCE
We expect you to use AI tools. We evaluate how you use them — not whether you use them. Evidence of iteration, redirection, and critical evaluation scores higher than a polished output with no process documentation.
The single highest-signal indicator: your video answer to the mandatory AI question. If you cannot name a specific moment where you redirected AI output, evaluators will assume you did not.
How Your Work Will Be Scored
What to Submit
Governance One-Pager
Format: .pdf, .doc, .docx, .rtf, .txt, .md
Produce a Governance One-Pager that demonstrates how you would structure this program. This is intentionally open-ended — we want to see how you think, not how thoroughly you can fill a template.
Your one-pager should address the questions that matter most to you as the program manager stepping into this role. Consider things like:
• How would you govern this program? Who decides what, at what level?
• What are the critical dependencies between these teams, and which ones keep you up at night?
• How would you handle the vendor API sunset timeline conflict?
• How would you communicate program health to the EVP of Engineering?
You do not need to answer all of these — and you may address things we haven’t listed. Prioritize based on what you think matters most for this program’s success.
Sign in to upload files
Video Walkthrough
Format: .mp4, .mov, .webm
Record a video walking through your thinking. This is the most important part of the submission. Address:
- Walk through your governance approach — why did you structure it this way?
- Which dependency or risk worries you most, and how would you manage it?
- How would you handle the vendor API sunset conflict in real life — what conversations would you have and with whom?
- What would you do in week one to establish yourself as the program lead?
Mandatory question:
Walk me through one moment where you disagreed with, pushed back on, or redirected what the AI gave you — and what you did instead.
Sign in to upload files
AI Usage and Learnings
Format: .pdf, .doc, .docx, .rtf, .txt, .md
In a short section (can be at the bottom of your one-pager or a separate document), briefly note how you used AI:
- What you asked the AI to help with
- What it gave you
- What you kept, changed, or rejected — and why
Three interactions documented is sufficient. The log does not need to be exhaustive.
Sign in to upload files
Create a free account to upload your work. Your progress saves as a draft until you submit.
On this page