Shakers for companies

Work with a senior Site Reliability Engineer

A certified SRE who turns operations into software: SLOs the business understands, alerts that fire before the customer notices and incidents closed with a written root cause analysis.

Senior tech talent for your platform's reliability, starting within days and on the infrastructure you already run in production today.

  • Certified talent in AI and agent skills
  • Meet up to 3 AI Builders in 72 h
  • Flexible collaboration models
Shakers panel with four available profiles
Looking for a Site Reliability Engineer
Allianz
BBVA
Bankinter
Microsoft
Qida
Accenture
Deloitte
Dcycle
HP
Línea Directa
Podo
Clicars
Sonosuite
Eroski
Civitatis
Alten
Vivla
Wayra
Cabify
Affinity
+600

European clients across different industries

Top 4%

We work with the top 4% of certified talent in our community

72 hours

Meet 3 certified candidates in under 72 h

4.7/5

Our clients' satisfaction on Trustpilot

The talent mix your company needs

At Shakers you will find AI Engineers, Site Reliability Engineer and specialists across Tech, Product and Data

Tell us your project
Certified Shakers profile: Mateo, Full Stack Developer
Ready to build
Mateo
Full Stack Developer
ReactNode.jsPythonTypeScriptNext.jsMongoDBAWSAIAPIs
Certified Shakers profile: Ana, DevOps Engineer
Ready to build
Ana
DevOps Engineer
DockerCI/CDAWSAzureKubernetesTerraformAmazon Bedrock
Certified Shakers profile: Lucas, Backend Developer
Ready to build
Lucas
Backend Developer
Node.jsPythonJavaGoPHPMySQLMongoDBDocker
Certified Shakers profile: Emma, Security Engineer
Ready to build
Emma
Security Engineer
Burp SuiteOWASP ZAPMetasploitNmapNessusTrivySnyk
Specialist sitting on a sofa with a tablet and a Ready_to_build label

Site Reliability Engineer: what this role brings to your project

A Site Reliability Engineer (SRE) applies software engineering to operations: they set service level objectives (SLOs) with their error budget, automate repetitive manual work (toil) and respond to incidents with blameless reports that close the root cause.

The role was born at Google and is now a craft of its own: where DevOps automates the software's path, the SRE keeps the system that already runs in production alive.

SLOobservabilityKubernetesTerraformPrometheusGrafanaAnsibleCI/CDDockerPythonGoincident response

One provider. One contract. Full traceability

How Shakers works for your company

Post your project

Tell us about the project, its scope, the expertise you need and when you want to get to work.

You get three options

We match your brief against certified talent and introduce the three AI Builders who fit best.

The last word is yours

Meet the three specialists and choose who you collaborate with; we handle the rest.

Why work with Shakers

The advantages of adding this profile with Shakers

SLOs and error budgets the business reads

Availability objectives measured as error budget: you stop debating whether the system is fine and see it in a number.

Alerts before the customer

Observability with thresholds and owners in Prometheus or your stack: what matters rings, the rest stays quiet.

Incidents closed at the root cause

Coordinated response and blameless reporting: every outage leaves a document that prevents the next one, not a Slack thread.

Toil automated away with Python or Go

Toil gets measured and eliminated: on-call checks and recoveries done by hand today move into scripts and code.

Runbooks and on-call without burnout

Rotation and escalation designed, with runbooks anyone on the team can execute at 4 a.m.

Capacity without growing headcount

An SRE by project, no hiring process: certified talent that joins with your access and your environments.

Frequently asked questions

Any other questions? Our team will answer them.

Tell us your project
What is the difference between an SRE and a DevOps Engineer?
DevOps automates the software's path: pipelines, infrastructure as code. The SRE keeps the system in production: SLOs, observability and incidents. The boundary is agreed project by project.
How much does a Site Reliability Engineer cost?
Scope sets it: which services the SLOs cover, whether there is on-call and how much automation is left. At Shakers the budget closes per project before kickoff.
Do I need an SRE if I already have DevOps?
It depends where it hurts. If deployment is manual, DevOps first. If production keeps falling and alerts arrive late, the SRE is the role: they measure availability and close incidents at the root.
Can an SRE work remotely?
Almost everything: the platform lives in the cloud and on-call is organised remotely. Only the odd physical datacentre incident asks for presence.
What does an SRE need to start the project?
Access to telemetry and current dashboards, the list of critical services and the last written incidents. With that, the SLO proposal and observability plan land in days.
Is an SRE just the same as a modern sysadmin?
No. The sysadmin administers machines; the SRE programs operations. The frequent way in is exactly that, but the craft is measured in SLOs and automation.
What gets delivered in the first weeks

The SLOs of your critical services with their error budgets, the observability dashboard that measures them and the first incident report on the outage people still shout about.

A craft the market asks for by name

328 active tech job ads in Spain mention site reliability and 1,040 use the SRE acronym, according to Shakers' market analysis (n=30,508, September 2026). LinkedIn lists over 2,000 Site Reliability Engineer jobs.

Where the SRE ends

They do not design your cloud architecture nor automate the deployment pipeline: they keep what already produces running. If the system falls over and nobody knows why, it is theirs.

A team by project, not a vacancy

The brief arrives with the symptom: on-call that burns people out, alerts nobody reads. Scope closes before kickoff.

Connect with AI specialists to build your next project

Find specialists in Tech, Product, Data to complement your team

DevOps Engineer

Their pipeline deploys what your SRE keeps alive: when deployment is the problem, the boundary starts there.

View profile →

Cloud Architect

Designs the platform whose availability you will measure: architecture decisions before setting SLOs.

View profile →

AWS DevOps Engineer

The DevOps cut of the Amazon ecosystem: when the environment is pure AWS and the problem is the pipeline.

View profile →

Backend Developer

Their services are the ones that page: when the failure is code rather than platform, diagnosis is shared.

View profile →

The AI talent you need Certified by Shakers

We introduce you to three ready_to_build AI Builders in 72 hours.