Time since we first saw it
Day 20
Similar jobs usually come down between day 6 and day 52.
From 2,085 similar postings that came down. Coming down is not always a hire.
Work setup in the employer’s posting: TELECOMMUTEFrom the employer’s posting
Design end-to-end data observability across pipelines and data platforms
Embed automated data quality checks into CI/CD pipelines and orchestrators
Configure anomaly detection for data drift, volume anomalies and pipeline failures
Root-cause data failures by tracing lineage upstream and drive problem management
Build reusable data quality and observability frameworks and accelerators
Design and implement end-to-end data observability across pipelines and data platforms
Embed automated data quality checks into CI/CD pipelines and orchestrators
Configure anomaly detection — including dynamic and ML-based thresholds — for data drift, volume anomalies and pipeline failures
Perform root cause analysis by tracing data lineage upstream to the exact origin of a failure
Build reusable data quality and observability frameworks, templates and accelerators adopted by multiple data product teams
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 20
Similar jobs usually come down between day 6 and day 52.
From 2,085 similar postings that came down. Coming down is not always a hire.
892 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
of manual UI configuration Reduce alert noise through event correlation, tagging standards and actionable alert design Build reusable data quality and observability frameworks, templates and accelerators adopted by multiple data product teams Lead post-incident reviews and translate learnings into systemic platform improvements Contribute to presales activities, client-facing assessments and internal training materials for the practice Requirements 4+ years in SRE, DevOps, Data Engineering or Data Platform Operations, with at least 1–2 years focused on data platforms or data pipelines Solid SRE fundamentals: Golden Signals, SLI/SLO definition and calculation, error budgets and burn rate, incident lifecycle, ITIL basics Strong SQL and practical Python for automation and validation scripting Hands-on production experience with at least one cloud platform: Azure, AWS or GCP Experience with at least one modern data platform and orchestration stack — Databricks (preferred), Snowflake, Spark, Airflow, Azure Data Factory, dbt Working knowledge of observability tooling: New Relic, Datadog, Splunk, Elastic Stack, Grafana / OpenTelemetry (any two or more) Infrastructure as Code with Terraform (Ansible is a plus) and CI/CD experience (Azure DevOps, GitLab CI, GitHub Actions) Experience with incident and change management tooling: ServiceNow, PagerDuty or equivalent Ability to troubleshoot complex distributed data issues under SLA pressure B2+ English — the role is client-facing and requires clear written and spoken technical communication Nice to have Databricks certification (Data Engineer Associate / Professional) or equivalent cloud data certification Hands-on experience with dedicated data observability platforms (Monte Carlo, Soda, Anomalo, Great Expectations) Data catalog and lineage tooling (Unity Catalog, OpenLineage, Collibra) FinOps: cloud, platform and telemetry cost optimization Exposure to AI/ML pipeline monitoring or AI Reliability Engineering Power BI or another BI layer, from a monitoring and reliability perspective Event correlation / AIOps experience (New Relic Decisions, IBM NOI, ServiceNow ITOM) Mentoring or team lead experience
What You’ll Get A practice that is actively building a new capability — your work becomes the standard, not a copy of someone else's runbook Engineering focus without 24/7 on-call rotation Internal certification and enablement tracks (Databricks, AI/LLM, Data Observability learning path in Learn) Cross-client exposure: enterprise-scale retail, financial services and manufacturing accounts Responsibilities Design and implement end-to-end data observability across pipelines and data platforms, covering the core data quality pillars: freshness, volume, schema, completeness and accuracy Embed automated data quality checks into CI/CD pipelines and orchestrators (e.g., dbt tests, Great Expectations, native platform checks) Configure anomaly detection — including dynamic and ML-based thresholds — for data drift, volume anomalies and pipeline failures Define, measure and report Data SLIs, SLOs and error budgets together with business and data product stakeholders Perform root cause analysis by tracing data lineage upstream to the exact origin of a failure
drive problem management so incidents do not recur Design architectural guardrails for data pipelines: circuit breakers, dead-letter queues, retry and rollback mechanisms, self-healing patterns Implement monitoring and alerting as code (Terraform / GitOps)
Complete your application on careers.epam.com. The employer’s form will show what is required.
Already applied? Track this application
New Data Governance postings at the employers we follow are up 164% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Governance, by the work the posting describes.
Data governance staff keep a company's data accurate, documented and used within the rules. They agree what key fields mean, set up quality checks, track who owns each dataset and look after master data.
Postings ask for SQL, a governance tool such as Collibra or Informatica, knowledge of privacy and data rules, and a lot of work with other teams.
A data engineer builds the systems that move data; governance staff set and check the standards that data has to meet.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Location not supplied.
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.