RepostedConfluent logo

Confluent · OA → Phone screen → Onsite

In process

Confluent Coding and System Design Questions: 33 Questions

Software engineer · InternshipSep 2026
Shared by

Confluent interview questions from 2018 to 2026: 33 coding, concurrency and system design problems, led by a URL shortener, a news feed API and tail -n.

At a glance

Coverage: 33 distinct Confluent interview questions built from 44 firsthand reports, November 2018 to September 2026: 18 coding, 2 concurrency and low-level design, and 13 system design. Phone screens and onsites; new grad to staff, mostly full-time. Nine questions last seen before November 2023 are under History.

Interview reference image

What came up

Each entry below is one question with every report that named it. Of the 24 questions seen since November 2023, half are coding and most of the rest system design.

Topic Questions Last seen
Coding 12 of 24 Sep 2026
System design 10 of 24 Sep 2026
Concurrency or thread-safety follow-ups 4 of 24 Apr 2026
Search across documents 2 of 24 Sep 2026
Storage internals (WAL, LSM, recovery) 2 of 24 Jan 2025

Questions we found

Report counts include every dated report of the question, 2018–2026. Each question is linked to practice in its entry below.

Algorithms / Data Structures

Question Reports Last seen
Windowed key-value map 6 Nov 2024
Implement tail -n 5 May 2026
Positive subset sum 3 Nov 2024
Variadic function signature match 2 Jul 2026
Detect a silent sensor 2 Apr 2026
Get best price 2 Apr 2025
Defenders against every hostile monster 2 Nov 2024
Word search across documents 1 Sep 2026
Phrase search across documents 1 Sep 2026
Sudoku board validation 1 Sep 2026
Sudoku solver 1 Sep 2026
LFU cache with thread safety 1 Dec 2024

Low-Level Design (concurrency)

Question Reports Last seen
Thread-safe delayed task runner 9 Jan 2025
Random-access FIFO queue 3 Apr 2026

System Design

Question Reports Last seen
URL shortener with idempotent codes 23 Jan 2025
Subscription news feed API and data model 12 May 2026
Ticket booking 6 Sep 2026
Disposable email service 5 Apr 2026
Log ingestion and search 4 Aug 2026
Podcast subscription feed 4 Jul 2025
Single-node key-value store crash recovery 4 Jan 2025
CI/CD pipeline 2 Jul 2026
Leader-based distributed key-value store 1 Nov 2024
Diagnose and scale a multi-region service 1 Aug 2024

24 questions with recent reports

01: Windowed key-value map

Reports: 6 · Report dates: March 5, March 8, May 11 and November 9, 2021; August 20, 2022; November 21, 2024 · Stage: onsite · Level: mainly full-time

  1. A map over a five-minute event window with put, get, delete and a frequently called average.
  2. Follow-ups: when entries expire, keeping average faster than a full scan, overwrites, and multithreaded access.

02: Implement tail -n

Reports: 5 · Report dates: March 4, April 3, April 15, May 2 and May 4, 2026 · Stage: onsite · Level: full-time

  1. The interviewer supplies file operations: read bytes, move a pointer, get the file size. Print the last n lines to stdout.
  2. Candidates discussed buffering forward versus scanning backward from the end.

05: Positive subset sum

Reports: 3 · Report dates: May 3, November 14 and November 21, 2024 · Stage: onsite · Level: full-time

  1. Does a subset of positive integers reach the target? The follow-up returns the chosen values.

06: Defenders against every hostile monster

Reports: 2 · Report dates: September 6 and November 21, 2024 · Stage: onsite · Level: full-time

  1. Nested monsters each have a name, the descendants they can_defeat, and a hostile flag. Return every friendly monster that can defeat all hostile ones.

07: Detect a silent sensor

Reports: 2 · Report dates: June 24, 2025 and April 15, 2026 · Stage: onsite · Level: full-time

  1. Given (sensorId, timestamp) pings, decide whether a sensor has three consecutive empty time slots.
  2. The reports pointed to a hash map plus binary search. Slot length was not given.

08: Match a variadic function signature

Reports: 2 · Report dates: July 28, 2020 and July 27, 2026 · Stage: phone screen · Level: full-time

  1. Match a requested type sequence against registered function signatures. In a variadic signature, the last declared type must appear one or more times.

09: Get best price

Reports: 2 · Report dates: April 9, 2024 and April 24, 2025 · Stage: coding round, virtual onsite

  1. Pick up to three menu entries that cover a requested set of unique items at the lowest total price. The second report gave matching menu and output cases.

