Confluent

Role: SSE2 (Senior Software Engineer)

College: Not Specified

Interview Date: May 2025

Interview Type: Full-Time

Result: No Offer (Overall Lean No Hire)

Difficulty: Hard

Rounds: 6 rounds

Topics Asked: Data Structures, Algorithms, API Design, SQL, Data Modeling, System Design, Behavioral

Experience:

The interview loop for an SSE2 role involved a good mix of algorithmic depth, API-level design, and real-world engineering conversations.

Round 1: Phone Screen (DSA)
Problem: Given a list of function signatures and a list of input arguments, return all matching functions based on parameter compatibility. The follow-up extended the solution to handle variadic arguments like `Integer... args`. The focus was on type matching and signature parsing.

Round 2: DSA
Problem 1: Check if a given Sudoku board is valid (partial board). Problem 2: Solve a complete Sudoku puzzle. Emphasis was on clean recursion, backtracking, and pruning optimization.

Round 3: High-Level Design (Podcast Service)
Topic: Design a Podcast Service with features like Feed view, Subscribe/Unsubscribe to podcasts, and Add podcasts and episodes. No architecture diagram was expected. The focus was on API design (verbs, response codes, headers), SQL queries, and Data modeling.

Round 4: High-Level Design (TempMail Service)
Topic: Design a TempMail generation service where generated emails are valid for 5 hours. Discussion focused on expiry mechanisms, storage strategies, access control and validation, and building sensible mail names.

Round 5: DSA / Code Debugging
Problem: Given an implementation of Quicksort, identify and fix bugs. Then optimize performance by discussing and applying pivot strategies to reduce the chance of hitting O(n²), covering randomized pivot, dual pivot, and median-of-three approximation.

Round 6: Culture & Value Fit
Topics discussed included going above and beyond to exceed customer expectations, taking initiative in challenging situations, pushing back on legacy decisions, suggesting improvements, mentoring peers, and handling ambiguity and complexity in large-scale systems.

Overall Experience: The candidate received strong hires in coding rounds but no strong hire in design rounds, leading to an overall "Lean No Hire" verdict. The process took over 2 months.