Cloud Infrastructure Architect

About this role

Infrastructure owns the path from commit to production and everything that keeps it standing: build, deploy, observability, capacity and incident response.

Own the shape of the cloud estate across regions — network, isolation, disaster recovery, and the bill.

Multi-region, containerised, with tenant isolation that has to hold under load. The interesting problems are in resource isolation and in making a deploy boring.

Primary responsibilities

• Design the cloud architecture across regions, including the data residency constraints that shape it
• Own the network topology, the account structure and the security boundaries between them
• Design for disaster recovery to a stated RTO and RPO, and test that the plan works
• Own cloud cost — architecture is where most of it is decided, not the billing dashboard
• Set the standards teams build to, and review the designs that deviate

Skills required

Day to day this role works with Terraform, AWS, Networking and Cost Optimisation.

• Ten or more years in infrastructure, including a multi-region production estate
• Seven or more years in cloud infrastructure with architecture ownership
• Multi-region design including data residency constraints
• Network topology, account structure and security boundaries
• Disaster recovery designed to a stated RTO and RPO, and tested
• Cloud cost as an architectural concern

Preferred

None of these are required. They are the things that would help, and a strong application is regularly missing all of them.