Mystifly | SDE2 | Bengaluru | April 24 [Selected but no offer]
Summary
I recently interviewed for an SDE-2 role at Mystifly in Bengaluru and successfully cleared both technical and techno-managerial rounds. Despite receiving positive feedback, I haven't received an offer due to reported hiring slowdowns, which has been quite a frustrating and disappointing experience.
Full Experience
I recently had an interview experience with Mystifly for an SDE-2 position in Bengaluru, around April 2024. I have 10 years of experience.
The first round was a technical interview lasting about an hour. I was asked a simple question on the classic 'trapping rain water' problem. Following that, I tackled a problem involving multi-threading and API optimization. Specifically, I was presented with a scenario where a client calls an API 10,000 times, with each call taking 5 seconds to respond. My task was to improve this client. My proposed solution involved using an executor service to parallelize these calls and implementing a scatter-gather pattern to efficiently collect the responses.
The second round was a techno-managerial interview with the CTO, Bharat Goyal. This round felt very different; it was quite easy and informal, almost like a normal work discussion rather than an interview. We discussed my projects, and then I was asked to clone a random repository, understand its codebase, and explain it.
I successfully cleared both rounds and received positive feedback. However, despite a month passing and my LWD (Last Working Day) fast approaching, HR has still not responded to my emails, citing that hiring has slowed down. They mentioned they don't know when it will speed up, but if I'm still available then, we could talk. Honestly, I consider this a waste of my time and effort, and I wouldn't recommend interviewing here.
Interview Questions (3)
I was presented with a simple coding problem related to calculating the maximum amount of water that can be trapped between given bars of an elevation map, often known as the 'Trapping Rain Water' problem.
I was asked to improve a client that calls an API 10,000 times. Each API call takes 5 seconds to respond, leading to a significant total execution time. The goal was to optimize the client's performance.
During the techno-managerial round, I was asked to clone a random GitHub repository, analyze its code, understand its functionality, and then explain it.