Senior iOS Developer

4 things to know about Purchasely: 🌍 A French startup with an international focus (80% of our customers) 📈 Our SDK is installed in 700+ leading apps 💥 20 billion requests per month, 1B+ monthly unique users 👫 A very experienced tech team that works with AI every day Purchasely was founded in 2020 to help apps grow their in-app revenue. At the heart of the company is a unique technology that deploys native screens remotely inside apps. It lets teams build entire funnels with no code, from onboarding to paywall. Our customers think of something in the morning and it is in production before lunch, without touching the app's code or waiting for a store update. We work with category leaders across every store category: Headspace, The Times, Wattpad, Busuu, TomTom, Le Monde, L'Équipe, MPG, Hatch, Muslim Pro, Reverso, Ornikar, Hoop… With 700+ large apps on board, you are probably already using us. At the core of this technology is our native SDK, written in Swift and Kotlin. It is what renders those screens natively on hundreds of millions of devices every month. 🤖 AI here is not a buzzwordWe build with AI every day and use it wherever it saves us time or adds precision:
• AI-assisted development, day to day
• MCP servers and agents in the product: for example, we moved our support onto advanced agents
• Advanced recommendations: we analyze our customers' metrics to produce internal briefs (where they stand, what worked and what did not, the next steps to recommend)
• Generating screens and flows from prompts
• Automated feedback on your Figma mockups (for example with Roast My Screen)
• You will join a team that actually builds agentic features, rather than talking about them. The problemThe Purchasely SDK renders fully native screens, configured remotely, that can be triggered at any moment in the app to display any kind of message or action: onboarding, paywalls, in-app campaigns, rewards, win-back. Built with UIKit and SwiftUI, it also handles StoreKit transactions and connects to our targeting, experimentation and analytics systems. Two constraints make this hard. It runs inside someone else's app. Hundreds of them, on architectures we did not choose, next to dependencies we do not control, on OS versions we cannot dictate. And once a customer ships their release, we cannot fix it. A change that works in 99% of integrations still breaks a real app in production, and we find out from a support ticket. So the job is not "build a screen". It is designing a system that stays light, fast, accessible and predictable while executing experiences that evolve without a new app release. The roleA hands-on individual contributor role. You take ownership of significant parts of the iOS SDK, working with the Head of Mobile Engineering and the rest of the mobile team. Six months in, success looks like this: you have shipped several SDK releases end to end, from API design through documentation and migration guides, and customers are building on capabilities you designed. What you will spend your time on:
• Designing, implementing, testing and releasing new SDK capabilities.
• Improving the engine that interprets remote configurations and renders them natively.
• Keeping public APIs stable, for native apps and for our React Native, Flutter and Cordova wrappers.
• Investigating integration bugs and crashes that are hard to reproduce, often starting from one customer report and a log file.
• Improving automated testing, CI, release safety and SDK observability.
• Helping external developers when an integration misbehaves. This is a real part of the job, not an afterthought.
• Tracking Apple platform changes and anticipating their impact.