Mobile App Developer

The Role

We build a mission-critical platform used every day by councils, governments and businesses. Your work goes into the hands of real customers: communities recovering from natural disasters, governments managing national parks and critical infrastructure, and facilities teams caring for places like the Australian Parliament House precinct.

You will design and build native iOS or Android apps for phones and tablets. Both apps are offline-first, because the crews using them are regularly somewhere with no signal and cannot come back later. Work queues locally, syncs when the connection returns, and has to survive being interrupted halfway. Getting that right is most of the interesting work.

Both apps also ship as several white-labelled variants for different customers, each with its own branding, configuration and store listing. A change has to hold up across all of them, not only the build on your machine.

We have a twelve-month plan to move shared logic onto Kotlin Multiplatform, so that domain models, business rules and permissions live in one place rather than two. The work has not started yet, which means you would be joining at the beginning of it rather than inheriting someone else’s half-finished version. You do not need Kotlin Multiplatform experience to apply, but you will end up working in it.

Who we are looking for

• Three or more years of software development, with apps you can point to.
• Takes ownership of the work and wants to see its effect in the product.
• Enjoys refining an app rather than declaring it finished at feature-complete.
• Says what they think clearly, in writing and out loud.
• Works well with testers, designers and the API team, because none of this ships alone.

Requirements

One of the following two, and the third:

• Strong Android development in Kotlin and Java. Our Android app is largely Java with Kotlin alongside it, and both matter.
• Strong iOS development in Swift with UIKit.
• Experience with device SDKs and APIs: camera, GPS and background location, local storage, networking on an unreliable connection.

Also expected:

• Comfort with an established codebase that has years of history in it, rather than a greenfield start.
• Git and pull request review.

Useful, not essential: offline sync and conflict resolution, mapping libraries, Kotlin Multiplatform, writing tests before the code, Azure DevOps.

What you will work with

Android. Kotlin and Java on AGP 8 and compileSdk 36, Dagger, Room, RxJava 3 and coroutines, Retrofit and OkHttp, CameraX, WorkManager, MapLibre GL, and an NDK layer for the heavier map work.

iOS. Swift with UIKit, CocoaPods and Swift Package Manager, MapLibre GL Native, SQLite through FMDB, Pusher for realtime updates.

Both. Azure Pipelines for build and release, Firebase for crash reporting and distribution, per-flavour signing across every white-label variant.

What you will get

• Purpose. Build technology people depend on when conditions are bad.
• Growth. A cross-platform migration starting from scratch, which is the fastest way to learn a codebase properly.
• Culture. A small team that values trust, ownership and progress.
• Flexibility. Judged on outcomes, not hours at a desk.
• Opportunity. A growing company taking its platform to global markets.