I started with resume submission, and once my application passed, I was pushed into an online assessment. The format varied a bit, but it consistently mixed multiple coding problems with a cognitive/IQ-style component and a culture-fit questionnaire. After that, the process moved toward the technical interview stage.
My technical round ended up being a pair-programming style exercise with an OOP-flavored prompt. The interview setup emphasized talking through my thinking as I coded, and I was allowed to use AI while working through the implementation. It felt very practical and iteration-focused: I implemented the core classes quickly, then answered follow-up questions that probed how I thought about software engineering basics like life-cycle responsibilities. There was also a strong expectation that I could explain my approach, not just produce code.
4 months ago
Average Positive Canada
My interview process ended up feeling compact and fairly friendly. I went through a coding stage where I lived coded in an online environment with two software engineers, and it was basically LeetCode-style problems. The vibe was that they cared a lot more about how I thought through the work than about getting to a single “perfect” answer.
After the coding round, I had a behavioral recruiter conversation. That part leaned on storytelling and motivation, and it felt less like generic HR questions and more like they wanted me to connect my career choices to my impact. I noticed they let me use AI during the technical work, and the interviewers didn’t treat that as a crutch; it was more about whether I could incorporate the output into a real solution.
4 months ago
Difficult Negative Canada
My process started off in a way that made it feel like it could go either direction: I passed an initial coding challenge focused on an LRU cache. Aft…
5 months ago
Average Positive Canada
My process ran for roughly three weeks and felt very structured from the beginning. It kicked off with an initial cognitive assessment, then moved int…
5 months ago
Easy Positive Montreal, QC
My interview journey was pretty quick and direct. After the online assessment, I moved into a technical/pair programming round, then shortly after int…
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
Initial Assessment & Online Coding
The interview process typically begins with an online assessment that includes coding challenges, cognitive tests, and culture-fit questionnaires. Candidates should prepare for a mix of technical and behavioral evaluations right from the start.
Online assessmentCoding challengesCulture-fit
Pair Programming Technical Round
Candidates will engage in pair programming sessions where they solve coding problems while explaining their thought process. The use of AI tools is encouraged, and interviewers focus on collaboration and reasoning rather than just the final answer.
Pair programmingOOPAI tools
System Design & Technical Deep Dive
For candidates progressing further, expect a system design interview that assesses architectural thinking and the ability to explain technical decisions. This round can be demanding, emphasizing clarity and depth in responses.
System designTechnical deep diveArchitectural thinking
Behavioral & Life Story Interview
A significant part of the process includes a behavioral interview focused on storytelling, where candidates are expected to connect their past experiences to their motivations and impact. This round is less about generic questions and more about personal narrative.
Behavioral interviewStorytellingMotivation
Overall Process Structure & Timeline
The interview process is generally well-structured and can vary in length, with some candidates experiencing a compact timeline while others go through multiple rounds over several weeks. Clarity and pacing are emphasized throughout.
Process structureTimelineClarity
Feedback & Outcome
Candidates often report a lack of detailed feedback after interviews, which can leave them feeling uncertain about their performance. While many find the technical challenges manageable, the overall experience may feel unresolved if not followed by clear communication.