The most comprehensive bank Interview Answer Review tooling available online.

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.

I once led a restructuring initiative aimed at aligning resources with delivery accounts and redesigning KPIs. While the planning and communication strategy were solid, I overlooked whether our data platforms could support the new changes. Just before rollout, I discovered serious data integrity issues. This setback required a major clean-up effort across teams, but we corrected course by prioritizing platform readiness and enhancing our validation processes for future initiatives.

Situation: During the first calibration of Non-Maturity Deposit (NMD) models, I was working with a senior colleague and a consultancy firm to implement these models. At that time, market rates were rising, and the consultancy firm suggested calibrating a key parameter, the "beta," to be highly sensitive to market rates. My manager agreed, but I disagreed, as I believed this high sensitivity could lead to inaccurate estimations in future calibrations.

Action: I engaged in discussions with my manager and the consultancy firm to fully understand their reasoning. They argued that a more sensitive beta could improve management of metrics like Delta EVE and Delta NII, which was valid. However, I pointed out that we lacked sufficient evidence to support such a high beta and that it might cause issues in future estimations. To address the disagreement, I conducted a sensitivity analysis, testing the model under various market rate scenarios.

Result: The sensitivity analysis helped us reach a compromise. We agreed to lower the beta, ensuring more stability in the model's performance. This adjustment allowed for a smoother transition of the parameter, ultimately improving the model's reliability while maintaining good risk management practices.

In 2022 one of the representatives I worked with was planning a one month long Power and Video evaluation. Before the evaluation was going to begin I was informed that he would not be able to cover because he was going out on medical leave to have heart surgery.

At first I was very concerned because there a lot of moving parts to an evaluation of this nature and magnitude. You have to know the surgeons preferences and technique, competitors instruments, various surgical procedures, and what instruments are compatible with other competitive instruments. I was going to be taking the lead on this with very short notice and not much time to plan before he was departing for medical leave. We sat down and meet everyday for a week and went over all the inventory ordered, surgeons, and procedures. I had every surgery day planned for.

When the eval started I got there an hour before the cases started to setup the room and make sure all the capital and disposable equipment was ready. I introduced myself to the surgeons before each case and stood in all the cases where our equipment was being used. After each case I would address any questions, comments, or concerns the surgeon had and ask for their support to move forward with purchasing the equipment.  After the day was completed, I ensured all the equipment was properly put away, sterilized, and ready for the next day.  I’d go back to the hotel, make notes on the day, and review my notes for the next day. I did this Sunday through Thursday night for 4 weeks.

When the 4 week evaluation concluded I gathered all the feedback from surgeons, addressed any concerns, and reinforced the positive feedback and once again politely asked for the business.

I was responsible for sending back all of the equipment so I spent a few extra days gathering equipment and ensuring nothing was left behind.

A few months later we found out that the surgeons really liked our equipment and we were awarded the power contract. That contract was the largest for that year and I was personally thanked in our monthly newsfeed by our CEO for my efforts.

Situation:

I was laid off from my first job just four months after joining due to budget constraints. This was a major setback for me as I had just started my career. Around the same time, my father suffered a heart attack, which required me to stay at home and take care of him while he was on bed rest for several months. The combination of losing my job and dealing with a family emergency left me feeling devastated, and I struggled to apply for new roles.

Action:

Despite these challenges, I remained determined to grow in my career. While caring for my father, I focused on upskilling myself:

• I attended mentor sessions on ADPList to gain industry insights.

• I reached out to experienced designers on LinkedIn for portfolio reviews and feedback.

• I enrolled in courses through Interaction Design Foundation (IxDF) to expand my knowledge.

• I continuously improved my portfolio and resume, incorporating the feedback I received.

I also actively networked with professionals, which helped me regain confidence and visibility in the industry.

Result:

My persistence paid off. Where I once struggled to pass resume screenings, I started receiving recruiter calls consistently. In fact, this very interview happened because I proactively connected with a senior designer, shared my portfolio, and received a referral for this role. This experience not only strengthened my portfolio and skills but also taught me the power of perseverance, networking, and continuous learning.