RevenueCat’s Head of Security Post Lists $305k Salary

The Surge

RevenueCat lists 20 salaried roles on the Zero G Talent board, with a median band of $215k, most engineering and product positions at $179k–$230k, and Zero G Talent's board data shows a Head of Security role at $305k posted in the past week. The remaining slots cluster in senior engineering: Senior Software Engineer (Product), Senior Software Engineer (Agents), Senior Backend Engineer, Senior DevEx Engineer, and an Engineering Manager for RC Capital, all U.S. remote. Functional coverage is narrow by design: no marketing, sales, or operations roles appear. The board shows zero non‑technical openings. Every listed engineering role sits at $230k, suggesting a single calibrated senior band.

The timing aligns with RevenueCat's shift from pure SDK provider to a full‑stack monetization platform with paywalls, experimentation tools, and analytics. The open roles — Senior Software Engineer (Product, Agents, Backend, DevEx), Engineering Manager (RC Capital), Head of Security — signal investment across product‑facing engineering, platform extensibility, and financial‑grade reliability.

Inside the Screen

RevenueCat's interview process has entered unusual territory. The company's most talked‑about hiring experiment — a $10,000‑per‑month contract for an "Agentic AI Developer Advocate" — explicitly requires the agent itself to pass the screen. "The agent will be who (what?) we'll interview, so it'll have to pass that process," the company told Hindustan Times in March 2026. That process includes the same technical and product‑sense evaluations human candidates face, with all output subject to human review before publication. "All content goes through human review before it's published. We're not adding noise - the same editorial standards we hold for any team member apply here." The agent role sits alongside active human hiring for iOS and Android Developer Advocates and "many other roles," RevenueCat clarified, not a replacement but a parallel track.

What the record does show is CTO Miguel Carranza's stated hiring philosophy: pragmatic, non‑dogmatic, and calibrated against the interviewer's own experience at the candidate's career stage. "Look at this person's experience and look at yourself when you have that experience," Carranza said in a 2024 interview. "If you feel like that person is impressive to you when you adjust the experience then we should hire. If that person is not that impressive then it means that you probably were better at that stage and it probably doesn't make sense."

Carranza has also described the organizational context candidates enter. The company moved from day‑long sprint cycles at five people to smaller, autonomous teams of two to three engineers with a tech lead coordinating only when collaboration is necessary. "Before like obviously when the company used to be five people, we were moving really fast like the sprint cycles were one day or one week maximum... but now that doesn't need to be the case anymore because you don't need a team with like three back end engineers, three front end engineers, SDK, whatever. No, it can be a team of two, three people and they can be moving really fast independently."

The AI‑agent interview precedent reveals one concrete assessment vector: the ability to produce technical content (documentation, case studies), run growth experiments, and surface actionable product feedback autonomously, scoped to public docs, APIs, and specific tools (no customer data or internal systems access). "Scoped to what's needed for the role - the same public resources. No access to customer data or internal systems."

The clearest signal remains Carranza's heuristic: would your past self hire this person?

What Moves Candidates Forward

RevenueCat's platform sits at the intersection of subscription infrastructure, growth experimentation, and cross‑platform data. The competencies that move a candidate forward mirror that intersection.

The subscription metrics that matter inside RevenueCat's customer base are specific and unforgiving. Trial‑to‑paid conversion averages 30–40 percent; anything above that is strong. Trial activation rates (start rates) of 5–10 percent are good, above 10 percent great, above 20 percent rare. LTV per customer around $3 is a commonly cited threshold for viable paid acquisition. Renewal dynamics shift month to month — some periods bring higher new revenue, others higher renewals; ad spend adjustments directly move profitability. These figures come from RevenueCat's own dashboard data shared publicly by developers in the ecosystem.

Growth mindset, in this context, means experimentation as a default. The platform's own feature set, including dynamic paywalls, plug‑and‑play experimentation tools, funnels, and attribution for Apple Ads, is built for rapid iteration. Developers in the ecosystem run money‑back guarantee tests on paywalls, hypothesize that web funnels may outperform app funnels, and pipe RevenueCat API data into LLMs for weekly automated analysis.

Cross‑functional communication shows up in how the platform is actually used. Most developers use only a fraction of RevenueCat's capabilities; the ones who extract full value tend to be the ones who bridge engineering, growth marketing, and product. They configure the platform as an MMP for Apple Ads, build custom paywalls when the native one is "pretty basic," and translate funnel data into pricing and packaging decisions.

The subscription expertise bar is high because the product serves companies for whom subscription is the business model. These are the daily vocabulary of RevenueCat's customers: understanding the difference between a 60 percent trial‑to‑paid conversion (an outlier) and a 35 percent baseline, knowing why LTV must exceed CAC before scaling ad spend, and recognizing that renewal revenue can mask new‑user acquisition problems.

Technical depth remains necessary but not sufficient. The backend roles demand distributed systems experience at scale (RevenueCat processes 2B+ API requests daily). The Security lead role reflects the trust requirements of handling purchase data and financial events (RevenueCat is SOC 2 certified).

Preparing Without a Playbook

