DevOps & Cloud Engineer

The role

You stand up and hold the entire estate: the production node, the pipelines that reach it, the observability that explains it, and a restore that has actually been performed rather than described. You also build fifteen workstations before nine people arrive on the same morning.

Key responsibilities

• Provision and harden production, and own database, cache and application deployment
• Build continuous delivery with automatic rollback — every merge tested, built and deployed to staging in ten minutes or less
• Own backup and disaster recovery to a four-hour restore and fifteen minutes of acceptable data loss
• Run a restore drill every month from September, each producing a filed evidence record
• Deliver observability in week one: structured logs correlated by job, metrics on gate and settlement variance, alerts that mean something
• Build and sign into fifteen complete workstations before the second wave arrives — a hard gate
• Write every procedure as a runbook somebody else could follow at two in the morning

Eligibility

• Four to six years in infrastructure, with a dedicated or bare-metal estate managed solo for two years or more
• Postgres-class database operations: backups, restores, replication, tuning
• A pipeline you built from nothing, including stabilising the flaky tests
• Disaster-recovery drills you personally ran, with a story about what failed the first time
• Monitoring built from scratch rather than bought as a bundle
• Cost awareness, and the instinct to read the exit clause before the price

What you get

• The whole estate, yours to design — hosting chosen on cost and exit terms, with no lock-in accepted
• A company that treats a rehearsed restore as the job, not as paperwork

How the process runs

• Fill in the short form on this page.
• We read it ourselves. Every application is read.
• If we want to meet you, we call you.