What you'll do
What we're looking for
Must have
Nice to have
- Support product teams. You will handle the team's support channel. That is where configuration questions, broken pipelines, failed deployments and ephemeral environments that won't come up arrive. You will troubleshoot them end to end (GitLab CI, Kubernetes, Helm, logs). When a problem keeps coming back, you will turn it into a platform or documentation improvement so it stops happening.
- Own the platform proactively. You will maintain the platform projects on your own initiative, as their owner. You will propose and drive improvements, migrations and modernisation work without waiting to be asked. You will prioritise by impact on teams and communicate changes clearly to everyone who uses them.
- In-house CI/CD tooling. You will own our CI/CD tool, written in TypeScript. From a single declarative file, it describes how each service is built, tested and deployed to Kubernetes across several business units and environments (test, preview, staging and production). Your work will include:its versioned JSON Schema and configuration validation;the engine that renders Helm releases and manifests;the CLI, the desktop visual editor and the documentation site;its semver release cycle, with consumer-facing changelogs.
- Ephemeral environments. You will evolve our ephemeral environment platform. It spins up a complete multi-service environment on demand for each branch or merge request, and is made up of a backend, workers, a web UI, a CLI and an MCP server. You will also own orphaned-resource purging, partial redeploys and pipeline integration.
- Helm charts and base images. You will contribute to the company's catalogue of base Helm charts and container images, which another team maintains. You will add the features the platform needs (hardening, cloud storage bucket mounts, high-availability topologies, new runtimes) while keeping them backward compatible for the teams that use them.
- Shared services and developer portal. You will own a set of cross-cutting services used by many teams, along with our internal developer portal.
- Technical reference. You will be a go-to person when a deployment fails. You will review teams' configuration changes, plan and carry out migrations (chart versions, clusters, regions) and make sure breaking changes can be adopted without downtime.
What we're looking for
Must have
- 5+ years in software engineering, including at least 2 in platform engineering, DevOps or internal infrastructure built as a product.
- Solid Kubernetes experience: Deployments, StatefulSets, CronJobs, PDBs, HPA, RBAC, ServiceAccounts, CSI and probes.
- Docker: multi-stage and distroless images, a minimal attack surface and reproducible builds.
- Experience building declarative tools and their contracts: schemas, validation, semantic versioning and deprecation policies.
- Hands-on AI tooling for software development. You use AI coding assistants and agents as part of your daily work, and you can build integrations for them, such as MCP servers, so that other teams can use them with the platform.
- An ownership mindset, shown by having maintained and evolved a product or internal tool over the long term, on your own initiative and without relying on a backlog handed to you.
- A service mindset and strong communication skills for supporting other teams. You can explain a problem, patiently and with good judgement, to developers with little infrastructure experience.
- Able to work autonomously on your own area and to write clear documentation for other teams.
- Native or fluent Spanish.
- Fluent English.
Nice to have
- Google Cloud Platform: GKE, GCS, IAM / Workload Identity.
- Advanced TypeScript/Node.js. This platform is real software: thousands of commits, a monorepo, and unit, e2e and BDD tests.
- Advanced GitLab CI: parent/child pipelines, runners and templates.
- Helm 3: designing reusable charts, versioning them and migrating between chart versions.
- Python and PHP/Symfony, the main stacks of the services the platform deploys.
- React and Electron, for the internal tools' interfaces.
- Backstage or other developer experience platforms.
- Running databases, message brokers and key-value stores on Kubernetes.
- Observability with Datadog or Grafana.
#LI-PS1
