Confluent Software Engineer Interview Guide

I started with a recruiter call that covered background and expectations, then was asked to walk through two coding problems verbally as part of the screening. It didn't feel like a full technical round—more like a quick bar-raising check. After that, I completed an online assessment as requested, but the process essentially stalled. I followed up via email multiple times and got nothing back: no rejection, no feedback, no closure. It was frustrating because other companies I interviewed with around the same time at least had the courtesy to send a decision email.

Based on what I pieced together from the process, the technical questions spanned a few different styles. Some were classic LeetCode-style problems like implementing an LRU cache or validating a sudoku board. Others leaned more old-school—like implementing a Linux tail command that efficiently handles very large files without scanning from the beginning. The interviews I did complete had professional interviewers who tried to clearly scope what they were looking for, which I appreciated. The hiring manager round was engaging and interactive.

What stood out most was the communication breakdown. Three technical rounds happened, but afterward, radio silence. No results, no next steps, no explanation. For a company that builds around data streaming and real-time communication, the irony wasn't lost on me. If you're interviewing here, prepare for a mix of classic data structure problems and systems-thinking questions, but also be ready for the possibility that the process might not give you closure at the end. It's worth asking the recruiter upfront about their feedback timeline and decision communication—that might save you the frustration I experienced.