Senior DevOps EngineerBuild a company's entire delivery platform from the first commit, own it outright, and never carry a pager. 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.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. What we build is the software that automates professional-services work — across roughly fifteen countries, for businesses drowning in process. 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 our first DevOps engineer, and for a while our only one.You are writing one.Hosts, networking, ingress, access, environments — committed, parameterised, reviewable.

Make deployment self-serve. 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.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.No rota, no pager, no phone number, no "just keep an eye on it this weekend". If something breaks at 3am on a Saturday, or in the second week of August, it gets fixed the next working morning.

Plenty of ads say "healthy on-call culture" and mean a rota. We mean there is no rota.Backups with a restore we have actually tested. Alerting that queues instead of paging,



because nothing on the other end of it is expected to answer at night.The PO, the developers and the DevOps engineer assigned to a product own that product's incidents — support is not shipped off to a separate team, it is part of owning the thing, and it is what keeps everyone honest about quality.A concrete example, because it tells you a lot about us: we do not run Kubernetes, and that was a decision rather than an omission.

Which is why we are asking for someone who has run Kubernetes in production and can tell us when it is not the answer. A proposal gets researched properly against the alternatives, it gets an answer, and if the answer is no you get the reasoning. On infrastructure, you are not one voice among many — you are the one who decides, within a budget you help set.You will get seriously good at building with AI agentsWe are an AI-native engineering team, genuinely — not a team that added a Copilot licence.

That is true of you too: a great deal of infrastructure work is now specified rather than typed, and you will get very good at driving that — where it works, where it fails, and how to read a diff and decide whether it is actually right.It also makes your job more interesting than the same title elsewhere, because agentic engineering creates infrastructure problems most teams do not have yet:Agents install packages into code that sits next to client data. Supply-chain hygiene stops being a compliance checkbox and becomes a live control you own.Brokering machine identity so the agent never touches the real key is a design problem, and it is yours.Per-project budgets, hard caps and an alert that fires before the cap,



not after it.Which means the guardrails between "an agent proposed this" and "this is in production" are infrastructure, not policy.If you are curious but not yet deep in it, that is fine — teaching this well is something we intend to be known for.Over your first two to three years here you work through a defined body of knowledge — our architecture, the agentic build method, how to take a product from an idea to something a business depends on, and how to run it well. When you have covered it and can demonstrably run a project our way, you are awarded the Mainloop Barcelona certificate.It goes on your CV, and we intend to make it mean something in this market — a signal that the person holding it knows how to build and run production software with AI agents to a standard.

You are the only DevOps engineer for a while. Flights, your first month's accommodation while you find somewhere of your own, the visa and paperwork costs, and an agent to handle the bureaucracy — the NIE, the TIE appointment, the apostilles — instead of leaving you to meet the Spanish administrative system alone. Spanish lessons if you want them.A relocation bonus, paid on arrival rather than dripped out.

Healthcare with no premium, no deductible and no network — from day one, and not tied to staying in this job.Thirty calendar days of holiday — that is 22 working days — plus fourteen public holidays, roughly seven weeks in total. We are not your tax advisor and you should get one — but ask in the first conversation and we will walk you through the comparison we ran, including the parts where the number comes out smaller.This is the one non-negotiable, and it is why the role is senior: there is nobody here to check your work, and the platform you put in place is the one everyone else builds on for years.You are comfortable running things on your own servers, not only on a managed cloud console. You have run Kubernetes in production — and you are equally comfortable saying when it is not the right answer.

Security is instinct, not a stage. English, fluently. Spanish is genuinely useful day to day. Catalan is not required.A project.

📌 Senior DevOps Engineer - Mainloop (Barcelona)
🏢 Leyton Et Associes
📍 Barcelona