RBC Software Engineer interview typically runs 3-4 rounds: online assessment, phone screen, behavioral, onsite. The process usually takes a few weeks and is resume-driven and conversational.
$98K
Avg. Base Comp
$107K
Avg. Total Comp
3-5
Typical Rounds
2-4 weeks
Process Length
We've seen a consistent pattern at RBC: the strongest candidates are the ones who can make their resume feel specific and defensible. Multiple candidates reported that interviewers spent far more time on past projects, tech stack choices, and ownership than on deep algorithmic puzzles. Even when coding showed up, it was usually easy-to-medium and often paired with object-oriented thinking or practical implementation details. That tells us RBC is screening for engineers who can explain what they built, why they built it that way, and what they personally contributed without drifting into vague team-level language.
A recurring theme is that RBC also cares about communication under low-to-moderate technical pressure. Candidates described friendly, conversational interviewers who still pressed on cloud familiarity, Android principles, system design tradeoffs, and scenario-based judgment. We also noticed several “Why RBC?” prompts and questions about motivation, which suggests they want a clear reason for joining beyond generic interest in finance. The non-obvious make-or-break factor here is not brilliance on a hard problem; it’s whether your answers sound grounded in real work and whether you can connect your experience to the role in a way that feels credible and calm.
Synthetized from 4 candidates 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
Create top_ads with the top 3 ads and return the row counts for inner, left, right, and cross joins with ads
| Question | |
|---|---|
| Why Do You Want to Work With Us | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Subscription Overlap | |
| Find the Missing Number | |
| Maximum Profit | |
| Prime to N | |
| Rolling Bank Transactions | |
| Comments Histogram | |
| String Shift | |
| Employee Salaries | |
| Random SQL Sample | |
| Closest SAT Scores | |
| Hurdles In Data Projects | |
| Rectangle Overlap | |
| Find the First Non-Repeating Character in a String | |
| Slacking Employees Salaries | |
| P-value to a Layman | |
| Over 100 Dollars | |
| Scrambled Tickets | |
| Minimum Change | |
| Cumulative Distribution | |
| Level Of Rain Water In 2D Terrain | |
| Sum to N | |
| Append Frequency | |
| Google Maps Improvement |
Synthesized from candidate reports. Individual experiences may vary.
Candidates typically start with a coding assessment on HackerRank or CodeSignal. The OA is usually LeetCode-style, with a mix of easy and medium questions, though some candidates saw a harder question as well. Time pressure is a theme, so speed and accuracy matter more than advanced algorithms.
The next step is usually a phone or Zoom interview with one or two interviewers, sometimes from other teams or senior engineers. This round is heavily focused on your resume, past projects, technologies you've used, and how clearly you can explain your own work, with only light technical questioning.
Some candidates also had a separate behavioral or manager-style round. Questions were standard behavioral prompts such as strengths, weaknesses, working with different people, handling change, and scenario-based judgment questions, with an emphasis on fit and communication.
For some loops, the technical interview went beyond resume discussion into an easy LeetCode-style question plus system design. Interviewers also dug into why you want RBC, your favorite project, and tradeoffs in your past work, so being able to defend your decisions was important.
The final stage could be an onsite in Toronto or a broader final round that combined behavioral, coding in Java, and presentation-style discussion. The coding was described as easy-level and often included object-oriented design style coding, while the behavioral portion stayed resume-driven and focused on Android principles, project ownership, and past experience.