Note: The job is a remote job and is open to candidates in USA. Growe is seeking a Payment Product Manager to lead the evolution and regional migration of its payment hub. The role owns payment system behavior, operational back-office tools, cross-system discovery, rollout sequencing, stakeholder alignment, and post-launch operational processes.
Responsibilities
- Decide how the hub behaves: make system behavior explicit (such as callback timeouts, withdrawal hold and release rules, gateway configuration setups, and player-facing error messages) rather than leaving these details in engineers' heads or partner systems
- Own the back office: drive and optimize the seven core operational screens used daily by internal teams (projects, gateways, payment groups, methods, orders, transactions, and logs) to ensure the hub remains fully usable
- Run discovery against internal systems: lead timeboxed spikes across eleven internal systems (including player accounts, wallet, KYC, fraud checks, reconciliation, and taxation) to rank findings by risk and resolve unknowns before they turn into rework
- Sequence the regional migration: define rollout stages, set validation rules using small percentages of live traffic and historical transaction replays, establish criteria for moving to the next step, and prepare clear rollback plans
- Keep regional teams aligned and informed: maintain strong trust and clear communication with local operations, support, and business owners regarding upcoming changes, potential risks, and contingency plans
- Plan for life after launch: establish operational processes for incident management, configuration changes, new method onboarding, and ongoing integration health once a region goes live
Skills
- 4+ years of product management experience, with at least 2 years in payments, fintech, or complex transactional systems, holding ownership over a product area rather than just managing a backlog
- Ability to read API contracts and follow a transaction across multiple systems independently
- Proven track record of writing clear requirements, with explicit outcomes, clear acceptance criteria, and well-defined boundaries
- Data-driven approach to product decisions, working comfortably with conversion, approval rates, failure reasons, and cost per transaction to separate signal from noise
- At least Intermediate level of English for all documentation, ticketing, and daily cross-team communication
- Comfort operating in ambiguity, with a knack for designing the smallest possible experiment to remove doubt when answers do not yet exist
- Strong sense of ownership and transparent communication, with the drive to inform affected regions early and plainly whenever something goes wrong
- Problem-solving skills - focus on reducing complexity, closing unknowns early, and preventing rework before development starts
Company Overview