14: LFU cache with thread safety

Reports: 1 · Report date: December 17, 2024 · Stage: senior onsite · Level: full-time

  1. Implement an LFU-style cache; the follow-up was thread safety. The tie-break rule was not given.

15: Word search across documents

Reports: 1 · Report date: September 4, 2026 · Stage: onsite · Level: full-time

  1. Find a word across a set of documents and return the document IDs. Tokenizing, ordering and duplicates were not specified.

16: Phrase search across documents

Reports: 1 · Report date: September 4, 2026 (same report as 15) · Stage: onsite

  1. Extend 15 to an ordered phrase using positional indexes. Follow-ups mentioned deduplication and layered compression.

17: Sudoku board validation

Reports: 1 · Report date: September 4, 2026 · Stage: onsite · Level: full-time

  1. Validate a Sudoku board first, as its own API.

18: Sudoku solver

Reports: 1 · Report date: September 4, 2026 (same report as 17) · Stage: onsite

  1. Solve the board, but only by calling the validator from 17, not bypassing it.

19: Thread-safe delayed task runner

Reports: 9 · Report dates: September 16 and November 19, 2020; March 8, May 11, June 29 and July 19, 2021; June 16 and August 20, 2022; January 16, 2025 · Stage: onsite · Level: mostly full-time

  1. Run tasks at their scheduled times using a deadline-ordered priority queue, blocking without spinning.
  2. Wake waiting consumers when a new task becomes the earliest deadline, then grow from one consumer to several workers.
  3. Interviewers probed waiting, notification, interruption, shutdown and using a monotonic clock.

20: Random-access FIFO queue

Reports: 3 · Report dates: November 20, 2024; July 20, 2025; April 3, 2026 · Stage: onsite · Level: full-time and senior

  1. Support expected O(1) add, poll and uniform getRandom.
  2. Follow-ups: comparing two queues for equality, a run-length-encoded version, and thread safety.

21: URL shortener with idempotent codes

Reports: 23 · Report dates: November 20, 2018 to January 16, 2025, at least one every year (one in 2023, in October) · Stage: onsite · Level: new grad to staff

  1. Design TinyURL, with a Confluent twist: the same normalized long URL must map to the same short code under retries and concurrent requests.
  2. Reports probed ID generation, collisions, storage size, caching, sharding, regional routing, and whether a database uniqueness constraint is enough without a distributed lock.

22: Subscription news feed API and data model

Reports: 12 · Report dates: March 21, 2019; February 18, 2020; March 5 and July 19, 2021; August 20 and September 22, 2022; October 10 and November 20, 2024; April 3, April 15, May 2 and May 4, 2026 · Stage: onsite · Level: new grad to senior

  1. Design a news feed's API and database: REST methods and URIs, REST versus RPC, mobile clients, tables, foreign keys, one-to-many and many-to-many relations, and feed queries.
  2. Several reports said no architecture diagram was needed; the API and schema were the point.

23: Single-node key-value store crash recovery

Reports: 4 · Report dates: March 8 and May 11, 2021; August 20, 2022; January 16, 2025 · Stage: onsite · Level: full-time

  1. Start with a single-node store, then explain the write-ahead log, snapshots, recovery, memtables, SSTables, Bloom filters, compaction, tombstones, caching and read, write and space amplification.
  2. The January 2025 report framed it as a Kafka-related key-value component and asked about WAL and snapshot recovery.

24: Leader-based distributed key-value store

Reports: 1 · Report date: November 21, 2024 · Stage: onsite · Level: full-time

  1. Make the local store distributed: consistent hashing, strong versus eventual consistency, leader and follower setup, how many leaders, leader failure, and how clients find the right owner.

25: Disposable email service

Reports: 5 dated (six records) · Report dates: June 18, June 24 and July 20, 2025; April 3 and April 15, 2026 · Stage: onsite · Level: full-time and senior

  1. Temporary email for about 100 million active users: generate human-looking usernames, check uniqueness fast, never reuse an issued address even after it expires, and support receiving and sending mail.
  2. Candidates discussed Bloom filters, but exact uniqueness still needs durable storage.

26: Podcast subscription feed

Reports: 4 · Report dates: June 16, 2022; October 20, 2023; June 18 and July 20, 2025 · Stage: onsite · Level: full-time and senior

  1. Model podcast subscriptions, refresh, pagination, storage, and read and write fan-out, with RSS-specific behavior.

