Cloud Platform Engineer
Posted 2 Oct 2026
Advertised as “Principal Cloud Platform Engineer”
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 10+ yrs
- Management level
- People management
- Employment
- Hybrid
- Contract
- Full-time
No salary listed for this role.
Field of studyComputer Science, Engineering (or related)
Study levelBachelor's or higher
Company Description
Nearmap is unique. An Australian global technology company with incredible people; a market-leader with energy and spirit. Nearmap was named as one of the world’s 10 Most Innovative Companies of 2020 by Fast Company magazine – and we’re growing.
Nearmap provides a virtual model of the real world – at a scale and detail that hasn’t been done before. Our ambition is to be the source of truth that shapes our liveable world. At Nearmap, we have an appetite for energetic and engaged people and we are currently seeking a Principal Cloud Platform Engineer to join our DevOps team.
Job Description
What you’ll do
As Principal Cloud Platform Engineer, you’ll own the cloud foundation that Nearmap AI runs on. You’ll lead a team of up to three engineers, set the technical direction for the infrastructure layer beneath our machine learning platform, and stay hands-on in the systems you design.
This is a leadership role for a seasoned engineer who thinks in systems. Nearmap captures and processes aerial imagery at a scale that breaks most infrastructure: thousands of EKS nodes running batch inference, GPU fleets spanning two clouds, and production model endpoints behind customer products. Someone has to make that substrate reliable, secure, and affordable. That’s you.
Reporting to the Director, AI Systems Engineering, you work side by side with the Principal AI Platform Engineer. They build the machine learning platform: workflow orchestration, distributed training, serving, and LLMOps. You build what it stands on: the Kubernetes fleet across AWS and GCP, GPU-capable compute, networking, identity, infrastructure as code, CI/CD, and the observability and security foundations every AICV service depends on.
To be clear about the boundary: you own the infrastructure platform, not the machine learning tooling that runs on it, and not the customer-facing AI products. Your first customer is AICV, and it is the most demanding infrastructure customer we have. What proves out there sets the pattern for the wider Nearmap developer platform, so you’ll co-own standards, paved paths, and shared components with the Platform team in ETO.
Day to day, you’ll:
-
Own the technical direction for cloud infrastructure across AICV: Kubernetes fleet design on EKS and GKE, compute, networking, identity, and storage.
-
Design and operate GPU-capable compute — node pools, drivers, device plugins, autoscaling, and multi-tenant isolation — so the AI platform team schedules against it without thinking about the hardware.
-
Make the critical infrastructure design calls, and run technical evaluation and build-versus-buy with the Director and your AI platform counterpart.