The most comprehensive bank Interview Answer Review tooling available online.

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

Earning the trust of a team is essential for effective collaboration and success. I approach this by:

1. Being Transparent: I prioritize open communication and honesty. For instance, during a project update meeting, I openly shared the challenges we were facing, which helped build trust among team members as they felt informed and included in the process.
2. Listening Actively: I make a conscious effort to listen to my team members’ ideas and concerns. When a colleague proposed a new strategy, I encouraged discussion and incorporated their feedback into our plans, demonstrating that I value their input.
3. Following Through on Commitments: I ensure that I meet deadlines and deliver on my promises. For example, when I noticed our team was at risk of missing a deadline on a key project, I took the initiative to reorganize our workflow, delegate tasks more effectively, and set up short check-in meetings. This allowed us to complete the project on time, reinforcing my reliability to the team.
4. Showing Empathy: I take the time to understand the individual needs and motivations of my team members. By being supportive during high-pressure times and recognizing their personal challenges, I create a safe space for open communication.
5. Encouraging Collaboration: I foster a team-oriented culture by celebrating collective achievements. After we completed a project successfully, I organized a small team celebration to recognize everyone’s contributions and strengthen our bond.
6. Being Approachable: I maintain an open-door policy, inviting team members to share their thoughts or concerns. This accessibility helps establish a friendly atmosphere where everyone feels comfortable engaging with me.

By implementing these strategies and sharing specific examples, I build a foundation of trust that strengthens team dynamics and enhances overall performance."

I have been working on same project since last 3 years, I want to explore different projects and learn new skills and Technologies with current market trends

So for my current role we move in a very fast paced environment, and we brainstorm new ideas everyday on how to make our workflow more efficient and more reliable, which can definitely get overwhelming over time. So I would first assess projects' urgency and impact, and then for each project, I break it down into small milestones. After that I track them on project management tools like Jira to ensure I allocate my time effectively and communicate proactively with stakeholders

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. 

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.

At hyperface we got requirement from product team to build a nudge engine, this will be a configuration driven engine and when a condition is met based on the configured communication pattern it is going to send the communication. Example : If user have done 5 transaction is flikart and an offer is going on to do 10 transactions to get a reward we will nudge user based on the communication channel and rules that nudge him on whatsapp this much time and send him the push notification.

When this product requirement came , product wanted to build each and everything as a single engine, but at that time I realized that having a separate notification service which will take care of all notification related stuff and we will be able to efficiently scale that system and prevent having a tight coupling  will be very helpful , but when I proposed this product did not agreed as they thought right now there is no usecase for making nudge engine and notification engine a separate component.

At that time I dicsucces this with my fellow EM and came to know that they are scenarios where they need to send notification for example otps , push notification and everyone is handling this in a custom way in there own code based . With all this data I went back to product team ann pitched them that having this notification engine all this custom handling will be gone we will have better mechanism to control notification  track metricies and and improve the experience by handling failure scenarios .

with this data I was able to convenience the product team to build to different systems.