Senior Mobile Platform Engineer

Responsibilities

• Proudly recognized as a Great Place to Work®, we are an AI-native customer experience platform purpose-built for emerging markets. With more than 25 years of conversational AI research and development, we serve over 5,000 enterprises across MENA and are pioneering sovereign, agentic AI through our Agentic Studio platform. As the category takes shape, the way Unifonic is perceived — by buyers, analysts, media, and the broader market — is a strategic asset. This role owns that perception.
• Our Engineering team is responsible for designing, developing, and maintaining the systems and technologies that drive Unifonic’s solutions. We work closely with other departments to ensure our products and services meet the needs of our customers. If you are passionate about technology and are excited about working on cutting-edge communication and engagement solutions, we want you on our team.
• As a Mobile Platform Engineer, you’ll own our SDK platform end to end—treating it like a product that developers rely on every day. You’ll shape the foundations that make our mobile experiences reliable, extensible, and easy to integrate.
• Designing the public API of the SDK on your primary platform and keep it idiomatic: async and AsyncSequence on iOS, suspend and Flow on Android, Promises and events on the web.
• Implementing features in the Rust core and the shell executors, with coding agents doing much of the typing and you owning every line that merges.
• Building and keeping green the release pipeline: one coordinated release produces the XCFramework, AAR, npm packages and sample apps, signed, with symbols, SBOM and privacy manifest.
• Running the consumer test matrix: tiny storefront apps per configuration (minimum Xcode and AGP, R8 full mode, arm64-only ABI filters, React Native new architecture, Expo prebuild, Vite, webpack, ).
• 7+ years of software engineering experience, including 2+ years working on a library, SDK, framework, or platform consumed by third-party developers.
• Strong experience with public API design and Semantic Versioning (SemVer), including managing deprecations without breaking existing customers.
• Hands-on experience with native build systems and packaging, including publishing to a package registry and troubleshooting third-party builds.

Languages