Cloud Engineer

You know the difference between something that looks scalable in a diagram… and something that actually holds up when data is flying through it all day.

This is the second one.

You’ll be working on a platform sat in the middle of real-world operations — ingesting, processing and moving data continuously, across regions, with no room for guesswork when it comes to reliability or security.

It’s not greenfield. It’s not a mess either.

It’s at that stage where good engineers make a big impact — tightening things up, improving how it scales, and making sure it doesn’t fall over when it matters most.

• Building Azure infrastructure properly (Terraform / Bicep — not portal clicking)
• Working across IoT Hub, Service Bus/Event Hubs, Functions, storage
• Designing systems that handle failure properly (retry, idempotency, dead-lettering)
• Running clean multi-environment setups (dev/test/prod)
• Monitoring, alerting, performance tuning — real accountability
• Implementing secure-by-design principles (RBAC, Key Vault, managed identities)

You’re not handing things off — you’re responsible for how it behaves in production.

• Infrastructure as Code (Terraform or Bicep)
• Event-driven architecture / messaging systems
• Someone who understands production systems — not just dev environments
• Solid grounding in security (access, identity, secrets, networking)

Nice to have:

• Experience in regulated / operational environments

• Systems that actually get used — constantly
• Engineering problems that don’t have obvious answers
• High ownership — you’ll feel your impact
• Plenty still to improve, not just maintain
• A platform that’s scaling, not standing still

Hybrid role — 2 days a week on-site in Oxford

If you care about how systems behave under pressure, you’ll like this one.