How do I approach System Design interview questions?

System Design questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master system design interviews.

What difficulty level is this interview question?

This is a medium difficulty System Design question, commonly asked during Onsite rounds at Confluent.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Confluent during technical interviews.

Design a News Feed and Mail Service | Confluent Interview Question

Quick Overview

This question evaluates a candidate's proficiency in large-scale system design, including distributed ingestion and deduplication, content ranking, API design choices (REST versus RPC), pagination and caching strategies, and techniques for generating and ensuring uniqueness of human-looking disposable email addresses.

Design the following systems:

Aggregate news feed Build a service that ingests articles from many publishers, deduplicates and ranks them, and serves feeds to multiple client types, especially mobile clients. Explain API design choices, including when to use REST versus RPC, how pagination should work, how caching should be handled, and how the API surface should adapt to different client capabilities.
Temporary email service Design a disposable email platform that creates inboxes on demand, receives inbound mail, and lets users read messages for generated addresses. Two hard requirements are:
- generated usernames should look plausibly human rather than obviously random, to reduce rejection by external websites;
- usernames must never be reused, and the system generates a very large number of new addresses every day.
Discuss how to generate human-looking addresses at scale, how to check uniqueness quickly, and what tradeoffs arise if probabilistic structures such as Bloom filters are considered.

Quick Overview

Design the following systems:

Aggregate news feed Build a service that ingests articles from many publishers, deduplicates and ranks them, and serves feeds to multiple client types, especially mobile clients. Explain API design choices, including when to use REST versus RPC, how pagination should work, how caching should be handled, and how the API surface should adapt to different client capabilities.
Temporary email service Design a disposable email platform that creates inboxes on demand, receives inbound mail, and lets users read messages for generated addresses. Two hard requirements are:
- generated usernames should look plausibly human rather than obviously random, to reduce rejection by external websites;
- usernames must never be reused, and the system generates a very large number of new addresses every day.
Discuss how to generate human-looking addresses at scale, how to check uniqueness quickly, and what tradeoffs arise if probabilistic structures such as Bloom filters are considered.

Design a News Feed and Mail Service

Quick Overview

Solution

Submit Your Answer to Earn 20XP

Design a News Feed and Mail Service

Quick Overview

Solution

Submit Your Answer to Earn 20XP