Mobile Engineer

We're building the next generation of cross-border fintech infrastructure powering payments, KYC, and global merchant experiences. Our merchants embed Glomopay directly into their own apps, which means our mobile SDKs are the product for a large part of our business. Today those SDKs are Flutter and React Native wrappers around our web checkout. That was the right call to get to market. It is no longer enough. Over the next year, we're taking mobile in-house and going native: first-class Android and iOS SDKs and native capability inside the cross-platform ones: camera-based document capture, liveness, secure file handling, on-device identity, and biometrics. You'll be the engineer who does that. You'll work alongside a senior mobile engineer, and you'll own delivery from day one.

The core responsibilities for the job include the following:

Own the mobile SDK surface:

• Build and ship the Flutter and React Native SDKs: versioning, releases, changelogs, and distribution across pub.dev, npm, Maven Central, and CocoaPods/SPM.
• Extend into native Android (Kotlin) and iOS (Swift) SDKs as we bring those in-house.
• Design consumer-facing SDK APIs that merchant engineers actually enjoy integratingsane defaults, clear errors, graceful fallbacks, and honest breaking-change management.

Build native capability into payments and KYC flows:

• Camera and document capture for KYC ID capture, liveness, and image quality handling on real-world devices.
• Secure file handling pickers, uploads, encryption at rest, and temp-file hygiene. Identity biometrics, keychain/keystore, secure token storage, and device attestation.
• On-device native bridges and WebView interop keep the hybrid surfaces correct while native capability grows underneath them.

Make releases boring:

• Reproducible, automated release pipelines. No direct-to-main, no phantom builds, no "works on my machine" release artifacts.
• Real-device E2E testing infrastructure across an Android and iOS device matrix.
• Crash-free rate and error observability per SDK, per merchant app.

Support merchants for real:

• Debug integration issues inside someone else's app, with partial information, on a device you don't have.
• Write integration docs and sample apps that answer the question before it gets asked.
• Work directly with merchant engineering teams during integration and go-live.

Requirements:

• 3-5 years building and shipping production mobile applications or SDKs.
• Apps that real users used, published to the Play Store / App Store, or SDKs consumed by external teams.
• Side projects and coursework don't count.
• Demonstrated stability (2+ years in at least one role preferred).

Technical strength:

• We are not expecting all four stacks. We are expecting real depth in one, working competence in a second, and genuine appetite for the rest.
• Deep in at least one: Android (Kotlin) or iOS (Swift), you understand the platform, not just the framework. Lifecycle, permissions, background behavior, memory, and the real reasons build and break.
• Working competence in at least one cross-platform stack: Flutter (Dart) or React Native (TypeScript).
• Comfortable crossing the native bridge in both directions: platform channels, native modules, and WebView messaging.
• Solid grasp of mobile release engineering: signing, provisioning, Gradle/Xcode build configuration, CI for mobile, and staged rollouts.
• Debugging on real devices, not just simulators, device fragmentation, OS-version differences, and OEM quirks.
• Testing instincts: unit, widget/UI, and E2E on device. Knows which is worth writing.

Product and domain:

• Security-aware. You'll work on payments and KYC. Card data, PII, and identity documents pass through your code. You treat logging, storage, screenshots, clipboard, and crash reports as security surfaces, not afterthoughts.
• Merchant empathy. Our SDK lands inside someone else's app, and their bug is our bug. You think about the integrator's experience, not just ours.
• Clear communicator. Asks early, flags risk early, and writes a PR a reviewer can actually review.

Nice to Have:

• Existing SDK or library published for external consumption.
• Fintech, payments, KYC, or compliance product experience.
• Experience migrating a hybrid/WebView product toward native.
• Familiarity with mobile observability (Sentry, Crashlytics) and crash-free rate as an operating metric.
• Exposure to accessibility and localization on mobile.