1. Role Requirements & Responsibilities

• The team aligned on the scope of the Cloud Engineering role, which includes:
  

• • Strong expertise in AWS services
    
  • Proficiency in Terraform for infrastructure automation
    
  • Experience with GitLab pipelines, scripting, and automation
    
  • Support for both on-premises infrastructure (VMware, physical servers) and cloud platforms
    

2. Core Technical Skills

• Adrian emphasised the need for:
  

• • Hands-on experience with Terraform, GitLab CI/CD, and scripting (Python/Bash)
    
  • Familiarity with Ansible for automation (potential expansion)
    
  • Building monitoring capabilities across hybrid environments
    

3. Infrastructure Scope

• The team supports:
  

• • In-house data centres managed by Alex’s team (VMware, trading platforms)
    
  • Cloud environments, primarily AWS, with some use of GCP
    
  • Standardisation and automation across both environments
    

4. AWS Services & Deployment Tools

• Key AWS services in use:
  

• EKS, RDS, EC2, S3, Athena, DataZone, Lake Formation, SNS, SQS
  

• Helm is used for Kubernetes add-ons; workload teams manage application deployments
  

5. Networking & Security

• Use of VPC endpoints and limited VPC peering
  
• Centralised network stack with firewall and load balancer support from the network team
  

6. Recruitment Process

• Candidates will complete a Terraform coding test via GitHub
  
• Solutions will be reviewed during interviews to assess practical skills
  

• Clarified distinctions between:
  

• Cloud Engineering – automation and cloud infrastructure
  
• Platform Engineering – tooling and deployment support
  
• Network Engineering – connectivity and security
  

• SME-level expertise expected for each role