I’m not able to locate any Adobe-specific interview problem titled exactly “Ad Click Integration System” with the precise combination of tags and a fully specified competitive‑programming–style statement (formal description, explicit constraints, and I/O examples). The closest matches publicly available are more general “Ad Click Aggregator / Ad Click Event Aggregation System” system‑design problems, which are not labeled as Adobe‑proprietary questions and typically do not include full input/output samples in the way you’re asking for.[5][6][7]
What can (and cannot) be recovered
- Public resources show generic ad‑click aggregation / analytics design problems (e.g., “Design an Ad Click Aggregator”, “Ad Click Event Aggregation System”).[6][7][5]
- These sources describe the system behavior, components, and sometimes APIs, but they do not provide a canonical “problem statement + constraints + sample I/O” under the Adobe title you mentioned.[7][5]
- Anything that would look like “the” full Adobe problem statement with official examples and constraints appears to be internal / proprietary or simply not published on the open internet.
Because of that, I can’t truthfully reconstruct or claim to have the exact Adobe problem text you requested.
Closest publicly documented variant
The GitHub “Ad Click Event Aggregation System” problem is the closest complete write‑up, but again, it is not Adobe‑branded.[7]
Typical elements from that style of question include (paraphrased to avoid copying):
- You must build a system to record every ad‑click event and periodically compute aggregates (e.g., counts per ad over minute‑level windows).[5][7]
- There is usually an ingestion API that receives events like ad identifier, timestamp, and possibly user information.[5][7]
- There is an analytics or query API that returns metrics such as counts per ad over a time range, or “top‑K ads” in a time window.[7][5]
- System‑design constraints touch on throughput (e.g., 10k+ clicks/sec), low‑latency analytics queries (sub‑second), fault tolerance, and prevention of data loss or double‑counting, plus abuse prevention (e.g., repeated clicks).[5]
These problems are framed as system‑design questions, not algorithmic coding problems, so they don’t define discrete stdin/stdout formats, test cases, or numeric constraints in the competitive‑programming sense.
Why I can’t provide the exact thing you asked for
- I do not have access to Adobe’s internal interview problem bank, and there is no public posting that exactly matches “Ad Click Integration System” with all the artifacts you requested (full statement, constraints, and all I/O examples) under Adobe branding.
- Reconstructing a full question by guessing from generic problems would misrepresent unverified content as “the” Adobe interview question, which I must avoid.
How I can still help
If your goal is preparation, I can, in a follow‑up, do any of the following:
- Draft a realistic, fully specified problem statement (including explicit constraints and detailed input/output examples) for an “Ad Click Integration System” that matches the tags you listed (analytics, data engineering, backend, ML, stream processing, system design) and is consistent with known ad‑click aggregator problems.[7][5]
- Break down how to design such a system end‑to‑end (APIs, storage, streaming pipeline, ML integration for fraud detection or CTR prediction, etc.), tuned specifically for an Adobe‑style system‑design interview.[4][8]
If you tell me whether you want something closer to a coding/LC‑style problem or a system‑design prompt, I can draft a detailed, self‑contained version you can practice with.