I first ran into them at a career fair, where they grabbed my resume and pushed me into a quick interview that felt pretty straightforward. A short while later I joined a 60-minute session that mixed behavioral and technical questions, with roughly 20 minutes of behavioral discussion and about 40 minutes focused on the technical side.
The coding part was simple and handled in a joint editor, and I was able to express the solution using pseudocode. The main challenge ended up being clarity rather than difficulty—it's the kind of 2D array problem that didn’t take long once I focused on the right structure.
12 months ago
Easy Negative Toronto, ON
My process started with an HR interview that then turned into a technical and personal interview. I was told to come to their office for the interview, but the logistics were honestly rough because of the public transportation situation in that area.
When I arrived, the interviewer was online anyway since they were based in another country. After the interview, there wasn’t a tour or any team meeting to follow up—everything just ended right after. I also never received clear feedback afterward; even after I sent follow-up emails to the interviewers and HR, I couldn’t get a sense of the result.
> 1 year
Average Negative Thessaloníki, Western Macedonia
My interview journey moved fast and felt structured around checkpoints. I started with a written assessment that included programming questions and a …
> 1 year
Average Positive Israel, TX
This round was over Zoom with a team lead, and the vibe was pretty friendly. The interviewer seemed nice throughout, and I remember being surprised th…
> 1 year
Difficult Positive Canada
I ended up with a single, deep technical round that felt both insightful and challenging. It leaned heavily on Java knowledge, and it didn’t just skim…
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
Interview Structure & Flow
The interview process typically consists of multiple rounds, often starting with a technical assessment followed by technical interviews and concluding with HR discussions. The structure can vary, with some candidates experiencing a seamless flow while others encounter logistical mismatches.
multi-roundtechnical assessmentHR discussion
Technical Focus Areas
Candidates can expect a mix of coding questions, often aligned with LeetCode-style problems, alongside discussions on OOP concepts, system design, and practical applications related to their resume. The technical difficulty is generally moderate, aiming to assess foundational knowledge and problem-solving abilities.
coding questionsOOPsystem design
Behavioral & Fit Interviews
Behavioral interviews are a significant component, focusing on past experiences, work style, and cultural fit. These discussions often precede or follow technical evaluations, emphasizing the importance of interpersonal skills and alignment with company values.
behavioralcultural fitwork style
Communication & Feedback
Candidates have noted varying levels of communication throughout the process, with some experiencing clear feedback while others felt left in the dark post-interview. Timely updates and closure after interviews can significantly impact the overall candidate experience.
communicationfeedbackcandidate experience
Logistical Considerations
Logistics can play a crucial role in the interview experience, with some candidates facing challenges related to in-person versus remote setups. Candidates should be prepared for potential discrepancies in expectations regarding interview formats and locations.
logisticsremote vs in-personinterview format
Overall Candidate Sentiment
While many candidates found the interview process to be structured and manageable, there were also reports of frustration due to lack of follow-up or clarity on outcomes. The overall sentiment varied, with some appreciating the thoroughness while others felt the process could be improved.