FintechSystems ThinkingProduct Execution
I help teams build products people trust—by understanding both the user journey and the systems behind it.
7+ years in fintech across GoPay and Tokopedia. I bring engineering rigor, product thinking, and cross-functional execution to complex product work.
User Trust
Useful · Usable · Reliable
Previously part of teams at
Computer Science — Universitas Indonesia
Philosophy
Great products emerge when quality, user needs, and business outcomes align.
Systems Thinking
I look beyond individual features to understand how products, users, and technical systems interact. A bug is never just a bug—it is a signal about system design, team alignment, or product clarity.
User-Centered Execution
I use data, feedback, and observation to identify problems worth solving. Execution without user validation is just motion. I care about shipping things that matter to the people using them.
Shift-Left Quality
Quality starts during discovery, not after development. The most expensive bugs are the ones built into the wrong feature. I bring a testing mindset into every phase of product thinking.
Featured Work
The work that shaped how I think about product and coordination.
More projects in progress. Each will reflect a different challenge: integration, growth, or user experience.
TokoFood Integration
The TokoFood integration was one of the first cross-organizational product initiatives following the GoJek–Tokopedia merger. Tokopedia's marketplace and its food delivery vertical had operated as entirely separate user experiences—a shopper who wanted to order food had to leave the app, creating friction that gave more integrated competitors an advantage. Bringing food discovery, ordering, and payment into the Tokopedia app required coordinating teams across the newly merged GoTo ecosystem, working across different backend systems, infrastructure, terminology, and organizational structures. My role was Test Engineer. At Tokopedia, test engineers participated actively in cross-functional planning and quality leadership—in practice, this meant I was involved from the start across product, engineering, and release coordination, not only QA execution.
Wise: What Happens After You Hit Send
Independent analysis. Not affiliated with Wise. Conducted as a genuine first-time user.
International money transfer carries a tension most financial products don't: the user must act before knowing the outcome. You enter an amount, confirm a recipient, authorize a payment — and then wait. I wanted to understand at what point in the Wise first-transfer experience anxiety peaks, and whether the product's design addresses it. The analysis is based on a first-hand walkthrough of the IDR → GBP corridor as a genuine first-time user, supplemented by App Store review analysis.
What Testing Taught Me
Testing taught me to start with failure.
Test engineering teaches you to read a product backwards. Start from the failure—the moment the user is left stranded, confused, or let down—and work back to the decision that caused it. The habit of asking "what has to be true for this to break?" is the same question a PM needs to ask before committing to scope.
That background does not make me a cautious PM. It makes me a precise one. I know where the risk lives in a system before I write the first requirement. I know which dependencies are actually fragile, which metrics are actually meaningful, and which bugs are really user problems dressed up as code errors. The difference between a PM who ships and one who ships something useful is usually whether they asked the right questions at the start.
- Systems thinking before feature requests.
- Failure modes as user empathy.
- Risk as a product variable.
- Quality starts in discovery.
- Every bug is a user story.
- Knowing where requirements break before writing them.
About
The most interesting bugs were never technical problems.
I studied computer science at Universitas Indonesia and moved into quality engineering because it put me closest to the product. QA is where you learn how users actually interact with a system — not how the team imagined they would. I spent years at GoTo Financial and Tokopedia doing that work: building test infrastructure, coordinating cross-team releases, and filing bugs that kept turning out to be product decisions in disguise.
The move to product management wasn't a pivot. It was a direction the work had been pointing toward for years. The questions I kept asking — why are we building this, who fails when this breaks, what's the simplest version that solves the real problem — are product questions. I wanted to be in the room where those decisions get made, not downstream of them.
I'm drawn to fintech because the stakes are real and the systems are genuinely complex. Getting a payment experience right isn't a UX problem. It's a trust problem — and trust is built through every edge case the team thought to handle before the user encountered it.
Location
Jakarta, Indonesia
Experience
7+ years, fintech & marketplace
Companies
GoTo Financial · Tokopedia
Education
Computer Science, Universitas Indonesia