My journey started with a recruiter phone screen, then quickly moved into LeetCode-style coding and a hiring-manager technical screen built around my past experience. The sequence kept escalating: I had real-world implementation where I had to write an API, and then I reached system design—which, for me, didn’t go well. After that, there were more coding rounds in a similar LeetCode style, and the process wrapped with a Topgrading/behavioral round with the engineering manager.
The difficulty felt all over the place, but it was definitely demanding enough that the whole timeline stretched toward close to two months. In that time, I also noticed some inconsistency in what would happen—though I was told there would be a system design interview, it didn’t always end up taking place as expected in the way I’d been prepared for. Even so, the rounds that did happen were heavily technical and designed to probe both communication and depth.
> 1 year
Average Negative Vancouver, BC
I experienced a surprisingly long and logistically messy process. Hiring for Vancouver went through an external HR layer, which meant I had to coordinate with extra people just to get calls scheduled. It wasn’t just slow—it also added overhead to every communication.
The steps started with a recruiter phone screen that didn’t go well because of the interviewer’s attitude. Then I was sent a HackerRank take-home test that included multiple choice questions and coding prompts, followed by another phone screen with a hiring manager. After that, I had a one-hour paired technical assignment on CoderPad, and the final stage was a four-hour onsite technical interview involving a coding project.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
