The most comprehensive bank Interview Answer Review tooling available online.

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.

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.

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.

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.