Overview
What this challenge is about.
Audit the current state via 8 interviews (4 in SF, 2 in Warsaw, 2 in Bangalore). Design 4-5 squads each owning a domain end-to-end (not split across timezones for handoff). Build a communication playbook: which decisions sync (calls), which async (Notion + Linear), expected response time per tier, and a 'no-meetings' overlap window. Design an on-call rotation that respects timezones (no 3am calls). Build a decision-making RACI for cross-squad architecture decisions. Author a 30-day onboarding plan for the 2 new hubs covering tooling, codebase tours, and culture. Deliver org design, comms playbook, on-call plan, RACI, and onboarding plan.
The Brief
What you'll do, and what you'll demonstrate.
Design org structure, communication cadence, on-call, and decision-making for a 43-person distributed engineering org across 4 timezones.
Earning criteria — what you'll demonstrate
- Design squad ownership that avoids cross-timezone handoffs
- Build a communication playbook that scales beyond founders
- Design an on-call rotation that respects timezone humanity
- Build a decision-making RACI for distributed architecture decisions
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Product Manager
Product managers fluent in async + sync decision tiers ship roadmaps that survive distributed-team scale.
This challenge sharpens
- decision-frameworks
- communication-design
- onboarding