Senior Engineer (Payment & Ops)

Hi! We’re Leaply — a product ecosystem in the Health & Wellness niche. Our mission is to create a platform users can fully trust with their health, so they can live healthier on autopilot. We launched in June 2024, found unit economics in less than two weeks, and have already grown to 200K+ users worldwide, with a 4.7 rating on the App Store and 4.4 on Trustpilot (20,000+ reviews). Our team of 60+ specialists is remote-friendly, and English is our working language.

At Leaply, we challenge traditional career paths — we value ownership over job titles, and impact over process. As we scale, we’re looking for a Senior Engineer to build the next generation of our payment infrastructure.

Role Overview:

We’re looking for a Senior Engineer to join Payment & Ops — the area every Leaply payment flows through: processing, subscriptions, and checkout. Today, all processing runs through a single provider (Cards, Apple Pay, PayPal). In your first months, you’ll focus on building alternative processing alongside it.

This is a high-impact individual contributor role for someone who has built payment systems under live traffic and is excited to build one from a clean slate.

You’ll have broad ownership over provider integration, subscription logic, parallel testing and traffic migration, service extraction, and payment observability. Your job is to build a payment infrastructure that no longer depends on a single provider.

Tech stack: NestJS (Node.js / TypeScript), PostgreSQL, GCP (GKE, Cloud Run, Cloud Functions), BigQuery, React / Next.js for internal tools. You don’t need NestJS experience specifically.

What You Will Do:

• Integrate a payment orchestrator or billing provider — onboard the company’s MID and configure payment methods by country. We’re choosing the provider right now, and you’ll take part in that decision

• Design our own subscription module for live traffic — subscription state, rebill scheduling, retries, cancellations, provider adapters, and state reconciliation with providers

• Run the legacy and new infrastructure side by side — A/B test payment flows by country and payment method, and migrate traffic in stages

• Extract the payment module from the monolith into a standalone service with its own database

• Build the payment observability layer — a payment dashboard, a payment data pipeline into BigQuery, and alerts across payment paths

What You’ll Need to Succeed:

• 5+ years of commercial experience in production-grade backend development with Node.js / TypeScript

• Hands-on experience in the payments domain — subscription billing, rebills and retries, chargebacks, and integration of at least one PSP (Stripe, Adyen, Braintree, Solid, or similar)

• Experience designing a service or module from scratch for live traffic — data models, idempotency, queues, webhooks, state reconciliation

• Experience integrating external APIs as a system — rate limits, error handling, retries, monitoring

• Strong ownership — you find risks on your own, come with solutions, and shape your zone’s backlog together with the business side of the squad

• You speak the language of business and can turn technical trade-offs into business impact

• You use AI in your daily work — in coding, code review, and data analysis

It’s great if you have:

• Experience with payment orchestrators (Primer, Spreedly, or similar)

• Experience extracting a module from a monolith into a standalone service

• BigQuery and data pipeline experience

• GCP, Kubernetes, Terraform, Argo CD

• React / Next.js for internal tools (about 10–20% of the time)

Why This Role

Build from a clean slate. Your task is to build a new parallel payment module from scratch, in the area every Leaply payment flows through.

Real ownership. Engineers at Leaply don’t just close tickets from a backlog. They make decisions on par with product, design, and marketing, and drive initiatives from idea to result. You design your module’s architecture and choose the technologies that fit the task.

AI is the standard. At Leaply, AI is how we work, not a trend.

Room to grow. Grow along the IC track, with a path to Tech Lead in the future. You’ll also be able to drive cross-team initiatives in infrastructure, code quality, and engineering culture.