Platform Engineer in London

Platform Engineer in London

London Full-Time 72000 - 88000 £ / year (est.) No working from home possible
G

At a Glance

  • Tasks: Own and optimise production platforms, enhance developer experience, and ensure system reliability.
  • Company: Gattaca, a forward-thinking tech company focused on impactful engineering.
  • Benefits: Top-tier salary, performance bonuses, equity options, and private healthcare.
  • Other info: Join a dynamic team with opportunities for growth and innovation.
  • Why this job: Make a real impact on engineering workflows and shape the future of our platform.
  • Qualifications: Experience in cloud infrastructure, automation, and a proactive problem-solving mindset.

The predicted salary is between 72000 - 88000 £ per year.

This role exists to increase the operating leverage of Gattaca’s engineering team. You’ll own the production platform, developer experience, observability, deployment workflows, internal tooling, and the feedback loops that let engineers ship quickly. At Gattaca, infrastructure directly affects market share and P&L. Strong production and platform engineers can have an outsized impact here because the platform is still early: there is room to set direction, establish the right operating model, choose the right abstractions and automations, and turn currently scattered workflows into reliable systems the whole team builds on.

Your day-to-day work will span these main areas:

  • Production systems and reliability: You’ll own the infrastructure and operational workflows that keep Gattaca’s production systems predictable. That means making deployments safe and repeatable, keeping rollback paths clear, improving host and service health, and making sure incidents are easy to understand when they happen.
  • Observability and alerting: You’ll help build the feedback loops engineers rely on to understand production. System metrics, logs, dashboards, traces, and alerts should make the state of the system obvious, especially when something is wrong. False alerting stops that, helping to really understand the system to know what to alert and what not to.
  • Developer experience: Given the rate of work and the size of the team, a lot of operational work can become manual unless someone owns it properly. You’ll improve the path from local development to production: faster CI, more reliable builds, better test environments, cleaner deployment tooling, simpler configuration and secrets workflows, and internal tools that remove repetitive manual work. Small improvements here compound across the whole engineering team and make a big difference.
  • Infrastructure performance: Our systems are latency-sensitive, and infrastructure details matter. You’ll work close to the boundary between application code and the machines it runs on: host-level tuning, networking behaviour, kernel settings, CPU isolation, resource contention, noisy neighbours, and the practical details of running high-performance services in production.
  • AI and internal tooling: We want to use AI where it genuinely increases engineering leverage. As the team moves quickly, useful context can become fragmented across scripts, docs, dashboards, incident notes, one-off fixes, and individual engineers’ workflows. You’ll help turn that into shared tooling that runs safely.
  • Security: You'll help maintain the security and integrity of our systems, from production infrastructure to developer workstations. This includes access controls, secrets management, endpoint and infrastructure hardening, vulnerability management, and security monitoring, with a focus on making secure practices part of everyday engineering workflows.

Requirements

  • High agency. A lot of the work will start as something vague. You should be comfortable finding these problems yourself, deciding what matters, and taking them from observation through to a real fix.
  • High drive. There is a lot to improve, and platform engineers can be huge levers on team output. We want someone who moves quickly, raises the standard around them, and keeps pushing important work forward without needing a queue of tickets.
  • Strong infrastructure fundamentals. You have experience deploying, managing, and automating cloud infrastructure.
  • Experience with infrastructure automation and CI/CD. You should be comfortable building processes with simple tooling or automation.
  • Good judgement around observability and operations. Alerts should be specific, actionable, and reserved for things that matter. Monitoring should reflect how the system actually behaves today, not how it behaved six months ago. If an alert becomes noisy, you should notice and fix it before the rest of the team notices it.

Skills we value, but aren’t a requirement:

  • Blockchain fundamentals, Ethereum infrastructure, the transaction supply chain, or Maximal Extractable Value (MEV).
  • Experience managing infrastructure on AWS/Latitude/OVH.
  • Experience with Terraform and Ansible.
  • Experience with high-performance or latency-sensitive Linux production systems.
  • Experience building internal tools used by other engineers.