No public forums, GitHub discussions, or social‑media compilations aggregate interview questions, take‑home patterns, or debriefs from recent RevenueCat applicants. What is publicly available, and what any serious candidate would treat as the primary study corpus, is RevenueCat's own technical surface area.

The company publishes extensive SDK documentation across six platforms — iOS/Swift, Android/Kotlin, React Native, Flutter, Kotlin Multiplatform, Web/JavaScript — each with installation guides, configuration references, and error‑code tables. Candidates targeting engineering roles can reasonably be expected to have read the "Configure the SDK" reference (apiKey, appUserID, isConfigured), the CustomerInfo listener patterns, the syncPurchases versus restorePurchases decision tree, and the entitlement‑checking flows at the heart of the product. The blog posts add applied context: tutorials on StoreKit 2 integration, Jetpack Compose paywalls, Expo cross‑platform subscription builds, and ad‑free subscription monetization strategies for Android and Flutter.

The seniority threshold shapes preparation: candidates aren't brushing up on syntax; they're rehearsing system‑design narratives around subscription infrastructure, including idempotent receipt validation, grace‑period state machines, cross‑platform receipt unification, and the analytics event pipeline that feeds RevenueCat's experimentation tools. The public docs describe the "what"; the interview asks for the "why" and "how it breaks at scale."

Without community‑sourced cheat sheets, the preparation loop collapses to first principles: read the docs, ship a micro‑project against the SDK, model the data flows, and be ready to defend architectural trade‑offs.

Where the Hires Land

The board's current slate, comprising the same senior engineering roles noted above plus the newly added Head of Security, points to investment across the full stack of a subscription platform.

RevenueCat has not published a "now hiring" blog post framing the wave as a strategic accelerant, nor linked the roles to announced roadmap changes, capacity metrics, or go‑to‑market motions. The board data simply shows open requisitions.

Available sources do not cover whether RevenueCat's current product organization can absorb 20 engineers without bottlenecking on product management or design. They do not cover whether the go‑to‑market team has pipeline coverage to monetize the output of those engineers. Nor do they cover whether the hiring plan is front‑loaded or staggered across the year. The board shows 20 salaried roles listed, but timestamps on 19 of them are not provided; only the Head of Security role carries a "past 7 days" signal.

What the data does support is a picture of a company staffing the full stack: core product, automation agents, developer experience, backend scale, financing, and security. Whether RevenueCat's internal planning matches that pattern or whether the roles represent replacement hiring, geographic expansion, or a specific customer commitment cannot be determined from available sources.

A Bellwether for Frontier SaaS Hiring

RevenueCat's 20‑role push arrives as the subscription‑platform layer of SaaS enters a structural shift. The global SaaS market reached $399.1 billion in 2024 and is projected to hit $819.23 billion by 2030, per IBM's July 2025 figures. Large enterprises now run an average of 131 SaaS applications each.

Publicly traded AI‑native companies are staffing aggressively, per BuiltIn's June 2026 snapshot.

Three forces are converging. First, the "SaaSpocalypse" of February 2026, a $300 billion market‑cap wipeout triggered by generative AI disruption, forced every subscription business to prove its AI strategy or face devaluation. Second, seat‑based pricing is cracking. SaaStr reports its own vendor seat counts are dropping as a dozen‑plus AI agents replace discrete human tasks. Third, pricing pressure is now the primary growth lever for mature SaaS vendors: half of software companies plan price hikes, and 60 percent mask those increases through bundling, credit multipliers, or seat‑model migrations. Gartner pegs IT budget growth at 2.8 percent annually while vendors hike 9–25 percent.

RevenueCat sits at the intersection. Its product lets developers implement in‑app purchases, manage entitlements, and analyze subscriber lifecycle across iOS, Android, and web.

Vertical SaaS and micro‑SaaS compound the demand. IBM's 2025 trend report notes industry‑specific platforms and ultra‑niche solo‑founder tools are proliferating. Each needs subscription infrastructure but cannot build it.

The talent market reflects this. Candidates who can design idempotent webhook handlers for App Store Server Notifications, model cohort retention in SQL, and communicate trade‑offs between Apple's 15/30 percent cut and Stripe's fee structure are scarce. RevenueCat's interview screen, heavy on product‑sense exercises and subscription‑domain problems, filters for exactly that profile.

What happens next depends on whether AI agents collapse the seat model faster than new subscription categories emerge. SaaStr's outlook calls that a 3–5 year wildcard. In the near term, 10–15 percent annual renewal increases are the new normal, AI bundling is mandatory, and multi‑year discounts are shrinking. Companies that own the metering layer and the engineers who build it capture the data exhaust that informs every pricing decision downstream. RevenueCat's hiring wave is a bet that the metering layer stays central, and that the talent to scale it remains the scarcest resource in the stack.

What This Story Leaves Out

The agent interview is already live. Carranza's heuristic, the same criterion, still governs the human screen. Twenty roles sit open on the board, each demanding the vocabulary of subscription mechanics: trial-to-paid at 35 percent, LTV above $3, renewal revenue that can mask acquisition cracks. The board shows one role added in the past seven days. The screen doesn't wait.

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.