Bumble Inc. Software Engineer Interview Questions
& Process

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.

Started with a recruiter call to discuss my experience, the company, and what to expect next. They mentioned no LeetCode style questions. Then had two 1:1 technical interviews. The live coding questions were pretty simple, but both focused a lot on Concurrency and Threading. When I asked if this was a common issue in the app, the interviewers said they had an abstraction for it, which seemed a bit odd given the focus. Even though the recruiter said no LeetCode questions, I was given a Tree question with only 5 minutes left. I made small mistakes in the coding sessions, like with 'frame vs bounds', but figured out the correct answers when discussing with the interviewers. The feedback mentioned I didn't get these right the first time, leading to a pass. The coding was done in CoderPad, missing features like auto-completion and compiler warnings, which aren't present in real-world coding environments where such issues are usually prompted. Missing these in CoderPad (and then correcting) resulted in a fail. The company seemed cool, but the interviewers felt like gatekeepers, expecting perfect answers immediately on minor issues that are easily fixed in actual work. The recruiter gave feedback afterward but didn't seem to take notes on anything I mentioned, appearing indifferent and just going through the motions.

Came in through campus recruiting, there were 3 rounds total. The first round was an in-person technical interview on campus. The second round was a virtual technical interview. The third round was an in-person behavioral interview at their office. For the first round, it's best to focus on correctness and edge cases first, then think about optimization. They ask questions that are doable and straightforward, similar to LeetCode questions. The team is very kind and friendly, and the recruiter was very communicative. I was able to ask for specific feedback after the interview.