Bumble Inc. logo

Bumble Inc. Qa 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

4.6 Rounds average
Average Typical difficulty
20% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Bumble Inc..

Showing 3 of 5
Bumble Inc. logo
Bumble Inc.

Senior QA Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding

My interview experience was bad. The interviewer was aggressive and tried to compare programming languages to football clubs. They asked irrelevant questions and kept interrupting me. The interview was supposed to be an hour but ended in 30 minutes because they had another one. This and the fact that my last interview had no one show up makes me think Bumble isn't a serious company.

Confirmed questions3 questions
  • What is the difference between Ruby and Java?
  • Can you explain the difference between an interface and an abstract class?
  • Explain polymorphism, specifically method overloading and overriding.
Bumble Inc. logo
Bumble Inc.

QA Engineer

Engineering · more than a year ago

Entry Average Positive experience Accept offer 1 round
Interview process
Recruiter call Technical screen Offer
Interview formats
Technical Behavioral

The interview process for me was pretty straightforward, with just one round that lasted about an hour. The questions weren't too tough, focusing on PHP and general testing procedures. I was offered the job at the end, which I accepted, and I started working the very next day.

Confirmed questions1 question
  • When testing something urgent and important, do you lean more towards manual or automation testing?
Bumble Inc. logo
Bumble Inc.

QA Engineer

Engineering

Mid Average Negative experience No offer 15 rounds
Interview process
Recruiter call Technical screen Phone screen Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen Technical screen Background check Offer
Interview formats
Technical Behavioral

It was exhausting, a lot of steps I didn't need. I talked to so many engineering folks by the time I got to the behavioral interview. Clearly, they don't talk to each other, so I had to repeat myself a bunch. One interviewer didn't even show up and gave a quick excuse when it was rescheduled. The worst part was at the end. After all those stages, they said the company was restructuring and the new CTO wasn't sure if the role would exist. After waiting two weeks, the recruiter still had no update. A few days later, I got an email with a sad emoji saying they weren't hiring QA engineers for now. A month after that, an automated email said the position was filled and they weren't considering more applicants.

Confirmed questions3 questions
  • Do you know the most recent iOS version?
  • What is the most recent Android version?
  • Is it possible to use JavaScript for object-oriented programming?

Bumble Inc. Qa Engineer Interview Questions

Quoted word for word from Bumble Inc. interview reports.

Is it possible to use JavaScript for object-oriented programming?

Read reports

Can you explain the difference between an interface and an abstract class?

Read reports

Explain polymorphism, specifically method overloading and overriding.

Read report

What would you do if you found a major bug but the dev says it's minor?

Read report

When testing something urgent and important, do you lean more towards manual or automation testing?

Read report

Formats, difficulty and experience

Across all 5 Bumble Inc. interview reports.

Interview formats

Technical 45.5%
Behavioral 27.3%
Coding 18.2%
Other 9.1%

Interview difficulty

Easy 20%
Average 80%
Difficult 0%

Candidate experience

Negative 80%
Positive 20%