The most comprehensive bank Interview Answer Review tooling available online.

In my role leading the launch of that new customer onboarding system, the pressure was really on. We had that tight three-month window and a lean team to build something that would be the first impression for all our new users. One specific hurdle we faced was integrating our legacy customer database with this brand-new system. The data structures were quite different, and initially, the data migration process was proving to be much slower and more error-prone than anticipated. This threatened to push our launch date.

To tackle this head-on, I didn't just delegate. I dove into the technical details with the lead engineer. We mapped out the data fields meticulously, identified the key transformation rules needed, and actually prototyped a more efficient data migration script using Python. This allowed us to automate a significant portion of the process that was previously manual.

Furthermore, to ensure we were building the right thing quickly, we implemented very short feedback loops. We'd build a small piece of the onboarding flow, get immediate feedback from a small group of internal users, and iterate based on their input. For example, early on, users found a particular step in the registration process confusing. Based on their feedback, we completely redesigned that screen within a couple of days, leading to a much smoother experience.

By getting into the technical weeds to optimize the data migration and by relentlessly focusing on user feedback through rapid iterations, we not only overcame the risk of a delayed launch but also delivered an onboarding experience that was significantly more user-friendly than initially envisioned. It was incredibly rewarding to see new customers move through the system so smoothly right from day one. That success really underscored the power of combining technical problem-solving with a user-centric approach

I am pretty passionate about Reddit. In a world where media is biased and polarized, Reddit threads gives me a sense of how local communities view the world. It helps me get grounded in reality of what different cadres of people are thinking by browsing different communities. Reddit is very engaging, as in, you can comment and instantly receive feedback. While there is a lot of "internet hate" and "misinformation" in Reddit communities and threads as well, looking at a wider spectrum of communities within Reddit, especially the differing ones, helps you form a less polarized and biased opinion. I prefer contributing by asking open-ended questions and if I have an opinion, posting it respectfully as a question. I also respond to scientific minded questions that I have qualifications to answer. By selectively responding and answering questions with some due diligence, I keep the communities I am a part of thriving and truth-based.

When buildling the next generation instance, during the planning phase I budget the amount of servers we will launch the product with. Given each server cost was over 2 million dollar I biased to towards frugality and provided a bare minimum number of server we could launch with. But what I completely missed was during the developement some servers will end up in bad state and the engineering team will short of servers to test the software and firmware getting built which made meeting the project timeline riskly and heavily dependent on delivery schedules of servers and them staying healthy. This quickly became a bottleneck that I realized. I quickly put togther a plan to request adittional server and provide a detailed breakdown on where and how these would be used during and after developement. Synced with the hardware and ODM team and executives to get a approval and ordered the parts to get the servers and racks build at ODM. 

I recently took over a team from a different tribe, my approach was to observe what the team was doing and how I could best help them. 

One of the observations was that a team member was not contributing as much as was expected and ultimately was underperforming. I raised this with the previous line manager and he validated my concerns and said that he will likely get another developing in performance review and be put on a PIP. 

After some initial conversation with the individual, discussing what I've observed and how his not meeting expectations, I was pretty sure, this person was checked out and was likely heading for a difficult performance review

However, after some further discussion and people a relationship with that individual, they opened up and start to share their difficulties they were having. This then allowed me reach out the necessary teams to get them the support they needed. 

Utlimately, they proved me wrong, as due the the hard work with both put in, his on track for a good performance review 

I

I believe my biggest achievement is building a high performing team amongst a lot of chaos. I started as an engineering manager for replenishment team, soon due to restructuring I was asked to lead a different BU called Parcel and I was given the team from scratch, 8 months into this I heard the leadership is deciding to put Parcel on KTLO and give me a new tier 1 service called channels. This service was highly unstable with a lot of issues and tech debt. This service was transitioned among 4 engg manager in past three years (4th me). 

TASK

My job was to do a successful transition of this service and keep the team motivated

Actions

- When I got to. know about Parcel KTLO and having a new product under me, I wanted to ensure this is communicated to the team clearly with empathy and I wanted to ensure the team that this will only benefit their growth

- I started with a team meeting, shared a couple of wins that we did in parcel, shared even though we did so much, Parcel is being put on KTLO for various xyz reasons.

- I told them every crisis situation is an opportunity and by channels coming under us, we can showcase that even the toughest of the services can be maintained if the tech debt is continuously addressed

- Post team meeting I kept 1:1 with every member and listened them, helped answer their questions

- A couple of team members did share that they felt proud about what they developed in Parcel and were feeling sad that it was going in KTLO.

- I shared that products coming in KTLO happens sometime and this in no way reflects the teams performance, infact our teams reputation is very good amongst the leaders thats why they have given us the most important service (which is also in the worst shape)

- Under previous engg managers there was minimal to no improvement in the service on tech and product side because they were busy fixing on call issues

- I worked with the team to fix this by assigning ywo people to on call and rest two on fixing the issues from root cause. 

- In a couple of months this gave us brwating space since the oncall issues reduced directly impacting reduction in customer queries

- We got appreciated by leadership for this

Result

- Team members were highly motivated

- Learnt a lot

- Got appreciated by leadership for this hard works