The most comprehensive bank Interview Answer Review tooling available online.

I’m my current role, during a core-team meeting I noticed conflicts between 2 team members, the MM and the EE. They were debating about why to include one component in the official BOM and discarding another one.

To understand their perspectives, I spoke with them separately in a friendly environment. The MM was frustrated because the EE didn’t provide any data or argument to discard the component that the MM suggested. This component had the same performance, was pin to pin compatible, and cheaper. On the other hand the EE explained he had bad experiences in the past with the component suggested by the MM and he refused to validate and qualify it to do not waste his time.

So… After being clear about the situation, I brought them together for a discussion and I emphasize to focus on the issue, not in personal discrepancies. Do, during the meeting, I encouraged both to consider the Project requirements, customers need and I worked with them brainstorming session.

Then, they agreed to meet with other stakeholders to get their inputs about these 2 components, they commit on a validation plan including both components. The one suggested by the EE as POR and the one suggested by the MM as alternate. They also agree to allocate 60% of the mass production volume to the EE component and 40% to the component suggested by the MM.

From my side, to ensure progress, I scheduled follow-up meetings with them to monitor their collaboration and for sure, I offered my support. Finally, both components are currently part of the product official BOM and these 2 guys improved their working relationship and communication.

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.

With a major product launch on the horizon, expecting to triple the user load. The infrastructure was non-optimized for demand and incident response was non-harmonious across teams with no set process.

As the SRE Manager, I'd have to implement project changes to infrastructure to accommodate high availability and scalability. I discovered a long-standing issue surrounding incident response and observability that would make it all the more difficult to achieve reliability under pressure and peak traffic.

Therefore, instead of fulfilling the project requirements as presented, I became an advocate for change across the organization. I established an observability platform with 100% stack coverage, created custom SLOs/SLIs/error budgets to enhance performance and reliability visibility, drafted and socialized an incident management playbook across the company and held hands-on trainings for all respective teams. In addition, I advocated for Terraform for Infrastructure as Code to help with deployment time and held FinOps reviews to help eliminate redundant costs in cloud spend.

As a result, we did not only survive the 3X traffic upon product launch with zero critical incidents, but we also achieved 15% saves the following years in cloud costs and 40% faster deployments. Many of the processes I created were adopted as company-wide best practices.