How Work Gets Done
RevenueCat processes more than 4 billion API requests daily and has handled over $16 billion in subscription revenue, according to RevenueCat's website, all built by a team that has never shared a physical office. The company has been remote-first since its 2017 founding, a choice that shapes everything from how engineers ship code to how product decisions get made.
The workforce numbers between 51 and 200 people, according to RevenueCat's LinkedIn profile, distributed across the United States with a nominal headquarters in Brandon, Florida. Every open role lists "Remote (US)" — Senior Software Engineer, Product; Senior Software Engineer, Agents; Engineering Manager, RC Capital; Senior Product Manager, Funnels/Workflow; Head of Sales; Head of Customer Growth. Decision-making authority follows the product-led growth model the company sells: teams close to the customer and the revenue data carry weight. The integrations ecosystem (Braze, Amplitude, Mixpanel, and dozens more) means engineers regularly ship changes that ripple across other companies' stacks, so coordination happens asynchronously through specs, RFCs, and shared observability. SOC2 certification and GDPR compliance add mandatory review gates, but the hiring profile (heavy on senior ICs and managers with "Product" or "Funnels" in their titles) points to a culture where the person writing the code also owns the outcome.
Publicly, the company signals its cadence through live office hours every other Friday, where the team demos the platform and fields questions in real time. Documentation is optimized for large language models, and the SDKs (iOS, Android, web) are designed so developers can integrate, test, and iterate without waiting on support tickets. What the research doesn't show is the internal meeting rhythm, sprint structure, or whether the company uses a formal framework like Shape Up or dual-track agile. Employee reviews and interview accounts fill those gaps. What's clear from the outside: RevenueCat's remote-first structure isn't a pandemic adaptation; it's the operating system the company was built on, and the product's scale proves it works.
The Operating Philosophy: Developers First
RevenueCat's operating philosophy centers on a single conviction: the company wins when developers win. CEO Jacob Eiting has stated this plainly — "Investors make more money when developers make more money" — and the claim is backed by how the company allocates capital and product energy. Rather than chasing growth-at-all-costs metrics that satisfy venture narratives, RevenueCat has kept burn low, halving its burn rate by mid-2024 while holding over $40 million in cash alongside roughly $20 million in ARR. That discipline bought the runway to absorb a 40 percent month-over-month surge in new developers shipping their first production app in March 2026 without breaking the onboarding flow.
The developer-first value shows up in concrete product decisions. Before the "vibe coding" wave made app creation accessible to non-programmers, RevenueCat had already invested in a low-friction onboarding experience. When AI tools like Replit, Lovable, and Claude Code collapsed the barrier to shipping a mobile app, new developers could integrate subscriptions in minutes instead of weeks. The company then formalized a native Replit integration so RevenueCat appears at the exact moment a builder needs billing. Each adjacent product (Paywalls, Funnels, ad tracking, the drag-and-drop paywall editor, virtual-currency tooling) expands the surface area that captures value from that growing developer base. A developer who comes for billing stays for the full platform.
Transparency operates as both cultural norm and product strategy. The 2024 acquisition of Dipsea, a subscription audiobook app, was explicitly framed as a "build in public" move. RevenueCat uses its own app as a live testbed: pricing experiments, paywall variants, and billing changes run on Dipsea before the company recommends them to paying customers. The same dashboard RevenueCat sells becomes a demo environment prospects can touch. Eiting set a public benchmark — "if you check a year from now and it's 50,000 subscribers, we f***** up" — turning the acquired app into an accountable proof point rather than a vanity asset.
Capital efficiency functions as a strategic lever, not a constraint. The Series C extensions — $12 million in April 2024, another $50 million in May 2025 — were raised from a position of strength, with existing investors doubling down. Eiting has described the approach as "counter to the prevailing narrative of how venture-backed companies should be built," but the board alignment lets the founders optimize for developer value over quarterly optics. The stated goal remains an IPO this decade, and the Shopify analogy Eiting invokes (core tools first, then fulfillment, lending, marketplace) maps directly to RevenueCat's roadmap: billing today, web payments and customer-acquisition tooling tomorrow, capital lending (RC Capital) and Japan/Korea expansion after that.
Experimentation is institutionalized. The engineering team ships features behind flags, measures impact on real transaction volume (over $14 billion in annualized mobile subscription revenue flows through the platform), and iterates. The same data pipeline that powers the company's public State of Subscription Apps reports feeds internal product decisions. When the 2026 report showed AI-powered apps convert trials 52 percent better but churn 30 percent faster, RevenueCat didn't just publish the finding; it shaped the next set of retention tooling.
Remote-first asynchronous work, as described by the founders, is the substrate these values run on. Decisions are written, not spoken; context lives in written artifacts, not in hallway conversations. That practice predates the post-2020 normalization; it was a deliberate bet that a distributed team could out-execute a collocated one on a product that itself enables distributed developers. The through-line is pragmatic long-termism. RevenueCat builds for the developer who will ship an app next month, next year, next platform shift. The values — developer success, transparent experimentation, capital discipline, platform breadth — are not slogans. They are the operating system the company runs on, and they show up in every shipping decision, every hire, every acquisition.
What the Hiring Bar Selects For
RevenueCat does not publish a hiring manifesto, a public interview rubric, or a detailed breakdown of the competencies it screens for. What exists in the open record is a pattern of roles posted, the seniority those roles imply, and the fact that every listing is designated "Remote (US)." That pattern is the clearest signal the company emits about who it hires.
The six most recent postings captured on Zero G Talent's board are all senior or lead-level positions. Salary bands cluster tightly:
| Role | Salary |
|---|---|
| Head of Sales | $363,000 |
| Head of Customer Growth | $259,000 |
| Senior Product Manager, Funnels/Workflow | $230,000 |
| Senior Software Engineer, Product | $230,000 |
| Senior Software Engineer, Agents | $230,000 |
| Engineering Manager, RC Capital | $230,000 |
The board's aggregate data shows a salaried band of $179,000–$233,000 with a median of $217,000 across 20 roles. In practice, RevenueCat is not hiring juniors. It is hiring people who have already owned outcomes (revenue targets, product surfaces, engineering systems) and can operate without daily oversight.
That seniority bias aligns with the company's stated model: a fully remote, high-autonomy environment where product-led growth drives decision-making. The "Head of" titles indicate RevenueCat is building out executive-layer functions (sales, customer growth) rather than filling individual-contributor quotas. The Senior Product Manager role, scoped to "Funnels/Workflow," signals a focus on the mechanics of subscription conversion and retention — the core product problem RevenueCat solves for its customers. The two Senior Software Engineer postings split along product and "Agents," the latter suggesting investment in AI-assisted or automated workflows, a direction the company has hinted at through its Shipaton events and Kotlin Multiplatform advocacy. The Engineering Manager role for "RC Capital" points to a dedicated financial-product line, likely the revenue-recovery and pricing-optimization tooling RevenueCat has expanded into.
All six roles are U.S.-remote. The company's LinkedIn profile lists a primary address in Brandon, Florida, but the hiring footprint is national. Candidates who need time-zone overlap with U.S. business hours, who can communicate asynchronously in writing, and who have managed or contributed to distributed teams will match the implicit filter. The absence of non-U.S. remote listings (at least in this posting set) suggests either a compliance or compensation strategy that keeps payroll domestic, or a deliberate choice to keep collaboration windows tight.
Compensation transparency is another signal. Each posting lists a single figure, not a range, which implies the band is narrow and the level is calibrated. Candidates who negotiate expecting wide bands or equity-heavy offers may find the structure more rigid than expected.
What the research does not show, and what no public source reviewed for this guide details, is the interview loop itself: whether RevenueCat uses take-home exercises, system-design reviews, pair-programming sessions, or values-based behavioral panels. The company's public blog and LinkedIn feed emphasize product launches (RevenueCat Ads, Android 16 readiness, Shipaton hackathons) and customer case studies (Opal, 500 million hours saved), not hiring process retrospectives. Glassdoor and Blind reviews do not yield a consistent, attributable description of the interview stages or the specific rubrics interviewers apply.
The upshot: the hiring bar selects for proven autonomy, U.S.-based remote readiness, and depth in subscription-commerce or adjacent domains (mobile SDKs, billing infrastructure, growth product management). It selects against candidates who need structure, mentorship, or time-zone flexibility outside U.S. hours. Beyond that, the process is opaque by design, or at least undocumented in public. Candidates should prepare to demonstrate owned outcomes, not potential.
Inside the Employee Experience
The public record on RevenueCat's employee experience centers on a single substantial source: a long-form 2024 interview with co-founder and CEO Jacob Eiting, published on YouTube. Traditional review platforms (Glassdoor, Blind, Levels.fyi, Comparably) surface in search results but the research provided contains no scraped ratings, verbatim reviews, or aggregate scores from those sites. What follows synthesizes the perspectives that do exist in the primary material, attributing each to its source and date.
Founder perspective as proxy for early-team sentiment
Eiting's own account functions as the closest thing to a first-person employee narrative for the company's formative years. Describing the period after he left his prior startup (Elevate) in late 2016, he said he "wandered the desert for a few months" before RevenueCat's idea crystallized two weeks before his wedding. The early team formed around a problem he and his co-founder had worked on together. On the decision to stay during a turbulent period ("the company was being shaking up"), Eiting recalled: "a lot of people left... and I decided to stay because the people that stayed were solid and people that I really enjoyed working with." That framing, from the 2024 interview, suggests retention in the early years hinged on interpersonal trust more than perks or process.
Remote-first culture through the founder's lens
Eiting addressed the remote experience directly in the same interview. "I always say remote work sucks but that's okay," he said. "Of course I would love if we could all teleport to the same place... but we wouldn't have been able to build this team." He tied the model to generational experience: "Millennial and younger... we all had the internet at like our pre-teen years... we built communities on the internet... to me building a remote first company feels very similar to World of Warcraft guilds." He acknowledged the trade-off: "there's a big difference when you see somebody in person for the first time," which motivates annual "upsides" (in-person gatherings). A tactical detail he offered: "one of the checklist items is just like set up your profile pictures because it matters... if somebody doesn't set their Slack profile up within like the first week it's like 50/50 chance it's probably not gonna work out."
Scale and organizational friction
At roughly 70–80 employees globally as of the 2024 interview, distributed across the US, Europe, Australia, Taiwan, and Latin America, Eiting described growing pains in candid terms. "It never feels like that on the inside... it always feels like we're just like barely Keeping Up Appearances." He characterized the operating mode: "the chaos is the process." On org changes: "adding or removing an individual person is a huge operation... even shifting organizations around is a huge operation and a lot of those operations are oneway doors... you can't like AB test that... these are people right and these are their livelihoods." He noted that "people problems sort of rhyme at every scale"; the same dynamics reappear with larger headcounts.
Values articulation as a management tool
Eiting explained the impetus for codifying values: "before the first day Jacob was like oh we should sit down and write out the company values... it's good to write them down to have a framework for people to behave when we're not looking and then to really highlight the behaviors that we want." He framed this as necessary for a remote, asynchronous organization where direct oversight is minimal. The same interview revealed his view on co-founder dynamics: "having a great co-founder is such a freaking cheat code... the cheapest 50% of your Equity you'll ever give away."
Gaps in the public record
No Glassdoor aggregate rating, Blind thread excerpts, Levels.fyi verification tiers, or Comparably culture scores appear in the research provided. The YouTube interview is a founder narrative, valuable for understanding leadership philosophy and early-team mythology, but not a substitute for anonymized employee feedback. Candidates should treat the above as the company's self-portrait and seek out current or recent employees directly for unvarnished perspectives on pace, review cycles, equity refresh practices, and whether the "chaos is the process" framing matches day-to-day reality at 80 people.
Who Thrives and Who Burns Out
The clearest signal of who lasts at RevenueCat comes from the onboarding checklist itself. Jacob Eiting, co‑founder and CEO, described one item bluntly: "set up your profile pictures because it matters like it helps with slack and stuff like that and like there's always your joke if if somebody doesn't set their slack profile up within like the first week it's like 5050 chance it's probably not gonna work out." The half‑joke reveals the actual filter: people who treat the low‑friction rituals of remote presence (avatar, status, async responsiveness) as optional tend to drift out. The company hires globally (Europe, US, Australia, Taiwan, Latin America) and has never been collocated; Eiting said "this team can only exist as an internet team as a remote first team." Candidates who need daily physical proximity to build trust or resolve conflict rarely make it past the first year.
Thrivers share three traits. First, they operate without a manager looking over their shoulder. Eiting framed the values document as "a framework for people to behave when we're not looking," written before the first employee's first day. The people who stay internalize that framework and make decisions that align with it without asking permission. Second, they tolerate (and sometimes prefer) the "constant struggle to keep us in that spot" Eiting described. He said "it never feels like that on the inside it always feels like we're just like barely Keeping Up Appearances … feels like it's just a constant struggle." Engineers and product managers who treat that chaos as the normal texture of zero‑to‑one scaling, not a sign of dysfunction, ship faster. Third, they communicate clearly in text. "Sometimes like you might be arguing arguing on slack or somewhere with somebody that you've never seen in person right and the connection that you have is never the same," Eiting noted. People who escalate to video or wait for an offsite to resolve tension create bottlenecks; those who write precise, kind, decisive Slack threads unblock the team.
Burnout clusters around the inverse profile. Employees who joined expecting a "hacker Treehouse" (Eiting's phrase for a low‑stakes coding club) leave when they hit the mission‑driven pace: "I'm not here to build a hacker Treehouse I'm here to build a company that like achiev a mission and often that requires like a broader set of skills requires like different people." Specialists who want deep technical ownership without product or customer context struggle; the org rewards generalists who can move across the subscription‑plumbing stack. People who rely on synchronous rapport (reading body language, hallway conversations) find the once‑a‑year offsite cadence insufficient. Eiting acknowledged that gap directly, but the company bets the flexibility and talent reach of remote‑first outweigh it. Candidates who need that gap closed will exhaust themselves trying to force it.
The market does the first filter; the profile‑picture test does the second.
Working in frontier tech? Zero G Talent tracks the openings: see every open RevenueCat role, browse frontier tech jobs, the companies hiring, and the people building the field.