My experience was relatively smooth and organized compared to what I’d heard elsewhere. It started with a recruiter phone conversation that covered my background, experience, and fit, and it felt friendly and informative. After that, I scheduled the next step where the interview format was very clean: a behavioral round and a technical round back to back.
In the technical part, the assessment was simple and more about fundamentals than trick questions—there was even an assessment style with multiple-choice questions on basic DSA and algorithms, time-limited and not overly intense. When the coding component showed up, it was framed like a straightforward LeetCode-style check, and the interviewer tone stayed supportive. In one case, the interviewers walked me through the process rather than shutting me down.
> 1 year
Average Positive Miami, FL
The process kicked off with an HR phone screening where I talked through my background, skills, and what I’d be bringing to the role. If that went well, the next step was a virtual video technical interview. That round paired a coding challenge with behavioral questions, and I ended up coding through a HackerRank-style prompt. I was allowed to reference external documentation, which helped me keep my focus on solving the problem rather than getting stuck on language minutiae.
After the coding portion, there was time for questions, and the interviewer was easy to talk to and gave me a real sense of the team and what working there was like. But I got tripped up on what the challenge was actually expecting: I prepared for one set of web-centric basics, and the evaluation ended up being more aligned with the “vanilla” JavaScript/CSS world than I expected. Even when I wasn’t lost on the problem itself, that mismatch made the round feel frustrating.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
