Confluent | Senior Software Engineer | Offer
Interview Experience
My experience regarding recent SSE interview rounds with Confluent - I took a referral. After 20 days, recruiter called me and asked to schedule a Qualifer round. Qualifier Round: I was asked a DSA+LLD...
Full Details
My experience regarding recent SSE interview rounds with Confluent -
I took a referral.
After 20 days, recruiter called me and asked to schedule a Qualifer round.
Qualifier Round:
I was asked a DSA+LLD question and was supposed to implement and run it on coderpad. There were followup question on time complexity and Concurrency(Locking especially).
Recruiter mailed after 3 days after followup and scheduled full onsite loop.
Onsite 1
Was asked a DSA question in 2 parts first being easy-medium and second being medium-hard. Again working code was required with good coding practice. Wrote it nicely and interviewer was impressed.
Onsite 2
Was Asked a LLD question particularly on optimizing memory while reading a huge file as part of the problem. Awareness of low level language memory constucts was key. Was able to solve it and run. Working code was important again. Discussed further optimization on memory access when asked but could not code as we were out of time. Struggled a little with API knowledge but was able to get through. Interviewer seemed fine in the end.
Onsite 3
Was Asked a HLD question and was the easist round as HLD being my favourite and forte. Had to draw and explain the thought process with tradeoffs being made. Interviewer seemed happy.
Onsite 4
This was a deep dive+cultural fit round. Usual question around the project and different phases and situations in project and how did i handle them. This went really well.
After one week, followed up with recruiter and they said its a hire call. They setup a role sell call post that.
All the interviewer were very nice and jolly. Everything happened as scheduled on time. It was a very nice experience.
Offer - https://leetcode.com/discuss/compensation/5161790/Confluent-or-Senior-Software-Engineer-or-Remote
Questions - https://leetcode.com/discuss/interview-experience/5047273/Confluent-Onsite-Interview-Experience-Rejected
Looks like OP of questions post and i got interviewed during exact same time xD
Note:- There are always followups on the question in terms of approach, testing, tradeoffs as the questions are quite open ended in terms of expectations.
About This Question
This is a candidate experience report from a confluent interview for a swe role (senior level) during the oa round reported in 2024.
It covers the following topics: Os .
Difficulty rating: Easy
Topics
More Confluent Interview Questions
About Confluent Interview Reports
This question was reported by a candidate who interviewed at Confluent. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Confluent are the higher-signal extractions to take from this report.
For broader preparation context, the Confluent interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Confluent reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Confluent Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Confluent reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.