How would you run the first 90 days after taking over Creator Studio

Problem Statement Description

Product context: Meta is a social technology company; its products include Facebook, Instagram, WhatsApp, Messenger, Threads, Quest, creator tools, and ads.

You have just taken over Creator Studio at Meta, with a focus on community admins who use the product to manage publishing, audience engagement, insights, moderation, and monetization across Meta surfaces. These admins may run large Facebook communities, creator-led groups, media pages, or interest-based communities where timely content, member trust, and operational efficiency are critical.

The interview asks how you would run your first 90 days in this role. This is an execution-focused question: you are expected to define how you would quickly understand the product, users, business context, team health, and performance gaps, then translate that understanding into an operating plan with clear priorities, owners, sequencing, and decision points.

Your response should account for Meta’s scale and complexity: multiple surfaces, creator and admin workflows, ads and monetization considerations, safety and integrity requirements, internal dependencies, competitive pressure from platforms such as YouTube, TikTok, Discord, and Snap, and the need to balance short-term execution with longer-term product direction.

The experience should consider:

- How you would structure the first 30, 60, and 90 days without jumping directly to a feature roadmap.

- Which users, internal teams, and stakeholders you would meet to understand creator and community-admin workflows.

- What data, dashboards, user research, support tickets, and operational signals you would inspect first.

- How you would identify the biggest execution risks, including trust and safety, reliability, content distribution, monetization, and cross-surface dependencies.

- How you would evaluate existing goals, team ownership, decision-making processes, and delivery commitments.

- How you would define near-term priorities, go/no-go criteria, sequencing, and communication rhythms.

- How you would handle inherited roadmap items, urgent escalations, and potential misalignment across product, engineering, design, data science, policy, and operations.

- What launch, rollback, measurement, and stakeholder communication mechanisms should be in place for the team going forward.

The goal is to describe a practical operating plan for taking ownership of Creator Studio in a high-scale Meta environment. Your answer should show how you would build context, establish trust, diagnose the current state, create execution clarity, and set the team up to deliver measurable impact for community admins and the broader creator ecosystem.