Almost 8 years in payments. Currently at Adyen, where I consult enterprise merchants on authorization optimization, ML fraud prevention, smart authentication routing, and payment cost reduction. Before that: built a risk engine from scratch at Paze, pitched fraud tools at PayPal/Braintree, and scaled a fraud team at Chime.
I've never held the title of Product Manager — but I've been doing PM work my entire career: scoping problems, writing specs, shipping systems, and measuring outcomes. I spend my weekends building Cellix.ai because I can't stop thinking about these problems. I'm ready to make the leap into product.
I've spent my career at the intersection of payments, risk, and technology — scoping problems, writing specs, shipping products, and measuring impact. Here's how my experience maps to what Product Managers do every day.
I advise 50+ enterprise merchants at Adyen on authorization rate optimization — designing A/B tests against competing processors, configuring intelligent payment routing, and translating basis-point auth improvements into dollar-denominated merchant revenue. I own the problem end-to-end: diagnosing root causes, recommending product configurations, and measuring outcomes across the full payment funnel.
I help merchants configure ML fraud scoring engines — setting risk thresholds, customizing action-based rules, backtesting rule performance, and tuning the balance between false positives and fraud catch rate. At Paze, I built an entire risk engine from scratch: 90+ signal-layered rules, vendor selection, API integration specs, and precision/recall tuning. This is product ownership in everything but title.
A PM's job is to translate technical capabilities into business value. That's what I do daily — connecting a 0.3% lift in authorization rates to a $2M annual impact for an enterprise merchant, writing the specs that engineering teams build from, and making the case to sales teams in language they can use. I understand the systems deeply enough to challenge assumptions and make trade-offs.
I work with merchants on authentication optimization — smart 3DS routing that applies authentication where required while leveraging exemptions where permitted. The ML models select the optimal auth route per transaction, balancing compliance with conversion. Understanding the regulatory landscape across markets is critical PM context.
Paze launched as a digital wallet with zero fraud infrastructure. I owned the entire buildout: evaluated vendors, wrote technical specs, defined API integration requirements, authored 90+ fraud rules, and ran tuning cycles against board-mandated auth rate targets. Shipped a complete risk engine to production in under 12 months — the kind of 0→1 work that teaches you how products actually get built.
An AI-powered dispute automation platform across 27+ processor integrations — built on nights and weekends. Not to launch a startup. Because after years of watching merchants lose disputes they should win, I wanted to see if I could build something better. From the 14-page technical spec to the ML scoring engine, every decision was a product decision.
Each role brought me deeper into payments — from operations to strategy to optimization. Here's the thread that connects them.
Advising 50+ enterprise merchants on the full Uplift suite — Protect (ML fraud scoring), Authenticate (smart 3DS routing), and Optimize (auth rate optimization). I design A/B tests against competing processors, configure intelligent payment routing, and translate basis-point improvements into merchant revenue. Generated $15M+ in ARR through Protect portfolio expansion. Every day, I'm doing the work of a PM — scoping problems, recommending configurations, measuring impact, and presenting outcomes to stakeholders.
Paze launched competing with Apple Pay and PayPal with zero fraud infrastructure. I owned the entire risk engine architecture: evaluated and onboarded signal vendors, wrote technical specs, defined API integration requirements with engineering, authored 90+ signal-layered fraud rules, and ran precision/recall tuning against board-mandated auth rate targets. Reported directly to the board weekly. This was 0→1 product ownership — the kind of build that teaches you how products actually get shipped.
Pitched fraud tools and risk solutions to enterprise merchants at Braintree/PayPal — covering dispute analytics, fraud recommendations, and compliance dashboards across 500+ accounts. Managed card program risk with Visa and Mastercard, preventing $2M+ in annual fines. Designed the merchant-facing product bundle that drove $500K+ in new ARR. This is where I learned how payment risk works at the enterprise level.
Built and directly managed a team of 10, while scaling the broader fraud ops site from a small pilot to 150+ investigators. Defined case routing logic, SLA frameworks, and accuracy thresholds. Built dispute forecasting models that predicted volume 30 days out and cleared 30% of backlog. This is where I learned how fraud operations actually work — before the ML layer.
Cellix.ai is an AI-powered dispute automation and payment intelligence platform. I built it on nights and weekends because the problem was too interesting not to. It's live in production with 27+ processor integrations.
After years of managing disputes manually across PayPal, seeing merchants struggle with card network compliance, and building fraud systems from scratch at Paze — I kept thinking: this should be automated, and nobody's doing it well. So I started building.
Cellix automates dispute investigations end-to-end — compiling evidence to Visa CE3.0 and Mastercard specs, submitting via processor APIs, and running fraud prevention across the stack. It solves a real industry pain point, and building it taught me more about product thinking than any job could.
Every role I've held has required product thinking — diagnosing merchant pain points, writing technical specs for engineering teams, designing A/B tests, measuring outcomes, and iterating. At Paze, I owned a 0→1 buildout end-to-end. At Adyen, I consult on the same product decisions PMs make internally. The work is the same — the title hasn't caught up yet.
I've worked across fraud operations at Chime, enterprise risk at PayPal/Braintree, risk engine architecture at Paze, and full-funnel payment optimization at Adyen. That breadth means I understand how authorization, fraud, disputes, and compliance interact — not just one slice. Payments PMs need to understand the full system, and I do.
I have a Master's in Data Science (4.0 GPA), hands-on experience building ML scoring engines, and the analytical skills to work alongside data science and engineering teams as a peer — not just a translator. I can query data, interpret model outputs, challenge statistical assumptions, and write specs that engineers can build from directly.
Talk is cheap. I built a production payment intelligence platform on nights and weekends — 27+ integrations, ML scoring, dispute automation, real-time monitoring. Every decision was a product decision: what to build, what to skip, how to scope, when to ship. Cellix.ai is the strongest evidence that I think and operate like a PM.
Most PMs come from engineering, consulting, or business school. I'm coming from almost 8 years on the front lines of the exact domain I want to build products in — with a weekend project that proves I can ship.
I'm ready to bring my domain expertise, builder mindset, and analytical skills to a PM role where I can have even greater impact.