Confluent Solutions Architect Interview Questions
& Process

I reached out to someone I knew at Confluent. A recruiter called me to discuss the role and my background. Then, I had a technical screening interview, followed by an interview with a Manager. After those two 45-minute interviews, I proceeded to a round of three more 45-minute interviews covering Distributed Systems, my Project work history, and a Code Comprehension interview. All interviews were well-designed and efficient. The interviewers made me feel comfortable throughout. The recruiter kept me informed about role availability and market changes.

I applied online and it took about a week to hear back and get shortlisted. Then I had an initial chat with HR. Komal from HR was super helpful in introducing herself and explaining the interview process in detail. The next step was a technical interview, which was actually pretty straightforward. It covered typical topics like Linux, Java, data structures, and system design. However, the interviewer wasn't great at asking questions clearly and seemed to expect textbook answers. They even used incorrect terms sometimes, like confusing garbage collector mechanisms with algorithms. The system design questions lacked clear guidance, and the interviewer started arguing about SLAs within the limited 10-minute window I was given for it. Honestly, I just wish the interview questions were clearer and not just straight out of a textbook.

This was my first in-person interview at Confluent, following positive conversations with other team members. I had a short-notice meeting at their London office with an interviewer from Confluent UK. The interviewer seemed disengaged from the start, slumping in his chair and sluggishly asking some technical questions, even yawning multiple times. Despite this unprofessional conduct, which may have stemmed from him not reviewing my resume, the rest of the interview process with Confluent was excellent. It's disheartening when one person's actions negatively impact the experience.