First a recruiter gets in touch with you to talk about the role and the company and you introduce yourself and talk a bit about your professional experience.
Then there are 2 technical interviews where the first is just 1 or 2 random Android questions and lots of others about algorithms and data structures. The last technical interview is a one-hour live coding session, again focused on algorithms and data structures.
All in all you have to constantly remind yourself that you're not applying to be a university professor instead of an Android engineer
The recruiter asked me some questions about myself and my professional background (experience, technologies, etc.).
The first technical interview was just a few random questions about Kotlin and the Android framework, followed by loads of others about algorithms and data structures. To be honest I felt quite uncomfortable because after every answer I gave the interviewer reacted as though I was just saying a load of nonsense, saying stuff like 'hmm yeah, ok I think I know what you mean...', but the recruiter said my score was 'pretty high', at over 75%.
The second technical interview was one hour of live coding where the interviewer described 2 non-Android related problems and I had to solve them with algorithms and data structures. This interviewer was a lot nicer than the first one, who in my opinion was quite stone faced.
The following metrics were computed from 2 interview experiences for the Bumble Senior Android Engineer role in London, United Kingdom.
Bumble's interview process for their Senior Android Engineer roles in London, United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Bumble's Senior Android Engineer interview process in London, United Kingdom.