What two candidates report about Bumble's Software Engineer interviews: recruiter and behavioral conversations, practical coding, time-conversion and testing questions, OOP fundamentals and a take-home test.
$140K
Avg. Base Comp
$186K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Bumble's software engineer reports come from two candidates, and both ended without an offer, so the details below are individual experiences rather than a fixed format. The two processes differed in structure, though both included practical coding, some testing or fundamentals questions, and a behavioral conversation.
One candidate began with a recruiter screen, then a behavioral round and a technical interview. The coding interview leaned toward real-world scenarios rather than LeetCode-style puzzles. A take-home tech test followed, including an obscure cipher implementation question, and a pop-up warned against leaving the tab, so looking things up wasn't an option. The virtual technical interview covered OOP ideas: abstraction, encapsulation, polymorphism and inheritance. This candidate also heard about a pair programming test and a final soft skills interview but didn't reach them.
The other candidate went through campus recruiting in three rounds. An in-person coding problem with a dating-app context came first, in a language of their choice. A virtual round on HH:MM time conversion followed, with emphasis on correctness and edge cases before optimization. The last round, at Bumble's office, was behavioral, covering background, communication style and fit. This candidate found the interviewers friendly and the recruiter responsive.
To prepare, practice small coding problems and say your edge cases and test cases aloud, refresh core OOP and computer science fundamentals, and have examples of your background and communication style ready.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Bumble process.
I went through Bumble's campus recruiting process, which had three distinct rounds. The first round was an in-person technical interview on campus. They gave me a straightforward coding problem with context relevant to dating apps — I got to choose my programming language, which was nice. The interviewers were supportive throughout, willing to help guide me through my thinking and ask follow-up questions when needed.
After that came a virtual technical round where I tackled another problem. This one focused on time conversion — converting between HH:MM formats — and then they dug into testing. The emphasis was really on correctness and edge cases first before worrying about optimization. The questions themselves weren't trying to trick me; they were doable LC-style problems with clear scopes.
The final round was in-person at their office and took a behavioral turn. They asked about my background, communication style, and fit for the role. The whole team came across as genuinely kind and friendly, and the recruiter was especially communicative and responsive. I was even able to ask for specific feedback after the process wrapped up, which I appreciated.
Ultimately I didn't get an offer, but I didn't feel like I was blindsided by the process or the difficulty level. The bar was clear, and the interviewers made space for me to show my thinking.
Prep tip from this candidate
Practice time-manipulation problems and think deeply about edge cases and test scenarios — they'll probe your testing mindset as much as your coding logic. The problems themselves are straightforward, so the differentiator is how thoroughly you handle boundary conditions and communicate your approach.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Bumble
Explain what a p-value is to someone who is not technical
| Question | |
|---|---|
| Client Solution Pushback | |
| Employee Salaries | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Weighted Keys | |
| Top 3 Users | |
| Raining in Seattle | |
| Comments Histogram | |
| Like Tracker | |
| Random SQL Sample | |
| Flight Records | |
| Largest Salary by Department | |
| Over-Budget Projects | |
| Liked Pages | |
| Google Maps Improvement | |
| User Experience Percentage | |
| Job Recommendation | |
| Retailer Data Warehouse | |
| Permutation Palindrome | |
| Find the Missing Number | |
| Recurring Character | |
| Scrambled Tickets | |
| Maximum Profit | |
| Size of Joins | |
| Employee Salaries (ETL Error) |
Synthesized from candidate reports. Individual experiences may vary.
One candidate says the process started with a recruiter screen before moving to a behavioral round and a technical interview. A campus candidate separately describes the recruiter as communicative and responsive, and said they could ask for feedback after the process ended.
The campus candidate's first round was an in-person coding problem with a dating-app context, in a language of their choice. The second, virtual round covered HH:MM time conversion, with questions on testing, correctness and edge cases before any optimization.
Another candidate describes a practical coding interview and a virtual technical interview probing abstraction, encapsulation, polymorphism and inheritance. A take-home tech test followed with an obscure cipher question and a pop-up warning against leaving the tab.
The campus candidate's last round was in person at Bumble's office and covered background, communication style and role fit. The other candidate mentions a behavioral round plus a pair programming test and final soft skills interview, which they did not reach.
