The most comprehensive bank Interview Answer Review tooling available online.

In my current organization, we integrate Analytics with various source teams,  As a PM of Analytics, i should focus on Global compatibility when i implement a feature, which can be compatible to all the SORs. 

We have one particular source system who asked for a specific requirement of profile filters, which when applied, its applicable to whole SOR, which inturn is expected to be applied automatically to the Analytics warehouse

Goal here is to apply the new feature of the source system to the downstream application analytics. 

I have had multiple discussions with the SOR and my analytics technical team and identified that, we do have some technical complexities to implement profile filters to analytics, this might impact other SORs. Work around for the current release, can be to push the notification to analytics application to apply the global filters in analytics again manually, and we can address this in next release, as this needs to be handled for that SOR specifically.

We had multiple discussions with the leaders of the SOR on the user satisfaction and the priority of the profile filters, but at the same time i presented the data of number of users that will be impacted from other source systems other than the one we will focus on, which might lead to drop of CSAT of other source systems

After presenting the data, the leaders were ok with the workaround i have suggested, and for the next release, we have separated user profile dimension for that particular sor and implemented the feature as requested. 

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.