What candidate reports describe for NAB software engineer interviews: a timed online coding assessment, stack-specific technical rounds, and project, managerial and behavioral conversations.
$103K
Avg. Base Comp
$120K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Most NAB software engineer reports start with a timed online coding assessment, and several name Codility. One candidate called it the real gatekeeping round. Expect three coding problems under a clock. One candidate said timeouts were heavily weighted, so brute force would not pass. Their hardest problem asked them to split an array into three sub-arrays while minimizing the maximum difference. Another scored above 80% on two easy questions and one medium, including a binary string reduction problem. A React candidate described a two-hour proctored assessment aligned to their stack. One candidate also faced a 30-question cloud architecture multiple-choice section with a 67% pass mark.
The technical round follows the team's stack. A Java candidate was asked about OOP, including the diamond problem. Another was asked about ArrayList default capacity, greedy versus dynamic programming, and Dijkstra's algorithm, and was questioned on the design choices in their projects. A React candidate built a live countdown timer and answered questions on Redux middleware, React Portal and useEffect versus useLayoutEffect. A backend candidate worked through Spring Boot custom beans and property loading. One senior candidate implemented a Stack from scratch in Java and fielded REST API and SQL questions. Another senior candidate had a conversational Zoom discussion that touched SQL, Linux basics, joins and triggers.
Later conversations focus on experience and fit. One candidate described a 20-minute HR round using STAR questions. A React candidate had a 90-minute behavioral session. A senior candidate faced a managerial panel focused on past architecture and system design. Outcomes ranged from offers to rejections, and one candidate withdrew after being asked to retake a round about a month later. Round counts are rarely stated, and the reports that describe a full process show three or four stages.
Synthesized from 8 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 National Australia Bank process.
I interviewed at National Australia Bank for a software engineer role and went through four rounds total. The process was well-structured, though I should mention upfront that it took about a month from the final interview to getting an offer decision, so patience is needed at the end.
The first round was technical and focused on questions directly relevant to the role. I was asked about my approach to handling deadline pressure—not just as a technical problem-solving exercise, but as a genuine behavioral question about how I perform under stress and what kind of team member I'd be. It wasn't just about my individual capability; they clearly wanted to see whether I could lift the performance of others around me too. That framing stood out to me. The interviewers were engaged and friendly throughout, which made it easier to think clearly even when the questions got challenging.
After the technical round, I had a conversation with the head of the team. This felt like a deeper culture and vision fit discussion—less about reciting algorithms and more about understanding how I'd actually work within their engineering organization. The final round was with HR, which covered the standard ground on compensation, role expectations, and why I was interested in NAB specifically.
Overall, the interview process felt genuinely thoughtful. They weren't just checking boxes; they were trying to assess both technical chops and how you'd show up as a teammate under pressure. The main thing to know going in is that the timeline from final interview to offer can be long, so don't assume silence means rejection. It just means their decision-making process is slower than some companies.
Prep tip from this candidate
Be ready to discuss how you handle deadline pressure not just as a solo performer, but as someone who elevates the team—that behavioral angle came up early and seemed important to their evaluation. Also prepare for a round with the team lead focused on culture fit and working style, not just technical depth.
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 National Australia Bank
Get the top 3 highest employee salaries by department
| Question | |
|---|---|
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| P-value to a Layman | |
| Rectangle Overlap | |
| Cumulative Distribution | |
| Top 3 Users | |
| Over-Budget Projects | |
| Slacking Employees Salaries | |
| Hurdles In Data Projects | |
| Sum to N |
Synthesized from candidate reports. Individual experiences may vary.
Most reports describe an online coding assessment, usually three problems. Reported difficulty ranges from medium DSA to a mix of two easy and one medium. One candidate said timeouts counted heavily, and a React candidate described a two-hour proctored assessment aligned to their stack. One candidate also reported a 30-question cloud architecture multiple-choice section.
Content depends on the role. Candidates report Java and OOP, Java Collections and data structures, React and Redux, or Spring Boot. Live tasks included a React countdown timer, a Stack implementation in Java and a Spring Boot custom bean. Two senior candidates also mentioned SQL, with one citing REST APIs and another Linux basics.
Several candidates describe talking through past projects and the reasons behind their design decisions. One senior candidate faced a managerial panel of two or three people from the Australian team, followed by a final round with the business and tech head.
One candidate described a roughly 20-minute HR round with STAR-style questions, such as handling a non-performing teammate and responding to critical feedback. A React candidate described a 90-minute behavioral session on experience and problem-solving. Follow-up varied: one candidate heard nothing after being rejected, and another was asked to retake a round about a month later.
