The most comprehensive bank Interview Answer Review tooling available online.

During my early days at Teradata in 2015, I received critical feedback from my manager and colleagues that, although I had strong technical skills, I wasn't very vocal in expressing my opinions during discussions. I initially found this feedback difficult to accept because I believed that my work alone should be enough to communicate my value.  The task was to enhance my communication skills, particularly during team discussions and design reviews, to ensure that my thoughts and ideas were being heard and valued, rather than relying solely on the quality of my technical work.  Taking the feedback to heart, I made a concerted effort to prepare thoroughly for design discussions and technical meetings. I started to actively participate by sharing my opinions on the designs, asking questions to gain clarity, and offering my technical insights. Additionally, I sought feedback from my colleagues to better understand how I could communicate more effectively in these settings.  By consistently engaging in discussions, I found that my opinions were appreciated and valued, which led to more productive conversations and collaborations. This not only helped me build stronger relationships with my teammates but also improved my overall presence in the team. Over time, I became more confident in expressing my ideas and saw growth in my ability to communicate complex technical concepts more clearly and effectively.

One project i'm proud of is my internship project which was a full stack project where i had the chance to create a prototype of a template manager , storing the data into a cassandra database, alongside using springboot and java to work on the module structure and life of the project, I then used js and react for UI. This prototype was then deployed and is now being used by internal payment team at jpmc, instead of going to search every resource, i store all the templates in one template manager and they can know just search the nav bar and get the exact template they need. I'm proud of this project not only because it was my first real project using the new languages and frameworks i was learning during internship but it also gave me the confidence of knowing and seeing that I can do this even though i dont have a degree in this field!

During final stages of testing upgraded version of core banking applications, we encountered a defect which required resolution from development team. After dev deployed the defect, I had very limited time to thoroughly retest and perform regression.

My task was to perform retesting and make sure there are no major defects after the release.

After resolution, based on my prior knowledge of the apps I grouped those testcases that had a potential impact to run automation regression to speed up the testing. While I manually tested the defects with some edge case scenarios. 

I kept the cross functional team updated about the testing progress and the risk involved if testing wasn't completed on time. 

But, I was able to mitigate the risk of not completing the testing on time and major risk of unexpected issues with the help to prior knowledge and proactive communication.

Thus, I learnt from this incident to carefully strategizing the situation and collaborative approach can help to mitigate risks.

I look after our email platform and our existing solution wasn't flexible enough to handle targeted messages at scale. We were missing an opportunity with users to send personalised messages at the right time to help increase engagement. I embarked on a project to implement a new marketing automation software. This project required alignment across our product, data, retail, security and legal teams. I spent time researching the availble tools in the marketing and workshopping requirements with relevant stakeholders, we created an RFP and sent to a number of suppliers. Each round of the RFP I assigned a score to the company and gathered feedback from stakeholders. This ensured the decision making process was fair and we had strong evidence when sharing the business case to senior leadership.

Once we decided on the supplier, I was responsible for implementing the tool which required support across various teams within the business. Implementing something cross-functionally

Success could be measured in multiple different factors. An engineer or a resource would be performing very well in the team, stupendous technically but their relationship with the team should also be desirable. They should be open to collaborate, have good relationship, trust with the team, help cross functional team for collaborating with multiple business teams. Should be able to understand the problem providing right solution at right time, mentoring others in the team and always posses the ability to communicate with at most clarity. 

All of this is a 360 degree feedback that one could be considered successful working in an organisation.

Have a curious mind and approach with understanding. Talk to the person 1x1, see what's up and go from there.