The most comprehensive bank Interview Answer Review tooling available online.

If it's a subscription based product,  After usage of the product I check how many users continue with the subscriotion after 7 days, 15days, 1 month, 3 months and 6 month. The % of users who continue to have the subscriotion after the above time periods are the retained users

For non subscription products, I can check weekly or monthly retention by finding % of users who come back to product the week or month after using

In my early days as Program Manager, I managed a project for one of our main customers. This project had a very tight schedule and I promised to deliver the first EVT samples in 3 months.

It was my responsibility to ensure everything would be completed on time, and achieve the quality standards defined by the program and inside the budget approved by leadership.

Unfortunately… when I started to deep dive into the project and analyze all the technical details, I realized that it was not possible to get the prototypes ready on time. I missed the deadline by 2 weeks. I felt bad at that time because I failed, so I immediately started to work on a new feasible schedule trying to mitigate the problem. In addition, I arranged a daily opening and closing meeting with the core team to monitor all activities. The root cause of the problem was a delay in some component's delivery and I also ignored one of the Reliability tests defined by Engineering.

So I highlighted the problem to my manager and I shared with him my new plan. I explained the situation to him and I shared the new timeline that I could meet. Then we worked together to commit to the new delivery date. So I learned a lot from that situation, now I’m always adding some buffer to my project schedules and I work more closely with core team members. But the most important learning was, how important is to be honest and raise your hand on time if something goes wrong.

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.

As an EM it is our responsibility to assist my team members so that they can grow. So I want to narate one scenario where I helped team member grow and it provided me an enormous learning. 

At hyperface when we were breaking monolith into micro service , there was a lot of work required at one of the component called integration service, this service was acting as a link between external bank system and hyperface Credit card as a service core engine . As work on this layer was more I moved one of the SDE-1 t that team , this team along with coding required lots of communication with business team as well , at that moment I found that the SDE-1 who was a good performer on core team started struggling in that team . I connected with him on 1:1 t ocheck is it because of he is not liking the work or is he having some personal issues as it was  hard to digest that person who is doing well in solving complex problem is struggling with not as challenging issue , at that moment I found that he is having issues in his communication , he feels underconfident interacting with other team , out of pressure commits what ever other team says. 

At that point fir I told him not to worry he is doing a good work and with him I created a framework to deal with this scenarios like always prepare before the meeting note done the important pointers , if you ae not sure d not commit always say I will get back after  discussing with team , for any communication rather then personal messages include relevant stakeholders as this will provide help . and also told him that improving communication is not an over night job. As a result of which withing one month following this practices his communication improved and it started reflecting in his work.

Learning : to help people grow always try to assign them the different type of tasks so that they will become aware where they are lacking and then help them grow

As Program Manager my biggest achievement was leading the development of a complex electromechanical module for HP. The project consisted of developing and producing a huge electromechanical module for a high-speed large format printer.

I was in charge of overseeing the entire Product Development Process, from requirements gathering and solution design to development, testing, deployment, and mass production release.

The Key aspects of this project included

1.Strategic planning: I developed a plan including the project Objectives, scope, and deliverables, as well as timelines, milestones, and resource requirements.

2.Stakeholders management: I engaged with key stakeholders such as business leaders, external vendors, and customers to keep them all on the same page, ensure alignment, and address concerns.

3.Risk Management: Identifying potential risks and challenges associated with product performance, compatibility with external modules, material availability, etc.

4.Collaboration and Communication: I facilitated collaboration and communication among cross-functional teams involved in the project, including engineering, operations staff, and materials, to ensure alignment.

5.Quality Assurance: Implementing robust testing processes and quality assurance measures to ensure reliability and performance.

6.Mass production release: Worked with all operational teams to ensure material and factory readiness to launch the program to mass production

Finally, the project was released on time and satisfied all stakeholders, internal and customer. This reinforced the importance of clear and transparent communication between stakeholders to drive successful technical outcomes and foster a collaborative team environment.

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.