After the online screening, I got sent an OA that felt brutally paced. The whole thing took about 70 minutes and opened with 7 multiple-choice questions that were manageable. After that came a single LeetCode-style medium, then two ML-focused coding tasks that had “from scratch” vibes.
I could handle the early questions, but the coding section ate most of my time. I spent close to 50 minutes battling tool constraints rather than making real progress, and that mismatch threw me off the most. By the end, it was clear I was running out of runway, and I didn’t feel confident that I’d landed the hardest parts the way they expected. I didn’t get an offer.
3 months ago
Average Positive Toronto, ON
My process started with an OA that mixed formats. It began with multiple-choice questions, then shifted into LeetCode-style problems centered on ML algorithms. After I finished the coding portion, I moved into a DS/A interview that started with resume questions and then turned into a more structured technical discussion.
The DS/A question I got was graph-based and split into multiple parts, which made the round feel like it had several checkpoints instead of a single problem statement. The difficulty felt in the average range overall, and I remember thinking I understood what they wanted conceptually, even though the graph breakouts required careful step-by-step reasoning. I ended up not receiving an offer.
4 months ago
Average Positive Canada
My first real evaluation was an online coding assessment that blended basics with ML. The problems included straightforward data-structure work like s…
6 months ago
Difficult Positive United States
I had a technical round that centered on SQL and Python, plus an experimental case study all rolled into a roughly one-hour block. The session include…
6 months ago
Difficult Positive United States
My OA was difficult from the start, and I could feel it escalating as it went on. There were some quick ML questions, then a neural-network forward in…
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Online Assessment (OA)
The online assessment typically includes multiple-choice questions, LeetCode-style coding problems, and machine learning tasks, often under tight time constraints. Candidates noted that the transition from basic questions to more complex ML coding tasks can be abrupt and challenging.
Online AssessmentLeetCodeMachine Learning
Technical Interviews
Technical interviews often cover a mix of SQL, Python coding, and machine learning concepts, with a focus on practical application and problem-solving. Candidates reported a variety of formats, including live coding and case studies, which can shift rapidly between topics.
SQLPythonTechnical Interview
Behavioral & Values Assessment
Behavioral interviews are typically structured around candidates' past experiences and collaboration skills, with a focus on storytelling rather than just technical skills. Candidates felt that these rounds often emphasized cultural fit and teamwork.
BehavioralCultural FitCollaboration
Difficulty & Pressure
Candidates frequently described the overall difficulty of the interview process as high, with significant pressure during both the OA and technical interviews. Many felt that the pacing and volume of questions could lead to a sense of being overwhelmed.
DifficultyPressurePacing
Recruiter Communication & Process Flow
Experiences with recruiter communication varied, with some candidates noting delays that affected their overall experience. A clear and responsive communication style was appreciated, while any lack of clarity could add to the stress of the process.
Recruiter CommunicationProcess FlowTiming
What Candidates Wish They'd Done
Many candidates reflected on the importance of practicing under timed conditions and familiarizing themselves with both coding and ML concepts to better handle the pressure of the assessments. Some wished they had focused more on the practical application of ML algorithms.