CloudBees logo

CloudBees Interview Questions
& Process

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

Based on 43 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
48.8% Positive experience

Which role are you interviewing for?

27 roles · 43 reports

Candidate interview experiences

First-hand accounts from people who interviewed at CloudBees.

Showing 4 of 43
CloudBees logo
CloudBees

Marketing Operations Manager

Marketing · nearly a year ago

Manager Easy Negative experience No offer 7 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite Panel Presentation Background check Offer
Interview formats
Behavioral Technical Presentation

I was contacted proactively by a recruiter about a Marketing Operations role. After replying promptly, there was a delay (about a week) before I heard back, making early communication feel inconsistent. The interview process was very long and time-intensive, spanning over four weeks and including seven interviews, each 45 minutes or longer. The initial call with the Talent Acquisition leader was professional. The discussion with the Chief of Staff went well. Interviews with four other team members were professional and constructive. The final conversation with the CEO felt very dry, and we ended the call after about 20 minutes as many of my questions had already been answered in previous interviews. After the full loop, I followed up a week later about next steps and received no response or closure. Investing over a month and seven interviews without follow-up or closure felt discouraging.

Confirmed questions1 question
  • What makes you want to join this company?
CloudBees logo
CloudBees

ML Engineer

Engineering · nearly a year ago

Mid Average Negative experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

Bad experience overall. The recruiting manager said they'd move forward with me, but after talking to a product owner, they changed their mind. This was weird, and the recruiting manager didn't explain why, even though I thought I did great. It was a really negative experience. Don't waste your time here!

Confirmed questions2 questions
  • Do you use co-pilot, and if so, how?
  • In your opinion, how can Generative AI enhance MLops?
CloudBees logo
CloudBees

Software Engineer

Engineering · a year ago

Senior Average Negative experience No offer 3 rounds
Interview process
Technical screen Technical screen Technical screen Background check Offer
Interview formats
Coding Technical

The interview process was fair and straightforward, with one coding round and two technical rounds. However, I wouldn't recommend accepting an offer from them. Even though I passed all the interviews, they waited 20 days to give me an offer because of the holidays in the US. Then, right when I was giving my notice at my old job, they suddenly told me they weren't moving forward with the offer. Companies can definitely withdraw offers for various reasons, but the way they handled this was super unprofessional. They assured me I had passed everything, so I started my notice period and turned down other job offers to be considerate of their timeline. This whole situation was really frustrating and put me in a tough spot. So, I can't advise relying on their offers.

Confirmed questions1 question
  • How would you build a simple gRPC app in Golang?
CloudBees logo
CloudBees

Integration Engineer

Engineering

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Technical Behavioral

My interview at CloudBees was pretty in-depth and engaging, with three main parts. First, I talked to a recruiter who gave me a good feel for the company culture and what they were looking for in the role, plus some insights on CloudBees' goals and values. Then, I had a more technical chat with the hiring manager and a tech lead to really get into my skills and background. This was my chance to show how I fit with what the team needs. Finally, two more tech leads interviewed me to check my technical chops again and see how I'd mesh with the team. All the interviews were structured well, with good questions and plenty of time for me to ask my own stuff. It was a solid, professional process that made me feel good about CloudBees and the people there.

Confirmed questions2 questions
  • Can you explain how to resolve a 504 timeout error on a Linux server?
  • What is your knowledge of SQL?

CloudBees Interview Questions

Quoted word for word from CloudBees interview reports.

Can you explain how to resolve a 504 timeout error on a Linux server?

Read report

Can you describe the structure of Kubernetes and its high availability features?

Read report

Formats, difficulty and experience

Across all 43 CloudBees interview reports.

Interview formats

Behavioral 46.2%
Technical 27.5%
Presentation 12.5%
Coding 12.5%
Other 1.2%

Interview difficulty

Easy 25.6%
Average 65.1%
Difficult 9.3%

Candidate experience

Negative 32.6%
Neutral 18.6%
Positive 48.8%

Reports by job function

Engineering 14
Marketing 8
Sales 6
Product 5
Operations 5
HR 2