Job Title: SRE / Observability Engineer – Kubernetes & AWS (Dublin)

Location: Dublin, Ireland

Contract role | Rates: €400-€500 per day

Term: 12 Months+ (Long term)

Working arrangement: Hybrid (1 day a week onsite)

Overview

Elwood Roberts Ltd is hiring a Contract Observability Engineer for a Dublin-based client operating large-scale production systems in AWS and Kubernetes. This role is ideal for an engineer who lives and breathes observability — someone who has built and owned monitoring and alerting systems, defined SLIs/SLOs, and proactively driven system reliability and performance improvements.

You won’t just “use” dashboards — you’ll design, implement, and evolve the observability stack, and play a key role in maintaining visibility across distributed services in production.

Key Responsibilities

• Own and enhance the end-to-end observability stack, including:
• Prometheus, Grafana, OpenTelemetry, Loki, and/or ELK
• Alerting pipelines, dashboards, logs, metrics, and traces
• Define and manage SLIs/SLOs for critical services
• Build and maintain monitoring-as-code practices using tools like Terraform and Helm
• Work closely with application teams to surface meaningful telemetry and reduce MTTR
• Operate and troubleshoot Kubernetes (EKS) clusters in production
• Maintain robust, scalable AWS infrastructure (IAM, EC2, EKS, CloudWatch, ELB, Auto Scaling)
• Contribute to incident response, on-call rotations, RCAs, and continuous improvement

What We're Looking For

• Production ownership of observability tooling — not just usage
• Hands-on setup and scaling of tools such as Prometheus, Grafana, OpenTelemetry, Loki, or ELK
• Ability to build meaningful alerting pipelines and drive visibility across systems
• AWS experience in production: EKS, IAM, EC2, CloudWatch, Load Balancers
• Deep Kubernetes (EKS) exposure: deployment, scaling, troubleshooting clusters
• Infrastructure automation with Terraform and Helm
• Real-world SRE practices: on-call, postmortems, and service-level thinking

We Are Not Looking For:

🚫 DevOps engineers who haven’t owned observability end-to-end

🚫 Candidates focused only on infrastructure provisioning with limited telemetry experience

🚫 Those with recent leadership-only roles without recent hands-on implementation

🚫 People with only academic or sandbox exposure to Kubernetes and AWS