The most comprehensive bank Interview Answer Review tooling available online.

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.

It would be at my thesis, of predicting SEPSIS with AI using multiple models, and the challenge was with time management, since we had 2 problems, the first problem was that we didn't had access to the data base until half of the second semester, since the process to get access to a hospital database was a rigorous process, so we weren't able to go quick with our application. The second one was that a team mate and I had a family member with cancer, so we needed to manage our work load in a manner that we could be present as family and team members, we needed to fulfil our duties on the project, so I planted a prioritization process in witch we focused on our best attributes I on sql queries and documentation, mostly but the situation with the family member of my companion worsen, so needed someone to help with his work load, so I also assisted him with his main tasks as the main designer of the project, mainly on the uml diagrams, so that we could end our thesis 

Situation: I was tasked with building a prototype of our DIGITS app on the Hololens 2, a mixed-reality device. This was new territory for us, and I was excited to explore how our telephony experience could translate to AR.

Task: My goal was to create a working demo that integrated our telephony SDK into the Hololens experience using Unity and C#. I had about two weeks to get something functional enough to evaluate viability.

Action: I dove deep into learning Unity3D and Hololens development from scratch, and spent considerable time trying to bridge our SDK — which was built in C++/C# — with the Hololens platform. Despite my efforts, I couldn’t get reliable communication between Unity and our SDK.

Rather than give up, I pivoted and simplified the approach by porting our existing Windows desktop app into the Hololens environment. This at least allowed for basic app functionality and UI testing. Through further research and prototyping, I discovered a key platform limitation: Hololens did not support background notifications, meaning incoming calls couldn’t be surfaced while another app was in use.

Result: I documented everything, demoed the prototype to my manager, and recommended that we pause development until the Hololens platform evolved. While I didn’t deliver the full solution I set out to build, I learned a ton, clearly communicated risks, and saved the team from investing more time into a blocked path. I see this as a failure in the original goal, but a success in terms of ownership, problem-solving, and protecting resources.

The product that I brought to market was a BNPL button for e-commerce checkout. The button was an SDK enable for the Magento Platform. The goal was to let merchants enable the payment button in less than 2 days instead of one month with the previous journey. The main challenge was that the company did not have the resources and knowledge to deploy this product. I made a comprehensive business plan showing how this initiative will grow revenues and reduce merchant onboarding cost. the way i approached this challenges was through partnering with a company based in Israel that had already deployed this feature successfully. I implemented successfully the initiative in 3 months, merchant onboarding accelerated in the digital space.

Situation/Task: Team had a growing backlog of inactive tickets that were over a year old, and the ticket queue was growing every week.

Action: Organized a bug bash to close old tickets or assign developers to work on them. Added longer running tickets to the next sprint backlog. There were certain tickets which were unassigned, asked team to have oncalls have a go at them to be discussed during next ops call, with a target of 5 oldest unassigned tickets to be resolved if possible.

Result: Ticket count went down 50% and old ticket (+1 year) count went down 90%. Oncalls were able to make sense of existing and new tickets without going through pages of left tickets.

1) Clarify the objective - so just for clarification, the objective of this case is to design an alarm clock that will be specifically be used by users without their sight?

Okay great

2) Identify the user - In this case we will be dealing with people who are unable to see, but can use their other senses

3) Identify pain points that blind users may have with the current features of the alarm clock. 

Blind users may have an issue locating the alarm clock

Blind users are unable to see the time on the clock 

Blink users are unable to set the alarm 

Blind users may have trouble locating the power cords or knowing if the batteries are running low

4) Prioritize the pain points and pick two to move forward with. Discuss value to user - 

Most important pain points is that Blind users are unable to see the time on the clock

Blind users may have trouble locating the power cords or knowing if the batteries are running low

5) User value and effort to implement improvements for each pains point 

Implementing a voice activated alarm clock that tells you the time when the user asks what time it is, this voice activation feature would also allow the user to set the alarm with voice activation

6) Recommendation - 

I recommend that in order to update the design of an alarm clock to best fit the needs of blind users, we should invest in voice activation technology in order to tackle the pain point of users not being able to see the clock and users being unable to set the alarm. Although there would be some knowledge transfer/additional resources to be learned in the process of implementing voice activation feature for blind users, I believe that the value being delivered to the customer heavily outweighs the cost of effort that will be required for our team to implement this.