Senior Android Engineer

The Mission:

Millions of people open their banking app every day, and it can't freeze or go blank when a backend service goes down. You'll make the iOS app resilient, and you'll help build Open Banking features that let customers link accounts from other banks.

The Role:

This is a contractor role open to candidates based in Australia. You'll join a mobile engineering squad at one of Australia's largest banks and build an offline-first architecture in Swift and SwiftUI. The app stores 30 days of account state, transaction history, and linked bank data on the device, so customers keep access to their financial dashboard during an outage. It uses a SQLite caching layer, with networking and database code generated from gRPC definitions. The first 2 to 4 weeks are onsite in Melbourne, then it moves to hybrid.

Most Important:

• 5+ years of native iOS engineering, with deep expertise in Swift and SwiftUI
• Extensive production experience with offline-first apps on SQLite, for local data caching and offline state management
• A track record of building mobile architectures that handle network latency, backend outages, and background data sync without breaking the user experience
• Practical experience with gRPC services, Protocol Buffers, and automated code generation on iOS
• Reactive architecture experience (MVVM, Redux, or TCA) for managing concurrent data loading and UI state
• iOS security fundamentals: Keychain, certificate pinning, and OAuth2 flows
• Based in Australia and able to work onsite in Melbourne for the first 2 to 4 weeks

The Bonus Skills:

• Code-generation pipelines that turn API specs into SQLite schema migrations and DAO layers
• Working knowledge of Kotlin and Jetpack Compose, to keep architecture consistent with the Android squad
• FinTech background: retail banking, Open Banking (Consumer Data Right), or financial dashboard apps

Personal Traits:

• You design for the bad day. When an API times out, the screen keeps working, not a blank state.
• You know what's happening under the hood of your persistence layer, including SQLite performance, concurrency, and migrations.
• You prefer strongly typed contracts over loose JSON, and you like it when tooling generates the boilerplate.
• You treat security and pen test findings as part of the build, and you share context easily with a new team, onsite and after.