Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Full-Stack Engineer (Backend Leaning) – Payments Engineering
- Salary
- Undisclosed
- Department
- Software Engineering
- Employment
- Full Time
- Experience
- Open level
- Published
- Apply before
- 4 Dec 2026
- Listing views
- 18
- Application actions
- 2
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
About this role.
About ElevenLabs
ElevenLabs is an AI research and product company transforming how we interact with technology.
We launched in January 2023 with the first human-like AI voice model. Today, we serve millions of users and thousands of businesses – from fast-growing startups to large enterprises like Deutsche Telekom and Meta. Our investors are some of the world’s most prominent, including Andreessen Horowitz, ICONIQ Growth and Sequoia. We’ve raised $781M in funding and our last valuation was $22B – multiples of 11, always.
We have expanded from voice into three main platforms:
ElevenAgents enables businesses to deliver seamless and intelligent customer experiences, with the integrations, testing, monitoring, and reliability necessary to deploy voice and chat agents at scale.
ElevenCreative empowers creators and marketers to generate and edit speech, music, image, and video across 70+ languages.
ElevenAPI gives developers access to our leading AI audio foundational models.
Everything we do is the result of the creativity and commitment of our team – builders doing the best work of their lives. We are researchers, engineers, and operators. IOI medalists and ex-founders. If you want to work hard and create lasting positive impact, we want to hear from you.
How we work
High-velocity: Rapid experimentation, lean autonomous teams, and minimal bureaucracy.
Impact not job titles: We don’t have job titles. Instead, it’s about the impact you have. No task is above or beneath you.
AI first: We use AI to move faster with higher-quality results. We do this across the whole company—from engineering to growth to operations.
Excellence everywhere: Everything we do should match the quality of our AI models.
Global team: We prioritize your talent, not your location.
What we offer
Innovative culture: You’ll be part of a generational opportunity to define the trajectory of AI, surrounded by a team pushing the boundaries of what’s possible.
Growth paths: Joining ElevenLabs means joining a dynamic team with countless opportunities to drive impact – beyond your immediate role and responsibilities.
Learning & development: ElevenLabs proactively supports professional development through an annual discretionary stipend.
Social travel: We also provide an annual discretionary stipend to meet up with colleagues each year, however you choose.
Annual team offsite: Each year, we bring your entire team together in a new location – past offsites have included Croatia, Italy and Cancún
Co-working: If you’re not located near one of our main hubs, we offer a monthly co-working stipend.
About the role
The Payments team owns how ElevenLabs charges customers: billing, usage tracking, pricing and payments across self-serve and enterprise. Everything we do has to be correct, because it underpins the company’s revenue and is immediately visible to every customer and team.
We are hiring full stack engineers (backend leaning) to expand and evolve our payments systems. Your responsibilities might include:
Building and maintaining usage tracking so that requests are metered accurately without impacting latency.
Leading our migration of enterprise pricing and usage processing, including new stream-processing services for usage events.
Making it easy for customers to upgrade and pay, including paying through different entities and supporting new payment providers.
Working with Finance and Tax teams to meet compliance, audit and reporting requirements.
Enabling pricing and Growth experiments with Growth and product teams.
Debugging complex customer billing scenarios: piecing together what happened from the customer’s experience, logs and code, and fixing the cause.
Collaborating with Sales, FDEs, Finance and engineers across the company.
Much of this work extends or replaces systems that already exist, so you will scope carefully, plan migrations, and roll changes out without disrupting customers.
Requirements
We do not require any formal experience, certifications, or degrees. Instead, we are seeking engineers who can show they have solved impressively hard problems, through past projects or GitHub contributions. We do require:
Expertise in Python.
A strong background in backend development.
Experience with common software and system design patterns and infrastructure, including APIs, cloud infrastructure tools, storage solutions and data structures.
Strong test design and security fundamentals.
Care and attention to detail when changing live systems that handle money.
The ability to learn a large existing system quickly and to debug complex production issues.
Bonus:
Experience with payment processing providers, or with billing and usage-based pricing systems
Experience with stream processing or high-throughput event pipelines.
Experience working with finance, tax or audit requirements.
Experience with Kubernetes.
Location
Our team is based across the UK, EU and US, and this is our main focus. We are flexible for exceptional candidates elsewhere. You can work remotely, or from our offices in Dublin, London, New York, San Francisco and Warsaw.
#LI-Remote
We are an equal opportunity employer and do not discriminate on the basis of race, religion, national origin, gender, sexual orientation, age, veteran status, disability or other legally protected statuses.
Annual salary information is not provided for this position. Explore salary ranges for similar roles in our Salary Directory ›
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.
Pace & Pressure
5/5Autonomy Level
5/5Communication Load
4/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 would decouple request handling from aggregation by emitting durable usage events asynchronously, with idempotency keys and clear event schemas. A stream-processing pipeline can validate, enrich, and aggregate events, while reconciliation jobs compare raw events with billed totals. I would define latency and correctness SLOs, add observability around event loss or duplication, and make downstream consumers replayable.
I would begin by mapping existing rules, data dependencies, edge cases, and customer contracts. The migration would use versioned pricing models, dual writes or shadow calculations, extensive reconciliation, and a phased rollout by customer cohort. I would retain a rollback path, monitor invoice and usage discrepancies closely, and communicate operational readiness criteria to Finance and support stakeholders.
I would reconstruct the billing timeline using the customer’s plan, pricing version, usage events, payment records, logs, and relevant code changes. I would compare source usage data with the aggregation and invoicing outputs to identify whether the issue originated in metering, pricing logic, tax handling, retries, or a user-facing workflow. After correcting the root cause, I would reconcile impact, communicate the resolution clearly, and add tests and monitoring to prevent recurrence.
I would minimize storage and exposure of sensitive payment data, use tokenized provider integrations, enforce least-privilege access, and protect service-to-service communication with strong authentication and encryption. I would also use audit logs, secure secret management, input validation, dependency scanning, and threat modeling for high-risk workflows. Changes affecting money movement should have strong review, testing, and release controls.
I separate experimentation from accounting truth through feature flags, isolated experiments, versioned business rules, and explicit guardrails. I use staged rollouts, metrics, alerts, automated tests, and reconciliation processes so that experiments can be measured without silently compromising billing accuracy. When uncertainty is high, I prioritize reversible changes and clearly document assumptions and rollback criteria.
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. .
