The "Design Netflix Billing System" question appears to be a variation of Netflix's real interview problem focused on a payment pipeline integrating rights management, financial accounting, and payments, rather than consumer billing. It tests distributed systems, payments consistency, and backend scalability.[10][13]
Problem Statement
Design system B (financial accounting) in a chain where:
System A (rights system) provides data on streaming rights (e.g., movies streamable by country and period).
System B processes this with user inputs like total contract amount (e.g., $1M for title A over 1 year), payment frequency, and usage/streaming data to compute owed amounts.
System B outputs accurate entries to system C (payment system) for settlements.
Key challenges include data reconciliation across services, handling failures, consistency in financial contexts, and scalability for Netflix's global volume.[12][13][10]
Functional Requirements
Fetch rights/usage data from A (e.g., title-country streaming windows).