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.

I look after our email platform and our existing solution wasn't flexible enough to handle targeted messages at scale. We were missing an opportunity with users to send personalised messages at the right time to help increase engagement. I embarked on a project to implement a new marketing automation software. This project required alignment across our product, data, retail, security and legal teams. I spent time researching the availble tools in the marketing and workshopping requirements with relevant stakeholders, we created an RFP and sent to a number of suppliers. Each round of the RFP I assigned a score to the company and gathered feedback from stakeholders. This ensured the decision making process was fair and we had strong evidence when sharing the business case to senior leadership.

Once we decided on the supplier, I was responsible for implementing the tool which required support across various teams within the business. Implementing something cross-functionally

As a QA leader I had to choose between run a full check of a new functionality that wasnt very popular or use or let the change pass over with the aprove of the PM for some time saving. I choose run the full check, take a few days more, but when the functionality goes to production it works well, without any bugs.

I try to understand their point of view and be open to new ideas. If I listen without being defensive I know  the other party will also listen. That way we can take the best idea from both and come up with great solution.

i think about my audience and what i want them to learn from the conversation so we can arrive at the right co-constructed decision. tha tmeans i communicate in the tone thats strongest for me, first, then adapted in voice for my particular colleagues. im consistent, but then meet them where they are or in the way theyre most likely to engage.

• There was a time the team was developed a search optimization capbility for users based on given requirements by product manager, so it could add more search filters for faster accessibility so . I asked the team to create demo on dev environment and to show customer, in order to make sure it is aligned with users need. I scheduled the meeting and we showed the demo, suddenly we undrestood all the usecase were not covered by program manager which lead to poor design it means some of the file type were not identified by specific locations. And that wasn't a feature for customer. On the other side we didn't have enough time. Since we needed to release this feature on time and as manula accessibility got block the program ​
• ​
• So I pushed the product manager to schedule meeting with diverse useres to make sure to capture diverse uses cases. I put together team and we discussed on options and tried reestimate we identified that by one more api resource we can have this feature on time. So I escalae that to leadership since the timeline was crucial for them, they assign api resource from india Lesson learned: 25 percent ​