Associate Engineer,Platform Engineering

Global Technology Solutions (GTS) at Res Med is a division dedicated to creating innovative, scalable, and secure platforms and services for patients, providers, and people across Res Med. 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.

• 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

• Implement platform networking features under mentorship (e.g., simple CRDs/Helm templates, ingress or DNS configs, Network Policy 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; learn safe rollout and rollback practices

• Practice secure defaults (least privilege security groups, minimal permissions, certificate hygiene)

• Continuously learn new networking and Kubernetes concepts and share concise summaries with the team

• BS in Computer Science or equivalent practical experience

• Proficiency in at least one programming language (Go, Python, Type Script, or Java) plus Git fundamentals (branching, pull requests)

• Academic, project, or internship exposure to core networking concepts (IP, DNS, HTTP, TLS) OR containerization fundamentals

• Ability to write unit tests and explain the difference between correctness tests and integration checks

• Basic understanding of Kubernetes objects (Pods, Deployments, Services) and curiosity about ingress, service discovery, and network policies

• Familiarity with scripting or simple automation (CLI tools, Makefile, shell, or basic Terraform)

• Foundation in observability basics (metrics vs logs vs traces) and desire to learn request tracing

• Unders…