Don’t Walk Into a JavaScript Interview Without Knowing This: Analytics Manager — Part 1

Theory, intuition, design trade-offs, and the mental models you should know before coding.

Summary

Variations of this problem have been publicly reported in frontend interviews at Uber, Flipkart, Swiggy, and other product companies.

The exact wording changes:

• one version asks you to batch data using a size threshold and a timeout,
• another asks you to build an Analytics SDK,
• another asks you to queue events, send them sequentially, and retry failures.

The surface problem is analytics.

The real problem is much broader.

It tests whether you understand:

• queues,
• async/await,
• Promises,
• timers,
• retries,
• exponential backoff,
• batching,
• concurrency,
• failure semantics,
• browser lifecycle,
• persistence,
• and the trade-off between throughput and latency.

If you understand the intuition behind these ideas, you do not need to memorize one company-specific solution.