Skip to content
CV Rocket
Get started
How it worksThe enginePricingBlogContactSign in

Open nowPosted 58 days ago

Mobile Engineer - Frontend

Glomopay9 open roles

Where
Bengaluru HQ
Work mode
Hybrid
Get the CV for this job

From $25 per CV, paid once. No subscription.

Your applicationOpen nowMobile Engineer - FrontendGlomopay · Bengaluru HQ

  1. YouYes, apply to this one.

  2. CV RocketCV written for this posting.

  3. 25 readersRecruiter, hiring manager, skeptic. Round after round.

  4. CV RocketApplied on Glomopay's own form.

The reply lands in your private mailbox

3×more interviews than doing it yourself with ChatGPT.

The clock on this job

Early applications get read.

8.1% of postings close within 7 days. Measured by our own scanner across the market.

Share of postings closed within
  1. 1.7%1 day
  2. 3.6%3 days
  3. 8.1%7 days
  4. 15.0%14 days
  5. 34.0%30 days
This job: posted 58 days ago

The posting

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 http://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

This role is scoped to grow. As you demonstrate ownership, the surface widens:

• 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.

We're building the mobile function from a small base. The person who owns it well ends up

leading it.

How We Work

We're a small, high-ownership team where engineers:

• 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.

From $25, paid onceGet the CV for this job

What happens when you press

One press. We do the rest.

  1. A CV for this posting

    Written against Glomopay's own wording, from every piece of relevant proof in your profile.

  2. 25 readers review it

    Recruiter, hiring manager, skeptic and more read every draft, round after round. You get the best round.

    The review screen in CV Rocket: how each CV was read, round by round.

  3. We apply on Glomopay's form

    Our application engine gets through the hardest forms there are. Where a question needs you, AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

    An application in CV Rocket: every answer filled in on the employer's form.

  4. Every reply, sorted

    Glomopay's answer lands in your private mailbox, and we classify it on arrival: interview, question, rejection.

    The CV Rocket inbox: each employer reply classified as an interview, an action or a rejection.

  5. Reply with AI

    AI helps you write the email, checks it and sends it. We show you whether the recruiter read it.

  6. The interview in your calendar

    Full integration with your calendar. The invitation goes straight in.

    An interview invitation in the CV Rocket inbox, added to the candidate's calendar.
Get the CV for this job

From $25 per CV, paid once. No subscription.

Why it works

3×

more interviews than doing it yourself with ChatGPT.

ChatGPT writes a CV and never learns what happened to it. We see every reply. For each CV we know:

  • How it was written, and how the review scored it
  • When we applied, and how long after the posting went up
  • Which posting, which company, which city
  • Who got the interview, and who heard nothing

That is how we know which CVs get called.

Get the CV for this job

From $25 per CV, paid once. No subscription.

The numbers game

More applications. More interviews.

Every application goes out with its own CV, written for that posting and paid once. Send enough of them and the law of large numbers finds you the job.

Get the CV for this job
By hand5–10
With CV Rocket100
applications a day

Nearby

Live postings like this one

Same employer first, then the same role elsewhere.

Before you press

Straight answers

Get the CV for this job

From $25 per CV, paid once. No subscription.

What if my background isn't good enough?

We make the most of the background you have. The CV uses every piece of relevant proof your profile holds, and one of the 25 readers reads your whole profile and flags what the CV left out.

Do you really apply for me?

Yes, on the employer's own form, the hardest ones included. Where a question needs you, you answer it right there and AI suggests the best answer. Don't want us applying from our IP addresses? Use our Chrome extension: we apply straight from your own browser.

Is it a subscription?

No. You pay once per CV, from $25. Every application goes out with its own CV, written for that posting.

One job. One CV.
Paid once.

Pick the posting you want. We write for it, apply for you and catch the reply.

Get the CV for this job

From $25 per CV, paid once. No subscription.