Bumble Inc. Interview Questions
& Process

The hiring process began with an HR screening, followed by interviews with the hiring manager and another stakeholder. I had a great experience with them, and felt I performed well. However, the recruiting team really dropped the ball. After waiting two weeks for feedback after the third interview, I followed up and was told there were internal delays but that I was moving forward. Then, two days later, I got a rejection email from a different recruiter with no explanation. It felt disrespectful of my time and the communication was confusing. The whole process took a lot of time, and I'm disappointed by the abrupt rejection and lack of clarity.

I started the interview process in October and wrapped up my final interview in the third week of November. They told me they needed more time to decide, so I followed up a week later, and they said a decision wouldn't be made until after the New Year. I reached out again after the new year because I hadn't heard anything, and they mentioned another delay, hoping to update me by the end of January. I never heard back and stopped following up. In May, they finally got in touch saying the role was available again, but I had already accepted a position elsewhere.

So the interview process had 5 interviews total. It kicked off with an HR screen, then we had two technical interviews that were pretty interesting and insightful. They weren't coding heavy, but more like rapid-fire questions on ML, Python, and Kubernetes. We also talked about past projects and design decisions. Finally, there was a cross-functional interview and one with the hiring manager/leadership.

The technical interview happened via video call with a shared code platform. HR sent an email beforehand listing potential topics, focusing on mobile apps and networking, but the actual interview didn't cover these. The first part involved PHP questions about character encoding (1-byte vs multi-byte), array manipulation, and using the PHP documentation to find obscure functions. This was interesting as it showed how I handle the unknown and find solutions. The second part was SQL, which was rough. The questions were tricky, like 'Here are 2 tables, get names and grades ordered by date, NO JOIN allowed' and a similar one. It was difficult because you're live with someone interrupting, silently watching, and not offering helpful guidance. It felt uncomfortable trying to figure out these 'questions'. The PHP part tested thinking, engine knowledge, CS fundamentals, and doc reading, but the SQL part was full of gotchas with no room to think or try solutions. I didn't get the job because I ran out of time on one SQL question, which I solved instantly afterward. Pretty disappointed.