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.
- Mentoring instinct — you improve the people around you through code review, pairing and knowledge sharing. Not as a chore — as part of how you work.
Strongly valued:
- Experience with Expo specifically
Also valuable:
- Experience with PHP/Laravel on the backend — the mobile team owns their API, and engineers who can work across both layers are significantly more effective
- Experience in healthcare, aged care, government or other regulated environments
- Offline-first or sync architecture patterns in mobile apps
- State management at scale (Zustand, Redux Toolkit, TanStack Query)
- CI/CD for mobile (EAS, Fastlane, GitHub Actions)
- Accessibility in mobile applications
- AWS experience (S3, CloudFront, Lambda)
How the role evolves
We're explicit about where this is heading:
Now — AI-assisted. You use Claude Code, agent tools and AI-assisted workflows daily for coding, debugging, testing and documentation. You're faster and more capable because of these tools.
Next — AI-augmented. Agents produce first-draft implementations. You own architecture decisions and validate quality — reviewing agent-generated code the way you'd review a junior's PR, but at much higher volume.
Then — architect. The role evolves toward system design, quality governance and the complex problem-solving that agents can't handle independently. The engineers who grow into this are the ones who understand domains deeply enough to know when the AI is wrong.
This isn't a vague promise. It's our published career framework and it's already underway.
Why this role, at this company
- The work matters. This isn't a consumer app chasing engagement metrics. Trilogy Care manages real funding for real people. When you ship a feature, it affects whether an older Australian and their family can see and manage the care they need.
- You'd shape the product. The mobile application is pre-beta. The architecture, the patterns, the testing strategy — these are decisions being made now, by the people in the room. If you've ever wanted to build something from the foundations rather than maintain someone else's choices, this is that opportunity.
- AI is real here, not a slide deck. We don't have an "AI strategy" — we have an AI way of working. Claude Code is in every developer's hands, every day. The team lead who'd interview you in round two built their workflow around it.
- The team is small enough to matter. ~20 engineers across three squads. Your decisions, your code reviews, your mentoring visibly shapes how the team works. You're not a number.
- Autonomy is genuine. Squads own their projects. You'll be trusted to make technical decisions, push back on requirements that don't make sense, and ship when the work is ready.
The process
- This application — we review your experience against what's above
- Phone screen — 20 minutes with our recruitment team
- First interview — 1 hour with the Head of Product Development. Cultural fit, systems thinking, how you work.
- Technical interview — 1 hour with the squad's senior engineers. Not a whiteboard exercise — a conversation about how you approach real problems.
- Reference checks and offer — we move quickly
Practical details
- Location: Bowen Hills, Brisbane. Hybrid — primarily office-based with flexibility.
- Salary: Competitive, commensurate with experience.
- Work rights: You must have the right to work in Australia. Pre-employment checks include a National Police Check, international police check where applicable, and the Aged Care Banning Orders register.