Real, anonymous reports from people who interviewed for Software Engineer at RBC, newest first and distilled into what to expect across the loop.
My process was noticeably focused on real engineering-style discussion rather than a long sequence of repeated coding tests. I went through two interview rounds total. The first one centered on building a small feature in Java and Angular end to end, and the second round shifted into system design where I had to talk through past projects and how I’d optimize them.
After a recruiter-style step, I ended up with an online assessment that was proctored and had four LeetCode-style questions. They felt like a mix—some were straightforward, and at least one was harder (medium to hard territory), which made me pace myself rather than try to rush.
Candidates typically start with an online coding assessment featuring 4-5 LeetCode-style questions, with varying difficulty levels. The assessment serves as a key filter before moving on to subsequent interview rounds.
Most candidates experience a strong emphasis on behavioral interviews, focusing on past projects and experiences rather than extensive live coding. These interviews often involve discussing how candidates handled specific situations and their fit for the role.
Technical interviews often include discussions about candidates' past work, system design, and specific technologies relevant to the role, rather than traditional coding challenges. Candidates are expected to explain their thought processes and decisions clearly.
The interview process is generally structured with a clear sequence, starting from an initial recruiter call to assessments and multiple interview rounds. However, candidates noted that the timeline can be lengthy, leading to uncertainty and delays in feedback.
Candidates report a mix of average to above-average difficulty in interviews, with some experiencing high-pressure situations, especially in panel interviews. The overall vibe can vary from relaxed to formal, impacting candidate comfort levels.
Many candidates expressed frustration with the lack of timely feedback and closure after interviews, often experiencing long waits without updates. This aspect significantly impacted their overall impression of the interview experience.
