Commonwealth Bank Software Engineer interview typically runs 2-4 rounds: recruiter/HR, technical interview, peer interview, management round. Timelines vary from quick to drawn out, with long gaps between rounds in some cases.
$105K
Avg. Base Comp
$176K
Avg. Total Comp
4-5
Typical Rounds
3-6 weeks
Process Length
We’ve seen a consistent pattern at Commonwealth Bank: they care less about flashy problem-solving and more about whether you can explain the basics cleanly under pressure. Across candidate experiences, the questions repeatedly circle back to fundamentals and stack fluency — SOLID principles, cloud concepts, Python data types, C#/React/JavaScript basics, and even simple dictionary-based string counting. In several cases, the technical bar wasn’t about inventing an elegant algorithm; it was about showing you understand the tools and can reason through them without hand-waving.
A recurring theme is that the bank also weighs communication very heavily. Multiple candidates reported STAR-style behavioral probing, case-study style prompts, and long stretches spent clarifying scope or walking through prior work. Even when the role was software engineering, interviewers wanted to hear how candidates framed past projects, handled ambiguity, and explained decisions. That matters especially here because the process can feel uneven: some candidates described rapid-fire technical grilling, while others got a more conversational, theory-led discussion. In both versions, the people who did best were the ones who could stay structured and precise.
We’ve also noticed that the non-obvious make-or-break factor is how well you match the interviewer’s expectations in the moment. One candidate was rejected immediately after answering everything they were asked, while another described a design prompt that felt underdefined and misaligned. That tells us the process can be sensitive to judgment calls, not just correctness. For Commonwealth Bank, the strongest signal is a candidate who can keep answers grounded, practical, and easy to follow when the conversation shifts quickly between coding, architecture, and experience-based questions.
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 Commonwealth Bank process.
The process started with a short 15-minute phone call that mixed behavioral and technical questions, and then moved into a coding interview. The coding round was very much LeetCode style and had four questions that ramped up from easiest to hardest, with no AI allowed. That part felt straightforward in format but still time-pressured because you had to keep moving through the set rather than spending too long on any one problem. After that, I had a peer interview and then a management round that included a task. The gaps between rounds were long, which made the whole process feel drawn out.
What stood out most was how much they leaned on STAR-style behavioral questions. They wanted case studies from prior marketing agencies and work, so even though the role was software engineering, a lot of the conversation was about how I handled situations in past teams and projects. The basics also came up early, like telling them about myself and walking through my role and responsibilities. Overall, the interviews felt less like a pure technical screen and more like a mix of coding, structured behavioral questions, and a task-based discussion with management. I didn’t get an offer in the end, but the process made it clear they cared a lot about communication and how you frame past experience, not just whether you can code on the spot. If I were doing it again, I’d prepare concise STAR stories and be ready for a coding round that starts easy and gets harder quickly.
Prep tip from this candidate
Prepare STAR-format stories from past projects, especially examples you can adapt into case-study style answers, since they asked for that repeatedly. Also practice a four-question LeetCode-style coding session where the problems ramp up in difficulty and you have to work without AI support.
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 Commonwealth Bank
What do you tell an interviewer when they ask you what your strengths and weaknesses are?
| Question | |
|---|---|
| Pool Matching | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Bagging vs Boosting | |
| Prime to N | |
| String Shift | |
| Comments Histogram | |
| Maximum Profit | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Cumulative Distribution | |
| Rectangle Overlap | |
| P-value to a Layman | |
| Google Maps Improvement | |
| Monthly Customer Report | |
| Slacking Employees Salaries | |
| Over-Budget Projects | |
| Hurdles In Data Projects | |
| Top 3 Users | |
| Sum to N | |
| Size of Joins | |
| Over 100 Dollars |
Synthesized from candidate reports. Individual experiences may vary.
The process often starts with a short phone call with HR or a recruiter. This round mixes basic behavioral questions with light technical screening, such as introducing yourself, walking through your background, and answering a few fundamentals about your experience.
The first technical round can vary by team, but it is usually focused on fundamentals rather than deep system design. Candidates reported questions on SOLID principles, cloud basics, Python data types, ETL, SQL, data warehousing, and simple coding tasks like counting character frequencies in a string.
Some candidates move into a dedicated coding round with LeetCode-style problems. One experience included four questions that increased in difficulty from easiest to hardest, with no AI allowed and a time-pressured format that required moving quickly through the set.
After the coding round, candidates may meet with a peer engineer. This stage appears to lean heavily on STAR-style behavioral questions and discussion of past projects, team situations, and how you communicate your experience.
The final interview is typically with a hiring manager or management panel and may include a task or case discussion. Candidates described this as a mix of behavioral questions, project discussion, and task-based evaluation, with a strong emphasis on communication and structured examples from prior work.