Your question is Design a Microservices Migration Plan. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are the Engineering Manager for a mature product that started as a monolith and now needs to move to microservices to improve release velocity, reliability, and team autonomy. The current system supports customer-facing workflows with tight coupling across billing, identity, and notifications, and the business wants to keep shipping while the migration happens. You also need to align product, platform, and support teams on what gets split first, what stays in the monolith for now, and how to avoid a prolonged period of duplicate logic and operational instability.
How would you approach designing a microservices architecture?