eiGroup

At eiGroup, we believe ideas can change industries - but only if they are nurtured with structure, science, and courage.

We’re an R&D and Innovation Venture Studio that transforms human ingenuity into technological value that scales.

Our ecosystem brings together researchers, engineers, and creators who turn complex challenges into scalable products - from subsurface imaging to AI-driven analytics, from remote sensing to digital transformation.

Our ventures are built in-house, born from research, and grown into independent companies.

Together, we’re shaping how innovation takes root in this region - and how it reaches the world.

• →Own CI/CD across Azure Pipelines and GitLab CI: YAML pipelines, multi-stage builds, environment promotion, approvals, artifact and container publishing, shared templates so each team isn't reinventing its own build
• →Provision and run our Kubernetes clusters, including standing up new ones from scratch with Rancher: workloads, ingress, secrets, resource limits, autoscaling, rollout and rollback strategy, Helm charts, version upgrades and etcd backups
• →Own our Azure estate — App Services, compute, networking, storage, Key Vault, managed identities — alongside self-hosted services running on our own infrastructure, including cost hygiene and right-sizing
• →Introduce Infrastructure as Code (Terraform or Bicep) from a largely manual starting point: reusable modules, state management, real parity between environments
• →Build and maintain monitoring and alerting: metrics collection, Grafana dashboards the teams actually use, centralised logging, and alerts that fire on real problems rather than noise
• →Own production: releases, incident response, root cause, backup and restore drills, and an on-call rotation designed to stay quiet
• →Manage secrets and access properly (Key Vault, managed identities, Entra ID, least-privilege RBAC) and put secret, dependency and image scanning into the pipelines
• →Work with the Project Managers across our ventures: take in infrastructure requests, prioritise them honestly against each other, and propose the cheaper version when there is one
• →Plan and report your work in Azure DevOps — break requests into tasks, create your own where the work originates with you, keep status current, and raise blockers early enough that PMs can plan around them

• 3+ years in DevOps, SRE or platform engineering, with real production ownership
• Strong hands-on Linux — comfortable in the shell, able to debug a failing service without a UI
• Proven CI/CD experience with Azure Pipelines, GitLab CI or equivalent, including pipelines other teams depend on
• Kubernetes in production: deployments, services, ingress, config and secrets, RBAC, autoscaling — and the ability to diagnose why a pod won't start or a rollout is stuck. Helm for packaging. You have built a cluster from scratch, not only deployed into one
• Solid Docker fundamentals: multi-stage builds, image size, base image hygiene
• Microsoft Azure: compute, networking, storage, Key Vault, managed identities, Entra ID, Azure Monitor
• Infrastructure as Code with Terraform or Bicep — nice to have
• Scripting in Bash plus Python or PowerShell — enough to automate a task properly instead of documenting a manual one
• Networking fundamentals: DNS, TLS and certificates, reverse proxies, load balancing, VNets, subnets, NSGs, firewall rules
• Databases from the operations side: backups and tested restores, connection pooling, working with developers on a slow query
• Sound security instincts — you notice the exposed secret, the public endpoint, the permission nobody needed
• Able to serve multiple teams with competing requests, work independently, estimate credibly and flag risk early
• Good written and verbal communication in English