The first part of my process was messy in a way that started to affect my confidence: I went through multiple phone screens—four of them, and it felt like they should’ve been consolidated. The onsite itself could’ve gone fine, but the logistics and attitude around the process were off, including issues with actually having space to interview.
There was one particularly frustrating moment with an engineering team member who kept disagreeing with how I was using JSON syntax even after I showed documentation. It made the technical discussion feel less like collaboration and more like arguing over basics, and that colored my overall impression.
> 1 year
Difficult Negative United States
I started with a coffee meet-and-greet with a manager where we talked about the company and the product. The vibe was genuinely good—I left feeling excited about the environment. After that, I was scheduled for a technical screen through an online editor where the interviewer and I could both see me type in real time.
The phone interview moved quickly into coding questions. I got fizzbuzz first, which felt straightforward—mostly loop logic, modulus, and conditional checks. Then I tackled the look-and-say sequence. That one was more awkward to reason about at first, because it didn’t feel as intuitive as it looked on paper, and I stumbled while trying to translate my approach into code under pressure.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
