Senior PHP/Laravel/Liverwire Developer

Summary Location: Remote — must overlap Australia / Sydney business hours (AEST/AEDT) Time Tracking: TimeDoctor (screenshots + activity tracking) — required for the duration of the contract Experience: 8+ years professional PHP / Laravel development Working hours: 40 hours/week Monday to Friday Positions: 3 — Clinical & Supplier Integrations, Business & Financial Integrations, Product Features About the Project We build and run a multi-tenant practice management platform used by healthcare clinics — patient records, appointments, clinical notes, prescriptions, invoicing, and reporting. The platform is a set of interconnected Laravel applications sharing a central PostgreSQL database, and we are progressively rewriting our main portal into Laravel + Livewire 3. We are hiring three senior Laravel developers. All three sit on the same platform and share the same bar; they differ in what each owns. This document is the baseline every candidate must clear before their specialisation is considered. Each role has its own job description covering what it adds on top. The Three Positions • Clinical & Supplier Integrations — supplier and laboratory ordering systems, health-claims and rebate platforms, partner clinical networks. Correctness over speed. • Business & Financial Integrations — accounting platforms, email and calendar providers, payment terminals and banking APIs. Money and communications, both unforgiving. • Product Features — new customer-facing features including AI-assisted clinical documentation and self-service financial tooling. UI-forward; the only role where Livewire is a hard requirement. Requirements Experience & Skills • 8+ years building production PHP applications, with at least 5 years in Laravel (Laravel 9+), hands-on and current. Not “I led a team that used Laravel”. • Large or long-lived production systems — code with history, constraints you did not choose, and users who noticed when it broke. A string of greenfield builds is a different kind of experience; this platform is not a greenfield. • You have owned something in production — not just built it, but carried it, watched it fail, and fixed it. Be ready to talk about a specific failure in detail. • Eloquent at depth — relationships, eager loading, query performance, and knowing when to drop to the query builder or raw SQL instead. • Strong SQL — non-trivial queries, joins, indexes, and the ability to read a query plan and act on it. PostgreSQL preferred; MySQL transfers fine. • Queues and background jobs — Laravel queues, Horizon, Supervisor or equivalent. You have debugged a job that failed silently in production. • REST and web services in general — HTTP semantics, auth headers / bearer tokens, status-code handling, retries/backoff, idempotency, and what happens when a request times out mid-write. • Reading code you didn’t write — much of this work is understanding existing systems before changing them. Comfort navigating an unfamiliar codebase is essential. • Multi-tenant awareness — every record here is scoped by account and practice; getting that wrong is a data-leak class of bug, not a cosmetic one. • Able to work independently — self-directed and comfortable owning a component end to end with minimal supervision. • Testing & QA — can write unit and feature tests (Pest or PHPUnit), perform manual QA, identify and log defects, and verify fixes against acceptance criteria. • Agentic Coding — familiar with Claude Code in coding, testing, and review in the workflow. • Project Management — capable of lightweight PM tasks: tracking milestones, updating task status, flagging blockers proactively, and estimating remaining effort. • Security Awareness — aware of data sensitivity and handling. This platform holds patient and financial records. • Good verbal and written communication in English — clear and professional in async written communication (Slack, Jira, Confluence) and comfortable in spoken sync calls. Tools & Workflow • Comfortable working in our toolchain: Jira (issues/sprints), Confluence (docs), Postman (API testing), Sentry (error monitoring), and Bitbucket (source control / pull requests). • Clean commits, clear pull requests, and clear written communication in English. Not Required Worth stating plainly, because it widens the pool without lowering the bar: • A degree. We care about what you’ve shipped. • Livewire — except for the Product Features role, where it is a hard requirement. • Tailwind or Alpine specifically — the fundamentals underneath them are what matter. • Python or Django — helpful for reading legacy business logic, not a requirement. • Healthcare or clinical software background — useful context, genuinely not a hard requirement. • PostgreSQL specifically — strong MySQL transfers fine. Working Arrangement • Project-based. 12-week initial term with milestones agreed up front. Extension expected for the right person. • Sydney business-hour overlap required for daily sync and quick turnaround on questions. A minimum of 6 hours of genuine overlap each working day is required — you don’t need to be Sydney-based. • TimeDoctor is used for time tracking and is a condition of the engagement; please only apply if you’re comfortable with activity monitoring. • Resources provided: codebase access, database schema documentation, and a staging environment to test against. How to Apply Please include: • Which of the three positions fits you best and why. If more than one does, say so — we’d rather place you well than fill a slot. • Relevant Laravel work — links or descriptions of comparable projects, and what you owned on them. • Links to any code you’ve written — GitHub, GitLab, personal projects, anything. • Your experience with agentic coding tools — which you’ve genuinely used, one task you completed with one, and one time the tool got it wrong and how you caught it. • Examples of working independently and owning a component end to end. • Any Testing, QA, or light project management experience. • Your time-zone and the daily hours you can overlap with Sydney. • Confirmation you’re comfortable using TimeDoctor, Jira, Confluence, Postman, Sentry, and Bitbucket. • A rough estimate / milestone breakdown for work of this shape, and your rate. Candidates who name the position they’re targeting and address its specifics directly (rather than a generic CV) will be prioritised.