Confluent Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 107 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Confluent.
Confluent
Software Engineer
Intern Average Positive experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Behavioral Coding
The initial recruiter call covered my background and what they were looking for. They also asked me to talk through two coding problems, which felt more like a quick screening. I was asked to do an OA, but after that, radio silence. No rejection email, no updates at all, which was disappointing. Other companies I've interviewed with recently have had better communication. I've been using Hack2Hire and LeetCode to practice, and most places at least give some feedback or let you know what's up. This one just kind of stopped without any closure.
Confirmed questions2 questions
- Recruiter asked about my background.
- I verbally explained how to solve two simple algorithm problems.
Confluent
Software Engineer
Senior Average Positive experience Accept offer 6 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Behavioral System Design Coding
Applied online and the recruiter got in touch in about 2 weeks. The entire process spanned approximately two months, covering these stages: First, a chat with the recruiter to learn more about the company and the hiring process. Then, a technical screening. After that, four rounds of interviews (one behavioral, one design, two coding). Finally, a team match. The recruiter was really helpful in keeping me updated and providing feedback, which made things go smoothly. There was also a preparation session that was super useful. The interviews were scheduled over two days, but one got canceled last minute. Fortunately, the coordinator sorted out a reschedule quickly, so it didn't cause a major delay. After all the interviews, I heard back from the recruiter after about 10 days with good news. Then it took about a week to get to the team match. Both the recruiters and the coordinator were professional and seemed enthusiastic, which was a big reason I decided to accept the offer.
Confirmed questions3 questions
- Tell me about yourself.
- Can you design X?
- Solve this coding problem; here are some follow-ups.
Confluent
Software Engineer
Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Coding
The first call with the recruiter was pretty standard, but then it took ages to set up the technical interview. One weird thing was having to sign an NDA for the interview. The technical interview itself involved implementing data access in a rolling time window. The interviewer didn't explain the problem very well and wasn't helpful when I asked clarifying questions, he seemed like he didn't even want to be there. I got a basic solution working pretty quickly and then focused on optimizing it. I left feeling pretty unimpressed with Confluent, so I wasn't shocked when they didn't move forward with me. Just a heads up, Confluent, your interviewers need some serious training.
Confirmed questions1 question
- How would you implement data access within a specified time window?
Confluent Software Engineer Interview Questions
Quoted word for word from Confluent interview reports.
“Create a data structure supporting get, put, and getAverage() APIs, where entries have an expiration time.”
Read reports →“Can you determine if a given string matches a pattern containing wildcards?”
Read reports →“Can you figure out if two strings are just one edit away from each other?”
Read reports →“How would you find the trailing zeroes in the factorial of a number?”
Read reports →“Could you implement a Trie to solve a prefix matching problem?”
Read report →“How would you solve the wildcard pattern matching problem using Dynamic Programming?”
Read report →“How would you process a stream of events given a specific window size?”
Read report →“Implement a concurrency problem where you have a token bucket of capacity N. Tokens are added to the bucket at a rate of 1 per second. If the bucket overflows, tokens are dropped. Several threads need one token to finish their work, so they grab a token (which is then removed) when invoked and continue. Your task is to implement this scenario and ensure synchronized access to the bucket.”
Read report →“How would you implement a Most Recently Used (MRU) cache?”
Read report →Formats, difficulty and experience
Across all 107 Confluent interview reports.