My backend developer interview at BitGo started with a video-explanation requirement that made the first round feel unusually strict. I had two questions in the round, and after solving each one I had to submit a short video explaining the solution right there in the process. One of the most memorable parts was that a friend had been rejected for not being able to explain clearly, and it put extra pressure on me to communicate well, not just solve.
I didn’t remember the exact prompts, but the level felt like medium coding problems from the usual LeetCode style. The key difference was the format: I couldn’t rely on quick code submission alone. I had to pause, present my reasoning, and keep the explanation tight.
9 months ago
Difficult Neutral India
I started with an online assessment on a coderbyte platform, and it immediately felt like two different challenges stacked back to back. The first round tested DSA through graph traversal and string manipulation with time constraints. The second round shifted into LLD: I had to design an in-memory database and include some optimization, also under a tight time window.
Even though the tasks were demanding, the overall panel felt decent and reasonably prepared. The difficulty was noticeable, especially in the LLD round where everything depended on making good design decisions quickly.
> 1 year
Difficult Negative Bengaluru
At first, the interview process seemed smooth and I performed well in the early rounds. But after those first two interviews, the process stalled. I d…
> 1 year
Average Negative India
My interview started with clear communication from HR, and it stayed structured throughout. There was a machine coding round where I used my local IDE…
> 1 year
Average Positive Bengaluru
I had a fairly long but organized interview loop with six rounds. It started with an online coding round, then a DSA round, followed by a machine codi…
Unlock every Backend Engineer interview experience
