Skip to content

Careers Engineering

Mobile Engineer (Flutter)

Ship apps to two stores from one codebase, including the offline case that nobody specifies until it fails.

Full-time Hybrid Pokhara, Nepal

Posted 25 Aug 2026

The job

Our mobile work runs alongside the platform it talks to, usually built by the same people. That means the interesting problems are at the seam: what happens on a bad connection, what happens when the local state and the server disagree, and what the app does on the third day rather than the first minute.

You would work on real apps with real users, and on the packages underneath them — some of which we publish, which means the API you design is one other people have to live with.

What you would be doing

  1. Build features against an API you helped specify, and push back when the shape is wrong.
  2. Treat offline and slow connections as the normal case, because for a lot of our users they are.
  3. Keep the release pipeline working — signing, store metadata, staged rollout, and the rollback when a build is bad.
  4. Profile before optimising, and keep the frame budget honest on a mid-range device rather than on yours.

What we need from you

Four or five things, not fifteen. A long list filters out the people who read it honestly and keeps the ones who do not.

  • You have shipped a Flutter app to both stores and dealt with the review process.
  • Comfortable with state management as a decision rather than a default, and able to justify the one you chose.
  • You test the parts that matter — the sync logic, the parsing, the money.
  • You have debugged something that only reproduced on a real device.

What would help, and is not required

  • Native experience on either platform when Flutter runs out.
  • You have published a package and maintained it.
  • Background sync, local databases, or anything involving a device that was offline for a week.

What you would work with

  • Flutter
  • Dart
  • REST / GraphQL
  • SQLite
  • Firebase
  • Fastlane
Apply for this role

It takes about ten minutes and goes to a person, not to an applicant tracking system. You will hear back either way.

Also open

Other roles

  1. Engineering

    Engineering Internship

    Six months on real work with a named mentor, real review, and your name on commits that ship.

    Internship On-site Pokhara, Nepal

  2. Engineering

    Senior Full-Stack Engineer

    Own a product surface end to end — schema, API, interface and the deploy — inside a client’s own repository and to their standards.

    Full-time Hybrid Pokhara, Nepal

  3. AI & Agents

    AI Engineer, Agents & Retrieval

    Build agent loops that can be audited and retrieval that holds up on somebody else’s documents, not on the demo set.

    Full-time Hybrid Pokhara, Nepal