AI Engineer at RevenueCat - Remote Global Role — Columbus
Traveler-Friendly Insight
Highly nomad-friendly: RevenueCat is a proven remote-first company with 150+ employees across 25+ countries — this isn't remote-by-exception, it's the default operating model. The role is explicitly async-compatible, with no fixed timezone requirements mentioned, making it genuinely workable from virtually any location.
Timezone flexibility: The hiring scope covers EMEA, LATAM, Canada, and the USA — a range spanning roughly UTC-8 to UTC+3. This breadth strongly implies asynchronous workflows for most collaboration. On-call rotation is mentioned, so you'll need reliable internet and the ability to respond to incidents, which is something to factor in when choosing short-term bases.
Nomad-relevant perks:
- $2,000 workspace setup stipend — great for a quality travel monitor, portable keyboard, or noise-cancelling headphones.
- $1,000 annual learning stipend — can fund AI/LLM courses while on the road.
- 4-5 weeks suggested PTO — generous enough to incorporate slow-travel periods.
Cost-of-living context (assuming a competitive senior engineer salary ~$150K–$200K USD equivalent):
- Lisbon, Portugal: ~$2,500–3,500/mo living costs — excellent runway, D8 digital nomad visa available.
- Medellín, Colombia: ~$1,500–2,500/mo — LATAM is explicitly in scope; Colombia digital nomad visa available.
- Bangkok, Thailand: ~$1,500–2,500/mo — APAC overlap may require timezone discipline for on-call.
RevenueCat removes the headaches of building and scaling in-app subscriptions. Since graduating from YC's S18 batch we've grown into the default monetization platform for mobile: we're in >40% of newly shipped subscription apps, we process $12B+ in annual purchase volume, and we help everyone from a solo dev in Brazil to the OpenAI mobile team understand and grow their revenue.
We're a remote-first crew of 150+, spread across 25+ countries, and guided by values we actually practice: Customer Obsession, Always Be Shipping, Own It, and Balance. If you want your work to touch hundreds of millions of end-users (and help the developers behind them get paid), you'll fit right in.
The Role
We're building an AI assistant that helps developers understand and grow their subscription revenue. It lives in Slack today and is expanding to our dashboard and API. It can pull real-time data, evaluate experiments, debug integrations, and explain what's happening in your app using natural language. We see a future where the majority of a user's interactions are either intermediated or automated by our agent.
We're a team that's historically built deterministic CRUD systems, and we need an engineer who can build the foundational agent infrastructure that everything else runs on: orchestration, tool execution, context management, evaluation, and the trust layer that lets us give an agent increasing autonomy over things that matter.
About You:
- You have 5+ years of experience shipping production systems.
- You have hands-on experience building with LLMs — not just prompting, but building the systems around them: tool use, structured output, context management, evaluation, orchestration.
- You have strong backend fundamentals. You've built systems that need to be reliable, observable, and secure.
- You are comfortable with ambiguity. This is an early-stage product inside a growth-stage company. The architecture is still being figured out.
- You are self-directed. You figure out what needs to be built, build it, and ship it.
- You collaborate well with others and can communicate effectively in a fully-remote culture.
Bonus:
- Experience with OpenAI/Anthropic APIs specifically.
- You've built agents that other people use.
- Experience with evaluation and observability frameworks (Langfuse, Langchain, etc).
- Familiarity with subscription business models, app stores, or developer tools.
- You've built Slack integrations or other conversational interfaces.
- Contributions to open-source AI/ML tooling.
In the first month, you'll:
- Ship your first agent feature and get familiar with the architecture, tool ecosystem, and how Rico talks to RevenueCat's APIs.
- Identify the biggest reliability or performance gap and start fixing it.
- Meet with the team, get set up with repos, dev environment, and debugging tools.
- Familiarize yourself with RevenueCat dashboards, logging, debugging tools, cloud providers, infrastructure management and general architecture.
Within the first 3 months, you'll:
- Launch a brand new agentic feature to tens of thousands of developers.
- Own a core infrastructure area — orchestration, eval pipeline, tool framework, or the trust/permissions layer.
- Be able to scope and work on projects self-sufficiently.
- Learn the basics of incident response and be part of the on-call rotation.
Within the first 6 months, you'll:
- The agent is measurably more reliable, faster, and capable because you're here.
- You've built infrastructure that the rest of the team ships agents with.
- Review code, create proposals, and contribute to architectural discussions.
- Have shipped a major product or feature.
Within the first 12 months, you'll:
- RevenueCat is an AI-native company. You built the engine underneath it.
- Know all the major components of our agent system and be able to debug complex issues.
- Have your own initiatives for improving our agent products, understanding the current issues and priorities.
- Mentor other engineers joining the team.
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
- Fully remote and flexible work environment
- 4-5 weeks of suggested time off annually for mental, physical, and emotional recharge
- $2,000 USD for workspace setup and $1,000 USD annual stipend for continuous learning
Curious about the interview process? Discover more in our blog post about how we hire and learn tips to help you succeed.
Frequently Asked Questions
Is this role truly remote or are there location restrictions?
What does the on-call rotation involve?
Is salary disclosed for this position?
What LLM or AI experience is required vs. preferred?
How much autonomy does this role have?
