The most comprehensive bank Interview Answer Review tooling available online.

In my current role, I led a team of 6engineers, 3quality analysts and 3 partner account managers to build and deliver a product for enabling integration with tax authorities government portal and partner tech systems to systematically onboard the partners and consume, validate and pay their invoices in line with local authorities regulatory requirements. My role involved partnering with internal xyz transportation business teams of outbound, import and returns business, financial operations, procurement and controllership teams to align on the business and tech requirements, understand the tech integration dependencies, accounting requirments and define the MVP, change management and then drive the go to market strategy through a dial up. 

1. Situation: Our cloud bill had been steadily increasing, but engineering teams lacked visibility into which workloads were driving the cost. Leadership wanted accountability, but SREs like me knew that finger-pointing wouldn’t solve anything without data.

2. Task:I wanted to design a way to give each team ownership of their spend — without adding operational overhead — while also uncovering unused or over-provisioned infrastructure.

3. Action:I built an internal “cost dashboard” that pulled billing data from our cloud provider’s API, tagged resources by team and environment, and visualized it by service, team, and project. But the innovative part was integrating it with our CI/CD workflows: before a PR deploying new infra could be merged, it would estimate the monthly cost impact. I also built a Slack bot that sent weekly team-level cost summaries and flagged idle resources.

4. Result: Within two months, teams identified and shut down $8,000/month in unused dev resources. More importantly, it shifted the culture — infra cost became part of architectural discussions. Finance even started using our dashboard during quarterly planning instead of relying solely on billing exports.

In my role leading the launch of that new customer onboarding system, the pressure was really on. We had that tight three-month window and a lean team to build something that would be the first impression for all our new users. One specific hurdle we faced was integrating our legacy customer database with this brand-new system. The data structures were quite different, and initially, the data migration process was proving to be much slower and more error-prone than anticipated. This threatened to push our launch date.

To tackle this head-on, I didn't just delegate. I dove into the technical details with the lead engineer. We mapped out the data fields meticulously, identified the key transformation rules needed, and actually prototyped a more efficient data migration script using Python. This allowed us to automate a significant portion of the process that was previously manual.

Furthermore, to ensure we were building the right thing quickly, we implemented very short feedback loops. We'd build a small piece of the onboarding flow, get immediate feedback from a small group of internal users, and iterate based on their input. For example, early on, users found a particular step in the registration process confusing. Based on their feedback, we completely redesigned that screen within a couple of days, leading to a much smoother experience.

By getting into the technical weeds to optimize the data migration and by relentlessly focusing on user feedback through rapid iterations, we not only overcame the risk of a delayed launch but also delivered an onboarding experience that was significantly more user-friendly than initially envisioned. It was incredibly rewarding to see new customers move through the system so smoothly right from day one. That success really underscored the power of combining technical problem-solving with a user-centric approach

Situation:

I was laid off from my first job just four months after joining due to budget constraints. This was a major setback for me as I had just started my career. Around the same time, my father suffered a heart attack, which required me to stay at home and take care of him while he was on bed rest for several months. The combination of losing my job and dealing with a family emergency left me feeling devastated, and I struggled to apply for new roles.

Action:

Despite these challenges, I remained determined to grow in my career. While caring for my father, I focused on upskilling myself:

• I attended mentor sessions on ADPList to gain industry insights.

• I reached out to experienced designers on LinkedIn for portfolio reviews and feedback.

• I enrolled in courses through Interaction Design Foundation (IxDF) to expand my knowledge.

• I continuously improved my portfolio and resume, incorporating the feedback I received.

I also actively networked with professionals, which helped me regain confidence and visibility in the industry.

Result:

My persistence paid off. Where I once struggled to pass resume screenings, I started receiving recruiter calls consistently. In fact, this very interview happened because I proactively connected with a senior designer, shared my portfolio, and received a referral for this role. This experience not only strengthened my portfolio and skills but also taught me the power of perseverance, networking, and continuous learning.

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.