Bumble Inc. logo

Bumble Inc. Android Engineer Interview Questions
& Process

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

Based on 9 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
44.4% Positive experience

Candidate interview experiences

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

Showing 3 of 9
Bumble Inc. logo
Bumble Inc.

Senior Android Developer

Engineering · more than a year ago

Senior Average Positive experience Accept offer 2 rounds
Interview process
Technical screen Take home
Interview formats
Technical Coding

The interview process has two main parts. The first part focuses on general Android knowledge, covering topics like lifecycles, Kotlin, SOLID principles, sealed classes, data classes, threading, concurrency, hashing, and data structures. The second part is technical, where you'll be given practical tasks. It's a good idea to practice on HackerRank, as the actual interview is mostly conducted on that platform, so getting familiar with it will help a lot.

Confirmed questions1 question
  • Can you explain what an Application Not Responding (ANR) error is and how to prevent it?
Bumble Inc. logo
Bumble Inc.

Senior Android Engineer

Engineering · more than a year ago

Senior Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Technical screen
Interview formats
Behavioral Technical Coding

First, a recruiter will reach out to discuss the position and the company. You'll introduce yourself and share some of your work history. Following that, there are two technical interviews. The first one includes a couple of general Android questions, alongside numerous algorithm and data structure queries. The final technical interview involves a one-hour live coding session, again focusing on algorithms and data structures. You really have to remember you're interviewing to be an Android engineer, not a professor.

Confirmed questions3 questions
  • The recruiter inquired about my background, experience, and technical skills.
  • The initial technical interview covered some random Kotlin and Android framework questions, followed by many algorithm and data structure questions. The interviewer's reactions were a bit discouraging, but the recruiter mentioned a high score of over 75%.
  • The second technical interview was a one-hour live coding session where I had to solve two non-Android related problems using algorithms and data structures. This interviewer was much friendlier than the first.
Bumble Inc. logo
Bumble Inc.

Senior Android Engineer

Engineering

Senior Average Negative experience No offer 2 rounds
Interview process
Technical screen Take home
Interview formats
Technical Coding

This was a really old school interview process. It had a theory part and a practical part. The theory part had some dry questions about equals/hashCode and sealed classes. Their tech stack is pretty dated (no compose/coroutines), they're using rxjava and some custom architecture software. The practical part involved 2 LeetCode exercises. Even though I was told I could do them offline, the interviewer didn't actually offer that option.

Confirmed questions3 questions
  • Can you explain the concepts of equals and hashcode methods in Kotlin?
  • How would you merge two sorted arrays into one sorted array?
  • What is the median of two sorted arrays?

Bumble Inc. Android Engineer Interview Questions

Quoted word for word from Bumble Inc. interview reports.

Solve the graph subcomponents problem (Zombie Cluster).

Read report

What if the reversed number goes out of integer range (check with Integer.MAX_VALUE & Integer.MIN_VALUE)?

Read report

Which is faster for traversing all items, ArrayList or LinkedList, and why?

Read report

How would you merge two sorted arrays into one sorted array?

Read report

Formats, difficulty and experience

Across all 9 Bumble Inc. interview reports.

Interview formats

Technical 34.6%
Coding 34.6%
Behavioral 19.2%
System Design 11.5%

Interview difficulty

Easy 11.1%
Average 77.8%
Difficult 11.1%

Candidate experience

Negative 44.4%
Positive 44.4%
Neutral 11.1%