This list contains only the countries for which job offers have been published in the selected language (e.g., in the French version, only job offers written in French are displayed, and in the English version, only those in English).
Global Technology Solutions (GTS) at ResMed is a division dedicated to creating innovative, scalable, and secure platforms and services for patients, providers, and people across ResMed. The primary goal of GTS is to accelerate well-being and growth by transforming the core, enabling patient, people, and partner outcomes, and building future-ready operations. The Platform Compute Networking (EKS) Team’s mission is to reduce the cognitive load of Resmed's development teams with an opinionated, yet empathetic experience that avoids surprise, balances usability with functionality, and abstracts the complexities of modern networking practices to accelerate the pace of Resmed’s next generation Healthcare Informatics platform. As an Associate Software Engineer in compute networking, you bring curiosity about how services talk to each other, how traffic stays secure, and how good abstractions help developers move faster. You will collaborate with experienced engineers to ship incremental platform features while growing toward larger design ownership.
Job Responsibility:
Implement platform networking features under mentorship (e.g., simple CRDs/Helm templates, ingress or DNS configs, NetworkPolicy modules)
Assist in design discussions—asking clarifying questions, researching options, summarizing trade‑offs
Contribute code, scripts, and automation that are tested, observable, and continuously deployable
Add or refine developer documentation (how‑to guides, “why can’t this connect?” checklists, glossary)
Participate actively in code reviews—applying team standards and proposing small improvements
Help build and refine sample patterns (internal service, public endpoint, secure egress)
Add basic telemetry (metrics, logs, traces) to new components and verify visibility
Triage and fix defects or configuration drifts with guidance
comfortable stating “I don’t know yet” and following up after research
Interest in learning: mTLS, certificate rotation, egress governance, rate limiting, and performance basics (latency, saturation)
Nice to have:
Exposure to GitOps (Argo/Flux), Infrastructure as Code (Terraform/CDK), policy engines (OPA/Kyverno), service mesh or Gateway API, eBPF/Cilium, cost or traffic dashboards is an asset
Exposure to basic cloud provider concepts (IAM roles/policies, VPC/subnets, load balancers) is an asset