RBC software engineer candidates report an online coding assessment followed by conversational interviews centered on resume projects, behavioral questions and basic technical concepts, with experiences varying by team and level.
$103K
Avg. Base Comp
$120K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates describing RBC software engineering and developer interviews most often mention an online coding assessment followed by a resume-driven conversation. One intern reported four questions in 70 minutes, two easy, one medium and one hard, and found the pacing the main challenge. Another candidate had three LeetCode-style problems on CodeSignal in an hour, and a Developer Amplify candidate started on HackerRank. Others described the assessment as easy to medium.
The live rounds are often conversational. Candidates say interviewers spent much of the time on projects, the tech stack they had used, and questions like "Why RBC?", a mistake you made, an achievement you are proud of, or a time you adapted quickly. Technical questions in these reports tend to be foundational: cloud awareness, your preferred language for a new project, and in one case an easy LeetCode-style problem followed by system design and a resume deep dive, with no live coding.
Expect variation by team. A Developer Amplify candidate described an onsite in Toronto with easy Java and OOD-style coding plus Android questions. Another candidate reported a group interview with a scenario-based presentation. Senior candidates reported Salesforce-specific panels or DevOps tooling questions. Several candidates also mention slow or missing follow-up after interviews. Prepare timed coding practice, a detailed walkthrough of every project on your resume, and a specific, honest answer to why you want RBC.
Synthesized from 22 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.
I went through two rounds for this role. The first was a phone interview with HR, and the question I remember most was an opener asking what the single most important thing they should know about me was. It's a simple prompt, but it set the tone for everything after it. Once I got through that call, I was moved on to a second round with the hiring manager, who was described as a branch manager. That conversation might be in person. I can't tell you what was covered there, and no technical questions came up in my process, so I can't speak to the coding or design side of things. I ended up declining the offer. If you're preparing, the early screening seems to be conversational, so have a clear, concise answer ready for how you'd introduce yourself and what you want the interviewer to know.
Prep tip from this candidate
Have a tight, specific answer ready for the opening HR screen question about what the interviewer should know about you, since that was the question asked in the first round.
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 | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Top 5 Turnover Risk | |
| Payments Received | |
| Total Spent on Products | |
| Maximum Profit | |
| Get Top N Frequent Words | |
| Top 3 Users | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| String Shift | |
| Prime to N | |
| Scrambled Tickets | |
| Comments Histogram | |
| Slacking Employees Salaries | |
| Last Transaction | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a timed online assessment. One intern had four questions in 70 minutes, and another had three LeetCode-style problems in an hour on CodeSignal. Difficulty ranged from easy to hard, so practice pacing across multiple problems.
Some experienced-hire candidates report a recruiter call covering background, the role and salary expectations. Intern reports often go straight from the assessment to an interview, so this step may depend on role and level.
Most reports describe a conversational interview focused on resume projects, tech stack and basic technical questions such as cloud awareness or preferred language. One candidate had an easy LeetCode-type question plus system design. Senior reports mention panels on Salesforce topics or on Python, Terraform and Java coding.
Candidates report behavioral questions about mistakes, achievements, adapting quickly and why RBC. One candidate had an onsite in Toronto combining behavioral questions with light Java coding. Another reported a group scenario presentation, and a senior candidate had a final discussion with leadership. This round may vary by team and level.
