Confluent Interview Questions — Page 3

Confluent·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at Confluent for a software engineer role. The whole thing was basically one giant question about building a disposable email service from scratch, and they wanted you to go pretty deep on almost every layer of the stack.

Design a disposable email service that issues auto-expiring addresses (like 10-minute inboxes) and can receive real messages. Walk through requirements, APIs, address generation with TTL semantics, SMTP ingress, spam controls, storage, retrieval, rate limiting, privacy, compliance, cleanup, observability, and capacity planning.
How would you design the storage schema for this service, including per-message TTL, indexing strategy, and how you'd handle cleanup of expired data at scale?
What consistency and availability tradeoffs would you make for this system, and how would you scale it to handle millions of inboxes per day while keeping costs under control?

“This was basically the entire interview compressed into one prompt.”

View Post

Confluent·Software Engineer·Onsite - System Design / Architecture

May 2026

System design round at Confluent for a software engineer role. The whole thing was essentially one big RSS feed design question with a lot of follow-ups baked in. Heavy emphasis on schema design and API shape, which I wasn't fully expecting.

Design an RSS news feed service that lets users subscribe to sources, ingests articles on a schedule, and serves each user a personalized feed.
Walk through your database schema: what tables do you need, what are the primary keys, and what indexes make the hot queries fast?
How do you handle deduplication during ingestion, especially when the same article reappears across re-fetches or gets syndicated by multiple sources?
Should you generate a user's feed at read time or write time? What are the trade-offs and which would you default to?
How would you implement cursor-based pagination on the feed endpoint, and why not just use OFFSET?
A source suddenly gets millions of new subscribers and publishes a burst of articles. How does your fanout-on-write path handle that without falling over?
If a user unsubscribes from a source after their feed was already materialized under fanout-on-write, how do you clean up without a slow synchronous delete?
Two different RSS sources syndicate the exact same article. How do you detect that at ingestion and decide which copy to show the user?
How would you add full-text search over article titles and summaries, and where does that index live?

“The scope here is wide.”

View Post

Confluent·Software Engineer·Technical Phone Screen

May 2026

Interviewed for a software engineering role at Confluent and got a question about variadic functions. Pretty short and focused, nothing too wild.

What is a variadic function and how does it work?

“Knew what it was but fumbled explaining it clearly under pressure.”

View Post

Confluent·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Confluent for a software engineer role. The whole thing was focused on designing a disposable email service from scratch, which sounds straightforward until you start pulling on the threads around SMTP ingestion and real-time delivery.

Design a temporary/disposable email service similar to TempMail or 10MinuteMail, covering address generation, mail ingestion, storage, TTL expiry, and real-time UI delivery.

“I went straight to address generation and talked about random vs pooled addresses, which felt safe.”

View Post

Confluent·Software Engineer·Technical Phone Screen

Jun 2026

Confluent SWE interview with a streaming data angle. The coding problem was more interesting than your typical LeetCode grind, which I appreciated, but it also meant I had to think more carefully about state and time.

You have a key-value store that continuously receives new entries. Implement a function that returns a windowed average for a given key over a sliding time window.

“The setup sounds like a basic data structure problem until you start thinking about what 'windowed' actually means in a streaming context.”

View Post

Confluent·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Confluent with two back-to-back problems. Both had real depth to them and the second one in particular went in a direction I wasn't expecting at all.

Design an aggregated news feed service that ingests articles from many publishers, deduplicates and ranks them, and serves different client types including mobile. Cover API design, REST vs RPC tradeoffs, pagination, caching, and how the API surface should adapt to different client capabilities.
Design a disposable email service where inboxes are created on demand and users can receive and read mail at generated addresses. Two hard constraints: generated usernames must look human enough to not get flagged by external sites, and usernames must never be reused even at very high daily generation volume. How do you generate human-looking addresses at scale, verify uniqueness efficiently, and what are the tradeoffs if you use a probabilistic structure like a Bloom filter?

“I spent too long on the ingestion pipeline and didn't get to the mobile-specific API stuff until they nudged me.”

View Post

Confluent·Software Engineer·Technical Phone Screen

Jun 2026

Coding round at Confluent for a software engineer role. The question was a classic tail -n implementation, but the setup requirement ate up most of the time and I never got to the follow-up.

Implement a version of the Unix `tail -n` command that reads the last N lines from a file.

“The part that killed me wasn't the algorithm, it was that the interviewer wanted me to write a txt file first and read from it as test input.”

View Post

Confluent·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026

Went through a behavioral round at Confluent for a software engineer role, all five questions were Amazon-style leadership prompts. Nothing too surprising but a couple of them pushed harder than I expected.

Tell me about a time you took on responsibilities that were clearly outside your defined role.
Describe a situation where you disagreed with a decision that was made. What did you do about it?
Walk me through a time you failed at something. What changed afterward?
Tell me about a time you had to ship something under a very tight deadline.
Describe a time you had to make an important judgment call without having all the information you needed.

“Had a decent story ready for this but I rambled into too much backstory.”

View Post

Confluent·Software Engineer·Technical Phone Screen

Jun 2026

Confluent software engineer interview with a pretty meaty algorithmic problem around phrase search in documents. The core challenge was non-trivial once you get into the ordering constraint, and the discussion kept pushing toward indexing design and complexity analysis.

Given a document (or list of sentences) and a multi-phrase query, find all occurrences where every phrase appears and their relative order matches the query order. Describe your indexing strategy, how you enforce the ordering constraint efficiently, and what the complexity looks like.

“My first instinct was a naive scan and I said it out loud before catching myself.”

View Post

Confluent·Software Engineer·Onsite - System Design / Architecture

Jun 2026

System design round at Confluent for a software engineer role. Just the one question, no whiteboard or diagram required, but they wanted real specifics on the data model and API layer.

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

“No diagram needed, which I thought would make it easier.”

View Post