Fans API

Who we are

We've built dozens of tools for creators and sold three of those businesses for seven figures or more. Now we're building our own platform where creators can sell subscriptions and PPV content, chat with fans, livestream and receive payouts. We have $10m in funding.

Who we're looking for

You'll own the iOS and Android app, which we're building from scratch with React Native, Expo and TypeScript. You'll work with our designers and the engineers building the backend and web app.

What you'll do

• Build the iOS and Android app in Expo and TypeScript.
• Ship to both stores and maintain the app after release. You'll handle builds, signing, app review, updates, crash reporting and push notifications.
• Add camera and media capture, secure storage and identity checks using Expo and React Native libraries. Handle background uploads and recover from interrupted transfers.
• Build payments, subscriptions and paywalls. Make sure restored purchases and failed payments leave users with the right access.
• Make chat work when people lose connection and come back. Keep long conversations fast to load and smooth to scroll, and handle messages sent while offline.
• Work in our monorepo. Share API types, client code and design tokens with web, and share UI components where they work on both platforms.

We expect you to look at the Laravel code when an API doesn't give the app what it needs, and work with the backend team to fix it.

What we need from you

• You know TypeScript well and have shipped and maintained React Native and Expo apps with real users. If you've sold an app you built, we'd like to hear about it.
• You've shipped mobile payments, subscriptions and paywalls. You know how to restore purchases and keep paid access in sync with the backend.
• You've taken iOS and Android apps through App Store and Google Play review.
• You understand the stores' billing rules and when you can use external payments.
• You can integrate native libraries in Expo development builds and debug problems on iOS and Android, including build and configuration issues.
• You can track down crashes, slow screens and connection problems on real phones. You understand how backgrounding, force-quit or force-stop, and reopening affect the app's work and recovery.
• You have a good eye for UI and UX. You build beautiful interfaces that feel good to use, with thoughtful transitions, animations and small interactions. When a design leaves out a state or interaction, you can work out what fits.

It's a plus if you've worked on a creator or UGC platform and dealt with its moderation rules. Experience with KYC or age checks, WebRTC, livestreaming, shared design systems or monorepos also helps. Writing Swift or Kotlin modules is a bonus.

Why join us

We already have an audience we can launch this app to. You'll work directly with us in a small team and make decisions about how we build it. The backend uses Laravel, PostgreSQL, Reverb and R2.

How we hire

One paid technical task, then a 30-minute walkthrough. No panel interviews. You have six-seven 🤷‍♂️ hours, including setup. You can use AI; we'll ask you to explain your code and decisions.

Who we are

We build APIs and tools for businesses working with creators. We're profitable, growing 30% month over month, and our founders have sold three businesses for seven figures or more.

We're expanding into a single API for multiple creator and social platforms. Customers should be able to integrate once and get consistent responses, webhooks and SDKs.

The work

Some platforms have undocumented APIs, bot detection and changes that arrive without notice. We need someone who can understand how those integrations work and keep them reliable when the platform, traffic or data changes.

We're hiring a senior full-stack engineer to keep production reliable and customer data correct. You'll plan for a workload of 50 million jobs a day, including bursts, slow upstream services and retries. You'll also build integrations and customer-facing features in Laravel 13, Inertia and React.

What you'll do

• Investigate production problems using logs, metrics and the actual request and job flow. Identify who is affected, contain the problem and verify the fix.
• Keep queues and webhook delivery reliable. Handle retries, duplicate events, rate limits and worker failures without losing data or letting one account hold up everyone else.
• Reverse engineer undocumented APIs and maintain integrations for authentication, posting, messaging, media and analytics.
• Make different platforms work through a consistent API. Keep documentation, SDKs and MCP tools aligned with the behaviour customers receive.
• Build useful dashboards and internal tools in Laravel 13, Inertia and React. Make the data accurate and the interface clear.
• Improve database queries, worker capacity and scheduling based on measurements. Add tests for the failures we cannot afford to repeat.
• Protect our APIs against abuse and check integrations when upstream behaviour changes.
• Challenge a decision when you think we're solving the wrong problem. Explain the alternative and its tradeoffs.
• Production incidents and incorrect customer data take priority. We agree with the team which integration and product work comes next.

What we need from you

• You've shipped and maintained Laravel applications with real users, and you're comfortable building in React. Inertia experience helps, but is not required.
• You have operated queue or worker systems in production at substantial volume. You understand concurrency, retries, duplicate execution, backpressure and how databases and external services limit throughput.
• You can describe a production incident you personally investigated, the evidence that led to the cause and how you proved the fix worked. Explain the workload you owned in concrete numbers.
• You have reverse engineered an API, web client or similar integration. You can reason about HTTP headers, cookies, request signing, TLS fingerprints and rate limits.
• You check that data means what the product says it means. Missing information, failed requests and legitimate zero values need different handling.
• You use AI regularly and can show how it improves your work. You verify its output and understand the code you ship.
• You investigate problems independently, keep the team informed and raise blockers early. You know when to involve someone else in a decision.
• You don't need to have handled exactly 50 million jobs a day. Tell us what you have operated, how it failed and how you measured its limits.

Nice to have

Proxy infrastructure, published SDKs, OpenAPI, MCP tools, security testing, PostHog or experience with creator platforms. Public code is welcome; confidential commercial work also counts if you can explain your contribution.

How we work

We're a small team. We work asynchronously and review progress weekly. Keep the team informed about decisions, blockers and incidents. We care about work reaching customers and continuing to work after release.

We will discuss working-hour overlap, incident coverage, response expectations and any on-call arrangement before an offer.

Remote, with a Prague office available. Czech Republic, Ukraine, Poland or UK preferred.

How we hire

A paid debugging exercise, a 30-minute technical walkthrough, then a decision. We agree a fixed fee before you start, and payment does not depend on the hiring decision. You have six-seven 🤷‍♂️ hours, including setup. The process usually takes under two weeks. You can use AI throughout; we'll ask you to explain your code and decisions.

Apply

Briefly describe a production problem you investigated, how you found and verified the fix, and the traffic or job volume involved. Tell us how you use AI and give an example of something you caught it getting wrong. A concrete example gives us more to talk about than a cover letter.