You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
IFS

Platform Engineer (Senior) - IFS Logistics

  • Hybrid
  • 6+ years

Salary

Not stated

Similar roles pay £45K - 75K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company helps enterprise shippers link transport data, control carrier spend and automate execution.

It is a small, focused team that works closely with the commercial side of the business.

The company builds SaaS products that customers can run themselves. The platform supports data-heavy logistics operations, where uptime and visibility are needed every day.

The team is growing and needs to ship faster. That calls for better visibility, stronger data pipelines and release controls that do not depend on individual memory or manual steps.

The Lead Platform Engineer currently carries too much of the platform work alongside the Agentic SDLC software factory. This role adds capacity to improve the platform and support production.

Within 6 months, monitoring should catch production problems before customers report them, pipeline failures should be detected, assigned and recovered cleanly, merge-request review and controlled production deployment should be enforced by the pipeline, weekly releases should run predictably, GCP spend should map to workloads and product areas with action taken on the main drivers, and the application and data teams should have a responsive platform partner.

Responsibilities

  • Work as the second DevOps specialist on the platform, alongside Diego Silva, the Lead DevOps Engineer, taking full ownership of major workstreams with application and data engineers.
  • Start on urgent work straight away: make sure every merge request is reviewed, production deployments are controlled and releases follow a predictable schedule. These habits are not yet applied consistently across the team.
  • Extend monitoring across more of the application and data estate, and make pipelines better at detecting failures, recovering from them and assigning ownership.
  • Support three live environments for enterprise logistics customers, roughly 130 repositories delivered through GitLab CI and Argo CD, 200 reconciled applications, a Terraform foundation built in 8 stages, and a service mesh and policy engine in production.
  • A change to the shared service chart reaches every service that uses it. The estate is dense rather than large, and it is live. Much of it still needs work, and that work is the job.
  • Build better signals, safer delivery paths, faster recovery and infrastructure the team can understand. This is hands-on work for someone who prefers improving a running platform to waiting for an ideal starting point.
  • Improve metrics, logs, traces and alerts across the Django API, data pipelines and warehouse so problems are spotted early and diagnosed quickly.
  • Make GitLab pipelines fast, reliable and hard to bypass, with review and deployment controls built into the workflow.
  • Remove direct production paths, strengthen release controls and help the team hold a dependable weekly release rhythm.
  • Make GCP spend visible by workload and product area, and cut waste without lowering service quality.
  • Improve Terraform and Kubernetes so environments are reproducible, secure and clearly documented.
  • Add failure detection, freshness checks, replay paths and clear ownership across Datastream, Pub/Sub, dbt and BigQuery.
  • Help shape incident management and on-call practice, then turn repeat failures into automated checks and safeguards.

Requirements

  • You have run production services on GCP over a sustained period.
  • You can operate and improve Kubernetes and Terraform infrastructure, not just deploy onto it.
  • You have designed and maintained CI/CD pipelines in GitLab or a comparable platform.
  • You have added metrics, logging, tracing or alerting to a real system and measured the improvement.
  • You have treated cloud cost as engineering work: attributing spend, finding waste and weighing trade-offs.
  • You have run data pipelines such as streaming ingestion, warehouse loads, dbt transformations or similar.
  • You will challenge an unsafe change and set out what must happen before it can ship.
  • You have hands-on experience with AI coding tools such as Cursor or Claude, including how you supply context and check infrastructure changes before accepting them.
  • You can judge an imperfect system, pick out the problems that matter most and carry the fix through to production.
  • You know enough Python to investigate or fix problems in a Django application.
  • You have done security or compliance work in an enterprise SaaS setting.
  • You have designed incident management or on-call processes.
  • You have tuned BigQuery for cost and performance.
  • Current stack: GCP, Kubernetes, Terraform and GitLab CI/CD; Python, Django REST, TypeScript, Node and React; BigQuery, dbt, Cube Cloud and Superset; Pub/Sub and Datastream. The team uses Claude for development, Notion for specifications and Jira for delivery.

Conditions

Ideally based in the UK or the Netherlands, or elsewhere in Europe on CET.

Remote team with clusters of people in London and Amsterdam.

Flexible and hybrid working options are available.

The company welcomes applicants from all backgrounds and values an inclusive workplace.

Where you’d work

Part of the week in the office

You can work from

  • United Kingdom

About the company

IFS

Office in London, United Kingdom

Also hiring in United Kingdom, United States, Madrid, Spain and 8 more places

10 of their 42 open roles are remote

Your chances

We've checked whether it's still hiring and how crowded it is.

  • 19 checks run
  • 0 red flags

Still hiring?

13 checks

No red flags

How crowded?

6 checks

No red flags

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details12 facts · Role, Location, Compensation, Employment
Tech stack
  • Python
  • Kubernetes
  • Terraform
  • CI/CD
  • GitLab
  • Argo CD
Seniority
Senior
Type
Full-time
Specialty
DevOps
Region
United Kingdom
Pay period
Annual
Show 6 more factsShow less

Role

Category
DevOps & Infrastructure
Specialty
DevOps
Seniority
Senior
Experience
6+ years
Tech stack
  • Python
  • Kubernetes
  • Terraform
  • CI/CD
  • GitLab
  • Argo CD

Location

Work model
Hybrid
Region
United Kingdom
Office
  • London, United Kingdom
Remote from
  • United Kingdom

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Full-time

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason