Apple·Software Engineer·Onsite - System Design / Architecture
- Design an ads-click aggregation system that handles click events from web browsers, mobile apps, and smart TV SDKs, where each source has different delivery guarantees and failure modes.
- How would you guarantee exactly-once click counting for billing purposes, even when clients retry or clocks are skewed across devices?
- How do you handle late-arriving events in a streaming pipeline, and how do you set watermarks appropriately?
- Popular ads and publishers create hot keys in your Kafka partitions. How do you deal with the resulting skew?
- How would you structure storage to serve both real-time dashboards and billing-grade batch reconciliation from the same pipeline?
- What signals would you use to detect fraudulent clicks, like bot traffic or click-spam from the same device?
- How would you approach cross-region availability and data residency requirements for a global ads system?
“I started with the event schema and worked outward, which felt right, but I underestimated how much time we'd spend on the multi-source ingestion piece.”