After a recruiter-style conversation, I ended up with a technical screen that felt like a Java-and-platform check more than anything. It included Java-style questions around core concepts, plus some SQL and a bit of database/DBMS thinking. The one problem that stood out was a string question about finding the longest substring, and it made me focus hard on clarity and step-by-step reasoning. Alongside that, they touched on general OS and DBMS topics, so it wasn’t just pure coding.
What really shaped the experience was how much time I spent on my own background. I had to talk about myself and go deep on one project, and the follow-ups pulled in multiple subtopics from what I’d described. The overall difficulty felt average, but it required tighter concentration and strong communication throughout.
9 months ago
Easy Positive Toronto, ON
My process started with something pretty low-pressure. I had an initial round that was mostly behavioral, and it stayed grounded in basics like AWS. It didn’t feel heavy on tricky questions—overall it was easy, and the main theme was that they expected familiarity with AWS fundamentals.
After that, I went through a more in-depth discussion of my professional experiences and the projects I’d worked on. They wanted me to tie my stories to foundational technical and conceptual questions, so I ended up walking through how I’d applied things rather than just listing tools. The format felt like a back-and-forth: tell me about your background, then answer questions that demonstrated analytical thinking and practical problem-solving.
11 months ago
Average Neutral Canada
My experience didn’t feel smooth from the start. The overall tone during the interviews came across unfriendly, and a couple of interviewers seemed di…
> 1 year
Average Neutral Boston, MA
I had a phone screen that moved quickly, and I expected it to be a straightforward check-in. I remember getting asked about my year level, and when I …
> 1 year
Average Positive Canada
The first step was focused on my resume. During the interview, they asked me about experience I had listed, and I had to explain my past work and proj…
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 HR & Behavioral Round
The interview process typically begins with an HR or recruiter call focused on the candidate's resume and background, often including behavioral questions that assess fit and familiarity with basic concepts like AWS or project experience. Candidates should prepare to discuss their past work in detail and articulate their contributions clearly.
HR roundBehavioralResume discussion
Technical Screening
Candidates can expect a technical screening that includes questions on core programming concepts, particularly in Java, as well as SQL and database management topics. It's important to demonstrate clarity in problem-solving and reasoning during this round.
Technical screenJavaSQL
Focus on Personal Contributions
Throughout the interviews, there is a strong emphasis on individual contributions to projects, requiring candidates to explain their specific roles and the technical skills they utilized. Be prepared to justify your experience and connect it to the role's requirements.
Personal contributionProject discussionTechnical skills
Multiple Rounds and Formats
The interview process often includes multiple rounds, such as technical interviews, managerial discussions, and HR evaluations, which may vary in format from coding assessments to group discussions. Candidates should be ready to adapt to different interview styles and maintain consistency across rounds.
Multiple roundsInterview formatsAdaptability
Interview Atmosphere and Tone
Candidates have reported mixed experiences regarding the interview atmosphere, with some finding it unfriendly or rushed, which can impact performance. It's advisable to remain composed and focused, regardless of the interviewers' demeanor.
Interview atmosphereToneCommunication
Outcome and Feedback
Many candidates did not receive offers, often citing a lack of clarity in the evaluation process or feeling that their skills were not adequately assessed. It's beneficial to seek feedback post-interview to understand areas for improvement.