RBC Software Engineer interview typically runs 3–4 rounds: online assessment, technical screen, behavioral, and optional onsite. The process spans a few weeks and is notably resume-driven, emphasizing project explanation over algorithmic depth.
$151K
Avg. Base Comp
$200K
Avg. Total Comp
3-5
Typical Rounds
2-5 weeks
Process Length
We've seen a consistent pattern across RBC software engineering candidates: the ability to defend your own resume in technical detail matters far more here than grinding hard algorithmic problems. Multiple candidates reported that interviewers spent the bulk of their time on past projects, ownership, and tech stack choices — not on LeetCode-hard puzzles. When coding did appear, it stayed in the easy-to-medium range and often leaned toward object-oriented design and clean implementation rather than pure algorithmic complexity. That signals RBC is screening for engineers who can articulate what they built, why they made specific technical decisions, and what they personally owned without retreating into vague team-level language.
A recurring theme is that the process is broader than a typical SWE loop, and this catches candidates off guard. We've seen rounds that include group presentations, scenario-based judgment questions, and system design conversations sitting alongside the coding screen — all in the same process. Cloud familiarity, preferred language choices, and "Why RBC?" prompts came up repeatedly, suggesting the team is evaluating cultural fit and genuine motivation alongside technical depth. It's also worth noting that the process varies meaningfully by team and service line; candidates interviewing closer to capital markets or infrastructure roles reported heavier system design emphasis, while others described almost entirely behavioral and resume-driven conversations.
The non-obvious make-or-break factor here is how grounded and calm you sound when explaining real work, not whether you can solve a hard problem under pressure. Candidates who received offers consistently described interviewers as conversational and friendly — but that relaxed tone can lull you into underpreparing the resume deep dive. The candidates who didn't advance often cited being caught off guard by the breadth of the process or by follow-up questions on projects they hadn't revisited recently.
Synthesized from 4 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Rbc process.
Mine was a pretty straightforward process overall, but it still had a couple of different formats. It started with an online assessment on HackerRank, then I moved to a 30 minute Zoom interview that was mostly about the projects on my resume. That round felt more like a deep dive into what I had actually built and what parts I owned, rather than anything especially algorithm-heavy. After that, I had an onsite in Toronto that combined behavioural and coding in Java. The coding portion was not leetcode-hard at all, more like easy-level problem solving with some object-oriented design style coding mixed in, so the bigger challenge was explaining my thinking clearly while keeping the code clean.
The behavioural side was very resume-driven too. I was asked to explain the principles of Android development and talk through my experience, and there was a lot of digging into past projects. In the earlier manager-style round, the questions were pretty standard interview questions like what I do outside of work and what my biggest weakness is, plus some scenario-based questions about what I would do in a given situation. One thing that stood out was how much they cared about how I talked through my background, not just whether I could solve a coding prompt. The process felt simple and not overly technical, but you do need to be ready to defend everything on your resume and answer basic behavioural questions without sounding rehearsed. I ended up getting the offer after following up, so I’d say the process was manageable if you prepare for both the resume deep dive and a light Java/OOD coding round.
Prep tip from this candidate
Be ready to walk through every project on your resume in detail, especially Android-related work and the principles behind it. Also practice a light Java/OOD coding exercise, since the coding round sounded closer to easy interview coding than leetcode-style grinding.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Rbc
Write a query to get the total three-day rolling average for deposits by day
| Question | |
|---|---|
| Size of Joins | |
| Hurdles In Data Projects | |
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Employee Salaries | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Google Maps Improvement | |
| Total Spent on Products | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically begin with a coding assessment on HackerRank or CodeSignal consisting of LeetCode-style problems ranging from easy to hard. Most candidates saw two easy and one or two medium/hard questions within a tight time limit, so pacing and avoiding over-polishing a single solution are critical. Some early-career tracks may also include a HireVue video screen at this stage depending on team and geography.
Some candidates received a short questionnaire about their technical interests and background before the main interview rounds. This appeared to help interviewers tailor the conversation toward the candidate's actual experience and stack rather than generic prompts.
The next step is typically a phone or Zoom interview with one or two interviewers, sometimes senior engineers or members from other teams. This round is heavily focused on walking through your resume, past projects, and technologies you have used, with light technical questioning and general prompts such as cloud experience, preferred language, and what you know about relevant platforms.
Many candidates had a separate behavioral or manager-style round covering standard prompts such as strengths, weaknesses, working with diverse teams, handling change, and scenario-based judgment questions. The emphasis was on fit, communication style, and whether candidates could answer naturally without sounding overly rehearsed.
For some loops, a dedicated technical round included an easy LeetCode-style question plus a system design discussion, with no live coding pressure but significant grilling on design tradeoffs and past project decisions. Interviewers also asked motivational questions such as why RBC and what your favorite project was, so being able to defend your own work and articulate interest in the role was important.
The final stage could be an onsite in Toronto or a broader virtual final round combining behavioral, coding in Java with object-oriented design elements, and in some cases a group presentation or scenario-based communication exercise. Coding difficulty was generally easy-level, but candidates were expected to explain their thinking clearly, defend everything on their resume, and demonstrate ownership of past work. Note that the exact format varies by team, service line, level, and geography.
