Company Description: Phymes is dedicated to making the Australian care system more accessible and human-centered for people who rely on NDIS, aged care, disability employment support, and end-of-life services. The organisation reduces complex paperwork, jargon, and administrative burdens so individuals and providers can focus on meaningful support instead of navigating bureaucracy. By connecting people with the right support providers aligned to their needs, culture, and life circumstances, Phymes helps ensure care is timely and relevant.

Phymes also equips providers with better tools to reach those they can genuinely help and fosters a strong community so no one has to manage the care system alone.

What you will actually do

1. Own infrastructure-as-code deployed into GCP environment with all data resident in ap-southeast-2 (Sydney). No exceptions, ever.
2. Build and harden CI/CD pipelines where security controls (ASD Essential Eight, ISM alignment) are enforced in the pipeline, not reviewed after the fact.
3. Design observability so that when a service degrades, we know which participant journeys were affected, not just which dashboards went red.
4. Operate with a least-privilege mindset: identity, access, secrets, and audit trails designed for a future ISO 27001 and ISO 27701 certification posture, and for scrutiny under the Privacy Act 1988 and Australian Privacy Principles.
5. Build sandbox experimentation infrastructure: fast, cheap, disposable environments where radical infrastructure ideas can be proven or killed within hours.
6. Work directly with the founder/CTO on architecture decisions. You will be challenged to defend every choice from first principles, and you will be expected to do the same to us.

Must-have skills





We hire on demonstrated ability, not job titles or degree pedigree. Show us the work, not the acronym list.

- Production experience running infrastructure-as-code (Terraform or equivalent) on GCP or another major cloud, with a disciplined approach to state, drift, and blast radius.
- Solid CI/CD engineering: pipeline design, automated testing gates, progressive delivery, and rollback you have actually rehearsed.
- Deep working knowledge of containerised, microservice deployment patterns and their operational failure modes.
- Practical security engineering: IAM design, secrets management, network segmentation, and audit logging. You can explain what Essential Eight controls mean operationally, not recite them.
- Scripting fluency (Python, Bash, or Go) and comfort automating away anything you do twice.
- Clear written communication. Our standards live in structured documents; if you cannot write precisely, you cannot operate here.

What you will not find here

- No cargo-cult "best practice" mandates. Every standard must earn its place against latency, cost, and failure-mode reality.
- No production-by-default heroics. We experiment in sandboxes and graduate deliberately.
- No compliance theatre. Controls exist to protect participants, not to decorate an audit binder.

Hiring process

1. Short written exercise: a small infrastructure design problem, reviewed by the CTO. No whiteboard theatre, no trick puzzles.
2. Technical conversation about your past systems and their failure modes.
3. Founder conversation: mutual fit, direction, and expectations.

Skills over credentials: if you have built and operated secure, compliant infrastructure and can prove it, apply regardless of your background.

📌 DevOps Engineer (Hervey Bay)
🏢 Phymes
📍 Hervey Bay