Functional Requirements (what the system must do)

Track ad clicks in real time — when a user on a website clicks an ad, record the event with ad_id, user_id (cookie), timestamp, and click metadata (IP, browser, referrer).
Aggregate clicks by time window — produce click counts per ad over windows like minute/hour/day. This powers the dashboards advertisers see.
Support demographic & contextual breakdowns — slice the data by age, gender, geo location, and the website where the ad appeared, so advertisers can see who clicked and where.

Non-Functional Requirements (how it behaves)

Real-time / low latency — advertisers make live budget decisions, so click counts must update in seconds, not hours.
Scalability — handle millions of clicks per day (or hour) across many ad placements — needs horizontal scaling.
Eventual consistency is acceptable — losing a click or showing a slightly stale count for a few seconds is fine; ACID transactions aren't needed. Availability matters more than strict consistency.

A good framing for the interview: high write throughput + near-real-time reads + a handful of aggregation dimensions is what drives most of your later design decisions.

Want to paste that into the Requirements panel and I'll review it, or would you like to go deeper on one of these (e.g., why eventual consistency is the right call here)?

Submissions

Displaying Solutions with Scores Ranging from 1 to 10

Submissions

Displaying Solutions with Scores Ranging from 1 to 10