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 strategy of GTS focuses on aligning goals and promoting collaboration across all organizational areas. This includes fostering shared ownership, developing flexible platforms that can easily scale to meet global demands, and implementing global standards for key processes to ensure efficiency and consistency. At Resmed, we are changing lives with every breath – we improve patient quality of life, prevent chronic disease progression and reduce healthcare system costs. 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. Our Ideal Candidate Is curious about how requests move (client → DNS → ingress → service → egress) and wants to demystify the layers (L3/L4/L7, TLS, policies) Enjoys backend/infrastructure work (containers, APIs, configuration) and is eager to learn Kubernetes networking patterns Writes clear, maintainable code with basic tests and asks for early feedback instead of getting stuck Treats simplicity, reliability, and maintainability as part of “done” Documents what they learn—turning tribal knowledge into quick start guides or FAQs Breaks problems into small, reviewable pull requests and iterates quickly Learns from production issues (postmortems, reading logs/metrics) to strengthen future changes Sees this role as a path toward owning connectivity abstractions and influencing developer experience over time