← Confluent Interview Insights

Confluent·Software Engineer·Onsite - System Design / Architecture·Senior

Senior
Jun 2026

Summary

Third round at Confluent for a software engineer role, this one was a system design interview focused on an RSS news feed. No whiteboard or diagram required, but the interviewer wanted a pretty thorough verbal walkthrough of the database schema and API layer.

Questions Asked (1)

Q1

Design an RSS news feed system. Walk through your database table design and API design in detail.

System DesignData ModelingAPI & Integrations
Author's notes

No diagram needed, which honestly threw me off a bit because I kept wanting to draw something to anchor my thoughts.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements: scale, read/write ratio, latency, and features like feed aggregation, search, and personalization. Then design a normalized schema for feeds, items, and subscriptions, and define RESTful APIs for CRUD operations and feed retrieval. Finally, discuss scaling strategies such as caching, sharding, and using a message queue for ingestion.

Pro tip: At Confluent, emphasize how you would leverage Kafka for ingesting and processing feed updates, and discuss the trade-offs between push vs. pull models for feed delivery.

1. Clarify Requirements

Ask about scale (users, feeds, items), read/write patterns, latency requirements, and desired features (e.g., search, personalization, real-time updates).

2. Design Database Schema

Propose tables for users, feeds, feed_items, subscriptions, and items. Discuss indexing, partitioning, and denormalization for read performance.

3. Design API Endpoints

Define RESTful endpoints for creating/updating feeds, subscribing, and fetching feed items. Include pagination, filtering, and authentication.

4. Discuss Scaling and Trade-offs

Explain how to handle high read throughput with caching (e.g., Redis), sharding, and asynchronous processing with Kafka. Compare push vs. pull models.

5. Address Reliability and Monitoring

Mention error handling, idempotency, rate limiting, and monitoring (e.g., metrics, logging) to ensure system robustness.

Key Points to Mention

  • Database schema: users, feeds, feed_items, subscriptions, items with appropriate indexes and foreign keys.
  • API design: RESTful endpoints with pagination (e.g., GET /feeds/{id}/items?page=1&limit=20), and proper HTTP methods.
  • Caching strategy: use Redis or Memcached to cache frequently accessed feeds and reduce database load.
  • Sharding and partitioning: shard by user_id or feed_id to distribute load, and partition feed_items by time for efficient retrieval.
  • Message queue: use Kafka for ingesting new items and fan-out to subscribers, ensuring scalability and decoupling.
  • Trade-offs: push vs. pull for feed delivery, consistency vs. availability, and denormalization vs. normalization.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.