Back to jobs

Lead Data Mesh Engineer

Pay
Pay not listed
Work setting
Remote — work setting source
Listed location: Hungary-Remote
Read the full posting
Employment
Full-time — employment source
Employment type in the employer’s posting: Full time
From the employer’s posting

What you’ll work on

Full posting
  • Provision and maintain multi-AZ AWS MSK clusters and NiFi runtimes on EKS using Terraform and GitOps

  • Enforce Avro and AsyncAPI data contracts through schema registries before payloads reach production topics

  • Optimize partitioning, storage auto-scaling and payload compression to cut cross-cloud data movement costs

  • Build fault-tolerant dead letter queue automated replay loops

  • Ensure streaming payloads carry out-of-band tracing context across service hops

From the employer’s posting
Architect, provision, and maintain multi-AZ Amazon Managed Streaming for Apache Kafka (AWS MSK) clusters and Apache NiFi runtimes on Amazon EKS (Graviton ARM64) using Terraform and declarative GitOps patterns.
Integrate vendor-neutral Schema Registries (AWS Glue / Apicurio) to enforce strict Apache Avro and AsyncAPI data contracts
Implement high-performance partition strategies, dynamic storage auto-scaling (gp3/io2), and mandatory local payload compression (Snappy/Zstd) to minimize cross-cloud data movement fees
Build fault-tolerant Dead Letter Queue (DLQ) automated replay loops
ensure all streaming payloads carry lightweight, out-of-band tracing context across service hops
Apply at Cloudera

Posting record

Report an error
Status in our records
Live
First seen by us
Sep 23, 202659 days ago
Recorded sightings
70
Last seen by us
Nov 16, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 59

Up longer than most. Similar jobs usually come down between day 6 and day 56.

Well past Cloudera’s usual: its jobs come down by about day 20.

From 14,771 similar postings that came down, and 9 of Cloudera’s. Coming down is not always a hire.

Cloudera is hiring

5 open jobs

Open jobs by the week we first saw them, last 12 weeks.

  • Hiring has slowed
  • Takes jobs down at a usual pace
Hiring record

See how this role fits your experience

Add 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.

  • AWS
  • Cloudera
  • Datadog
  • Hadoop
  • Hive
  • Kafka
  • Kubernetes
  • Terraform
Where the posting names them
We are building an enterprise-grade, Everything-as-Code (EaC) Data Mesh that transforms corporate IT from a manual ticket-driven delivery model into an automated, machine-executable software factory. As the Lead Data Mesh Engineer, you will own the architectural execution and hands-on delivery of our high-throughput, asynchronous event-streaming infrastructure and hybrid data pipelines. Operating in an environment where every asset, route, and policy must exist as declarative code inside Git, you will architect the "Data-in-Motion" backbone across multi-cloud environments (AWS MSK, Apache NiFi on EKS) and insulate our core on-premises data lakehouse. As a Lead Data Mesh Engineer, you will:
As a Lead Data Mesh Engineer, you will: - Event-Streaming Architecture (IaC): Architect, provision, and maintain multi-AZ Amazon Managed Streaming for Apache Kafka (AWS MSK) clusters and Apache NiFi runtimes on Amazon EKS (Graviton ARM64) using Terraform and declarative GitOps patterns. - Contract-First Schema Governance: Integrate vendor-neutral Schema Registries (AWS Glue / Apicurio) to enforce strict Apache Avro and AsyncAPI data contracts defined in our central Governance Hub before payloads hit production event topics.
- Event-Streaming Architecture (IaC): Architect, provision, and maintain multi-AZ Amazon Managed Streaming for Apache Kafka (AWS MSK) clusters and Apache NiFi runtimes on Amazon EKS (Graviton ARM64) using Terraform and declarative GitOps patterns. - Contract-First Schema Governance: Integrate vendor-neutral Schema Registries (AWS Glue / Apicurio) to enforce strict Apache Avro and AsyncAPI data contracts defined in our central Governance Hub before payloads hit production event topics. - Egress & FinOps Optimization: Implement high-performance partition strategies, dynamic storage auto-scaling (gp3/io2), and mandatory local payload compression (Snappy/Zstd) to minimize cross-cloud data movement fees and optimize compute consumption.
- Distributed Observability: Practical understanding of out-of-band telemetry exhaust, OpenTelemetry standards, and W3C distributed tracing context propagation (Datadog, Otel/OpenTelemetry). - Core Streaming & Orchestration: 6+ years of deep, hands-on experience architecting and operating Apache Kafka (preferably AWS MSK) and Apache NiFi in containerized Kubernetes environments (EKS). - Data Serialization & Contracts: Expertise in Apache Avro, AsyncAPI, and schema registry management for Master Data Management (MDM) enforcement.
Job Description: At Cloudera, we empower people to transform complex data into clear and actionable insights. With as much data under management as the hyperscalers, we're the preferred data partner for the top companies in almost every industry. Powered by the relentless innovation of the open source community, Cloudera advances digital transformation for the world’s largest enterprises. About the Team & Role
- Exposure to Policy-as-Code tools (Open Policy Agent / Rego). - Hybrid Mesh & Lakehouse Integration: Demonstrated background connecting cloud event meshes to enterprise data lakehouses or big-data monoliths (Cloudera CDP, Hadoop, Hive). - Infrastructure-as-Code & GitOps: Advanced proficiency with Terraform and GitOps deployment tools (ArgoCD or Flux) operating under a strict pull-based model.
- Bsc/Msc in related field or equivalent experience - Distributed Observability: Practical understanding of out-of-band telemetry exhaust, OpenTelemetry standards, and W3C distributed tracing context propagation (Datadog, Otel/OpenTelemetry). - Core Streaming & Orchestration: 6+ years of deep, hands-on experience architecting and operating Apache Kafka (preferably AWS MSK) and Apache NiFi in containerized Kubernetes environments (EKS).
- Hybrid Mesh & Lakehouse Integration: Demonstrated background connecting cloud event meshes to enterprise data lakehouses or big-data monoliths (Cloudera CDP, Hadoop, Hive). - Infrastructure-as-Code & GitOps: Advanced proficiency with Terraform and GitOps deployment tools (ArgoCD or Flux) operating under a strict pull-based model. What you can expect from us:

