Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Senior Backend Engineer
Review the role, location requirements, compensation details, and application process before deciding whether this opportunity fits your next career move.
- Salary
- USD 230k–230k / yr
- Department
- Software Engineering
- Employment
- Full Time
- Experience
- Senior
- Published
- Apply before
- 25 Nov 2026
- Listing views
- 49
- Application actions
- 3
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
The role, at a glance.
RevenueCat is hiring a senior individual-contributor backend engineer to own end-to-end product capabilities for a high-scale mobile subscription platform. The role covers problem scoping, architecture, implementation, production rollout, observability, incident response, and long-term maintenance. Candidates need at least eight years of backend engineering experience, strong SQL skills, and ideally Python and PostgreSQL expertise. This remote role emphasizes pragmatic delivery, customer empathy, clear asynchronous communication, and technical leadership through reviews and mentorship. The engineer will contribute to reliability, scalability, performance, and product direction while participating in an on-call rotation.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
5/5Autonomy Level
5/5Communication Load
5/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I start by clarifying the customer problem, success metrics, constraints, and operational risks. I then propose a small, measurable initial scope, align with product and stakeholders, implement and test the solution, instrument it for adoption and reliability, and use production feedback to iterate.
I would first define the affected endpoints and compare latency, error, and database metrics before and after the regression. I would inspect query plans, slow-query logs, lock contention, indexes, connection-pool behavior, and recent releases, then validate a targeted fix with load testing and production monitoring.
I separate irreversible or high-risk decisions from changes that can be safely iterated. I protect correctness, security, observability, and rollback capability, while reducing nonessential scope so the team can deliver customer value early and improve it using real usage data.
I would first learn the architecture, dashboards, logs, runbooks, common failure modes, and escalation paths. During incidents, I communicate status clearly, prioritize mitigation and customer impact, document findings, and drive follow-up work that prevents recurrence.
I use AI tools to accelerate routine exploration, boilerplate, and alternative implementation ideas, but I retain responsibility for the design and correctness. I review generated code carefully, verify assumptions with tests and documentation, and assess security, performance, and maintainability before shipping.
About this role.
RevenueCat gives app businesses the infrastructure and tools to build, run, and improve their monetization. Since graduating from YC’s S18 batch, we’ve grown into the default monetization platform for mobile.
We’re in 50%+ of newly shipped subscription apps, we process $16B+ in annual purchase volume, and we help everyone from a solo developer to the OpenAI mobile team understand and grow their revenue.
We’re a remote-first team of 150+ people across 25+ countries, guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance.
This isn’t the right fit for everyone. The systems you’ll build here manage billions of dollars and touch hundreds of millions of end users, and we don’t take that lightly. You’ll be expected to work hard and hold a high bar for what you ship, alongside some of the sharpest, most driven people you’ve worked with. If that sounds energizing rather than exhausting, keep reading.
The Role
We’re looking for a Backend Engineer to design, build, ship, and own end-to-end product features used by thousands of developers and hundreds of millions of end-users.
This is a hands-on IC role. We want someone that loves shipping products, not just code. You are an engineer obsessed with the customer and passionate about software. You’ll take ownership from problem scoping to production rollout to long-term maintenance. You have both the engineering fundamentals to write performant systems that operate at huge scale near flawlessly and the product sense that doesn’t let “perfect” get in the way of “shipped today.”
About You
You have 8+ years of experience as a backend engineer designing complex, fast-growing systems that didn’t exist before you.
You can write advanced SQL statements beyond basic SELECT and UPDATE statements.
You hold a high bar for quality and instinctively know which details matter, but also are discerning enough to cut scope when needed while still delivering value.
You’re customer-obsessed: you imagine yourself as the developer, product manager, or marketer using the feature or experiencing the issue.
You’re a builder, not an implementer: scoping, prioritizing, and driving rollout in partnership with our Product team. This isn’t a role where you check off items from a detailed specification.
You can quickly familiarize yourself with code you didn’t write yourself and improve it.
You’re comfortable coding alongside AI tools like Copilot, Cursor, or Claude Code. You use them to move faster on the parts that don’t need your full attention, and you’re detail-oriented enough to catch when they’re wrong.
You’re scrappy and biased toward shipping. You’d rather ship a good version today and iterate than wait to ship a perfect one next quarter.
You communicate clearly, both in real-time and asynchronously. We’re a fully remote team, and how you write is as important as how you code.
You’ve shipped meaningful user-facing features to production, monitored their usage and adoption, and improved them over time.
You write high-quality, well-tested code, debug issues methodically, and help raise the engineering bar through thoughtful feedback and mentorship.
You act like a founder: you notice problems, propose improvements, and follow through fast.
Ideally, you have:
Experience in Python.
Experience in PostgreSQL.
Experience building SDKs.
Shipped a mobile app with in-app purchases.
Some experience with React and SPA applications.
In the first month, you’ll:
Meet frequently with your team and mentor to get up to speed.
Set up and get familiar with repositories, task management, and the dev environment.
Implement and ship your first project.
Get familiar with RevenueCat’s dashboards, logging, debugging tools, cloud providers, infrastructure, and general architecture.
Learn about the mobile app economy and subscription-business concepts that shape our product decisions.
Within the first 3 months, you’ll
Scope and work on projects self-sufficiently, end to end.
Talk to customers or support directly to understand how the systems you own actually get used and where they break down.
Learn the basics of incident response and join the on-call rotation.
Participate in code reviews and contribute to reliability and quality across the codebase.
Understand every product your team owns.
Within the first 6 months, you’ll
Review code, write proposals, and contribute to architectural discussions.
Contribute to your team’s roadmap and technical direction — the “why,” not just the “how.”
Be the go-to person on a couple of your team’s focus areas.
Have shipped a major product or feature, start to finish.
Within the first 12 months, you’ll
Know all the major components of our system and be able to debug complex issues across it.
Have your own initiatives for improving our products, grounded in real customer and business priorities.
Spec and architect medium-to-large projects, gather feedback, and drive design validation and rollout plans.
Mentor other engineers joining the team.
Push the org to improve reliability, scalability, and performance.
What we offer:
Competitive equity in a fast-growing, Series C startup backed by top-tier investors, including Y Combinator
10-year window to exercise vested equity options
A fully remote environment designed around autonomy and flexibility
4-5 weeks of flexible time off annually
Paid desk at a co-working space
Workspace budget and continuous learning stipend
Interviewing at RevenueCat
Our interview process is rigorous on purpose. We want to be sure that everyone we bring on is genuinely excited about this work, aligned with how we operate, and ready to meet our high bar for performance. Curious what that actually looks like? Read more in our blog post on how we hire at RevenueCat, including tips to help you succeed.
More on how we work:
How we think about hiring and team design: Building a Winning Team
The values that guide how we work: Our Values
How we work as a remote team: How We Work Remotely at RevenueCat
What to expect from our interview process: Interview Expectations
What to expect from comp and employment: Employment FAQ
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.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
