Nationwide Building Society Interview Questions
& Process

Applied online with my CV. HR reviewed it and then I had a 2-hour interview. We talked about my CV and experience, then some standard questions. There was a case study where I was given time to read material during the interview and then discuss it with the interviewers. I also had a chance to ask questions. We could take a short break if needed. It was a single interview, not multiple rounds, so it was pretty efficient.

The hiring process was pretty simple. You apply on their website and upload your resume. If they like your application, they'll call you for an initial phone interview. Make sure you ask them questions to get a better understanding of the role, because sometimes the job descriptions aren't super clear. For instance, this job said you'd be giving mortgage advice, but that wasn't actually part of the job.

For this role, you'll need to show your programming skills, how you solve problems, work with others, and if you're keen on tech. Use examples from school, projects, or jobs to show you can adapt and learn new things. They might ask about your coding background, how you team up, deal with changes, your interest in new ideas, and if you're up for moving or working partly from home, to make sure you fit their graduate program. You can ask about what happens after the program, if you'll get a mentor, training, what kind of projects you'll do, and how the company culture is with new ideas, including people, and growing long-term. The whole process starts with sending your CV, then an online check, a video chat, and finally an assessment centre. If you do well, you get into the graduate program with training and mentors, and a shot at a permanent job.

It was a two-step process. A recruiter first reached out to introduce themselves and invite me to the interview process. The first interview involved a coding question similar to LeetCode, but the emphasis was on the thought process, allowing for verbal explanation or pseudocode, alongside general questions about my background. The second interview also included a coding question, more technical questions, and some competency-based questions aligned with their values. I liked that the process was mostly efficient, the interviewers were friendly, and the questions seemed relevant and not overly hard. The initial recruiter was very supportive and seemed willing to make reasonable adjustments for my disability, but I was disappointed that they couldn't offer much beyond extra time. I was also left waiting for nearly three weeks for feedback after following up twice; after the first follow-up a week later, I was told I had good feedback but they were waiting for another candidate to complete their final interview. Overall, it wasn't a bad process and was better than some I've experienced, but it could be improved, especially regarding support for candidates with disabilities and communication, as the end was a bit disappointing.