After a recruiter call, I moved into a fairly structured sequence. The next step was a technical screen where I worked on LeetCode-style problems—one that felt easy and a couple that were medium—on a coding assessment. A short while later, I went through rounds that mixed deeper discussion with more technical evaluation.
The final leg stood out because it was heavier on the details of what I’d built and how the pieces fit together. I talked through my projects and my familiar tech stack, and the interviewer asked some targeted technical questions. Then, late in the session, I had to solve a LeetCode-style problem at the end, which made the round feel like it built momentum and pressure at the same time.
2 months ago
Average Neutral Canada
My process ended up being much simpler than I expected. It started with a quick behavioral interview that was about 30 minutes, with situational questions that didn’t feel particularly hard. I was told they’d follow up with my application status within a week.
After that, the waiting period stretched out. I didn’t hear back after almost two weeks, so I sent a follow-up email thanking them and asking about timing. That email didn’t get a response either. By the end, I was left without closure, which was honestly the most frustrating part of the whole experience.
2 months ago
Easy Positive Canada
My interview journey started with an online assessment that ended up being the biggest hurdle. I was given a set of LeetCode-style questions in a proc…
3 months ago
Average Positive Canada
I experienced RBC as a pretty light process overall. I started with an online assessment and then moved into a small Zoom interview that mostly revolv…
4 months ago
Average Positive Canada
My path was short and very project-and-structure focused. I only had two interviews total. The first one centered on building a small end-to-end featu…
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
Online Assessment
Candidates typically start with a proctored online assessment featuring LeetCode-style questions, which range from easy to medium difficulty, with some reports mentioning tougher questions that can be challenging under time constraints.
LeetCodeProctoredCoding Assessment
Technical Interviews
Following the assessment, candidates engage in technical interviews that often focus on their past projects, technical skills, and problem-solving abilities, with some interviews including system design discussions or coding exercises.
Many candidates experience behavioral interviews that emphasize their work history, collaboration, and fit within the company culture, with a mix of situational questions and discussions about teamwork and communication.
Behavioral QuestionsCultural FitTeamwork
Interview Structure & Flow
The interview process can vary in structure, with some candidates noting a clear sequence of rounds while others report a more disorganized experience, leading to confusion and uncertainty about the timeline and next steps.
Interview FlowTimelineProcess Clarity
Communication & Follow-Up
Candidates frequently express frustration over slow or lack of communication regarding their application status, with some waiting weeks for updates after interviews, which can add to the overall stress of the process.
CommunicationFollow-UpStatus Updates
Overall Difficulty & Experience
The overall difficulty of the interview process is often described as average, with candidates feeling that while the technical challenges are manageable, the lack of clarity and communication can make the experience feel more intense than it should be.