Rakuten Rewards
Senior Staff Software Engineer · iOS
2015 — present
One iOS app used by millions, and eleven years owning what it was built on.
Cash Back shopping at thousands of stores, online and in person — and the iPhone app millions of people keep on their home screen to get it.
- iOS
- Swift
- SwiftUI
- UIKit
- Objective-C
- CI/CD
- Release engineering
Highlights
- Eleven years on the same product, taking on more of the platform every couple of years.
- Owned client architecture for a large consumer app and the shared foundations several product teams built on.
- Planned and drove multi-team projects end to end, across iOS and Android.
- Mentored more than ten engineers across teams, mostly by proposal and example — writing the first version, proving the pattern, then handing it on.
- Owned the release, CI and quality systems that carried continuous shipping.
- Modernized a long-lived codebase without ever stopping the release train.
How the job has changed
-
2023 — present
Setting the direction
Most of what I do now lands through other engineers: the architecture I propose, the reviews I give, the patterns that outlast the project that started them. I’m still writing code every week, because direction is a lot sharper coming from someone who is actually shipping.
-
2021 — 2023
Foundations and tooling
I moved off features and onto the shared foundations, and onto the tooling around building, testing and shipping. It’s the highest-leverage code in the building: write it once and every product team is faster on top of it.
-
2017 — 2021
The calls that spanned the app
Features start to finish, plus the decisions that reached past one screen — the ones where the answer had to hold for the whole codebase, not just the thing in front of me.
-
2015 — 2017
Learning a codebase with history in it
I joined the iOS team in an Objective-C codebase with years of decisions already baked into it. I learned my way around fast, and shipped features to millions of people.
