All remote jobs

Senior Backend Engineer (Mobile Monetization) | Feeld

AI Summary
This is a senior backend engineering role focused on the subscription, in-app purchase, billing, and entitlement systems of Feeld's mobile application. The engineer will own revenue-critical services, build scalable Node.js and TypeScript APIs, and integrate mobile monetization platforms such as RevenueCat or Adapty. Core work includes receipt processing, subscription lifecycle management, payment-data synchronization, production reliability, and experimentation instrumentation. The role requires independent architectural decision-making and close collaboration with Product, Engineering, and Data teams. Remote eligibility is limited to Poland, Portugal, and Spain.
Remote from
Spain, Portugal, Poland
Salary
Undisclosed
Employment
Full Time
Experience
Director
Published
Apply before
11 Dec 2026
Listing views
31
Application actions
2
Application toolkit

Make your next move.

Prepare your resume, explore your fit, and draft a cover letter for this opportunity.

Opportunity details

About this role.

GT was founded in 2019 by a former Apple, Nest, and Google executive. GT’s mission is to connect the world’s best talent with product careers offered by high-growth companies in the UK, USA, Canada, Germany, and the Netherlands.

On behalf of Feeld, GT is looking for a Senior Backend Engineer to help them improve their inclusive dating application.

About the Client

Founded in 2014 as a dating app, Feeld gathered millions of users in one place to create a safer and more inclusive space online for everyone open to experiencing people and relationships in a new way. Their mission is to elevate the human experience of sexuality and relationships and create a world where everyone is more intimately connected to each other and themselves.

The technology stack of the project: Node.js, NestJS, GraphQL/REST, TypeScript, AWS, DynamoDB, PostgreSQL, SQS, EventBridge, WebSockets.

About the Role

We are looking for a Senior Backend Engineer (Mobile Monetisation) to take ownership of the backend systems powering Feeld’s subscription and in-app purchase experiences across iOS and Android.

The ideal candidate brings strong hands-on experience with mobile monetisation platforms such as Adapty, RevenueCat, or similar solutions, as well as integrating mobile payment flows with custom backend services. This includes managing subscription lifecycles, synchronising payment data, handling receipts, and ensuring accurate entitlement management.

We’re looking for a highly experienced, proactive engineer with the potential to act as a technical lead, capable of independently driving complex technical initiatives, contributing to architectural decisions, and ensuring the reliability and scalability of revenue-critical systems.

📌 Full-time, long-term
⌛️ Preferred immediate start

Responsibilities:

  • Take ownership of the backend systems supporting Feeld’s monetisation, ensuring their reliability, performance, and contribution to business goals.

  • Design, develop, and maintain scalable backend services and integrations for subscriptions, billing, payment processing, entitlements, pricing, and promotional features.

  • Ensure the accuracy, stability, and reliability of monetisation flows, proactively identifying and resolving production issues that could impact revenue or user experience.

  • Support the development and optimisation of subscription and payment flows, including improvements to system performance, scalability, and error handling.

  • Implement and maintain feature flags, testing, and analytics instrumentation to support experimentation and continuous improvement of monetisation features.

  • Collaborate with Product, Engineering, and Data teams to build and improve analytics and reporting capabilities, providing insights into revenue performance, user behaviour, and system health.

Essential knowledge, skills & experience:

  • 5+ years of commercial backend development experience, ideally building high-load, business-critical systems.

  • Proven experience with mobile monetisation and subscription platforms, such as Adapty, RevenueCat, or comparable solutions.

  • Hands-on experience implementing mobile in-app purchases and subscription flows for iOS and/or Android applications, beyond web-based payment integrations.

  • Experience integrating mobile payment platforms with custom backend systems, including payment data synchronisation, receipt handling, subscription status tracking, and entitlement management.

  • Strong understanding of mobile subscription and payment lifecycles, including renewals, cancellations, refunds, failed payments, and subscription state changes.

  • Experience ensuring the accuracy, reliability, and consistency of revenue-critical backend systems, including troubleshooting production issues.

  • Strong backend development experience with Node.js or TypeScript or JavaScript, ideally using NestJS and building GraphQL or REST APIs.

  • Good understanding of event-driven architectures, asynchronous processing, and distributed systems.

  • Experience writing reliable unit and integration tests.

  • Strong technical ownership, independent problem-solving, and architectural decision-making skills, with the potential to take on technical leadership responsibilities.

  • Strong communication skills and full professional proficiency in English.

