My process started with a behavioral-style screen, but it quickly turned into a deeper dive on my resume and the way I’d implemented past applications and products. I spent a lot of time explaining what I’d done personally, how the pieces fit together, and the specific technical skills I’d used. They also asked practical logistics questions around things like legal status and whether I could handle on-call, plus how I’d worked with people across different countries or time zones.
On the technical side, I ran into a mix of Java-focused questions and database-related topics. There were concept checks (including core Java ideas and SQL), plus a coding-style problem about strings where I had to reason through something like the longest substring. The interviews felt like they wanted both concentration and clear communication, and when I got to the later conversations, there was more pressure to go deep on projects and describe the subtopics accurately.
> 1 year
Average Positive Toronto, ON
After a recruiter-style chat, I had about a week pass before another screen where the conversation centered mostly on my background. They walked through my resume and asked me to talk through my experience and what I’d built, and I could feel they wanted specifics on the technical side rather than broad statements. A couple of “why Sun Life” and “why software” questions came up too, and the focus stayed on how I applied my past work instead of chasing abstract theory.
What surprised me was how light the technical questioning was. In the round I did, the technical prompts were basically answerable in a sentence or two, and they didn’t press deeply. I also got some context about the team and what they did, which helped frame the expectations. Overall it felt pretty straightforward, and the whole thing wrapped up on a fast turnaround after the final response came back a couple of weeks later.
> 1 year
Average Positive Vellore
After initial shortlisting, my process moved into an online remote coding round, followed by a physical group discussion with around 8–10 candidates. …
> 1 year
Negative India
A recruiter booked me into a weekday slot and told me it would be a quick technical round—about 30 minutes. The screen ran over Zoom and started stron…
> 1 year
Easy Positive Toronto, ON
I started with an HR call, and then moved into back-to-back conversations with a hiring manager and the technical lead. Those later interviews felt pr…
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
Behavioral & Background Screening
The interview process typically begins with a behavioral-style screen focused on the candidate's resume and past projects, emphasizing specific technical contributions and experiences. Candidates should prepare to discuss their motivations for applying and their work history in detail.
BehavioralResumeMotivation
Technical Fundamentals
Candidates can expect a focus on foundational technical concepts, including core Java, OOP principles, and basic SQL. The technical questions are generally straightforward and assess familiarity with essential programming and database skills rather than complex algorithms.
JavaOOPSQL
Coding Assessments
Some candidates may encounter a remote coding round, which tests practical coding skills through specific problems, such as string manipulation or API concepts. It's important to be prepared for both coding exercises and discussions about coding practices.
CodingAPIsString manipulation
Interview Structure & Format
The interview process can vary in structure, with some candidates experiencing a mix of remote and in-person interviews, including group discussions and one-on-one technical interviews. This variety is designed to assess different dimensions of a candidate's capabilities.
Interview structureGroup discussionOne-on-one
Interview Atmosphere
Candidates have reported mixed experiences regarding the interview atmosphere, with some finding it friendly and others feeling pressure or dismissiveness from interviewers. It's advisable to remain calm and communicate clearly, regardless of the interview tone.
AtmosphereCommunicationPressure
Timeline & Follow-up
The overall timeline for feedback can vary, with some candidates experiencing delays after the final interview. It's common for candidates to wait a few weeks before receiving any updates from HR, so patience is essential during this period.