The most comprehensive bank Interview Answer Review tooling available online.

In the first company I worked as tech lead, even though my performance rating was good, I received a 360 degree feedback on my interpersonal skills as well. One of them said that I sounded a bit rude in couple of discussions. When I asked for the instances, I got examples where I got the feedback from and not whom. So I had to explain my manager that it was not intentional and the aggressive demanding nature of mine could have been perceived as rude. But I considered the feedback and identified, corrected myself, toned down the way I speak in certain instances which made a set of teams in my org ex: production support teams reach out to me more often now for guidance. So this helped me gain valuable experience and unlock a totally different perspective in terms of collaboration with other squads in the company.

It would be at my thesis, of predicting SEPSIS with AI using multiple models, and the challenge was with time management, since we had 2 problems, the first problem was that we didn't had access to the data base until half of the second semester, since the process to get access to a hospital database was a rigorous process, so we weren't able to go quick with our application. The second one was that a team mate and I had a family member with cancer, so we needed to manage our work load in a manner that we could be present as family and team members, we needed to fulfil our duties on the project, so I planted a prioritization process in witch we focused on our best attributes I on sql queries and documentation, mostly but the situation with the family member of my companion worsen, so needed someone to help with his work load, so I also assisted him with his main tasks as the main designer of the project, mainly on the uml diagrams, so that we could end our thesis 

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.

So I'd say the time I took the risk was, I actually went against the recommendation of my manager. Not directly, but essentially I was put on a project at Niagara and I was looking at a lot of the contract amendments and I analyzed our contract negotiation with Uber. And so as I was looking at the whole data, trying to see the discrepancies and really seeing, okay, what lanes should we negotiate, seeing what are the terms of negotiation that we should use, and then finally, I wanted to also forecast on terms of a long-term growth. So not just necessarily for just this term, but see how that would last for the future quarters as well. So kind of taking those into consideration while I put them all out into a matrix and showed the team, the director, and a lot of my team was thinking that we should go with the option that saves us the most amount of money. I'll put the $700,000 to $800,000 for the quarter, implementing this new amendment that I actually disagreed. And I suggested we just take somewhere closer to about the $600,000 range because for two reasons, one, I noticed that the lanes that we included in the $600,000 would lead to better client relations with Uber as a long-term and one of our biggest carriers. And two, I also noticed that in the long run, we actually would save a little more just because in the future quarters with seasonality to keep into account, those lanes were not always going to save us the most amount of money. So maybe while the $700,000 to $800,000 option would save us that much in the first quarter, when it comes down to the winter, it would save us only about $300,000 versus the $600,000 option is a little more consistent throughout the seasons. And so we actually noticed that in terms of a long-term growth for the year, we would save a lot more. So that was a time where I kind of took a risk to go against and maybe recommend something slightly different than my manager. But I think the director, when he heard me say these things, he took those into consideration and saw my analysis and saw that I was able to back up kind of my decisions and this type of risk to making sure I'm minimizing it as much as possible. So I think that was something that he really appreciated and that the VP of supply chain ended up deciding to work towards.

• There was a time the team was developed a search optimization capbility for users based on given requirements by product manager, so it could add more search filters for faster accessibility so . I asked the team to create demo on dev environment and to show customer, in order to make sure it is aligned with users need. I scheduled the meeting and we showed the demo, suddenly we undrestood all the usecase were not covered by program manager which lead to poor design it means some of the file type were not identified by specific locations. And that wasn't a feature for customer. On the other side we didn't have enough time. Since we needed to release this feature on time and as manula accessibility got block the program ​
• ​
• So I pushed the product manager to schedule meeting with diverse useres to make sure to capture diverse uses cases. I put together team and we discussed on options and tried reestimate we identified that by one more api resource we can have this feature on time. So I escalae that to leadership since the timeline was crucial for them, they assign api resource from india Lesson learned: 25 percent ​

I was working with 5 customers at once, and had to focus on those activities where I could make a difference, make the most impact, that I could not delegate, and where I could balance with other priorities - in order to do that, I measured the priority of the tasks by the cost of delay, in other words, the impact of not doing them at that time. Then, with more clarity about the priorities, I thought which ones I could delegate to other team members, and if that made sense, with the required support and guidance from my side. Working as a team and not trying to get everything done yourself is key in the long term with multiple, competing priorities. Then, organizing my time well in short, focused timeslots for the most important tasks, made a difference.

I would like to talk about situation. When I was an engineering  manager at digital commerce platform org at Amazon, I was handling close to 11 services, and 

as part of the Rolling Stone initiative where Amazon was trying to move all its services away from Oracle, I had four services that I was trying to migrate from Oracle to the databases hosted on Azure. All my fellow colleagues who were owning services of DCP were doing similar exercise. One of the colleague who was owning digital redemption service had to go on maternity leave, and then couple of engineers earmarked to do this migration for digital redemption service wwere transition out of the organization. That is when I offered to help with the migration of the service. 

So I now had 5 services with competing  priorities where I 

had to manage very tight schedule of service migrations. Planning a very ruthless prioritization, figuring out an optimal execution path of a completely unknown service, interacting with the service upstream clients whom i had not worked with prior, working with an amalgam of My team members and the service owner team members were few of the ambiguous paths I navigated to help do on time migration completion of the   service owned by my collegues.