The recruiter contact led to a phone conversation first, where I talked through my background and they also explained how they were thinking about their frontend—specifically a move from reflux to redux, and later the expectation that frontend folks would do some backend too. I felt generally aligned with that direction, so I went into the next step with decent confidence.
Then I had an onsite that was essentially back-to-back technical segments totaling about two hours. One interview started with walking through my background and then a practical explanation of redux for someone who wasn’t familiar with it. After that, the conversation shifted into JavaScript questions, including a few trickier ones that I overthought and ended up getting wrong, plus more straightforward questions. The interviewer also offered an algorithm choice: either writing out a method to check whether a number is prime or removing duplicates from an array. I paused briefly, but instead of fully committing to the prime option, I asked if I could do the duplicate-removal one since I already knew the exact approach.
> 1 year
Average Neutral New York, NY
I remember how long it took to actually get scheduled, even after I had already applied and seemed to be in the running. My phone interview was rough in the sense that it was basically a stream of questions with very little real interaction, and it didn’t feel like a two-way conversation.
Eventually I got invited in person, and the onsite start was nicer than the phone screen—people were at least pleasant when I arrived. But once the interview day ended, it went quiet. I didn’t hear anything back for about a month, and the follow-up felt absent enough that it became clear the process wasn’t going anywhere.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