30: Diagnose and scale a multi-region service

Reports: 1 · Report date: August 14, 2024 · Level: senior and staff

  1. Start from traffic and bottleneck evidence, then evolve the topology: read and write paths, region and zone failure, replication, migration, RPO and RTO, capacity and operational signals.

31: Log ingestion and search

Reports: 4 dates (five posts) · Report dates: June 10, 2021; August 4, August 21 and August 25, 2026

  1. Candidates named a logging system without many specific requirements: ingestion, buffering, storage, indexing, search, retention and failures.

32: CI/CD pipeline

Reports: 2 · Report dates: November 19, 2020 and July 24, 2026

  1. A CI/CD design discussion, with no stable company-specific details.

33: Ticket booking

Reports: 6 · Report dates: July 30, 2024; July 15, July 27, August 9, September 6 and September 8, 2026

  1. Design ticket booking with consistent inventory worldwide: holds, expiry, payment state, idempotency and no overselling.

History (before November 2023)

H03: LRU cache with a concurrency follow-up

Reports: 4 · Report dates: November 20, 2018; March 21, 2019; February 18, 2020; June 16, 2022 · Stage: onsite · Level: new grad and full-time

  1. A standard LRU cache with put and get, using a hash map and a hand-written doubly linked list.
  2. The follow-up was locking: get changes recency, so it is not really read-only.

H04: Wildcard matching with stars

Reports: 3 · Report dates: February 18 and September 16, 2020; March 8, 2021 · Stage: phone screen · Level: new grad and full-time

  1. Match a string against a pattern with * wildcards. One report ruled out the usual DP; another went from at most one * to many.

H10: Serialize a binary search tree

Reports: 1 · Report date: March 21, 2019 · Stage: onsite · Level: full-time

  1. LeetCode 449: preorder serialization, recursive first, then an iterative version.

H11: Knight dialer

Reports: 1 · Report date: June 10, 2021 · Stage: Security team onsite · Level: full-time

  1. Knight Dialer, named without a full contract.

H12: Least-strong common defeater

Reports: 1 · Report date: October 18, 2022 · Stage: phone screen · Level: full-time

  1. In a directed acyclic "can defeat" graph, find the weakest node that defeats every target. For Snakes and Goblins the answer was Zombies, since Dragons is a stronger common defeater.

H13: Validate a nested object against a schema

Reports: 1 · Report date: October 18, 2022 · Stage: Full Stack onsite

  1. Recursively validate an object against a nested schema of string and number types. Example: name plus nested location.x and location.y.

H27: Priority-aware distributed worker platform

Reports: 1 · Report date: January 15, 2022 · Stage: onsite · Level: full-time

  1. Workers and queues with priorities, leases, retries, idempotency, backpressure and observability.

H28: Kafka on Kubernetes

Reports: 1 · Report date: May 5, 2022 · Stage: onsite · Level: full-time

  1. Broker lifecycle and control plane for Kafka on Kubernetes: partitions, durable storage, rebalancing, recovery, safe rollouts and tenant isolation.

H29: Infinite-scroll social feed

Reports: 1 · Report date: October 18, 2022 · Stage: Full Stack onsite

  1. A frontend-heavy round on infinite scrolling.

Patterns across the reports

  1. Thread safety turns up as a follow-up. The windowed map (01), LFU cache (14), task runner (19), random-access queue (20) and the older LRU cache (H03) all added concurrency after the single-threaded version.
  2. Exact contracts matter. API methods, URIs and schemas carried the news feed round (22); idempotency drove the URL shortener (21); the Sudoku solver had to call the validator (17, 18).
  3. Storage internals repeat. WAL, snapshots, LSM parts and compaction came up in 23 and 24.

Common questions

What system design questions does Confluent ask?

The URL shortener is the most reported (23 reports, 21), then the news feed API and data model (12, 22). Ticket booking (33) and disposable email (25) are the newer repeats.

What coding questions does Confluent ask?

tail -n over a given file API (02, five reports in 2026) and the windowed key-value map (01, six reports) repeat most. Recent one-offs include document search and Sudoku (15–18).

Does Confluent ask concurrency questions?

Yes. The delayed task runner had nine reports (19), and caches, queues and maps often got thread-safety follow-ups (01, 14, 20).

Keep practicing

Interview reference image

Sources: Anywhere useful interview info can be found.

5 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.