Tech Lab Senior DevOps Engineer Build a company's entire delivery platform from the first commit, own it outright, and never carry a pager. 03 Secrets management, including for agents 04 Observability, backup and a tested restore Hosts, networking, ingress, access, environments — committed, parameterised, reviewable. Make deployment self-serve. standing up a new one needs admin rights and two undocumented footguns. 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.

No rota, no pager, no phone number, no "just keep an eye on it this weekend". 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. We are an AI-native engineering team, genuinely — not a team that added a Copilot licence.

Every engineer gets their own Claude Max subscription and a desktop orchestrator that runs several coding agents in parallel, each in its own branch.

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.

More than the other seats here, and for a real reason: you are standing up physical-ish infrastructure and access for a team being assembled around you, in its first year, and most of that goes faster in a room. 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 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. 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 - Hybrid (Cataluña)
🏢 Mainloop AI
📍 Cataluña