The most comprehensive bank Interview Answer Review tooling available online.

My favorite research method is the one that fit the research goals the best. For example, some questions need qualitative research, some quantitative, some data analysis. Also it should be realistic and feasible, if team doesn't have time or resources to run longitudinal study I should offer second best option considering the deadline.

I am looking for a new job because my previous company got acquired and they decided to let go of the entire product team and engineering team.

1. Because it is a new design for streaming music platform, I would like to test the usability of the new design , evaluate comprehension, effectiveness and efficiency , findability of the new design.

2. My tasks would revolve around basic tasks that every music platform offers which is - users can save a playlist, play music effortlessly, search for top trending music understand if users are able to, create different playlists. Other than this, I would discuss with the stakeholders in order to understand what other features have been added that i can test or they want to test.

3. Based on my objectives I would conduct a moderated and unmoderated usability testing on the new design.

I was managing organization wide restructuring program where goal was to map all resources with their delivery accounts to keep a track of account’s PnL and manage capability as cost centre. We also intended to design KRA and KPIs for each individual level to make our Performance Assessment data driven and transparent. This was a big change at employee level at professional and emotional level too. It meant changes in their reporting structures, extra reporting and performance management by all managers, clear KPIs alignment and selection.

Planning Level: We identified all the major business account heads, capability and other function head and organized a communication platform to make them aware and comfortable with the changes. We undertook their inputs on pros and cons and some caution to be exercised

Execution Level: We started executing these changes with L0 level employees and moved up to leadership team. Along the way we encountered some risks and outlier conditions to be managed.

Communication Strategy: We worked with all business and functional heads on our communication strategy to reach out to all the employees. Head multiple events and workshops to discuss the changes.

Data Platform changes: Evaluated all the data platform changes required and planned a phased out approach to bring those changes in the system as well.

However, when we were about to reach closure of this program, I realized that I have made a big mistake of readiness of our existing platforms to support all the changes required and existing data integrity. It really took a toll on everyone involved to clear up data accuracy before the changes could be introduced.

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.

I would take a step back and review the problem we're trying to solve for, look at if the questions i'm asking are the right ones and if still the data feels sound - I will start looking at deep lying proxy indicators which may be hinting to a chnage or something else taht's a true problem. meaning the hate for the ux could just be a symptom, and clients are trying to say something else