Rakuten

I built a small internal tool that quietly saved the QA team about two hundred hours a year — the unglamorous kind of automation nobody notices until you take it away, and exactly the kind of thing that pays for itself a hundred times over precisely because nobody has to think about it again.

I also worked directly with a team at Google to fix a battery-drain problem on Rakuten Bank's Android app, used by sixteen million people. Most people know Rakuten for e-commerce; Rakuten Group also runs a bank, and “this app drains my battery” is the kind of complaint that gets a banking app deleted, not just tolerated. Fixing it meant working inside someone else's review process and technical standards, not just my own team's — a different discipline than shipping alone.

Separately, I moved the release process onto a Jenkins pipeline for staging-to-release, and shipped a transaction-filtering feature into production. Neither shows up in a demo. Both are the difference between a team that ships confidently every week and one that's scared to.