Senior Devops Engineer - Mainloop

Leyton Et Associes; Madrid; Presencial; EUR 80.000 - 120.000; Jornada completa

Descripción de la vacante

Leyton Et Associes is hiring a Senior DevOps Engineer in Barcelona to own and build the delivery platform from the first commit. You will be the first, and possibly the only, DevOps for a growing product family in a multinational group.

Expect to craft reproducible environments, self-serve deployments, and robust secrets handling, with no routine on-call. You’ll report directly to the platform lead as you shape the architecture and culture.

Formación

• Senior DevOps background with platform-building experience.
• Proven ability to design and own infrastructure from scratch.
• Strong expertise in CI/CD, automation, and cloud tooling.

Responsabilidades

• Build the platform from code including hosts, networking, and environments.
• Make deployment self-serve with minimal human intervention.
• Own secrets management and secure credential handling.
• Develop and test the release path with automated checks and rollbacks.
• Maintain observability and cost discipline across products.

Conocimientos

Kubernetes

CI/CD

Cloud platforms

Terraform

Docker

Herramientas

Kubernetes

Docker

Terraform

AWS

Descripción del empleo

Senior DevOps EngineerBuild a company's entire delivery platform from the first commit, own it outright, and never carry a pager. Both halves of that sentence are deliberate.This is a senior role and it is not a role we can hire junior into — you are the first, for a while the only, and the platform everyone else builds on is the one you put in place.Mainloop is a new engineering team inside an established international group. We are in Barcelona, we are being built from scratch this year, and we have the backing, the customers and the product portfolio of a company that has been around for decades. You get the interesting part of a new team without the part where you check whether payroll clears.Two more things about where this comes from and where it goes. The group has been running a tech lab in Casablanca for more than eight years — Barcelona is its second, built to sit closer to the teams we build for, and AI-native from the first commit, because it starts from a blank page. And the plan does not stop at internal work: within about a year and a half we intend to externalise — external clients, our products sold on the market, products developed for it. The first eighteen months are deliberately spent building as much as possible for the group while the machine gets set up. You would arrive at the start of that curve, not after it.What we build is the software that automates professional-services work — across roughly fifteen countries, for businesses drowning in process. We build those products and we run them. That second half is why this role exists, and it is not a formality: a team that owns how its software is built should own how it ships.You are the person who ends that. You are our first DevOps engineer, and for a while our only one.What the job actually isYou are not inheriting a platform. You are writing one.There is no infrastructure-as-code in our estate today — not a line. The environments that exist were built by hand and are reconstructible only from a runbook and one person's memory. Your first job is to make that permanently untrue: every environment we run reproducible from a committed repo, from your first week, before the habit sets.In your first few months you will:Build the platform from code. Hosts, networking, ingress, access, environments — committed, parameterised, reviewable. It is the cheapest moment this will ever be done, and you get to do it properly instead of retrofitting it.Make deployment self-serve. Today, shipping an existing app is a git push; standing up a new one needs admin rights and two undocumented footguns. That gap is yours to close, down to one command, so a developer never holds a platform credential.Own secrets properly. A real machine secrets manager, and — because we run a lot of AI agents — credentials brokered so an agent process only ever holds a placeholder, never a key. If you have opinions about how you stop a prompt-injected agent leaking a production credential, you will enjoy this part; almost nobody gets to design it from scratch.Prove the restore. We have a written standard that says "someone deploys it" is not "someone has proven the restore works." You will run the drill, write the report, and be the reason the honest answer to "is it backed up?" changes from no to yes, and here is the evidence.Build the release path. Commit to production, an automated test gate, per-branch preview URLs a stakeholder can open from their phone, and a rollback that everyone on the team has rehearsed before they need it.Then keep it all running — and keep making it duller. Observability, cost caps, dependency hygiene, the unglamorous work that decides whether a small team can own a lot of products.And you will have the authority to match. You are not implementing someone else's platform design. You report directly to Edouard, there is no layer in between, and how this is built is yours to decide. We are hiring at senior level precisely so that those decisions can be yours — the platform every product here runs on is the one you put in place, and we would rather bring in the judgement than supervise it.Nobody is on call. Ever.No rota, no pager, no phone number, no "just keep an eye on it this weekend". Alerts post to a team channel and wait there. If something breaks at 3am on a Saturday, or in the second week of August, it gets fixed the next working morning. This is a decision on the record, not an oversight we will rediscover later — and it applies to every product we own, with no exceptions.We are telling you this up front because it is not a perk we are quietly hoping you will waive. Plenty of ads say "healthy on-call culture" and mean a rota. We mean