> Markdown version of [/jobs/ext/4745371-senior-platform-engineer](https://www.wearedevelopers.com/jobs/ext/4745371-senior-platform-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Platform Engineer - **Company:** Hackajob Ltd - **Location:** London, United Kingdom (Remote available) - **Experience:** Expert - **Salary:** £12,000 - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Amazon Web Services, Amazon Cloudfront, Amazon S3, Microsoft Azure, Cloud Computing, Continuous Integration, DevOps, Programming Tools, Github, Identity and Access Management, Python (Programming Language), PostgreSQL, Node.Js, Redis, Test Execution Engine, TypeScript, YAML, Datadog, AWS Cdk, Amazon ElastiCache, Delivery Pipeline, Large Language Models, Multi-Cloud, Cloudformation, Kubernetes, Sentry, Cloudflare, AWS Fargate, Apache Kafka, Vertica, Functional Programming, Terraform, OpenSearch, Docker - **Published:** November 16, 2026 - **Apply:** https://www.totaljobs.com/job/senior-platform-engineer/hackajob-ltd-job108316875 ## About the Role * 4+ years in platform, infrastructure, SRE, or DevOps, with hands-on AWS at scale: ECS/Fargate, RDS/Aurora, Lambda, networking, IAM, KMS. ## Description We're looking for a Senior Platform Engineer to own how our client is built, shipped, and run, as we scale across our own cloud and into our customers' clouds. You'll own the infrastructure behind the platform, our deployment pipeline and developer tooling, and how we package our client to run inside customers' own AWS, GCP, or Azure accounts. It's a hands-on role with broad scope. You write code and tooling, you own the IaC other engineers depend on, and you set the standard for how every new repository gets deployed and secured. You'll report directly to the CTO and work closely with our Security Engineer and tech leads., * Own our infrastructure at scale: the AWS estate today (ECS Fargate, Aurora, ElastiCache, MSK, OpenSearch, Lambda, KMS) and the AWS CDK to Terraform migration. Keep it reliable, observable, and cost-aware. * Build out the deployment pipeline as we consolidate toward a monorepo: the CI/CD that ships every service, plus an automated end-to-end testing harness with incremental (affected-only) testing that stays fast as we grow. * Ship into customers' own clouds (self-hosted / BYOC): the Terraform modules, container images, runbooks, and documentation for internal teams and customers. * Own the release and upgrade path for self-hosted customers: versioned, signed releases, a supported-version policy, and a call-home for usage and version reporting. * Set the standard for new repositories: partner with the Security Engineer and tech leads so new projects (product, internal tools, and vibe-coded prototypes) ship secure and deployable from day one. Templates and golden paths, not gatekeeping. * Raise reliability: SLOs, observability, and incident response. Make the system easy to operate when something breaks at 3am. * Treat infrastructure as a product: paved roads and self-serve tooling so product engineers ship without waiting on you. * Use AI in the workflow: lean on LLMs and agents for IaC generation, test scaffolding, and runbook drafting, with guardrails you trust., * Deep IaC ability: Terraform and hands-on AWS CDK or CloudFormation. Our estate is CDK today and migrating to Terraform, so you will work in both. You are comfortable owning modules other teams build on. * Strong CI/CD and monorepo build experience: caching and incremental/affected-only test execution. You've made a slow pipeline fast. * Strong coding in TypeScript, Python, or Go. You build tooling, not just YAML and configs. * Containers and Kubernetes in production: Docker, and Kubernetes you have run yourself. Cluster setup, upgrades, resource limits, and the reasons a pod won't start. * Security-minded: you bake secure defaults into pipelines and repo templates, and partner with security rather than routing around it. * A clear writer: docs and runbooks that internal engineers and external customers can follow. * End-to-end ownership: you scope, ship, and measure, and automate instead of running manual checklists. Nice to have * Shipping software into customers' own cloud or on-prem (BYOC / self-hosted), or a platform like Nuon, Replicated, or Omnistrate. * Multi-cloud (GCP or Azure) IaC, and exposure to Temporal, Kafka/MSK, ClickHouse, or OpenSearch. Our stack * Cloud & infra: AWS (ECS Fargate, Aurora Postgres, ElastiCache, MSK, OpenSearch, Lambda, S3, KMS, CloudFront, WAF), GCP, Cloudflare (Workers, WAF) * IaC: Terraform and AWS CDK (migrating off CDK) * Data & messaging: Postgres, Redis, Kafka, OpenSearch, ClickHouse * CI/CD: GitHub Actions * Observability & analytics: Datadog, Sentry, Metabase * Languages: TypeScript (Node.js), Python