AI Job Summary

- Shipped React Native apps to both iOS and Android, handling platform issues and build/release process.
- Uses TypeScript as the working language, writing it daily and understanding its type system beyond basics.
- Daily AI-assisted development practice using tools like Claude Code/Cursor/Copilot (not occasional/optional).

Role Type

Permanent • Full time • Mid-level Senior

Description

Senior React Native Engineer

Trilogy Care | Brisbane (Bowen Hills) | Hybrid | Full-time

We’re building a mobile application that puts aged care recipients and their families in control of their care — budgets, providers, schedules, notes, the full picture. It’s a React Native / Expo application backed by a Laravel REST API, and it’s about to go to beta.

The mobile team is new and growing fast. Right now there’s one permanent engineer, with two more starting this month. We’re hiring senior engineers to join them and help shape the product, the architecture and the team culture from the ground up. You won’t be inheriting a legacy codebase — you’ll be building the one that lasts.

We practice a full AI SDLC. Claude Code is how we build — not an experiment, not optional. If you’ve been waiting for a team that takes AI-assisted development seriously, this is that team.

The code you write directly affects whether older Australians and their families can see and manage the care they’re funded for.

What you’d actually work on

The mobile application is the care recipient’s window into their services. It handles:

- Care visibility — what services are scheduled, who’s providing them, notes and updates from care partners
- Budget and spending — real-time view of approved budgets,



utilisation and remaining funds across funding streams
- Provider management — viewing and interacting with their network of care providers
- Notifications and communication — keeping care recipients and their families informed as things change
- Onboarding and profile — the experience of a new care recipient getting set up and oriented

The application is built on React Native with Expo, targeting web, iOS and Android from a single codebase. It interfaces with the existing web portal through a dedicated REST API built in Laravel/PHP. The mobile team owns that API — you’ll work across both the React Native frontend and the PHP backend that feeds it.

You’d join a squad that’s forming now. This is a genuine greenfield opportunity — the architecture decisions you make in the first six months will define how the application scales.

What we expect from a senior

This isn’t a role where you receive a Jira ticket with acceptance criteria and implement it. Our seniors own the solution:

- Understand the problem — work with BAs and stakeholders to understand what care recipients actually need, not just what’s specified
- Design the approach — contribute to architectural decisions for a mobile application in its formative stage. Navigation structure, state management, offline patterns, API contracts — these are live decisions,



not settled ones.
- Build it with AI — use Claude Code as a core part of your daily workflow, not as an occasional shortcut
- Ship it — automated tests, code review, store submissions, OTA updates, monitoring
- Raise the bar — substantive code reviews, pairing with other engineers, setting the technical standard for the squad

The mobile team is small. Your influence on its direction will be outsized.

What you need

Non-negotiable:

- Production experience with React Native — you’ve shipped applications to both stores, dealt with platform-specific issues, managed the build and release process. Not a personal project — production, with real users.
- TypeScript as your working language — not something you’re planning to learn. You write TypeScript daily and understand its type system beyond the basics.
- AI-assisted development as a daily practice — Claude Code, Cursor, Copilot or similar. You should already be working this way. We’re not looking for someone who’s “open to trying AI tools.”
- Mobile-specific depth — you understand the differences between mobile and web development at an architectural level: navigation, app lifecycle, push notifications, deep linking, background tasks, OTA updates, platform-specific behaviour. You’ve solved real problems in these areas, not just read about them.
- REST API consumption and design — the mobile app depends on well-structured API contracts. You can design them, not just call them.
- Automated testing — you write tests because they make you faster, not because someone told you to. Jest, Detox, Maestro — the tool matters less than the habit.
-

📌 Senior React Native Engineer (Brisbane)
🏢 Employment Hero
📍 Brisbane