🎁 Avant de postuler, entraînez-vous à cet entretien. Créez votre compte WorkMundi gratuit et recevez un Entraînement à l'entretien sur HelpsYouSpeak — sans frais, sans carte. Je veux mon entraînement →
We are looking for an Observability Engineer — Data Platform to help us build reliable, scalable and reusable observability capabilities for our data platform and critical data pipelines. This is a hands-on engineering role for someone with a strong Observability, Platform Engineering, SRE, DevOps or Cloud Engineering background. The role starts with data pipeline observability, but the ambition is broader: to contribute to observability standards that can progressively support product teams and wider IT capabilities. You will help Enovos move towards an OpenTelemetry-based observability approach, improve alerting reliability, and make observability easier to adopt for engineering and product teams. Your tasks • You design and implement observability standards for data pipelines, data products and platform services. • You support the progressive adoption of OpenTelemetry for logs, metrics and traces. • You will work with existing tools such as ELK / OpenSearch, Fluent Bit, Grafana and Prometheus. • You define reusable patterns for instrumentation, dashboards, alerting and runbooks. • You improve detection and diagnosis of data pipeline incidents, delays, failures and SLA breaches. • You correlate telemetry with meaningful context such as pipeline, run ID, dataset, data product, owner and environment. • You build actionable alerts and reduce noise from non-relevant or redundant alerts. • You support incident response, root cause analysis and post-incident improvements. • You automate observability onboarding using CI/CD, Infrastructure as Code and reusable templates where relevant. • You enable self-service observability for product and engineering teams. • You explore pragmatic AI-assisted use cases for anomaly detection, alert correlation or incident analysis. Your profile • You have at least 5 years of experience in observability, SRE, platform engineering, DevOps, cloud engineering or a similar role. • Strong hands-on experience with production systems. • Good understanding of modern observability: logs, metrics, traces, alerting, dashboards and incident response. • Practical experience with OpenTelemetry, or strong knowledge and motivation to lead its adoption. • Experience with tools such as Grafana, Prometheus, ELK / OpenSearch, Fluent Bit or similar. • Experience with cloud environments, preferably AWS. • Experience with Infrastructure as Code, preferably Terraform. • Ability to automate, standardise and document engineering practices. • Interest in data pipelines and data products, even if your core background is not Data Engineering. • A pragmatic mindset focused on production reliability, operational value and continuous improvement. • Good communication skills in English. French and/or German are considered an advantage.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.