Hi there, I’m Javier.

Platform engineer with a decade building reliable, scalable infrastructure for fast-moving teams — from bare metal to Kubernetes, from on-call to GitOps.

Personal Details

Languages: Spanish, English

I Am a

Over a decade designing and operating cloud-native platforms — from financial services to travel-tech. I work at the intersection of infrastructure, reliability, and developer experience: building the systems and pipelines that let product teams ship fast without sacrificing stability.

The mindset.

Good engineering is as much about how you think as what you ship. These are the principles that guide how I approach reliability, delivery, and collaboration.

Automate to eliminate toil

Manual, repetitive work is a reliability risk and a morale drain. Every process that can be codified — provisioning, testing, deployments, remediation — should be. Automation scales your capacity without scaling headcount and shifts engineers from reactive firefighting to building systems that stay healthy on their own.

Ship small, ship often

Deployment frequency is a leading indicator of team health. Small, frequent releases reduce blast radius, accelerate feedback loops, and make rollbacks trivial. A mature CI/CD pipeline is not a tooling choice — it's an organizational one, enabling teams to own the full lifecycle of what they build.

Declare state, eliminate drift

Infrastructure defined as code is infrastructure you can review, reproduce, and audit. Version control becomes your change log, pull requests become your approval process, and every environment is disposable by design. GitOps takes this further — the desired state lives in Git, and the system converges to it automatically.

Platform thinking over siloed ops

The role of a platform team is to build internal systems that empower product engineers to self-serve — not to be the bottleneck between developers and production. A good platform treats developers as customers, reduces cognitive load, and embeds reliability practices into the path of least resistance.

Error budgets, not blame

Failure is not exceptional — it is a property of distributed systems at scale. SRE practice formalizes this with error budgets: an explicit contract between reliability and velocity. Blameless postmortems shift the focus from who to what, turning incidents into a compounding knowledge base that makes the next failure cheaper.

Observability over monitoring

Traditional monitoring tells you something is broken. Observability tells you why. SLIs and SLOs turn vague uptime goals into measurable commitments. DORA metrics quantify delivery performance. Without data, improvement is just opinion.

Work Experience

These are the roles and tasks that I have performed in my years of experience.

DevOps Engineer

Quadrant Travel Technologies 2022 -

Designing and operating cloud-native platform infrastructure using IaC and GitOps principles, with a focus on reliability, security, and scalability across the full delivery lifecycle.

Site Reliability Engineer

2gether 2021 - 2022

Embedded with product teams to own reliability as a first-class requirement — defining SLOs, building observability stacks, and automating incident response for a regulated fintech platform.

R&D Consultant

Yogabot 2020 - 2021

R&D engagement exploring blockchain architecture and tokenomics to support a decentralized wellness ecosystem.

Personal development

2020

Completed a long-pending university degree while deepening knowledge in investments, financial markets, and distributed ledger technologies.

DevOps Engineer

Fintonic 2017 - 2020

Led infrastructure modernization for a regulated Spanish fintech — migrating to containerized workloads, building CI/CD pipelines, and raising platform reliability across engineering squads.

Junior Systems Architect

Kimia 2015 - 2017

First professional IT role — provisioning and operating bare metal Linux servers, building CI/CD with Jenkins and Ansible, and managing cloud infrastructure on AWS for a global ad-tech platform.