Couchbase logo

Couchbase Site Reliability Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 5 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
20% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Couchbase.

Showing 3 of 5
Couchbase logo
Couchbase

Senior Site Reliability Engineer

Engineering · more than a year ago

Senior Easy Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Technical screen Technical screen Background check Offer
Interview formats
Technical Coding System Design Behavioral

So basically the process was standard - screened my resume, then had 3 technical rounds (technical, coding, and design), and finally met with the HM. The interviewers were cool, but the HM experience was terrible. He said things looked good and he was pretty sure about offering me the job, but mentioned a re-org might cause delays. Then, a week later, I got a rejection email citing a skill mismatch. I thought that was pretty unexpected after they'd already screened my resume and talked to me about my experience.

Confirmed questions4 questions
  • A standard Leetcode easy question was asked.
  • We discussed questions related to monitoring.
  • We discussed questions related to alerting.
Couchbase logo
Couchbase

Site Reliability Engineer

Engineering · more than a year ago

Mid Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Technical Coding Technical

It was a really structured interview process. We began with a chat to see if my background and what I'm looking for in the future fit what they need for the role, then went through a bunch of technical interviews and got some feedback.

Confirmed questions6 questions
  • We did a pair programming exercise.
  • There was a problem-solving component.
  • We talked about Kubernetes.
Couchbase logo
Couchbase

Site Reliability Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen Phone screen
Interview formats
Technical Coding Behavioral

The interview process had some red flags. It included two video calls, each lasting about an hour. Both were technical interviews. The first one was with the manager of the SRE team. I answered some general technical questions and then did a coding exercise where I guided the manager through writing and benchmarking code. This part was okay, but then I found out the manager wasn't actually a Couchbase employee, but from an external consultancy helping set up the SRE team. He mentioned they were replacing consultants with direct hires and he'd eventually be replaced too, which was weird. The strangest question was about being ready to work non-stop. The next interview was hard to schedule because the manager kept changing times. He ended up not showing up, but I spoke with two engineers from the SRE team. It was more broad technical and architectural discussion. Turns out, they also weren't Couchbase employees but from the same consultancy. They seemed disengaged and spoke negatively about Couchbase's SRE efforts. That's when I decided I wasn't interested. The manager scheduled another meeting but rescheduled multiple times before just canceling and sending an automated rejection. Honestly, it felt like Couchbase just wants to get big and IPO, treating employees like cogs. If you're okay with that and a potential IPO lottery ticket, go for it. But if you want to be treated like a human, I'd pass.

Confirmed questions2 questions
  • Are you prepared to work hard for a startup?
  • Are you ready to put in the effort for a startup environment?

Couchbase Site Reliability Engineer Interview Questions

Quoted word for word from Couchbase interview reports.

Formats, difficulty and experience

Across all 5 Couchbase interview reports.

Interview formats

Technical 40%
Coding 33.3%
Behavioral 20%
System Design 6.7%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Neutral 20%
Negative 60%
Positive 20%