The most comprehensive bank Interview Answer Review tooling available online.

I was having a team member, who was technically strong, but when it came to gelling with the team members, he was having problems. His comments/feedback for the technical artefacts, or for ones understanding of a problem, was showing people in a bad light. Team members were apprehensive, working with him. People started to unplug themselves while that person was around. I could sense that, the team’s engagement had started to wane. If that had continued, we were at risk of losing that person from the team.

I initially un-plugged him from the team discussions and meetings and started to have a daily sync-ups with him. Sensitised him about working as a team and how successful teams thrive in the organisation. Made him enrol for some trainings like - Seven habits of highly effective people. Recommended that training mainly because of the focus it lays on - personal change, collaborations with the team etc.

Then he started to show empathy towards the team members, started to mingle with team, started to give constructive feedbacks for the technical contributions and started to show respect to the fellow team members. The bridge that was created, started to disappear. And we finally made him part of all the discussions and meetings and today, he is one of the go-to person in the team.

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

l, I initially built automation scripts for trade reconciliations and reporting using standalone Python and UNIX-based cron jobs. These worked well for smaller data volumes, but as our operations scaled across global teams in London, Hong Kong, and the Bahamas, performance and maintainability became a bottleneck.

I realized I needed to adapt my workflow to better support large-scale, distributed processes. So, I changed how I worked by migrating critical pipelines from PostgreSQL and flat scripts into a more robust ETL framework using Databricks and Delta Lake. I restructured batch processes into streaming jobs and modularized the Python code to be production-grade. I also started using Kafka and Kubernetes to improve system reliability and orchestration.

At Auctane, while we were working an critical project, one my key Sr. Eng left the company. This put the project in jeoprady. External hire was not feasible as they needed system knowledege and the project would be understaffed. I had prior knowledege that another dev had worked on this system before and I came up with a approach of borrowing the resource for some time.

I convinced that manager that by borrowing this is a win-win for both of us as the Sr. Dev would learn new web skills as they had projects in the pipline to move their projects as well. After that I talked to my manager and borrowed this resource, I took two weeks time to do the KT and could deliver the project on time and within budget. the lesson i learnt was to have plan B an antiscipate any changes and plan for continegency.

At my current job one of our biggest customer raised the  issue they were facing in our notification service. The issue was they were not receiving any notifications from our system on their new infrastructure. Their production infra was working fine.

I reviewed their configuration and everything was looking fine at the same time we hadn't done any changes to on our end which could cause this issue. Since their contract was up for renewal the issue, we needed quick resolution. I setup a live debugging session with customer to understand the issue in detail and their new infrastructure. After the first call it was clear that the issue was happening during https handshake or at network layer. To keep the momentum going I setup recurring call with with them and assured them that we are treating this as a high priority. On the next call I involved our security expert and SRE team for further debugging. However the issue not futher progress was made, at this point I insisted SRE team that we contact Azure support to understand if there is any issue at the tcp layer. Azure team looked at the turned on debug logs and found that our network was default MTU (maximum transmission unit) was higher than customers network MTU and customer network was dropping packets.

Finally I worked with SRE team to lower our MTU to match the customer configuration and ran tests. After the config change issue was resolved, our customer confirmed that they could see the notifications. This was really difficult issue I had ran across but I worked with various teams to get to the bottom of it and delivered results to customers satisfaction.