I want to hear about a time when you had to compromise

One requirement was completely missed by the cross-functional team. The requirement pertains to Oracle Transportation Management and involves incorporating a specific lane to deliver goods from the contract manufacturer to the destination warehouse, and subsequently to the customer. This lane includes specific lane sheet changes and logic that needed to be addressed by the cross-track team to accommodate these CDC orders.

Unfortunately, this requirement was overlooked during Test Cycle 2, leading to testing failures. As a result, we had to close Test Cycle 2. Within two weeks, UAT (User Acceptance Testing) and BAT (Business Acceptance Testing) were scheduled to begin. However, the cross-track team required additional time to incorporate the missed requirement.

This left us with limited time to complete testing before UAT and BAT. To meet the project timeline, I collaborated with the team to work over 2-3 weekends, ensuring end-to-end testing and defect resolution were completed. I also convinced the team to accept compensatory time off after the completion of BAT and UAT. Ultimately, the team successfully implemented the change without impacting the overall project timeline.

Sure, back when I was working at OpenText there was an issue related to best framework for automating our test cases. And we had an inhouse framework that was a variation of Selenium so that was present as an option but since I was tasked in finding the best framework that would have better test coverage I ventured out and tried to find a better one. On top of that I just had a two weeks to find a framework and also complete the testing so that the product can go for production. Given the time constraints it was difficult to go for new framework so I had to compromise and complete the test cases using the inhouse framework and then once we had a successful release I made sure to venture out and try out different frameworks like Puppeteer, Playwright. And after that we struck out with Puppeteer but yeah I had to compromise on picking out puppeteer before the release but after the release we migrated towards puppeteer.

When I developed the tools to review the high-risk customers transactions, I started alone and did it in my own way. When I started collaborating with colleagues, they brought their own feedback and had their own ideas on what should be included in the tool; I did not agree with all of their ideas. However what is most important is our common mission, our common goal; since a whole team is going to use this tool, it is important that they feel that their opinion is valued too, and so I compromised and added all of their ideas to the tool.

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.