• Build the mobile SDK from the ground up. Design, develop, and maintain native iOS (Swift) and/or Android (Kotlin) SDKs that platform partners embed directly into their applications. • Obsess over the developer experience. Your primary users are other engineers. The SDK's API surface, documentation, error messages, and integration patterns need to be clear, predictable, and hard to misuse. • Connect software to hardware. Build in-app payment flows where NFC radios, Bluetooth peripherals, and backend APIs converge into a seamless experience for the end merchant. • Ship code that runs everywhere. Your SDK will operate across a wide range of devices, OS versions, and host app architectures. You'll think constantly about compatibility, binary size, dependency management, and graceful degradation. • Harden what we ship. Mobile payments surface unique challenges around secure data storage, network resilience, certificate pinning, and offline capability. Security and compliance aren't afterthoughts; they're core to the SDK's value proposition. • Own the full lifecycle. From architecture and implementation through testing, packaging, versioning, and distribution. You'll define how the SDK is released, documented, and supported. • Ensure unquestionable reliability and resilience. Work with Payabli architects, SREs, and other engineers to integrate your SDK with Payabli's APIs, while handling real-time data, async operations, error states, and edge cases gracefully. You understand that observability is part of reliability. • Set the standard. As the founding mobile engineer, you'll establish code review practices, testing strategies, CI/CD pipelines, and architectural patterns that the team will build on as it grows.