Product leader Engineering foundation
At Complyance, I work across the product experience for direct customers and partners. That includes country expansion, onboarding, platform and API flows, pricing, and the execution needed to make those pieces hold together.
Product at Complyance
Product core
Living systemScroll to change its state
Inside the system
The product is the core. The difficult work lives in the forces around it.
A market can be ready for development long before it is ready for customers. I separate the signals so teams can move with confidence without manufacturing certainty.
Build. Prove. Interoperate. Approve.
Partner work continues through onboarding, mapping, invoicing, visibility, and recovery. A green response matters, but only inside the complete path.
Visible is not the same as valid.
Packaging decisions become entitlements, allocations, quotes, checkout behaviour, and support obligations. The commercial rule has to survive implementation.
A test can prove a rule. It cannot approve a price.
The source, assumption, test, owner, and remaining uncertainty should travel together. That is how a team distinguishes momentum from wishful thinking.
Proof is part of the product system.
Field note 01
Most of my work begins where the clean product brief ends. A country requirement changes. A partner flow exposes a gap. A commercial decision needs product and engineering judgment in the same room.
What I work on
Turning country requirements, customer needs, and platform constraints into a product people can actually use.
Working across onboarding, operational workflows, and API journeys for finance teams, ERP partners, and ISVs.
Connecting packaging and pricing choices to real product behaviour, delivery cost, and customer value.
Using agents to move faster through research, specification, implementation, and QA while keeping human judgment in the loop.
Inside the work
My work sits inside regulated systems, where a clean interface can hide unresolved operational, technical, or commercial questions. These are a few problems I keep returning to.
A market can be ready for development long before it is ready for customers. I work on separating build readiness, local proof, external interoperability, and market approval, so teams know what can move and what still needs evidence.
Readiness is a set of gates, not a percentage.
Pricing decisions eventually become entitlements, allocations, quotes, checkout behaviour, and support obligations. I work on translating commercial policy into versioned rules that can be tested, while keeping candidate decisions private until the evidence and approvals are there.
A passing test can prove a rule. It cannot approve a price.
An API can return a successful response while the partner experience remains broken. I trace the full path through onboarding, mapping, invoicing, visibility, and recovery, then separate partial proof from complete readiness.
Visible is not the same as valid.
How I work
Regulated products reward patience with detail. I like work where the answer has to survive contact with customers, engineers, operations, and the underlying rule.
The visible feature is usually one part of a longer path through regulation, data, APIs, operations, and support.
A decision is stronger when the source, assumption, test, and remaining uncertainty stay attached to it.
My engineering background helps me challenge abstractions, work directly with implementation details, and make better tradeoffs.
CurrentlyProduct at Complyance
Background
I started in software engineering, working close to the code and the people using it. Over time, the questions I cared about moved outward: which problem deserves attention, how the whole journey fits together, and what tradeoff the business can defend.
That path now informs my work at Complyance. I can move between a customer workflow, an API contract, a country requirement, and a pricing assumption without treating them as separate worlds.
Earlier engineering work on GitHubGet in touch
Especially when regulation, platforms, AI, or commercial decisions make the obvious answer less obvious.