Confluent Interview Experiences

12 results

• 

  HackerRank, Sudoku, Machine Coding and a DevProd Values RoundConfluent · Software Engineer · Onsite · Sep 2026

  Online Assessment A 60-minute HackerRank test with 3 coding problems. Phone Interview (DSA Round) Verify Sudoku (check whether a Sudoku board is valid) Solve Sudoku Machine Coding Round Find word in a list of documents (find a specific word in a list of documents). Find Phrase in the same sequence they appear in list of documents (find a phrase in the list of documents, with the words in the give…

• 

  Variadic Screen, Phrase Search and a Podcast Design LoopConfluent · Software Engineer · Senior+ · Onsite · Aug 2026

  I'm in Canada, interviewing for Senior I. Their old careers site has been shut down and you now have to apply through IBM, otherwise nobody pays any attention to you. It seems to be a transition period right now and the internal hiring pipeline is a bit of a mess. In two of my interviews, the interviewer didn't know they had to log into Teams, which threw things off. Screen: the classic isVariadi…

• 

  Confluent Software Engineer interview with a four-round virtual onsiteConfluent · Software Engineer · Technical Screen · Apr 2026

  A recruiter reached out to me on LinkedIn, and the process started with a coding conversation with a senior engineer. That round went really well. I finished confidently, and the interviewer seemed genuinely impressed. What followed felt chaotic and stressful. I was moved into a virtual onsite almost immediately. It covered four rounds over two days, including coding, a hiring manager discussion,…

• 

  Confluent Software Engineer interview: LeetCode-focused technical rounds over several weeksConfluent · Software Engineer · Technical Screen · Apr 2026

  My interviews followed a fairly standard sequence of two or three steps. I started with an initial recruiter screen, moved into technical interviews, and later had a behavioral or manager-focused conversation. The period from my first interview to the final decision lasted a couple of weeks, while the rounds themselves were usually quick and back to back. The early stage was a coding-focused tech…

• 

  Confluent Account Executive interview and the IBM acquisitionConfluent · Account Executive · Mar 2026

  I started with a recruiter conversation about how the recent IBM acquisition might affect hiring. The recruiter was transparent, but I came away with more uncertainty than clarity, especially about what the acquisition would mean for the day-to-day work in the Inside Sales role. In the later interviews, I kept asking for specifics: how the role fit into the larger sales organization, what the KPI…

• 

  Confluent Account Executive interview with a defense-sector role mismatchConfluent · Account Executive · HR Screen · Feb 2026

  My experience started with a recruiter who seemed supportive, but the initial description of the role, especially its stated focus on the defense sector, didn't match what I later heard from the interviewers. That mismatch made me wary of how clearly the role had been defined. Once I entered the interviews, it was hard to pin down the day-to-day responsibilities and scope. Both conversations star…

• 

  Passed Both Codings, Failed Both System DesignsConfluent · Software Engineer · Senior+ · Onsite · Feb 2026

  Rejected

  The technical screening round overall was pretty simple. They give you a function query signature and have you determine whether there's a registered function that matches it. Later on this expands to cases involving optional arguments and variable number of arguments. The onsite had four rounds total. The first coding round was to implement something like printing the last N lines of a file, alo…

• 

  A Linux-Heavy Super Day With No FeedbackConfluent · Software Engineer · Senior+ · Onsite · Jan 2026

  Role: Confluent - Senior Software Engineer - Cloud Traffic Screen: look up a word in a given file — each line of the document is one sentence. First find a word in the document, then as a follow-up find a phrase/sentence in it. Just talked through the approach at a high level; optimizing with a hashmap was enough. The feedback said I needed hints. VO (super day) — Specialty: intense grilling on L…

• 

  Confluent Frontend Engineer: JavaScript, React, and rolling-window data accessConfluent · Frontend Engineer · HR Screen · Jan 2026

  The process started with a recruiter chat and quickly moved into interviews tied to practical work instead of abstract puzzles. The recruiter call covered my background and expectations, after which I took a frontend coding challenge. That round focused on JavaScript and React. I also had a UI design discussion that moved into broader system basics before shifting to behavioral questions and team…

• 

  Confluent Software Engineer interview with system design and DSA roundsConfluent · Software Engineer · Technical Screen · Nov 2025

  My process had three segments. First, I completed a qualifying technical round. Then came the heavier middle section: three rounds combining system design with DSA, with the DSA portion mostly resembling LeetCode medium difficulty. The final segment was a behavioral round with a senior manager. The process felt difficult because the middle block required sustained technical thinking across severa…

• 

  Confluent Software Engineer interview with two technical rounds and harder follow-upsConfluent · Software Engineer · Technical Screen · Nov 2025

  Rejected

  My interview had a small set of core stages: recruiter coordination, two technical interviews, and a manager round. The problems were medium overall, with some harder follow-ups that required me to stay sharp after I thought I’d settled into the first question. I had a generally positive impression of the process. The recruiters were responsive and supportive, and it took only a few weeks from my…

• 

  Confluent Solutions Engineer interview: cloud and data management focusConfluent · Solutions Engineer · Technical Screen · Oct 2025

  Rejected

  My biggest issue started before the technical work. The role requirements felt misrepresented. I spent time with the recruiter and hiring manager discussing my background in detail, and they explicitly told me that specialized knowledge of their products or data streaming wasn't required. When the one-hour technical interview came, the focus didn't match what I had been led to expect. The convers…