Initial call with the recruiter describing the position. The problem was the description didn't match reality. The recruiter mentioned some projects and technologies the interviewers weren't even aware of.
Take-home challenge. Implement a self-updating tweeter feed.
"Pair programming" - this stage went really bad. The recruiter set me up for failure. He said it will be a discussion about the take-home solution and architecture and decisions made and maybe some updates to that code. In reality, the 2 interviewers, without even making an introduction, put a CodeSandbox in front of me and presented 3 tasks that had to be done under pressure with no warning whatsoever.
Because I had no idea of what to expect beforehand and the task was very niche, it took me some time to solve the tasks but the entire "pairing" experience was terrible. I knew straight away I didn't want to work there with those people.
After the interview the recruiter, Joe Brown, ghosted on me - I sent him an email, he didn't call back or ever replied to any of my emails.
It was one of the worst candidate experiences I've seen on the market.
You need to implement a self-updating tweeter feed.
On-site you need to know the ins and outs of scrolling a page and computing the top and bottom of the page.
The following metrics were computed from 1 interview experience for the Bumble Senior JavaScript Engineer role in London, United Kingdom.
Bumble's interview process for their Senior JavaScript 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 JavaScript Engineer interview process in London, United Kingdom.