The most comprehensive bank Interview Answer Review tooling available online.

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.

The last conference I attended was the Open Source Security Foundation. As I was leading the Dart & Flutter security program I wanted to learn about the innovations, tooling and services that other open source projects were using.

There were interesting conferences for tooling to sign artifacts with a single command and how the open source community was working in tooling to build, sign and release artifacts in a secure way for everyone using GitHub.

I learned that there were many technical innovations that I could use to speed up the Flutter Security Program, for example implementing secure build workflows using github actions. I also met several people working on similar projects and took the opportunity to share our lessons learned and challenges. Later on the connections with the open source security foundation proved very useful during technical reviews and collaborations.

This is a product which we release recently it would check the recent breaches that happened exploiting certain vulnarability in the recent past and also check the vulnarabilties in the infrastructure and then provide a score based on severity. the higher the severity the higher the chance of getting breached. This was a great hit but two of our customers came back with a specialised request, the wanted to quantify the severity in terms of revenue loss so it would help them prioratize fixes on the infrastructure. This not only required heavy research but also defining the scope as well that where it fits in. The reason it was important to think about this feature because it was a big contract and our company wanted close it before the end of Q2. I had a planning sessions with the stake holders and product team, we defined the scope of the feature and then communicated with the customer and got all the buy ins, there had to be some repriorization required to imediatle start working on the project, I had a chat with my team and transperantly explained why this was such a high priority for the company and how it aligns with the company goals. This gave boosted their morale and also they saw the advantages of adding this feature and the moral was high.

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

I was managing organization wide restructuring program where goal was to map all resources with their delivery accounts to keep a track of account’s PnL and manage capability as cost centre. We also intended to design KRA and KPIs for each individual level to make our Performance Assessment data driven and transparent. This was a big change at employee level at professional and emotional level too. It meant changes in their reporting structures, extra reporting and performance management by all managers, clear KPIs alignment and selection.

Planning Level: We identified all the major business account heads, capability and other function head and organized a communication platform to make them aware and comfortable with the changes. We undertook their inputs on pros and cons and some caution to be exercised

Execution Level: We started executing these changes with L0 level employees and moved up to leadership team. Along the way we encountered some risks and outlier conditions to be managed.

Communication Strategy: We worked with all business and functional heads on our communication strategy to reach out to all the employees. Head multiple events and workshops to discuss the changes.

Data Platform changes: Evaluated all the data platform changes required and planned a phased out approach to bring those changes in the system as well.

However, when we were about to reach closure of this program, I realized that I have made a big mistake of readiness of our existing platforms to support all the changes required and existing data integrity. It really took a toll on everyone involved to clear up data accuracy before the changes could be introduced.

• Self-Motivated: I thrive on challenges and take initiative to learn and grow without external prompts.

• Passion for Exploration: I love exploring new places, immersing myself in diverse environments, and gaining fresh perspectives.

• People-Centric: I enjoy engaging with new people, building connections, and exchanging ideas.

• Mentorship: Mentoring others is something I genuinely enjoy, as it allows me to share knowledge and help others grow.

• Appreciation for Art and Culture: I have a deep love for art, culture, music, and world cinema, which enriches my creativity and worldview.

• Cooking Enthusiast: I love experimenting in the kitchen and trying out new dishes, blending culinary skills with creativity.