Cloud Engineer in Slough

The Role

We are looking for a highly technical Principal Cloud Engineer to help define and build our cloud strategy from

the ground up.

This is a senior individual contributor role where you will help shape our cloud direction, define the target architecture and work alongside engineering teams to build the foundations.

We are looking for someone who can combine strong architectural thinking with hands-on technical experience

- someone who can help us determine the right approach for Telco Customer, explain the trade-offs and then work with engineers to make it a reality.

You will have significant autonomy and influence over our cloud architecture, engineering standards and technical direction.

Cloud Strategy & Architecture

• Help define our overall cloud strategy and target architecture.

• Work with our Architecture community to establish and roll out practical architectural principles and standards.

• Define the foundations required to support scalable, secure and resilient workloads.

• Create a pragmatic roadmap from initial cloud foundation through to production.

• Make architectural decisions based on business and technical requirements.

• Work with technology leadership, architects, Solution Designers and engineering teams to align on the

approach.

Build the Cloud Foundation

• Cloud account/subscription and landing-zone architecture.

• Identity and access management.

• Network architecture and connectivity.

• Security and governance foundations.

• Infrastructure as Code and automation.

• CI/CD and deployment patterns.

• Observability, logging and monitoring.

• Secrets and key management.

• Resilience, backup and disaster recovery.

The aim is to create a secure, scalable and well-automated cloud foundation that engineering teams can build on.

From Architecture to Reality

• Work directly with engineers to build the initial platform.

• Create reference architectures and reusable patterns.

• Develop prototypes and proof-of-concepts where useful.

• Review and challenge technical designs.

• Help establish engineering standards and patterns.

• Get involved in complex technical problems when required.

You should be comfortable moving between high-level architecture discussions and detailed conversations

around networking, IAM, Kubernetes, APIs, distributed systems, Infrastructure as Code and cloud services.

Must-Have

• Significant experience designing and implementing cloud architectures.

• Proven expertise in designing and implementing solutions on AWS and Azure cloud platforms.

• Strong understanding of modern cloud architecture and distributed systems.

• Strong networking and Infrastructure as Code experience.

• Experience designing secure, highly available and resilient systems.

• Strong understanding of cloud security and identity.

• Experience with containers and Kubernetes or comparable technologies.

• Experience with APIs, integration, messaging and event-driven architectures.

• Experience influencing cloud or technology strategy at senior level.

• Strong architectural judgement and ability to explain technical trade-offs.

• Experience working closely with engineers and Solution Designers to turn architecture into working solutions.

• Ability to work independently and create clarity from ambiguity.

• Strong communication and influencing skills, with the confidence to navigate complex stakeholder environments and engage effectively with senior architects, engineering leaders and security stakeholders.

Preferred

• Experience building a cloud platform or foundation from the ground up.

• Platform engineering experience.

• Experience with CI/CD and cloud automation.

• Experience establishing reusable engineering and architectural patterns.

• Experience working across complex technology estates or highly integrated platforms.

Telecom / MVNO Experience

• Telecom or MVNO experience is nice to have, not essential.

• Experience with highly integrated, high-volume or customer-facing platforms would also be valuable.

The Person

• Enjoys starting with a blank sheet of paper.

• Thinks strategically without losing technical depth.

• Wants to build, not simply advise.

• Is comfortable making decisions with incomplete information.

• Challenges assumptions constructively.

• Understands that architecture is about practical trade-offs.

• Can communicate effectively with both engineers and leadership.

• Is comfortable operating in an environment with multiple senior technical stakeholders and competing

perspectives.

• Takes ownership from architecture through to implementation