Compensation:

  • Top-of-market base salary.
  • Bonus tied to company and individual performance.
  • Equity on joining, with more earned through performance.
  • Private healthcare.

Platform Engineer in London employer: Gattaca

Join a leading technology business in Central London as a Customer Success Manager, where you'll thrive in a dynamic and innovative environment. With a strong focus on employee growth, the company offers excellent training opportunities and a collaborative work culture that values your input and fosters professional development. Enjoy the unique advantage of working in a vibrant city, surrounded by like-minded professionals, while making a meaningful impact on customer success and satisfaction.

G

Contact Details:

Gattaca Recruitment Team

StudySmarter Expert Advice🤫

We think this is how you could land Platform Engineer in London

Join Local Tech Meetups

Get out there and mingle with fellow developers by joining local tech meetups. It’s a fantastic way to meet people who might be working at Gattaca or know someone who does. Plus, you can pick up some trendy tech skills and trends while you're at it!

Contribute to Open Source Projects

Show off your coding chops by jumping into open-source projects. Not only does this give you practical experience, but it also gets you noticed in the dev community. You'll create a killer portfolio that speaks volumes about your skills to Gattaca.

Tap into Online Developer Communities

Don’t underestimate the power of online developer communities like GitHub, Stack Overflow, and even Reddit. Participate in discussions, share your projects, and build your visibility. We can often find opportunities through these channels that can lead to a full-time gig at companies like Gattaca.

Explore Job Boards Specifically for Tech Roles

Keep your eyes peeled on job boards that focus on tech roles. Sites like TechCareers or Stack Overflow Jobs can often have listings for companies like Gattaca that might not show up on broader job sites. Make it a habit to check these regularly, and don’t hesitate to apply directly through our website!

We think you need these skills to ace Platform Engineer in London

Production Systems Management
Infrastructure Automation
CI/CD Processes
Observability and Monitoring
Alerting Systems
Developer Experience Improvement
Cloud Infrastructure Management

Some tips for your application 🫡

Show off your coding skills:When applying for a software engineering role, it's super important to showcase your coding skills. Make sure your CV includes your tech stack, any relevant programming languages you’re comfortable with, and examples of projects you've worked on. If you have a GitHub profile, link it up! We love to see code in action.

Tailor your portfolio:For a full-time role, we’d expect to see some solid examples of your work in your portfolio. Make sure to include at least two or three projects that highlight your problem-solving skills and your ability to work with different technologies. Focus on the projects that are most relevant to the position at Gattaca.

Craft a killer cover letter:Your cover letter is your chance to stand out—make it personal! Explain why you want to work at Gattaca and how your skills align with the role. Show us your passion for software development. We dig enthusiastic candidates who understand the value of collaboration and continuous learning!

Be clear and concise:When it comes to writing your CV and cover letter, clarity is key. Avoid jargon that could confuse us and stick to simple, direct language. Highlight your achievements with quantifiable results where possible, and keep everything easy to read. A well-organised application goes a long way!

How to prepare for a job interview at Gattaca

Brush Up on Your Coding Skills

For a full-time software engineering role, it's crucial that we stay sharp with our coding abilities. Expect technical questions that might involve solving problems on the spot or discussing algorithms. Practise on platforms like LeetCode or HackerRank to get comfortable with the types of questions that often come up.

Know Your Tools and Frameworks

Make sure we’re well-acquainted with the tools and technologies listed in the job description. Familiarise ourselves with any specific frameworks or programming languages mentioned. If Gattaca uses React or Node.js, for instance, be ready to discuss how we’ve used them in previous projects or coursework.

Showcase Your Projects

Bring along a portfolio that highlights our best work. This could be code samples, GitHub repositories, or any side projects we’ve built. Make sure we can talk through our thought process for each project, especially the challenges we faced and how we solved them—this shows our problem-solving skills in action.

Prepare for Behavioural Questions

While technical skills are key, full-time positions also require cultural fit. Be ready to discuss our previous experiences and how we handle teamwork, conflict, and deadlines. Brush up on the STAR method—Situation, Task, Action, Result—to clearly articulate our past experiences when discussing how we've contributed to a team.