Dlocal29mo ago

Site Reliability Engineer, Technical Referent

Madrid (hybrid),MadridFull Timemid

EngineeringDevOps & InfrastructureSite Reliability EngineerDevops EngineerInfrastructure & Cloud

0 views0 saves0 applied

Apply Now

Quick Summary

Requirements Summary

Leverage Infrastructure-as-Code (IaC) to provision and manage monitoring tools, alerting rules, and our observability configurations across OTEL Pipelines.

Technical Tools

EngineeringDevOps & InfrastructureSite Reliability EngineerDevops EngineerInfrastructure & Cloud

Why should you join dLocal?

dLocal enables the biggest companies in the world to collect payments in 40 countries in emerging markets. Global brands rely on us to increase conversion rates and simplify payment expansion effortlessly. As both a payments processor and a merchant of record where we operate, we make it possible for our merchants to make inroads into the world’s fastest-growing, emerging markets.

By joining us you will be a part of an amazing global team that makes it all happen. Being a part of dLocal means working with 1000+ teammates from 30+ different nationalities and developing an international career that impacts millions of people’s daily lives. We are builders, we never run from a challenge, we are customer-centric, and if this sounds like you, we know you will thrive in our team.

What's the opportunity?

We are looking for a Site Reliability Engineer (SRE) to join our team! As our Site Reliability Engineer (SRE), you will be focused on the design, implementation and continuous maintenance of our centralized observability platform using OpenTelemetry (OTEL) as its backend. You will be part of a talented team that works on mission-critical applications with big customers like Netflix, Amazon, Nike, Facebook & more!

As a Site Reliability Engineer, you are always expected to ask the necessary questions:

What data do we need to understand how our systems are performing?

How do we collect this data?

What patterns are we looking for in the data and what do they mean?

Who should be notified when a certain system is not working properly?

Do we have any systems that we need more data for?

An SRE engineer designs systems and processes to answer the questions above and to provide automated support and response where possible.

Own OpenTelemetry Pipelines: Design, implement, and maintain observability pipelines across the three main signals—logs, metrics, and traces—ensuring standardized, scalable, and efficient data ingestion. Optimize ingestion strategies to balance cost, performance, and usability.

Empower Engineering Teams: Build self-service automation and tooling that enables development teams to instrument and leverage observability without requiring manual intervention from the SRE team. Drive adoption of best practices while ensuring teams own their telemetry.

Support Incident Management: Be the Engineering side of our Incident Management Team, designing the processes, playbooks, checklists, and automations for them and other engineers to follow during an incident.

Collaborate Across Teams: Interact with members from almost all teams across the business to understand their monitoring, alerting and SLO / SLA requirements and design systems and processes that ensure we meet or exceed these requirements. Influence architectural decisions during initial design stages to ensure resiliency and scale at the outset of software development.

Automate Observability Infrastructure: Leverage Infrastructure-as-Code (IaC) to provision and manage monitoring tools, alerting rules, and our observability configurations across OTEL Pipelines.

Define Baseline Observability Standards: Design base level requirements for new and existing services to ensure that all dLocal infrastructure and code are monitored consistently and accurately at a basic level.

Own Technical and Security Health: Take full ownership of dLocal’s infrastructure reliability, ensuring adherence to key availability and security KPIs.

Optimize Alerting Systems: Continuously refine alerting signals to minimize noise and ensure them are always actionable, reducing fatigue and improving response efficiency.

Over 4 years’ of experience as SRE Engineer or in a very similar role more focused on observability.

Expertise in Kubernetes, including its core components, deployment methodologies, and monitoring best practices.

Some understanding of OpenTelemetry, including setting up OTEL collectors, instrumentation, and pipeline optimization.

Proficiency with monitoring and logging tools such as Grafana, Prometheus, Loki, New Relic, or Datadog.

Hands-on experience with IaC tools (Terraform) and GitOps CI/CD solutions (ArgoCD, GitHub Actions, or similar).

Experience integrating incident management platforms (PagerDuty, Jira) with automated alerting workflows.

Strong scripting abilities (Python, Go, or similar) for automating observability tasks.

A problem-solving mindset, with the ability to collaborate across multi-functional teams to drive reliability improvements.

You will stand out if you have:

Cloud experience, especially AWS and ECS-based workloads.

Experience managing observability pipelines at scale in high-throughput environments.

Familiarity with Configuration-as-Code (Ansible, Chef, or SaltStack) for managing configurations across legacy instances.