Mobile Engineer - Frontend

glomo; Bengaluru; On-site; INR 1,800,000 - 3,200,000; Full time

Job summary

Glomo is hiring a mobile-focused engineer to own the SDK surface and drive native Android and iOS capabilities in addition to Flutter and React Native wrappers. You will ship on-device security features, cross-platform APIs, and robust release pipelines for merchant integrations.

You will work with a senior engineer from day one, delivering production-grade SDKs that merchants embed in their apps, with an emphasis on reliability, performance, and secure handling of payments and identity data.

Qualifications

• 3–5 years building and shipping production mobile applications or SDKs.
• Apps published to Play Store / App Store, or SDKs consumed by external teams.
• Stability: 2+ years in at least one role.

Responsibilities

• Build and ship Flutter and React Native SDKs — versioning, releases, distribution.
• Extend into native Android (Kotlin) and iOS (Swift) SDKs as we bring in-house.
• Design consumer-facing SDK APIs with sane defaults and clear errors.
• Release pipelines, real-device E2E testing, and crash-free observability.

Job description

About the Role

We're building the next generation of cross-border fintech infrastructure — powering payments, KYC, and global merchant experiences. Our merchants embed Glomo 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.

What You’ll Do

Own the mobile SDK surface

• Build and ship the Flutter and React Native SDKs — versioning, releases, changelogs, 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 integrating — sane defaults, clear errors, graceful fallbacks, honest breaking-change management.

Build native capability into payments and KYC flows

• Camera and document capture for KYC — ID capture, liveness, image quality handling on real-world devices.
• Secure file handling — pickers, uploads, encryption at rest, temp-file hygiene.
• On-device identity — biometrics, Keychain/Keystore, secure token storage, device attestation.
• 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.

What We’re Looking For

Experience

• 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 course work 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 behaviour, memory, the real reasons builds 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, WebView messaging.
• Solid grasp of mobile release engineering: signing, provisioning, Gradle/Xcode build configuration, CI for mobile, staged rollouts.
• Debugging on real devices, not just simulators — device fragmentation, OS-version differences, OEM quirks.
• Testing instincts: unit, widget/UI, and E2E on device. Knows which is worth writing.

Product & 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, writes a PR a reviewer can actually review.

How you work

• Uses AI tooling (Cursor, Claude Code, Copilot) for non-trivial work — and reviews its output critically. We expect this from day one.
• Self-directed. This role runs with high autonomy and low supervision.
• Finishes things. Ships on the date, or raises the flag well before it.

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 localisation on mobile.

As You Grow

• Own the mobile technical roadmap end-to-end across Flutter, React Native, Android, and iOS.
• Set mobile engineering standards — architecture, release process, testing, observability.
• Mentor engineers and lead code review across the mobile surface.
• Represent mobile in cross-team architecture and product decisions.
• Contribute to hiring and building out the mobile function.

How We Work

• Own features end-to-end — not just tickets.
• Ship fast, with a strong focus on quality.
• Work directly with founders and leadership.
• Build systems running in real production environments, moving real money.

What We Value

• Ownership: takes initiative and drives outcomes to done.
• Craft: cares about performance, UX, and the details users feel.
• Pragmatism: balances speed with long-term maintainability.
• Curiosity: open to learning new platforms and new domains.
• Honesty: clear about what they know and where they're growing.

Why This Role

• Own a product surface, not a backlog — our SDKs are how merchants experience Glomopay.
• Take a hybrid product native, from the ground up, with real architectural latitude.
• Build in fintech at scale — payments, KYC, compliance, cross-border.
• Clear runway to lead the mobile function as it grows.