You Are Here
cv.riera.co.uk
Personal site, operator profile, and hands-on infrastructure layer. This is the best starting point if you want to understand how I think about building, running, and improving systems.
Current CV siteFocused on OpenAI's London infrastructure buildout
Hands-on platform engineering, infrastructure, and site leadership
I am a hands-on engineering and operations leader with 20+ years across research infrastructure, enterprise IT, and HPC environments. I currently serve as Deputy Head of Operations at EMBL-EBI, helping shape services behind a 150PB+ archive, high-volume data transfer, identity systems, and observability used by researchers around the world.
The role I am most interested in now is a London-based infrastructure leadership seat where I can act as both a technical leader and a site builder: helping found or scale a talent-dense team, raise the technical bar, and own the platform foundations behind availability, deployment, observability, CI/CD, and reliable product delivery.
Related Surfaces
cv.riera.co.uk is the CV and operator layer. cxo.riera.co.uk is the strategy and executive layer. sme.riera.co.uk is the practical SME systems and demo layer. The live automation stack and app URLs remain on joanmarcriera.es.
You Are Here
Personal site, operator profile, and hands-on infrastructure layer. This is the best starting point if you want to understand how I think about building, running, and improving systems.
Current CV siteStrategy Layer
The executive and strategy-facing layer: operating models, transformation, leadership framing, and broader decision-making context for technical work.
Open cxo.riera.co.ukSME Systems Layer
The practical small-business systems and demo layer. It provides a front door for the SME automation stack while leaving the live applications running on joanmarcriera.es.
Open sme.riera.co.ukWhat I Bring
I have built teams and operating models from scratch more than once, including at EMBL-EBI and earlier at Barcelona Media. That means defining ownership, standards, service boundaries, and the culture needed for engineers to do strong work.
My background is full of messy estates: legacy transfer stacks, archive migrations, fragmented monitoring, identity sprawl, and operational bottlenecks. I reduce complexity, improve reliability, and make services easier for teams and users to live with.
I am comfortable with architecture reviews, procurement, service design, cost models, and long-term roadmaps. The Cambridge CTO programme and Oxford executive finance studies sharpened that layer, but the habit was already there: make technical decisions that stand up commercially and operationally.
Selected Impact
15PB to 140PB
Helped take FIRE from an emerging archive capability to a production platform supporting major scientific resources, with governance and service practices that let it grow without losing trust.
15PB/month
Consolidated roughly 35 transfer platforms down to 9, improved throughput by 500%, and turned a historically fragile estate into something dependable during periods of intense demand.
2025
Pushed for VLAN stretching and cross-team coordination that made a seamless migration possible, removing a class of operational pain that had previously been accepted as normal.
>100PB
Personally drove a major tape archive procurement, cutting disaster recovery costs while improving the long-term resilience of mission-critical data services.
OpenAI Fit
I have not built LLM inference systems directly. What I have done, repeatedly, is build the kind of runtime, reliability, deployment, and operating foundations that ambitious product and research teams depend on when they need to move fast without breaking trust.
At EMBL-EBI I built the platform services function from zero: no existing team, no playbook, no established culture. I hired the early engineers, defined service boundaries, introduced incident reviews and ownership expectations, and helped create a high-trust, high-agency engineering culture.
My work has covered the underlying systems product teams rely on: deployment patterns, service integration architecture, observability, CI/CD, IAM, network changes, transfer runtimes, infrastructure as code, and Kubernetes-era service modernisation.
I am used to operating services that matter, where reliability and delivery speed both count. That has meant reducing platform sprawl, improving throughput, removing operational fragility, and keeping systems credible with stakeholders who depend on them every day.
I live south of Cambridge and can get into London directly. I want the in-person part of building a new engineering presence: hiring carefully, setting standards early, and helping create the local culture of a growing office rather than only participating remotely.
Skills
Rather than anchor this page to one job title or a stack of tailored CVs, these are the capability areas that show up consistently across my work.
Experience
2021 - Present
Leading multidisciplinary teams across orchestration, monitoring, authentication, transfer, mail, and other central services. Responsible for reliable delivery, roadmap shaping, stakeholder alignment, and long-term sustainability of core research infrastructure.
2016 - 2020
Grew from transfer services leadership into platform leadership across archive systems, automation, observability, and service-oriented delivery. This period included major FIRE growth, Kubernetes-era redesign work, and cross-functional governance around data services.
2011 - 2016
Owned architecture, service delivery, and team leadership across enterprise customers. Worked across OpenStack, HPC, big data, automation, and service management, including large bare-metal rollouts and multi-year infrastructure planning.
2007 - 2011
Built an internal IT function for a fast-growing research organisation, hired and mentored engineers, and supported a broad estate spanning identity, messaging, monitoring, backup, and research platforms.
Credentials
Some of the older technical certifications have expired, but they still reflect years of practical systems, Linux, automation, and database work before I moved deeper into broader leadership roles.
What I Am Looking For
Contact
Email is the fastest route. LinkedIn and GitHub are here if you want more context first.