interview prep

1. Why Nedbank?

I want to work at Nedbank because of your philosophy on Risk, the way you want profitable lending, but where the risk is understood, well-priced and controlled.  That long-term approach aligns with how I think about credit.

And more over is mainly because I know one of your graduate programmes managed to raise over 900 thousand to help communities such as Matla Secondary School with their vegetable garden for their feeding scheme. This shows you see social responsibility as more than an obligation but an opportunity to do good.

Why did you apply for the Credit Analyst Graduate Programme?

Credit Risk appeals to me because it’s where analysis directly affects capital allocation. It’s where you understand cash flows, downside risk and structure, and these decisions have real consequences. I love the discipline and Judgement the role requires, especially in a market like South Africa.

1. What do you know about Nedbank’s values, and how do you align with them?

I know the values include Integrity, respect, Accountability, People-centered and client-driven, but the one that stays with me is Accountability. I believe that these core values enforce the opportuity to get my hands dirty in a flat based and learn while taking responsibility

1. Why should we choose you over other graduates?

I believe I should be considered because I bring more than just a technical background. As someone who is already in a graduate program, I am not looking for just a Job, I am looking for an opportunity to learn Nedbanks Credt risk Approach and understand its impact on the baking Industry. I bring the hunger to learn.

1. Tell us about a time you had to analyse information to make a decision.

During a SharePoint project, I was responsible for analysing file shares to support a migration design. I needed accurate information on file sizes, structures, and prerequisites to decide how the migration should be planned. I built a PowerShell script that automatically analysed different file shares and calculated the required information for the design document. Based on this analysis, we were able to make informed decisions on scope, timelines, and migration approach, which reduced errors and saved time during planning.

• How can my background help me?

• As an automation engineer, I’m trained to question data quality and logic, which is critical when assessing credit risk.

1. Describe a situation where you had limited information but still had to act.

In my final year, I was leading a group project with ten students, but after the proposal stage most of the team deregistered, leaving me with very limited resources. I still had to deliver a complete project within the deadline, largely on my own. I reassessed the scope, prioritised the most important parts, and taught myself the Python libraries needed to complete the work. When I realised the original timeline was no longer realistic, I documented the risks and proactively discussed a revised plan with my lecturer. As a result, the project was completed to an acceptable standard after an approved extension, and I learned the importance of taking ownership, making decisions with limited information, and communicating risks early.

1. Describe a situation where you had limited information but still had to act.

I worked on an Endpoint Management and Security project where we were deploying baseline Intune policies across the organisation. I was responsible for automating the deployment using PowerShell, but the senior colleague I would normally shadow was on leave, and the deadline still stood. I reviewed existing documentation, researched Intune automation best practices, and tested the script in a controlled environment before deployment. I also documented the full process for future use. As a result, the policies were deployed successfully and on time, my documentation became a reference for the team, and I was recognised for working independently under uncertainty.

1. Tell us about a time you identified a risk and how you handled it.

During a Microsoft Defender and Exchange Online project, I was asked to review a client’s tenant setup to identify any security or performance risks. While analysing the email security settings, I found an SPF configuration error that could affect email delivery and increase security risk. I documented the issue, explained its impact in simple terms, and outlined the steps needed to fix it. As a result, the client addressed the risk, expanded their budget to cover the fix, and I received recognition as a graduate for adding value.

1. How do you approach problem-solving when the answer isn’t obvious?

"When the answer isn’t obvious, I follow a structured approach.

First, I clearly define the problem and gather all the information I can. Then, I break it into smaller parts, research possible solutions, and test them in a controlled way.

I also document what works and what doesn’t so I can learn from it. For e This approach helped me solve the problem effectively and minimise risk.”

1. Tell us about a time you had to learn something quickly.

• During a company-wide data migration from file shares to SharePoint, we discovered that not all files could be migrated at once using the standard tool. With the go-live deadline only days away, I needed to quickly build a PowerShell-based solution to complete the migration reliably. I taught myself how to structure CSV mapping files, understood SharePoint library logic, and automated the migration using PowerShell. I validated permissions and escalated complex issues to senior architects to manage risk. As a result, the migration was completed successfully before go-live, the script was stored in our DevOps repository for reuse, and I was recognised for delivering under pressure.

