Architect dynamic region-specific pricing for a global SaaS product

WHAT THIS TESTS: This question tests whether you can separate product identity from commercial terms. A senior engineer should show they understand catalog abstraction, immutable pricing snapshots at checkout, tax jurisdiction logic, and subscription state machines across legal entities. The interviewer wants to see systems thinking that prevents SKU sprawl while supporting finance and compliance requirements.

A GOOD ANSWER COVERS: First, a single global product catalog where one SKU maps to many rate plan charges, each with an explicit market-based list price in a specific currency rather than a dynamically converted FX rate. Second, a jurisdiction-aware tax engine that computes VAT or sales tax based on the customer billing address and stores the tax amount immutably on the subscription or invoice line item so audits are deterministic. Third, checkout logic that resolves the correct currency and price using the user region, then locks that price into a subscription snapshot to prevent catalog changes from altering already-committed terms. Fourth, a migration strategy for permanent moves that uses subscription amendments to either grandfather the old pricing in the new currency or terminate and recreate the subscription under the new local legal entity, depending on tax residency rules.

COMMON WRONG ANSWERS: Cloning the catalog so you have Pro Plan USD, Pro Plan EUR, and Pro Plan JPY as separate products. This breaks global revenue analytics and forces product managers to update features across dozens of SKUs. Auto-converting prices using daily exchange rates, which creates volatile customer-facing prices and reconciliation nightmares for finance. Storing tax as a computed field without an immutable snapshot, which makes historical invoices non-deterministic if tax rules change retroactively. Ignoring legal entity boundaries, which violates data segregation requirements for tax and compliance in multi-subsidiary setups.

LIKELY FOLLOW-UPS: How would you handle a customer who disputes a tax calculation after a regulatory rate change? What happens if a user uses a VPN to purchase from a cheaper region? How do you support purchasing power parity without leaking price differences that encourage arbitrage? Describe how your design changes if the company acquires a subsidiary that already has its own product catalog.

ONE CONCRETE EXAMPLE: Imagine a Pro Platform License with Global ID 1001. The rate plan charge has USD 100, GBP 90, and JPY 12000 as explicit list prices. A customer in London sees GBP 90 at checkout. The tax engine adds 20 percent VAT based on the UK billing address and stores the total as an immutable invoice line. Six months later the customer moves to Japan. The system triggers a subscription amendment: because the move is permanent, the old subscription is cancelled and a new one is created under the Japan entity using JPY 12000, preserving revenue recognition per local tax rules.

Source: zuora.com