I went through a pretty direct coding-focused screening. It started with an online HackerRank-style screen, where I answered a small set of questions that were mostly easy to medium, with a lot of emphasis on array manipulation. After that, I had follow-up steps that looked like resume context plus a team interview, but the technical meaning of the conversation felt oddly unclear.
In my case, there was a live team conversation where I expected a more classic technical evaluation, yet the questions I was asked didn’t match what I felt the screening had been aiming for. Communication was also a factor: the interviewer’s English wasn’t strong enough for fluent technical back-and-forth, and a translator sat between us. That made it harder to tell whether I was missing technical nuance or whether the questions were just being interpreted in a way that didn’t lead to a clear assessment.
> 1 year
Difficult Positive India
I had a harder time than expected right from the start. The process was short for me—only two rounds—because I didn’t clear the second one. Even though both rounds felt well-structured, they left me with a strong sense of where I stood relative to their expectations, and honestly it was pretty humbling.
The first part centered on coding/problem solving, then the rest leaned into behavioral discussion mixed with technical concepts. I remember being asked about how I thought through performance characteristics like space and time complexity after solving a problem, and they also wanted to hear how my resume mapped to their needs. The vibe wasn’t chaotic, but it felt more demanding than the typical “quick screen,” especially because the questions required me to be precise, not just reach an answer.
> 1 year
Easy Negative Tokyo
I went through a fairly straightforward process that dragged on just over a few weeks. It started with a simple skills check focused on GitHub, and on…
Unlock every Frontend Engineer interview experience
