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.

With a major product launch on the horizon, expecting to triple the user load. The infrastructure was non-optimized for demand and incident response was non-harmonious across teams with no set process.

As the SRE Manager, I'd have to implement project changes to infrastructure to accommodate high availability and scalability. I discovered a long-standing issue surrounding incident response and observability that would make it all the more difficult to achieve reliability under pressure and peak traffic.

Therefore, instead of fulfilling the project requirements as presented, I became an advocate for change across the organization. I established an observability platform with 100% stack coverage, created custom SLOs/SLIs/error budgets to enhance performance and reliability visibility, drafted and socialized an incident management playbook across the company and held hands-on trainings for all respective teams. In addition, I advocated for Terraform for Infrastructure as Code to help with deployment time and held FinOps reviews to help eliminate redundant costs in cloud spend.

As a result, we did not only survive the 3X traffic upon product launch with zero critical incidents, but we also achieved 15% saves the following years in cloud costs and 40% faster deployments. Many of the processes I created were adopted as company-wide best practices.

when I was in college robotics club I conducted workshops for line tracing robot using IR sensor. I was assigned as a mentor to a team. I helped them to build that robot from the kit, also helping them understand the concepts behind it. I cleared their doubts.

At Auctane, I had a senior dev working on tech debt, this was critical for some small segment of customers and my PM was looking forward to it being devliered. A churn happend on other team and they had a higher priority project. That EM approaced me to help him deliver the project. I had to reshffle the resource and had to push back on the timing for this tech debt project . The compramise I made was to put hold the project we had been working and convince my PM that this was most optimal approach for the company.

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.