
Synthesized from 15 candidate submissions for ALL.
Confluent’s hiring process is highly rigorous, emphasizing both technical depth and cultural fit across all roles. Candidates often report multi-round interviews spanning coding, system design, low-level design, and behavioral assessments, with a strong focus on scalability, concurrency, and real-world problem-solving. The process is known for its thoroughness, sometimes involving up to 22+ interview rounds, and is designed to evaluate both technical prowess and alignment with the company’s values.
The candidate faced multiple rejections across several companies before eventually receiving offers from Confluent and Zepto. They selected Confluent after going through over 22 interview rounds across more than 20 companies.
Three technical interview rounds covering topics like DSA, projects, internal workings of HashMap/Sets, hashing, and Linux.
Low-Level Design (LLD) round focusing on system design and database design.
Another technical round, likely involving problem-solving and system design.
A round assessing cultural fit and alignment with the team.
The candidate went through five rounds, including technical coding, system design, and behavioral assessments. The process evaluated problem-solving, system scalability knowledge, and teamwork.
Coding round focused on matching function signatures to queries, with and without variadic flag support.
Given k function signatures with input-output types and queries, return all functions that match the description. Follow-up: Also consider a variadic flag for functions and queries.
Coding round involving a time-based key-value store with a 5-second window. Tasks included optimizing get() and getAverage() operations.
Implement a time-based key-value store with a 5-second window. Optimize get() and getAverage() operations for performance.
Coding round to validate and solve a Sudoku puzzle. Required memory-efficient implementation and printing invalid rows/columns/boxes.
Write code to validate a Sudoku puzzle using a map to store counts. Print invalid rows, columns, or boxes. Include validation for numbers between 1-9. Follow-up: Write code to solve a Sudoku puzzle using backtracking.
Round focused on scaling systems and detecting bottlenecks. Discussed load balancers, slow query detection, database load analysis, and infrastructure as code.
How to detect bottlenecks in a system and remedy them? Discuss load balancers, access logs, multi-region load balancing, slow query detection, database load analysis, master-slave architecture, and replica lag. Also discuss infrastructure as code (e.g., Terraform) and splitting a monolith into microservices.
Behavioral round with questions about company fit, teamwork, challenges, and customer interactions.
Why Confluent? Have you ever had a disagreement with a teammate, and how did you handle it? What is the most challenging work you have ever done? Why are you leaving your current company? Discuss a time you introduced a bug in the system and how you identified and fixed it. What is one strength as an engineer? Have you ever dealt with customers, and how did you go about it?