Can you give an example of a situation where you saw a problem coming and came up with a strategy to prevent it?

Situation - We were migrating from the legacy stack to the new stack and we had different integration with our partner teams. All the partner teams provided sign off on their integrations but still we were finding bugs when we were doing the testing from our end.

Action - I set up meetings with all our partner teams individually to understand their design and how they integrated with our tech stack. I also worked with them to understand what testing they conducted from their and how the testing was done, verified their test results. Had an engineer from the team to work with them to get the details on the testing done and ensured all the different edge cases were covered.

Result - We were able to find multiple gaps and new integrations that were needed earlier in the development cycle before going ahead with the launch which helped in ensuring we had no issues post launch and all the partner teams are on-boarded successfully.

At X bank , the auth team moved from stateful auth to JWT token and will become common mechanism for authentication for mobile app and back office team like CRM , the rules were simple that token will expire in 30 min , and user again need to authenticate him self , when these solutions were discussed I saw one major drawback as CS agent were working on CRM through out the day , it will decrease there throughput to login every 30 mins again and again and will decrease there productivity as any unsaved changes can be lost.

So I cam with a solution that based on the configuration(from where the token is being used), tokens can be regenerateed For example for app we will not regenerate the token but for CRM we will generate the token based on some limit like 12 refresh per day so that back office team is not affected and limiting the refresh will not impact the security of product as any one could have gamed the system.