• Strengths

• My biggest strength is adaptability, whether learning a new tool at work or the measures of credit risk, I had to learn quickly and under pressure, so I am very comfortable being uncomfortable.

• Coming from a background of Mathematics and Computer Sciences, I was wired to solve complex problems into logical solutions is solving problems.

• Weakness

• When working on projects, I tend to be too detail-oriented, which affects my delivery time, and I have been working on this by dividing my work into time intervals so that I can always deliver the key deliverables.

• I have always had problems communicating my solutions to non-technical people, but by being in consulting, I was given the opportunity to learn how to bridge the gap between the Technical side and the business side.

1. Where do you see yourself in 5 years?

I see myself as a senior Credit Analyst here at Nedbank, and as someone new graduates can come to shadow and not because of the position I will be in, but because of the skills I would have started as a graduate myself. I am not sure if I want to continue through the CFA, MBA or Master’s in Finance.

1. Tell us about a time you worked in a team with different personalities.

• I worked in a team with very different personalities, including someone who preferred to take control of most decisions. I stayed focused on my responsibilities, communicated clearly, and kept collaboration professional rather than personal. As a result, the team delivered successfully, and I learned how to work effectively with strong personalities.

1. Describe a situation where you had to explain something complex to others.

Situation:
While working with a client, I needed to explain how file and SharePoint permissions work, as there was confusion around access levels and security risks.

Task:
My role was to help non-technical stakeholders understand how permissions are deployed and managed so they could make informed decisions.

Action:
I used a simple file-cabinet analogy, comparing folders to drawers and permissions to keys, to explain inheritance, access levels, and why least-privilege matters. I tailored the explanation to the client’s level of technical understanding and encouraged questions.

Result:
The client clearly understood how permissions worked, approved the correct access structure, and avoided misconfigurations that could have led to security or data-leak risks.

1. How do you handle conflict in a team?

I see conflict as unavoidable in a workplace, especially when people care about outcomes. When it arises, I focus first on understanding the other person’s perspective and separating the issue from the individual. I address concerns early, communicate calmly using facts, and work toward a solution that aligns with the team’s objective rather than personal preferences.

1. What do you hope to achieve in your first 90 days of the program?

• First 30 days: I would focus on understanding the firm’s credit risk framework, internal rating models, key risk metrics (PD, LGD, EAD), and the systems and data used for credit decisions.

• Days 31–60: I would begin supporting live credit assessments, monitoring portfolio risk trends, and applying the models and policies to real exposures with guidance from the team.

• Days 61–90: I aim to work more independently, contribute insights to credit reviews, and identify at least one area where risk analysis, reporting, or process efficiency can be improved.

20: Tell us about a time you worked under pressure or tight deadlines.

Situation:
During my honours year, I was under constant pressure balancing my own studies, attending classes, seeing my supervisor, working as a Lecturing Assistant, attending departmental meetings, and going to interviews.

Task:
I needed to manage all these responsibilities without falling behind on any of them.

Action:
I developed a strict planning routine, scheduling tasks the day before and prioritising critical deadlines, which helped me stay organised and ahead.

Result:
I was able to meet all my academic and work commitments on time, maintained high performance, and learned how to manage multiple responsibilities effectively under pressure.

1. Current Events and How They Can Help Nedbank.

The current South African rates are high, so that’s causing the rand to gain strength against the USD, and this causes investors to have more confidence in this. And it helps the credit risk team at Nedbank to keep interest rates stable, which means lending won’t be expensive.

But its going to be bad for exporters that uses rand

Why are you leaving you current Job?

I’m leaving my current role because it’s focused on IT delivery, while my long-term career goal is in credit analysis. Through my studies and exposure to risk and decision-making, I realised I’m more interested in analysing information, understanding risk, and supporting lending decisions. I’ve gained strong analytical and problem-solving skills in IT, and I now want to apply those skills in a credit analyst role where they align better with my career direction.