Senior Product Engineer - Payments Risk

W

Senior Product Engineer - Payments Risk

WeTravel

Yesterday

New

Nairobi

Full Time

Confidential

Share link

Share on WhatsApp

Share on LinkedIn

Share on Facebook

Share on Twitter

Share via SMS

Language Requirement:

English

Work Type:

Full Time

Working Hours:

8 to 5

Applicant Location:

Kenya

Job descriptions & requirements

Every organizer collecting payments on WeTravel passes through a series of decisions: whether they can sell their trips and products here, how much of their payout we hold back and how quickly we release it, and what happens when a good account starts going bad. Today these decisions are still largely manual and they will not scale to $10B. Your job is to make them sharper and faster, and to take the manual work out of them. You will own the systems behind them.

Some major problems worth solving:

Assessing an organizer at signup and then through the life of the account, so how much we hold payout and how quickly we release it reflects how strong the business actually is.

Reserves that track what an organizer actually owes their suppliers on a given trip, so a hold reflects real forward obligations rather than a flat percentage.

Exposure, disputes, balances, payout history, and verification state in one place, so a decision takes minutes rather than hours.

What you’ll do day-to-day:

Lead projects end-to-end: discovery with Product, Payment Operations and our KYC/Verification team, solution design, build, rollout, and the monitoring that proves it works.

Shape how we decide, not only how it gets built. What we assess, what we measure, and which manual steps automation should take over are all yours to influence.

Weigh protection against user experience. Anything you build has a cost to a legitimate organizer, and finding that balance is part of the work.

Own the reliability of what you ship, and help raise the engineering bar across the team.

How we work:

We’re focused on the impact. We don’t subscribe to any one framework or execution ideology, and we adapt based on what’s impactful.

We’re using the latest hardware and constantly on the look out for better tools & ways to work.

We have AI-first development experience and work with the latest models and agentic dev tools.

Stack: We’re developing React/TypeScript, Ruby on Rails and Kotlin Microservices. Our services run on Kubernetes. We also use and love MongoDB, MySQL, Postgres, Cockroach DB, Snowflake and we’re working with the major LLM providers.

You should apply if you have:

Basic qualifications:

7+ years of product engineering expertise, with 4+ years dedicated to risk, fraud, or underwriting systems that move real money.

Deep expertise in the systems that decide about money, such as exposure and credit models, decision and rules engines, holds, reserves and payout limits, transaction monitoring, and the ledger those balances sit on.

Strong backend mastery in Ruby on Rails, Kotlin, Python, Go, Java, or Node.js with the agility to ramp up on Ruby quickly.

Direct production on-call experience, including authoring post-mortems and leading incident response.

Excellent written and verbal communication skills, including cross-functional collaboration experience, and the ability to thrive in a distributed, multicultural environment.

Pragmatic adoption of AI tools to optimize your engineering workflow, including the ability to mentor and train others on AI concepts.

Preferred Qualifications

• Experience at a merchant of record, payment facilitator, marketplace, or lender, where the platform carried the loss rather than passing it on.
• Experience automating an underwriting or periodic review program that previously ran on manual review.
• You might not be the right fit if you:
• Your risk expertise is limited to tuning rules in a vendor dashboard like Stripe Radar or Persona. We need someone who builds the engine underneath and owns what it does to real balances.
• You are hesitant to take full ownership of mission-critical money movement or participate in the on-call rotation when systems fail.
• You need complete data and settled requirements before you will commit to a decision. Risk work means making the call on partial information and sharpening it as more arrives.
• You are looking for a siloed IC position without the need for cross-functional collaboration or product-level discovery.
• You require a rigid, pre-defined roadmap; we prefer to sharpen our strategy and direction as we scale the team.
• Every organizer collecting payments on WeTravel passes through a series of decisions: whether they can sell their trips and products here, how much of their payout we hold back and how quickly we release it, and what happens when a good account starts going bad. Today these decisions are still largely manual and they will not scale to $10B. Your job is to make them sharper and faster, and to take the manual work out of them. You will own the systems behind them.
• Some major problems worth solving:
• Assessing an organizer at signup and then through the life of the account, so how much we hold payout and how quickly we release it reflects how strong the business actually is.
• Reserves that track what an organizer actually owes their suppliers on a given trip, so a hold reflects real forward obligations rather than a flat percentage.
• Exposure, disputes, balances, payout history, and verification state in one place, so a decision takes minutes rather than hours.
• What you’ll do day-to-day:
• Lead projects end-to-end: discovery with Product, Payment Operations and our KYC/Verification team, solution design, build, rollout, and the monitoring that proves it works.
• Shape how we decide, not only how it gets built. What we assess, what we measure, and which manual steps automation should take over are all yours to influence.
• Weigh protection against user experience. Anything you build has a cost to a legitimate organizer, and finding that balance is part of the work.
• Own the reliability of what you ship, and help raise the engineering bar across the team.
• How we work:
• We’re focused on the impact. We don’t subscribe to any one framework or execution ideology, and we adapt based on what’s impactful.
• We’re using the latest hardware and constantly on the look out for better tools & ways to work.
• We have AI-first development experience and work with the latest models and agentic dev tools.
• Stack: We’re developing React/TypeScript, Ruby on Rails and Kotlin Microservices. Our services run on Kubernetes. We also use and love MongoDB, MySQL, Postgres, Cockroach DB, Snowflake and we’re working with the major LLM providers.
• You should apply if you have:
• Basic qualifications:
• 7+ years of product engineering expertise, with 4+ years dedicated to risk, fraud, or underwriting systems that move real money.
• Deep expertise in the systems that decide about money, such as exposure and credit models, decision and rules engines, holds, reserves and payout limits, transaction monitoring, and the ledger those balances sit on.
• Strong backend mastery in Ruby on Rails, Kotlin, Python, Go, Java, or Node.js with the agility to ramp up on Ruby quickly.
• Direct production on-call experience, including authoring post-mortems and leading incident response.
• Excellent written and verbal communication skills, including cross-functional collaboration experience, and the ability to thrive in a distributed, multicultural environment.
• Pragmatic adoption of AI tools to optimize your engineering workflow, including the ability to mentor and train others on AI concepts.
• Experience at a merchant of record, payment facilitator, marketplace, or lender, where the platform carried the loss rather than passing it on.
• Experience automating an underwriting or periodic review program that previously ran on manual review.
• You might not be the right fit if you:
• Your risk expertise is limited to tuning rules in a vendor dashboard like Stripe Radar or Persona. We need someone who builds the engine underneath and owns what it does to real balances.
• You are hesitant to take full ownership of mission-critical money movement or participate in the on-call rotation when systems fail.
• You need complete data and settled requirements before you will commit to a decision. Risk work means making the call on partial information and sharpening it as more arrives.
• You are looking for a siloed IC position without the need for cross-functional collaboration or product-level discovery.
• You require a rigid, pre-defined roadmap; we prefer to sharpen our strategy and direction as we scale the team.
• Log In and Apply
• Important safety tips
• Do not make any payment without confirming with the BrighterMonday Customer Support Team.
• If you think this advert is not genuine, please report it via the Report Job link below.
• Report Job