Platform Engineer, Liverpool: £45,000 to £60,000

If your idea of good work is infrastructure that other engineers barely notice because it simply holds, this page is for you. As with every role on this site, the difficult parts are printed, not implied.

What will you actually do as a platform engineer here?

You will be the platform specialist among product squads, owning the paths that everyone else's code travels. In practice:

• Building and maintaining infrastructure as code in Terraform on Azure, written so that product engineers can read it, review it and safely propose changes to it.
• Owning CI/CD through GitHub Actions: keeping deployments fast, boring and reversible, and improving the pipeline as the team and codebase grow.
• Engineering for multi-tenancy at scale: isolation between hundreds of client configurations, fair resource usage, tenant-safe rollouts, and the ability to trace a problem to one tenant quickly.
• Building observability that answers questions: metrics, logs and alerts tuned so that pages mean something and dashboards tell the truth.
• Handling security and reliability work to the standard enterprise clients audit us against, because they do audit us.

Day one, you inherit a working platform, not a greenfield or a ruin. Your first weeks are learning its shape and taking the on-call runbooks personally. Within a quarter, you should own improvements that product engineers can feel: faster pipelines, clearer alerts, safer rollouts.

What will you work on?

The substrate beneath everything on this site. Every product feature the other roles describe, conversational navigation, AI content generation with its LLM API pipelines and structured data, smart SEO automation, analytics dashboards, easy-apply overlays, runs on infrastructure this role shapes. The AI workloads are a growing and genuinely interesting slice: LLM-backed features have cost, latency and reliability profiles that classic web workloads do not, and building sane platform patterns for them is live work right now, not a roadmap promise. Full detail sits on the tech stack page.

What are the honest hard parts of this platform role?

Multi-tenant blast radius is real. A platform change here does not affect one site, it affects hundreds of client sites at once, including some belonging to the largest employers in the world. The care that demands is constant, and some engineers find that weight heavier than they expected.

You are a team of few among teams of many. Platform is a specialism here, not a large department. You get autonomy and ownership, and you also get fewer platform peers to debate with day to day. If you need a big platform guild around you, we are honestly too small for that yet.

Interruptions are part of the job. Product engineers bring you deployment issues, environment questions and the occasional self-inflicted wound. Protecting your project time while staying genuinely helpful is a skill this role never stops exercising.

On-call exists. The rota, its frequency and its compensation are stated plainly during the process. We will not pretend a production platform runs itself on business hours.

AI-era ground shift hits platform too. The LLM landscape changes quarterly, and cost and capacity planning for AI features is genuinely harder than for conventional workloads. Some of your best work will need revisiting sooner than you would like.

Who is this platform job not for?

• Engineers who want to gatekeep. The goal here is paved roads that make product teams faster and safer, not a ticket queue that makes them wait. If your instinct is control rather than enablement, we will frustrate each other.
• Pure Kubernetes-first purists who would resent Azure's managed services. We use the platform's managed offerings deliberately and spend our complexity budget elsewhere.
• People who need their work to be visible to be satisfying. Great platform work is invisible by definition, and praise arrives mostly as an absence of complaints.
• Anyone who wants to write product features half the week. This is a platform role. You will code plenty, but in Terraform, pipelines and tooling, not React.

How do you apply for this platform engineer job in Liverpool?

Apply through this page with a CV and a short description of an infrastructure problem you solved that you still think about, including what broke, or nearly did. War stories told honestly beat certifications listed neatly. The process includes a practical exercise around a realistic multi-tenant scenario, no whiteboard trivia, all described on the interview process page. Every application gets a human reply either way.

Frequently asked questions

Kick the tyres properly first

Platform engineers make decisions on evidence, so gather some: read the tech stack in full, look at what the Liverpool tech scene offers your career beyond us, and compare this against the other open roles. If the evidence stacks up, we would like to see your name come through.