Your question is Multi-tenant CRM Backend. 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).
Design a multi-tenant CRM backend for HighLevel — where tenants are agencies and sub-tenants are their client accounts. Core entities: contacts, pipelines, automation triggers.
Asked in the System design round stage. Discussion covered tenant isolation, noisy tenants, Kafka-based automation triggers, and Redis caching. Reported follow-ups: How do you handle webhook delivery with retries? What if a contact's pipeline stage changes twice within 1 second, does both changes fire triggers?
Address the data model, tenant isolation, APIs, event flow, caching, trigger execution, webhook delivery, ordering, retries, observability, and failure recovery. Explain where deterministic rules are preferable to ML and how optional anomaly detection could protect the shared platform.