After reaching out and talking with HR, I moved into a straightforward screening-style flow where the recruiter was friendly and made it easy to share my background in a normal way—work history, education, and projects—with plenty of time to speak. A few days later I had a technical session that felt centered on practical coding rather than anything overly theoretical. I coded through a problem using a live platform and even started going beyond the obvious happy path by looking at extra test cases and edge cases.
The technical interview itself was collaborative and pretty supportive when I got stuck. I remember the interviewer acknowledging that my approach was strong and that with a little more time I could have finished tightening up remaining edge cases. After that, the process moved quickly but didn’t turn into an offer—there was a standard rejection message shortly afterward. Overall it felt like an evaluation where communication mattered as much as correctness, but the finish line was still precision on the details.
11 months ago
Difficult Negative Waterloo, ON
I went through a more intense algorithm-focused sequence that started with a recruiter screen to align on the basics, then moved into multiple rounds of technical work. The main theme was leetcode-style problem solving and data structures, with the later parts feeling harder and less predictable. Even when interviewers were willing to hint, the problems demanded very specific patterns and efficient execution.
In one of the technical rounds, I had a prep guide that emphasized certain graph topics and even very specific material, but the actual question tested a different advanced sweep-line style interval scheduling pattern that wasn’t reflected in what I was sent. When I struggled with that unfamiliar structure, I did get hints, but the explanations didn’t really connect in a way that helped me complete the solution. Time pressure made it worse—near the end, the interviewer shifted into a “do you have questions” moment rather than letting me finish.
> 1 year
Average Positive Toronto, ON
My experience was smoother structurally, but the evaluation approach didn’t always feel like it matched what the role was supposed to require. I start…
> 1 year
Average Positive Waterloo, ON
After a quick recruiter call, I did a CodeSignal OA that lasted about 70 minutes, followed by a roughly three-hour block of back-to-back interviews: t…
Unlock every Full Stack Engineer interview experience
