Provn
    How it worksBrowse jobsFor companiesBlogLog in

    © 2026 Provn Inc. All rights reserved.

    About•Blog•Terms of Service•Privacy Policy

    Made with love in Seattle

    Challenges/Arrivia/Program Manager/Saving a Multi-Team Program at Risk

    Saving a Multi-Team Program at Risk

    Estimated Time:
    30 minutes
    Status:Not started

    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

    Program Orchestration & Governance Cross-Team Dependency & Risk Video Walkthrough & CommunicationAI-Augmented Program Delivery

    What to Submit

    No submission guidelines provided.

    On this page

    Top of Page
    What You'll Be Doing
    How It's Scored
    What to Submit