Your next step

Complete your application on cloudera.wd5.myworkdayjobs.com. The employer’s form will show what is required.

Applying through Workday

  • You create an account with each employer before you can upload anything. Every Workday employer has its own account, so one sign-up doesn’t carry over.
  • “Autofill with Resume” comes right after sign-in, before the My Information and My Experience steps. Check every field it fills in those steps, since that’s what recruiters see.
  • Your application status lives in that employer’s Candidate Home, under the same sign-in.

Already applied? Track this application

Job description

View original posting ↗

Business Area:

IT

Seniority Level:

Mid-Senior level

Job Description: 

At Cloudera, we empower people to transform complex data into clear and actionable insights. With as much data under management as the hyperscalers, we're the preferred data partner for the top companies in almost every industry.  Powered by the relentless innovation of the open source community, Cloudera advances digital transformation for the world’s largest enterprises.

About the Team & Role

We are building an enterprise-grade, Everything-as-Code (EaC) Data Mesh that transforms corporate IT from a manual ticket-driven delivery model into an automated, machine-executable software factory. As the Lead Data Mesh Engineer, you will own the architectural execution and hands-on delivery of our high-throughput, asynchronous event-streaming infrastructure and hybrid data pipelines.


Operating in an environment where every asset, route, and policy must exist as declarative code inside Git, you will architect the "Data-in-Motion" backbone across multi-cloud environments (AWS MSK, Apache NiFi on EKS) and insulate our core on-premises data lakehouse.


As a Lead Data Mesh Engineer, you will:


  • Event-Streaming Architecture (IaC): Architect, provision, and maintain multi-AZ Amazon Managed Streaming for Apache Kafka (AWS MSK) clusters and Apache NiFi runtimes on Amazon EKS (Graviton ARM64) using Terraform and declarative GitOps patterns.
  • Contract-First Schema Governance: Integrate vendor-neutral Schema Registries (AWS Glue / Apicurio) to enforce strict Apache Avro and AsyncAPI data contracts defined in our central Governance Hub before payloads hit production event topics.
  • Egress & FinOps Optimization: Implement high-performance partition strategies, dynamic storage auto-scaling (gp3/io2), and mandatory local payload compression (Snappy/Zstd) to minimize cross-cloud data movement fees and optimize compute consumption.
  • Resiliency & Out-of-Band Telemetry: Build fault-tolerant Dead Letter Queue (DLQ) automated replay loops and ensure all streaming payloads carry lightweight, out-of-band tracing context across service hops.


We are excited if you have (Required Experience):

  • Bsc/Msc in related field or equivalent experience
  • Distributed Observability: Practical understanding of out-of-band telemetry exhaust, OpenTelemetry standards, and W3C distributed tracing context propagation (Datadog, Otel/OpenTelemetry).
  • Core Streaming & Orchestration: 6+ years of deep, hands-on experience architecting and operating Apache Kafka (preferably AWS MSK) and Apache NiFi in containerized Kubernetes environments (EKS).
  • Data Serialization & Contracts: Expertise in Apache Avro, AsyncAPI, and schema registry management for Master Data Management (MDM) enforcement.


You may also have:

  • Exposure to Policy-as-Code tools (Open Policy Agent / Rego).
  • Hybrid Mesh & Lakehouse Integration: Demonstrated background connecting cloud event meshes to enterprise data lakehouses or big-data monoliths (Cloudera CDP, Hadoop, Hive).
  • Infrastructure-as-Code & GitOps: Advanced proficiency with Terraform and GitOps deployment tools (ArgoCD or Flux) operating under a strict pull-based model.

What you can expect from us:

  • Generous PTO Policy 

  • Support work life balance with Unplugged Days

  • Flexible WFH Policy 

  • Mental & Physical Wellness programs 

  • Phone and Internet Reimbursement program 

  • Access to Continued Career Development 

  • Comprehensive Benefits and Competitive Packages 

  • Paid Volunteer Time

  • Employee Resource Groups

EEO/VEVRAA

#LI-EO1

#LI-HYBRID

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 845, the most 1,344, and the latest week had 1,007.
August 17Last week

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.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Hungary-Remote

About the Team & Role We are building an enterprise-grade, Everything-as-Code (EaC) Data Mesh that transforms corporate IT from a manual ticket-driven delivery model into an automated, machine-executable software factory. As the Lead Data Mesh Engineer, you will own the architectural execution and hands-on delivery of our high-throughput, asynchronous event-streaming infrastructure and hybrid data pipelines. Operating in an environment where every asset, route, and policy must exist as declarative code inside Git, you will architect the "Data-in-Motion" backbone across multi-cloud environments (AWS MSK, Apache NiFi on EKS) and insulate our core on-premises data lakehouse.
More source context
- Exposure to Policy-as-Code tools (Open Policy Agent / Rego). - Hybrid Mesh & Lakehouse Integration: Demonstrated background connecting cloud event meshes to enterprise data lakehouses or big-data monoliths (Cloudera CDP, Hadoop, Hive). - Infrastructure-as-Code & GitOps: Advanced proficiency with Terraform and GitOps deployment tools (ArgoCD or Flux) operating under a strict pull-based model.

More relevant text appears in the full description.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.