Envié una solicitud electrónica. El proceso duró 1 semana. Acudí a una entrevista en Bumble Inc. (Londres, Inglaterra) en dic 2023
Entrevista
First talk to a recruiter, on a relaxed conversation, and then they will schedule a technical interview with 2 engineers.
They get into a set of platform questions, and then an algorithmic exercise
Preguntas de entrevista [1]
Pregunta 1
General Platform questions, what’s an ANR, concurrency on android, and some basic kotlin
El proceso duró 3 semanas. Acudí a una entrevista en Bumble Inc. (Madrid) en sept 2024
Entrevista
Very old-fashioned interview process. There was a theoretical and a practical part. In the theoretical there were boring questions about equals/hashCode and sealed classes. The stack they are using is very old (no compose/coroutines), they use rxjava and a custom architecture software.
The practical part consisted in 2 leetcode exercises. Although I had been told that I could take them offline, the interviewer didn't offer this option.
Preguntas de entrevista [3]
Pregunta 1
What do you now about equals and hashcode methods in "Kotlin"?
Solicité el puesto a través de la recomendación de un empleado. El proceso duró 3 semanas. Acudí a una entrevista en Bumble Inc. (Londres, Inglaterra) en ago 2021
Entrevista
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
Preguntas de entrevista [3]
Pregunta 1
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.
