You'll be the senior technical owner of AWS infrastructure connecting cloud services to a fleet of distributed edge devices. It's cloud engineering with real physical world consequences and it comes with a set of problems most cloud roles never touch, plus the rare chance to set the standards other engineers will work to for years.
The Technical Challenge:
- Design and run secure, multi-account AWS environments at a scale where governance isn't optional.
- Build the cloud-to-edge integration layer device connectivity, secure telemetry ingestion, OTA update infrastructure connecting cloud services to hardware in the field.
- Solve for devices that don't have a guaranteed connection: design for intermittent connectivity, fail-secure automation, and graceful degradation when a device drops offline mid-fleet.
- Manage firmware and update rollouts that can't afford to get it wrong compatibility across hardware revisions, staged rollout, safe rollback.
- Build tamper-evident audit trails and compliance logging fit for infrastructure operating in a regulated space.
- Own threat modelling, vulnerability analysis, and risk mitigation across infrastructure where downtime has real-world consequences.
- Keep cloud costs predictable as the device fleet and the data it generates keeps growing.
- Drive DevSecOps practice and architect the networking backbone (Transit Gateway, VPC, Route53) underneath it all.
The Culture Challenge:
- This isn't a role where you inherit someone else's playbook you're setting the engineering standards for cloud and edge infrastructure from the ground up, and what you establish now becomes how the organisation works for years.
- Good infrastructure that nobody trusts doesn't get used you'll need to build platform and security practices that teams actually want to adopt, not ones they go around.
- Turn hard-won lessons into docum