Mid Cloud Observability Engineer

Serasa Experian

About The Position

A cloud observability engineer’s day is about making complex systems understandable, improving signal quality, and enabling faster, smarter debugging across teams. This role involves checking system health, reviewing alerts/incidents, triaging alerts, investigating issues, improving observability instrumentation, building and improving dashboards, optimizing alerts, and working collaboratively with development teams and other engineering partners on continuous improvements and release support.

Requirements

SRE, DevOps, or Cloud Engineering
Cloud platforms AWS
Experience in AWS services including CloudWatch, X-Ray, Lambda ECS/EKS, API Gateway RDS, DynamoDB, S3
Hands-on with experience with an observability tool Dynatrace Splunk Datadog OpenTelemetry Prometheus, Grafana AWS Distro for OpenTelemetry
Strong understanding of: Containers & orchestration (Docker, Kubernetes)
CI/CD pipelines
Infrastructure as Code (Terraform, CloudFormation)
Monitoring/observability tools

Nice To Haves

Experience building observability platforms at scale in AWS
Familiarity with multi-account AWS environments
Experience with cost optimization for observability (logging/metrics ingestion)
Experience in high-scale distributed system

Responsibilities

Check system heathy, review alerts/incidents.
Triage alerts
Investigate issues
Improve observability instrumentation
Build and improve dashboards
Alert optimization
Work with development teams and other engineering partners.
Continuous improvements.
Release support.
Design and implement observability frameworks using metrics, logs, and distributed tracing
Develop dashboards, alerts, and visualizations to monitor system health
Standardize observability practices across engineering teams (logging, telemetry, tracing)
Implement and manage native monitoring tools. Amazon CloudWatch (metrics, logs, alarms, dashboards), AWS X-Ray (distributed tracing), AWS Distro for OpenTelemetry (ADOT)
Build alerting systems (avoid alert fatigue)
Participate in on-call rotations
Build intelligent alerting
Improve System Reliability/ proactively reduce risk
Identify reliability risks to help harden systems against failure
Reduction in alert noise / false positives
Increased observability coverage (% of services instrumented)
Improved SLO compliance
Embed observability into applications
Add tracing/metrics into code
Standardize logging formats
Ensure all services are observable end-to-end
Support Microservices (EKS, ECS), Serverless (Lambda, API Gateway), Data services (RDS, DynamoDB, S3)