The most comprehensive bank Interview Answer Review tooling available online.

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 

At Auctane, I had a senior dev working on tech debt, this was critical for some small segment of customers and my PM was looking forward to it being devliered. A churn happend on other team and they had a higher priority project. That EM approaced me to help him deliver the project. I had to reshffle the resource and had to push back on the timing for this tech debt project . The compramise I made was to put hold the project we had been working and convince my PM that this was most optimal approach for the company.

For prioritizing the product backlog, I evaluate each product across the dimensions of 1) impact on metrics/organization level goal the needle which it is trying to move, 2) reach of product as to how many personas or stakeholders experience will it improve 3) technical feasibility or complexity of the product being delivered which also includes dimensions of clarity in requirements and 4) if its of strategic importance to future growth

In my previous role, I led a team to launch a new kit. The team included individuals from product support, segment marketing, sales, and customer support, and we were tasked with launch the product to market within a specific time frame to address a rising demand.

We faced the challenge of managing tight deadlines and aligning cross-functional teams with diverse priorities. To address this, I ensured that everyone understood the key objectives and customer needs, fostering collaboration and creating a detailed project roadmap. I set clear milestones and facilitated regular check-ins to ensure we were on track.

One of the biggest hurdles was getting buy-in from the sales team on the new product's value proposition. I worked directly with sales leaders to develop tailored sales tools and training materials, ensuring the team could effectively communicate the product’s benefits to customers.

By maintaining a clear focus on customer needs and empowering the team to collaborate effectively, we launched the product on time, surpassing adoption targets by 15% in the first quarter. This experience reinforced the importance of strategic planning, transparent communication, and making customer satisfaction a central part of the team’s mission.

I was working on a high stake project with very high visibility from my senior management.

Me and my manager were thinking of can we leverage the quality of the development using help from QA team. He wanted to keep the QA team separate. His point of view was that a separate team would keep clear focus for the team and they would focus on finding more customer facing bugs. I thought that we should have QA embedded in the scrum team as that would help in easier collaboration and quicker bug fixes plus this is a more efficient way. Though I understood his point of view I always believed that in QA embedded inside the scrum team. I went back had a thought to measure the merits and demerits of the proposals. I put down in a slide the merits and demerits of each. Merit from having a separate team, clear focus and better filtering of quality, demerits less collaboration with development team. I then proposed that the QA engineers attend the calls of dev teams but keep a separate QA board for their tasks. This will give clarity of what bugs they find, what test scenarios they create and finally the metrics to measure the bugs reported per development. My boss and I both agreed as it solved the problems of each proposals

So I'd say the time I took the risk was, I actually went against the recommendation of my manager. Not directly, but essentially I was put on a project at Niagara and I was looking at a lot of the contract amendments and I analyzed our contract negotiation with Uber. And so as I was looking at the whole data, trying to see the discrepancies and really seeing, okay, what lanes should we negotiate, seeing what are the terms of negotiation that we should use, and then finally, I wanted to also forecast on terms of a long-term growth. So not just necessarily for just this term, but see how that would last for the future quarters as well. So kind of taking those into consideration while I put them all out into a matrix and showed the team, the director, and a lot of my team was thinking that we should go with the option that saves us the most amount of money. I'll put the $700,000 to $800,000 for the quarter, implementing this new amendment that I actually disagreed. And I suggested we just take somewhere closer to about the $600,000 range because for two reasons, one, I noticed that the lanes that we included in the $600,000 would lead to better client relations with Uber as a long-term and one of our biggest carriers. And two, I also noticed that in the long run, we actually would save a little more just because in the future quarters with seasonality to keep into account, those lanes were not always going to save us the most amount of money. So maybe while the $700,000 to $800,000 option would save us that much in the first quarter, when it comes down to the winter, it would save us only about $300,000 versus the $600,000 option is a little more consistent throughout the seasons. And so we actually noticed that in terms of a long-term growth for the year, we would save a lot more. So that was a time where I kind of took a risk to go against and maybe recommend something slightly different than my manager. But I think the director, when he heard me say these things, he took those into consideration and saw my analysis and saw that I was able to back up kind of my decisions and this type of risk to making sure I'm minimizing it as much as possible. So I think that was something that he really appreciated and that the VP of supply chain ended up deciding to work towards.

Question: Tell me about a time when you assisted a colleague in his work. What was the result?

Answer:

Sure. I really enjoy helping others on the team, especially when they’re stuck and not sure how to move forward.

S – Situation:
Once, someone on a neighboring team was struggling with a production issue for a few days. I noticed that he seemed frustrated and wanted help, but didn’t quite know how to ask.

T – Task:
After finishing my work early one day, I proactively messaged him on Teams and offered support. He was happy, but mentioned he wasn’t even sure how to describe the problem clearly.

A – Action:
So I sat down with him and tried to understand the issue. He told me that after one of his code changes went live, a dropdown component in our shared UI broke — its layout was completely messed up, even though his change didn’t touch that component directly.
I helped him debug the issue step by step. After ruling out rendering or layout bugs, I noticed the problem was actually due to a CSS variable conflict — the styles weren’t properly isolated, which caused unexpected overrides.
Together, we fixed the CSS scoping issue and verified the dropdown worked as expected.

R – Result:
The bug was resolved and the fix was shared with the wider team via email, to prevent similar issues in the future. My teammate was really grateful, and after that, our collaboration improved significantly.

To juniors, more leading, coaching, and "instructing" on what to do

To Staff engineers, partnering to help them unblock, incorporating their feedback, etc