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.
8 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 Negative Toronto, ON
I applied expecting a software engineering interview that matched a front-end focus, but the process didn’t really reflect that. It dragged out over a…
> 1 year
Average Negative Canada
The recruiter outreach and the early framing set the tone for how I felt about the process. I had a sketchy vibe from the start—there were comments th…
> 1 year
Average Positive Canada
I did a fairly direct interview loop that started with a live technical conversation with a senior engineer. I solved a medium leetcode-style problem …
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Recruiter Interaction
The initial recruiter call is generally straightforward, focusing on background and role fit, but experiences vary widely in engagement and professionalism. Some candidates felt the recruiter was disinterested, while others found the communication efficient and supportive.
RecruiterEngagementInitial Contact
Online Coding Assessment
Candidates typically complete an online coding assessment using platforms like CodeSignal, which includes multiple timed questions focused on data structures and algorithms. The time pressure is often a significant factor, with some candidates feeling it detracted from their ability to demonstrate their skills effectively.
Coding AssessmentTime PressureData Structures
Technical Interview Rounds
The technical interviews often consist of live coding sessions that emphasize practical problem-solving and collaboration, but the difficulty and focus can vary. Some candidates reported a mix of algorithmic questions and system design discussions, with a notable emphasis on backend topics even for frontend roles.
Live CodingAlgorithmsSystem Design
Behavioral Interviews
Behavioral interviews are included in the process, with a focus on cultural fit and values alignment, but the depth and engagement of these conversations can vary. Candidates appreciated when interviewers were genuinely interested in their experiences, but some felt the behavioral rounds were scripted and lacked engagement.
BehavioralCultural FitValues
Overall Process Experience
Candidates' overall experiences varied from feeling well-structured and organized to chaotic and inconsistent, with some expressing frustration over mismatches between role expectations and interview content. The speed of the process also varied, with some candidates receiving quick feedback and others experiencing delays.
Process StructureFeedback SpeedCandidate Experience
Outcome and Feedback
Rejections were common, and many candidates expressed dissatisfaction with the lack of clear feedback on their performance, leaving them uncertain about what could have been improved. Some candidates felt that the evaluation criteria were not transparent, which contributed to a negative overall impression.