The most comprehensive bank Interview Answer Review tooling available online.

Success could be measured in multiple different factors. An engineer or a resource would be performing very well in the team, stupendous technically but their relationship with the team should also be desirable. They should be open to collaborate, have good relationship, trust with the team, help cross functional team for collaborating with multiple business teams. Should be able to understand the problem providing right solution at right time, mentoring others in the team and always posses the ability to communicate with at most clarity. 

All of this is a 360 degree feedback that one could be considered successful working in an organisation.

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.

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.