The most comprehensive bank Interview Answer Review tooling available online.

I was working on a high stake project with very high visibility from my senior management.

Me and my manager were thinking of can we leverage the quality of the development using help from QA team. He wanted to keep the QA team separate. His point of view was that a separate team would keep clear focus for the team and they would focus on finding more customer facing bugs. I thought that we should have QA embedded in the scrum team as that would help in easier collaboration and quicker bug fixes plus this is a more efficient way. Though I understood his point of view I always believed that in QA embedded inside the scrum team. I went back had a thought to measure the merits and demerits of the proposals. I put down in a slide the merits and demerits of each. Merit from having a separate team, clear focus and better filtering of quality, demerits less collaboration with development team. I then proposed that the QA engineers attend the calls of dev teams but keep a separate QA board for their tasks. This will give clarity of what bugs they find, what test scenarios they create and finally the metrics to measure the bugs reported per development. My boss and I both agreed as it solved the problems of each proposals

My favourite research method is user interviews. The circumstance it would be best applied in is the discovery phase of a product. When you are trying to gain as much insight into the users and the context of where and how they would use the product. The pros of using this methodology, is since it is generative in nature, you gain a lot of rich data on the users and the context of the product use. This research method can be unstructured giving the interviewer complete freedom on how the interview is shaped or semi structured, giving the interviewer more control in the questions asked and the insights discovered. A con of using this methodology is that since it is generative in nature, unless the interviewer is focused, the interview can get away from them, leading to an information dump from the user. This could lead to waste of time and a lot of unrelevant data.

I try to understand their point of view and be open to new ideas. If I listen without being defensive I know  the other party will also listen. That way we can take the best idea from both and come up with great solution.

At my previous role, I was leading a fraud detection AI model deployment for a financial services client. The model aimed to reduce fraudulent transactions by 25% while maintaining a low false positive rate.

I was confident in the model’s performance in the test environment, but when we deployed it in production, we noticed an unexpected spike in false positives. Transactions flagged as fraudulent were legitimate, causing disruptions for customers and increasing manual review work. To resolve this, I:

1. Investigated the issue by comparing training and production data.

2. Identified data drift—the model was trained on historical data, but recent transaction patterns had changed.

3. Worked with data engineers to implement real-time data monitoring.

4. Retrained the model with up-to-date data and adjusted hyperparameters to improve generalization.

This fix reduced false positives by 25%, improved fraud detection accuracy, and ultimately saved $500M in operational savings across multiple initiatives. This experience taught me the importance of continuous model monitoring and proactively accounting for data drift. Now, I always incorporate data validation pipelines and feedback loops into AI deployments to prevent similar issues.

As my last semester as a system engineer student, I went above and beyond on time management of the time of the team and mine, this was on my thesis as student. while we where a team of 4 members, one of our members and I had one of our parents fighting cancer, so we needed to do time management to work in the project and have a correct time management of personal and work time. What I did was stated my focus, helped my companion doing the same noticing in what of the project we where helping the most and focus on that on my case the SQL queries & documentation of the project. Propose the solution to the other members, while also covering more and more in the written part of the project, this solution was applied by me, but i also had to cover sometimes my team member, doing what was also his tasks in this case the design of the project processes, most of the UML diagrams, because the situation of his family member worsen and some one needed to pick up the pace of the project and that person was me