Nice to Have

  • Experience with AWS cloud infrastructure, SQL and NoSQL databases. Our current stack includes ECS, DynamoDB, SQS, EventBridge, and PostgreSQL.

  • Experience working directly with Apple App Store and Google Play billing ecosystems.

  • Experience running monetisation experiments, including A/B testing, subscription pricing changes, and conversion optimisation.

  • Experience managing regional pricing, multiple currencies, and country-specific monetisation strategies.

  • Experience analysing the performance of monetisation experiments, including revenue, subscription conversion, and retention metrics.

  • Previous experience acting as a Tech Lead or Lead Backend Engineer, mentoring engineers, and driving technical decisions.

Interview Steps

  1. GT interview with Recruiter

  2. GT technical interview

  3. Client technical interview

  4. Final interview

  5. Reference Check

  6. Offer

Apply now >

This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.

Role DNA

A quick view of the complexity, pace, ownership and collaboration implied by the job description.

Job Complexity

5/5
EasyHard

Pace & Pressure

4/5
RelaxedFast-paced

Autonomy Level

5/5
GuidedFull ownership

Communication Load

4/5
IndependentCollaborative
AI insightThe role owns business-critical monetization infrastructure where failures can directly affect revenue, subscriptions, and user experience. It requires deep mobile billing knowledge, distributed-systems expertise, and the ability to lead complex technical decisions independently.

Salary analysis

Estimated compensation compared with the broader US market for similar roles.

Estimated job median (per year)Market rate
$150,000
US market range (per year)$135k–$175k
AI insightThe yearly pay period is inferred from the job context; it was not explicitly stated by the employer. No employer compensation was disclosed. The annual figures are estimated USD base-pay benchmarks for a senior backend engineer specializing in mobile monetization and revenue-critical systems; the yearly period is inferred from the full-time senior professional role.

Core skills

Skills and capabilities most closely associated with this opportunity.

Sample interview questions
How would you design a backend service to keep subscription entitlements synchronized across Apple App Store, Google Play, and an internal application database?

I would use provider webhooks and periodic reconciliation jobs as authoritative event sources, storing immutable payment events and deriving entitlement state idempotently. The service would validate receipts or provider events, use durable queues for asynchronous processing, and maintain audit trails, retry policies, and alerting for failed or inconsistent updates.

What are the most important edge cases in a mobile subscription lifecycle?

Key cases include renewals, cancellations, grace periods, billing retries, refunds, chargebacks, upgrades and downgrades, introductory offers, expired receipts, delayed webhooks, and duplicate events. The system should treat provider notifications as eventually consistent and make all state transitions idempotent.

How would you investigate a production incident where users report paid subscriptions but do not receive premium access?

I would first assess scope and impact using entitlement, payment, and error metrics. I would trace affected transaction identifiers through webhook ingestion, queue processing, receipt validation, and entitlement persistence, then apply a safe remediation such as replaying idempotent events or reconciling the affected accounts while documenting the root cause and preventive monitoring.

How would you use event-driven architecture for monetization features?

I would publish domain events such as subscription purchased, renewed, canceled, refunded, or entitlement changed. Independent consumers could update entitlements, analytics, notifications, and reporting, while queues and dead-letter handling would isolate failures and preserve reliable processing.

How would you evaluate a subscription pricing or onboarding experiment technically?

I would use feature flags and deterministic user assignment, record exposure events before conversion events, and define clear success metrics such as conversion, retention, refund rate, and net revenue. I would ensure analytics events are reliable, protect against sample-ratio mismatches, and coordinate rollout and rollback criteria with Product and Data teams.

This analysis is generated from the job description. Salary estimates, role characteristics and sample answers are guidance, not employer-provided facts.
Next step

Apply now.

Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.

Did you apply?Let us know, and we’ll help you track your application.

Continue on the employer website

Protect your personal information and never pay to secure an interview or job offer. .

Log in to save
One quick step before you apply

Sign in to continue.

Sign in or create a free account to continue to the employer's application.

Add alert
Jobs Talent AI Tools Salaries
Menu