I got contacted by a recruiting coordinator to move into the interview rounds, and it was a little confusing because the roles of the different recruiters weren’t very clear at first. My process ended up being two structured one-hour interviews. The first half of each interview focused on the team and product—starting with a “tell me about yourself” style intro—then I had time to ask questions about culture and what the day-to-day actually looked like. The second half was coding, and everything was run in HackerRank.
For the first interview, the coding was a straightforward JavaScript-principles assessment—closures and arrays. After I finished, we talked through how I could optimize and clarified what certain concepts were called, and it felt pretty calm rather than trick-oriented. The second interview followed an almost identical structure, but the coding part switched to a more practical React task. I was given a UI plus requirements to implement. I ran into bugs and used quick searching while working, and I didn’t finish within the time limit, but I was able to explain how I would have completed the remaining pieces.
> 1 year
Average Negative Kirkland, WA
I went through a phone screening using an online development platform and then had an onsite interview that felt unusually tool-driven. The exercises didn’t feel like they were mostly measuring my knowledge of concepts; instead, they were heavily focused on whether I could type efficiently and navigate their platform quickly.
One interviewer paid more attention to whether I could get code running on their tool than to whether I truly understood the underlying knowledge, and I remember finding that the least enjoyable part was how much emphasis went into syntax and basic mechanics. The interview also had at least one moment where a round felt more about searching and typing than about deeper reasoning.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
