Site Reliability Engineer

PLENIT; Madrid; Presencial; EUR 70.000 - 110.000; Jornada completa

Descripción de la vacante

PLENIT is seeking a Senior Site Reliability Engineer to ensure the stability, availability, and performance of its cloud platform in production. You will proactively identify risks, improve capacity planning, and drive reliability initiatives while coordinating incident response and recovery efforts.

You will work with Linux, networking, databases, and web infra, applying observability and automation to reduce manual work and outages. On-call rotations may be part of the role.

Formación

• Extensive experience operating critical production environments.
• Strong ability to troubleshoot complex systems and drive reliability improvements.
• Proven experience with incident handling, RCA, and operational excellence.

Responsabilidades

• Lead incident response, define impact, coordinate diagnosis, and restore service.
• Identify and mitigate reliability risks; maintain backlog of risks and improvements.
• Improve observability with metrics, logs, traces, and dashboards; write runbooks and procedures.

Conocimientos

Incident response

Root cause analysis

Observability

Kubernetes

Linux

Networking

Load balancing

SRE fundamentals

Communication

Herramientas

NGINX

Apache

Load balancers

Monitoring tools

CI/CD tooling

Cloud platforms

Descripción del empleo

About this role

The challenge As a Site Reliability Engineer, you will play a critical role in ensuring the stability, availability, resilience, and performance of our cloud platform in production.
Your mission will cover two complementary areas. First, you will work proactively to prevent incidents by identifying operational risks, anticipating capacity constraints, improving production changes, resolving recurring problems, and driving reliability improvements, migrations, and corrective initiatives.
Second, when incidents occur, you will help restore service quickly by coordinating technical diagnosis, controlling the situation, communicating impact, and leading recovery efforts.
This is a senior, hands‑on role for someone with a strong operational mindset who is comfortable working in complex production environments, investigating technical issues, making decisions under pressure, and taking ownership of platform reliability.
You will be part of the Site Reliability Engineering team, working in a practical environment focused on keeping the platform stable while continuously reducing operational risk and manual effort.
A key part of the role will be to identify what could affect the platform before it becomes an incident. You will assess risks, make them visible, define mitigation or correction plans, assign ownership, and follow actions through to completion.
You will also contribute to capacity planning, production scaling, infrastructure improvements, migrations, observability, automation, and operational readiness.
When incidents happen, you will act as a technical reference and coordination point. You will help establish control, assess impact, accelerate diagnosis, involve the right teams, communicate clearly, and restore service as quickly and safely as possible.
You will work closely with engineering, systems, networking, storage, database, security, and product teams. Your operational perspective will help ensure that reliability, scalability, recoverability, and operability are considered in platform changes and evolution.
Participation in an on‑call rotation and response to critical incidents outside regular working hours are part of the role.

Requirements that are important for us

We are looking for a senior Site Reliability Engineer with strong experience operating critical production environments and a proven ability to identify risks, troubleshoot complex issues, and drive long‑term reliability improvements.

Relevant experience and expected outcomes

• Operating critical production infrastructures while ensuring availability, stability, performance, and recoverability.
• Identifying technical and operational risks and driving mitigation, correction, or contingency plans.
• Maintaining a prioritized backlog of risks, recurring problems, capacity constraints, and reliability improvements.
• Leading incident response processes, including impact assessment, technical diagnosis, coordination, communication, and service restoration.
• Performing root cause analysis and implementing corrective and preventive actions.
• Managing recurring problems and ensuring they remain visible, owned, prioritized, and followed through to resolution.
• Monitoring demand, system limits, growth trends, bottlenecks, and saturation points.
• Contributing to capacity planning and executing infrastructure scaling in production environments.
• Reviewing infrastructure changes, deployments, maintenance activities, and migrations from a reliability perspective.
• Defining implementation, validation, rollback, and contingency plans for production changes.
• Improving observability through metrics, logs, traces, alerts, dashboards, and service‑health indicators.
• Improving runbooks, diagnostic playbooks, recovery procedures, and operational documentation.
• Identifying repetitive tasks, unnecessary escalations, and manual processes that should be automated or simplified.
• Working with systems that support web applications, including a solid understanding of HTTP, DNS, TCP/IP, and load balancing.
• Administering technologies such as NGINX, Apache, load balancers, databases, and related web infrastructure.
• Strong experience with Linux systems and working knowledge of Windows environments.
• Good understanding of networking, virtualization, storage, databases, and infrastructure dependencies.
• Familiarity with Kubernetes and containerized platforms is highly valuable.
• Experience with cloud infrastructure is highly valuable.

Key skills and expected impact

• Strong troubleshooting capabilities and the ability to analyze metrics, logs, traces, events, and system behaviour.
• Broad technical knowledge across infrastructure, applications, networks, storage, and databases.
• Strong risk‑based thinking, with the ability to distinguish urgent work from important preventive work.
• Ability to turn operational concerns into concrete actions, owners, deadlines, and measurable outcomes.
• Ability to remain calm under pressure while acting decisively and proactively.
• Strong ownership of platform stability and service recovery.
• Strong coordination skills during incidents, migrations, changes, and technical escalations.
• Clear communication with technical teams, stakeholders, and affected parties.
• Ability to challenge unsafe changes or insufficient operational preparation constructively.
• Strong documentation habits and commitment to shared operational knowledge.
• Continuous‑improvement mindset focused on reducing incidents, recovery time, operational effort, and manual intervention.
• Motivation to act as a key technical reference during complex and high‑impact scenarios.

Tools

• Observability tools for metrics, logs, traces, alerting, and dashboards.
• Infrastructure and system‑administration tools across Linux and Windows environments.
• Networking, virtualization, storage, and database technologies.
• Web infrastructure tools such as load balancers, NGINX, Apache, and proxies.
• Cloud infrastructure and configuration‑management platforms.
• Kubernetes and container orchestration technologies.
• Incident‑management and on‑call tools.
• Operational documentation tools, runbooks, playbooks, and incident procedures.
• Capacity‑planning, performance‑analysis, and infrastructure‑scaling tools.
• Automation and scripting tools.

What success looks like

Success in this role means that operational risks are identified early, capacity issues are anticipated, production changes are safer, recurring problems are permanently addressed, and the platform becomes progressively more observable, resilient, scalable, and easier to operate.
When incidents occur, they are controlled quickly, communicated clearly, and resolved with reduced recovery time. The objective is not only to respond better, but to reduce the number, frequency, and impact of incidents over time.