Senior Product Engineer - Payments Risk

Role Overview

WeTravel is building the systems that determine whether trip organizers can accept payments, how much of their funds should be reserved, and when payouts can be released. You will lead the engineering of these decisions from initial assessment through the life of an account, turning manual risk reviews into reliable, data-informed workflows that protect the business without creating unnecessary friction for legitimate organizers.

Key Responsibilities

• Lead risk-system projects from discovery and product definition through design, implementation, launch, and ongoing performance monitoring.
• Collaborate with Product, Payment Operations, and KYC and Verification teams to identify decision-making gaps and translate them into practical engineering solutions.
• Develop account assessment and review capabilities that use business strength, exposure, disputes, balances, payout history, and verification status to guide decisions.
• Build reserve and payout controls that better reflect organizers’ expected obligations to suppliers, rather than relying only on blanket percentages.
• Improve the information available to reviewers so they can assess an account quickly and make consistent, well-supported decisions.
• Determine which risk signals and review steps should be automated, while weighing financial protection against the impact on organizers.
• Take responsibility for the reliability of systems that affect funds, including production on-call participation, incident response, and post-mortem follow-up.
• Contribute to engineering standards and help colleagues make effective, responsible use of AI-assisted development tools.

Requirements & Qualifications

• At least 7 years of product engineering experience, including 4 or more years building risk, fraud, or underwriting systems that govern real-money transactions.
• Strong knowledge of financial decision systems, such as exposure and credit models, rules or decision engines, reserves, payout limits, transaction monitoring, and ledgers.
• Advanced backend engineering skills in Ruby on Rails, Kotlin, Python, Go, Java, Node.js, or a comparable language, with the ability to become productive in Ruby if needed.
• Hands-on production operations experience, including taking on-call shifts, leading incident response, and writing post-mortems.
• Clear written and verbal communication skills, with experience working across functions and in distributed, multicultural teams.
• Practical experience using AI tools to improve engineering workflows, along with the ability to share AI concepts and practices with teammates.
• Experience at a merchant of record, payment facilitator, marketplace, or lender is an advantage, particularly where the platform bears potential losses.
• Experience replacing manual underwriting or recurring account reviews with automated processes is preferred.

What We Offer / Why Join

• Work on consequential financial decisions where a single system or policy change can have significant monetary impact.
• Help build infrastructure for group travel payments, serving organizers and travelers around the world.
• Take on complex engineering challenges involving dependable financial systems and responsive user experiences.
• Influence engineering practices and team culture while mentoring colleagues and promoting high standards.
• Remote-friendly work, flexibility, competitive compensation, and generous paid time off.

2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2

• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2
• 2