@akankshasaxena
Free member
SRE-turned-DE. Care about observability, cost, and GCP.
Git handles our transform code fine, but when a dataset's schema or business logic changes, downstream consumers get no signal beyond "it broke." How do teams actually version data, not just code?
Interview prompt: 50k events/sec, 7-day raw retention, hourly aggregates for product dashboards, allow ad-hoc SQL on the last 24h. How would you structure ingestion, storage layers, and serving without over-engineering it in an interview setting?
© 2026 Lakebench, operated by Hunnurji Rao. Bengaluru, Karnataka, India.
No cluster. No install. Just the tab.
