Confluent logo

Confluent Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 329 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
47.1% Positive experience

Which role are you interviewing for?

30 roles · 329 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Confluent.

Showing 4 of 329
Confluent logo
Confluent

Customer Solutions Consultant

Sales · nearly a year ago

Entry Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral Technical

Had a weird screening interview that was only 15 minutes. The interviewer was reading off a script and didn’t listen to anything I said or even look at me. When I asked at the end about the career path at Confluent, she misunderstood and thought I was asking if this role was in Customer Success because she was not listening. She told me to go to her LinkedIn profile and repost her posts so the hiring recruiter could see that I was familiar with the company. These types of recruiters should not be working in this field. You have to treat people like humans not robots.

Confirmed questions1 question
  • Are you familiar with a particular technology used by the company?
Confluent logo
Confluent

Solutions Engineer

Engineering · nearly a year ago

Staff Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Technical

The interview process was not great because they told me the wrong things about what the job required. I talked to the recruiter and the hiring manager multiple times, and they both looked at my background and said I didn't need to know Confluent products or data streaming. But then the technical interview, which lasted an hour, was all about cloud stuff and data management, with only like two minutes on Kafka. After all that, they told me they couldn't move forward because they needed someone with data streaming experience. This really wasted my time and theirs. They should have been upfront about what they wanted from the start, even before contacting anyone, to make sure everyone was on the same page and the process was fair and efficient.

Confirmed questions5 questions
  • Can you answer some basic technical questions about cloud technologies?
  • Can you answer some basic technical questions about networking?
  • Can you answer some basic technical questions about databases?
Confluent logo
Confluent

Sales Specialist

Sales · a year ago

Entry Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral

I interviewed for the Cloud Acquisition role at Confluent. After the recruiter screening, I spoke with the hiring manager. The conversation was quite something, as the manager kept interrupting me and assumed I didn't know what Confluent does, even though I've worked with similar tech for years. While I'm not perfect, I'm confident I have the skills to close the SMB deals for this position. The questions seemed off, not really digging into my qualifications or experience beyond asking about my sales process. It felt like they cared more about personality fit than skills, which is probably why the next step is a technical interview. Honestly, I'm okay with not moving forward; I don't want to work where personality or likeability is valued over actual skills and experience.

Confirmed questions1 question
  • Can you walk me through your typical sales process?
Confluent logo
Confluent

Software Engineer

Engineering · a year ago

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 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

Following up on the LRU implementation, how would you make it thread-safe?

Read report

How would you solve the wildcard pattern matching problem using Dynamic Programming?

Read report

Given that Kafka has an open-source solution, what are the customer motivations for using the paid version (managed solution of Kafka)?

Read report

Could you explain what asynchronous means and what an event loop is?

Read report

How would you process a stream of events given a specific window size?

Read report

Formats, difficulty and experience

Across all 329 Confluent interview reports.

Interview formats

Behavioral 33.7%
Technical 28.5%
Coding 18.1%
Presentation 7.5%
System Design 6.8%

Interview difficulty

Easy 12.5%
Average 64.7%
Difficult 22.8%

Candidate experience

Negative 36.2%
Neutral 16.7%
Positive 47.1%

Reports by job function

Engineering 180
Sales 78
Analytics 13
Marketing 11
Operations 11
HR 7