The most comprehensive bank Interview Answer Review tooling available online.

Power is the ability of a test to correctly identify a significant effect. Suppose we are performing a test to see if the mean age of two groups is different or not. If the power of this test is 0.8, we can see there is a 80% chance that if the two groups have different mean age, the test is going to correctly detect it

with the constant standard deviation, we'll need to the sample size of n/100 to get ME of 0.3. Since ME = Pop standard deviation / sqrt(n)

I was working on a large scale program that had integration points with Lab and external 3rd party team . We were following a strict timelines and had intially aligned on end to end delivery and various cross coordination effort . since we were dealing with major cross coordination feed files for further processing from 3rd party team we had highlighted the risk to the leadership team but didn't receive a strong follow up on the risk and commitment from the 3rd party organization on the delivery date . This caused us to miss the go live date had to delay . However going forward we had frequent checkpoint calls and also as a backup for testing effort we build mockster and service virutalisation for testing effort so that we can mock the service behavior of the feeds and data that we were supposed to receive from 3rd party team and moved ahead in our schedule .Therefore for all major delivery and critical delivery of the product we assumed variability and defined on the process of backup scenario in case we encounter Andy hurdles / risk

I have more than a decade experience working as customer success engineer in which I tried my best to solve a customers problem. During this course I have interacted with several product engineering and product managers and worked very closely with them. I aspired to be a product manager because I wanted to solve a customers problem even before they realized it by understanding their use case, feature requirement, motivation to use a product. I found this role to be very challenging and exciting as I have to think more like a customer than an engineer trying to solve a problem, identify their persona and how I can ease their day to day job. So when I eventually got an opportunity in my past organization to work as a product manager I took it.

l, I initially built automation scripts for trade reconciliations and reporting using standalone Python and UNIX-based cron jobs. These worked well for smaller data volumes, but as our operations scaled across global teams in London, Hong Kong, and the Bahamas, performance and maintainability became a bottleneck.

I realized I needed to adapt my workflow to better support large-scale, distributed processes. So, I changed how I worked by migrating critical pipelines from PostgreSQL and flat scripts into a more robust ETL framework using Databricks and Delta Lake. I restructured batch processes into streaming jobs and modularized the Python code to be production-grade. I also started using Kafka and Kubernetes to improve system reliability and orchestration.

I think a product deployment starts with ideation.  I would crowdsource and get multiple inputs for product content to ensure the deliverable is valuable to our customers.  Then product development, which is tested iteratively by internal quality assurance and beta customers in a sandbox test environment.  Prior to deployment, I would again get feedback and iterate based on the beta customers experience.  During deployment, I would ensure that communications are delivered to customers and internal stakeholders, complete with documentation in multiple areas, including reference documents in knowledge base articles and customer forums.  During support, I would provide feedback on the most impactful areas of the product and those that generate the most time and energy to support.  This would result in product improvements and enhancements during the mature phase.  Once ready to sunset, I would develop a transition plan for our customers to the replacement product or service, mapping the old and new workflows and highlighting the changes that may be required to business processes with the new product.  Upon retirement, I would provide a complete lesson learned document to the new product service owners.

One project i'm proud of is my internship project which was a full stack project where i had the chance to create a prototype of a template manager , storing the data into a cassandra database, alongside using springboot and java to work on the module structure and life of the project, I then used js and react for UI. This prototype was then deployed and is now being used by internal payment team at jpmc, instead of going to search every resource, i store all the templates in one template manager and they can know just search the nav bar and get the exact template they need. I'm proud of this project not only because it was my first real project using the new languages and frameworks i was learning during internship but it also gave me the confidence of knowing and seeing that I can do this even though i dont have a degree in this field!