The interview process consisted of one phone interview, followed by a take-home assignment, and then another phone interview. I received a rejection email at this stage.
The recruiters were very slow to respond, lacked in communication, and generally seemed confused and not eager to hire. Initially, the recruiters mentioned that their process involved only a take-home assignment and then an onsite round. However, they later requested more phone interviews.
I was initially told there would be multiple remote interviews, but only one was scheduled.
Overall, they were not effective in communicating what they were looking for, which resulted in wasted time for both sides. Be cautious about investing your precious time interviewing here, especially with take-home assignments or multiple phone interview rounds before an onsite, as the turnaround times are very slow.
Despite investing significant time in the process, I did not feel I learned much about the company, its challenges, product strategy, or culture.
To be fair, the interviewers (engineers) seemed friendly and humble, and the recruiters were also friendly (and not rude or arrogant like at other places).
The take-home assignment was a significant chunk of work, taking about 6 hours in total. It involved implementing a multi-threaded data structure.
I highly recommend revising up on locks, condition variables, and other language primitives before starting on this.
Design Interview
The following metrics were computed from 20 interview experiences for the Confluent Software Engineer role in United States.
Confluent's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having very good feelings for Confluent's Software Engineer interview process in United States.