Build the first production path for PostgreSQL publishing tables, Debezium CDC, Kafka topics, and catalog registration
Create GitOps-style workflows that validate and reconcile data contracts, schemas, and ownership as code
Operate and improve the CDC runtime, including offsets, replay, resnapshotting, and recovery
Build tooling that gives product engineers fast feedback before they publish or change data products
Integrate platform metadata into DataHub for discovery, ownership, lineage, and impact analysis
From the employer’s posting
Build the first production path for platform-managed PostgreSQL publishing tables, Debezium CDC, Kafka topics, and catalog registration.
Create GitOps-style workflows where contracts, schemas, ownership, lifecycle, compatibility, policy metadata, and runtime desired state are reviewed, validated, and reconciled as code.
Operate and improve the CDC runtime model, including Kubernetes workloads, source-specific isolation, offsets, schema history, heartbeats, signal channels, lag visibility, replay, resnapshotting, and recovery.
Build tooling that gives product engineers fast feedback before they publish or change data products.
Integrate platform metadata into DataHub so engineers can discover data products, understand ownership, trace lineage, and reason about the impact of changes.
Strong experience building and operating production software systems, preferably in platform, infrastructure, backend, or data-intensive environments.
Deep understanding of distributed systems trade-offs: reliability, idempotency, replay, eventual consistency, ownership boundaries, compatibility, and operational failure modes.
Practical experience with PostgreSQL or other relational databases, including schema design, migrations, transactions, replication, or operational performance.
Experience with Kafka, event streaming, CDC, Debezium, or adjacent data-movement technologies.
Experience building software that other engineers use: CLIs, internal platforms, control planes, automation, CI validation, developer tooling, or self-service workflows.
Familiarity with Kubernetes and cloud or infrastructure platforms, including runtime isolation, deployment, observability, and operational ownership.
Qualification wording
Strong experience building and operating production software systems, preferably in platform, infrastructure, backend, or data-intensive environments.
Deep understanding of distributed systems trade-offs: reliability, idempotency, replay, eventual consistency, ownership boundaries, compatibility, and operational failure modes.
Practical experience with PostgreSQL or other relational databases, including schema design, migrations, transactions, replication, or operational performance.
Experience with Kafka, event streaming, CDC, Debezium, or adjacent data-movement technologies. Direct Debezium experience is valuable, but strong fundamentals matter more.
Experience building software that other engineers use: CLIs, internal platforms, control planes, automation, CI validation, developer tooling, or self-service workflows.
Familiarity with Kubernetes and cloud or infrastructure platforms, including runtime isolation, deployment, observability, and operational ownership.
About Smartly
Smartly is the AI-powered advertising technology company transforming ad experiences for brands and their consumers.
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.
Python
Ruby
TypeScript
BigQuery
ClickHouse
Iceberg
Kafka
Kubernetes
PostgreSQL
S3
Go
Where the posting names them
- Experience supporting analytics, AI/ML, feature-store-style access patterns, or cross-domain product-service integrations.
- Experience with JVM languages and Python, TypeScript, Go, or Ruby.
What we offer you
- DataHub or other data catalog, lineage, or governance systems.
- Open table formats such as Apache Iceberg, object-store-backed data lakes, S3, BigQuery, ClickHouse, or analytical storage systems.
- GitHub Actions, policy-as-code, infrastructure-as-code, controllers, operators, or reconciliation-based systems.
Smartly is building the standard path for governed data sharing across product services, analytics, and AI/ML. The Data Platform team owns the contracts, control mechanisms, publication paths, catalog metadata, lifecycle rules, lineage, permissions, and runtime building blocks that make reusable data safe and practical at scale.
This is a role for someone who wants to shape a platform early, while working on concrete production problems from the start. Smartly already has the production systems, Kafka backbone, PostgreSQL databases, analytical consumers, and AI/ML use cases that need a better data foundation. The challenge is to turn that reality into a standard path that engineers actually want to use.
Our first milestone is focused: centrally managed publishing tables in service-owned PostgreSQL databases, captured through Debezium CDC into Kafka, and registered in DataHub with ownership, lifecycle, lineage, and impact-analysis metadata. Longer-term, the platform expands toward self-service data products, governed materialisations, durable shared state, and reusable data across Smartly’s operational and analytical systems.
This is a role for someone who wants to shape a platform early, while working on concrete production problems from the start. Smartly already has the production systems, Kafka backbone, PostgreSQL databases, analytical consumers, and AI/ML use cases that need a better data foundation. The challenge is to turn that reality into a standard path that engineers actually want to use.
Our first milestone is focused: centrally managed publishing tables in service-owned PostgreSQL databases, captured through Debezium CDC into Kafka, and registered in DataHub with ownership, lifecycle, lineage, and impact-analysis metadata. Longer-term, the platform expands toward self-service data products, governed materialisations, durable shared state, and reusable data across Smartly’s operational and analytical systems.
This is not a role where you only maintain an existing reporting pipeline. You will help design and build the platform path that other engineering teams use when they publish and consume shared data.
- Design and build platform services, tools, and workflows for contract-driven data publishing and consumption.
- Build the first production path for platform-managed PostgreSQL publishing tables, Debezium CDC, Kafka topics, and catalog registration.
- Create GitOps-style workflows where contracts, schemas, ownership, lifecycle, compatibility, policy metadata, and runtime desired state are reviewed, validated, and reconciled as code.
- Practical experience with PostgreSQL or other relational databases, including schema design, migrations, transactions, replication, or operational performance.
- Experience with Kafka, event streaming, CDC, Debezium, or adjacent data-movement technologies. Direct Debezium experience is valuable, but strong fundamentals matter more.
- Experience building software that other engineers use: CLIs, internal platforms, control planes, automation, CI validation, developer tooling, or self-service workflows.
- Help define how Smartly models data products, publishing contracts, schema evolution, field stability, deletion semantics, access policy, lineage, and cost attribution.
- Operate and improve the CDC runtime model, including Kubernetes workloads, source-specific isolation, offsets, schema history, heartbeats, signal channels, lag visibility, replay, resnapshotting, and recovery.
- Integrate platform metadata into DataHub so engineers can discover data products, understand ownership, trace lineage, and reason about the impact of changes.
- Experience building software that other engineers use: CLIs, internal platforms, control planes, automation, CI validation, developer tooling, or self-service workflows.
- Familiarity with Kubernetes and cloud or infrastructure platforms, including runtime isolation, deployment, observability, and operational ownership.
- Ability to turn ambiguous architectural direction into practical increments, make trade-offs explicit, and deliver useful production systems without waiting for perfect certainty.
- Deep understanding of distributed systems trade-offs: reliability, idempotency, replay, eventual consistency, ownership boundaries, compatibility, and operational failure modes.
- Practical experience with PostgreSQL or other relational databases, including schema design, migrations, transactions, replication, or operational performance.
- Experience with Kafka, event streaming, CDC, Debezium, or adjacent data-movement technologies. Direct Debezium experience is valuable, but strong fundamentals matter more.
Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.
Applying through Greenhouse
No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.
We are looking for a Senior Data Platform Engineer to join the Data Platform at Smartly!
Smartly is building the standard path for governed data sharing across product services, analytics, and AI/ML. The Data Platform team owns the contracts, control mechanisms, publication paths, catalog metadata, lifecycle rules, lineage, permissions, and runtime building blocks that make reusable data safe and practical at scale.
This is a role for someone who wants to shape a platform early, while working on concrete production problems from the start. Smartly already has the production systems, Kafka backbone, PostgreSQL databases, analytical consumers, and AI/ML use cases that need a better data foundation. The challenge is to turn that reality into a standard path that engineers actually want to use.
Our first milestone is focused: centrally managed publishing tables in service-owned PostgreSQL databases, captured through Debezium CDC into Kafka, and registered in DataHub with ownership, lifecycle, lineage, and impact-analysis metadata. Longer-term, the platform expands toward self-service data products, governed materialisations, durable shared state, and reusable data across Smartly’s operational and analytical systems.
This is not a role where you only maintain an existing reporting pipeline. You will help design and build the platform path that other engineering teams use when they publish and consume shared data.
What you will do
Design and build platform services, tools, and workflows for contract-driven data publishing and consumption.
Build the first production path for platform-managed PostgreSQL publishing tables, Debezium CDC, Kafka topics, and catalog registration.
Create GitOps-style workflows where contracts, schemas, ownership, lifecycle, compatibility, policy metadata, and runtime desired state are reviewed, validated, and reconciled as code.
Build tooling that gives product engineers fast feedback before they publish or change data products.
Help define how Smartly models data products, publishing contracts, schema evolution, field stability, deletion semantics, access policy, lineage, and cost attribution.
Operate and improve the CDC runtime model, including Kubernetes workloads, source-specific isolation, offsets, schema history, heartbeats, signal channels, lag visibility, replay, resnapshotting, and recovery.
Integrate platform metadata into DataHub so engineers can discover data products, understand ownership, trace lineage, and reason about the impact of changes.
Work with product, infrastructure, data engineering, analytics, and AI/ML teams to make the standard path easier and safer than bespoke point-to-point integrations.
What we are looking for
Strong experience building and operating production software systems, preferably in platform, infrastructure, backend, or data-intensive environments.
Deep understanding of distributed systems trade-offs: reliability, idempotency, replay, eventual consistency, ownership boundaries, compatibility, and operational failure modes.
Practical experience with PostgreSQL or other relational databases, including schema design, migrations, transactions, replication, or operational performance.
Experience with Kafka, event streaming, CDC, Debezium, or adjacent data-movement technologies. Direct Debezium experience is valuable, but strong fundamentals matter more.
Experience building software that other engineers use: CLIs, internal platforms, control planes, automation, CI validation, developer tooling, or self-service workflows.
Familiarity with Kubernetes and cloud or infrastructure platforms, including runtime isolation, deployment, observability, and operational ownership.
Ability to turn ambiguous architectural direction into practical increments, make trade-offs explicit, and deliver useful production systems without waiting for perfect certainty.
Clear written and spoken communication in English. This role involves aligning multiple engineering teams around standards, contracts, and ownership boundaries.
Useful experience, but not required
DataHub or other data catalog, lineage, or governance systems.
Open table formats such as Apache Iceberg, object-store-backed data lakes, S3, BigQuery, ClickHouse, or analytical storage systems.
GitHub Actions, policy-as-code, infrastructure-as-code, controllers, operators, or reconciliation-based systems.
Data contracts, schema registries, Protobuf, Avro, JSON Schema, compatibility checking, field-level metadata, or contract testing.
Experience with JVM languages and Python, TypeScript, Go, or Ruby.
What we offer you
At Smartly, we offer a place where you can do meaningful technical work while growing with a global team.
Inclusive global culture built on trust, transparency, open feedback, and respect for different perspectives.
Global impact through technology used by major brands to plan, create, optimize, and understand digital advertising at scale.
Wellbeing support, paid holidays, family leave, and sustainable ways of working.
Equity options, performance-based rewards, competitive compensation, and career development opportunities.
A flexible hybrid workplace that balances office collaboration with focused remote work. At Smartly we work 3 days a week from the office.
About Smartly
Smartly is the AI-powered advertising technology company transforming ad experiences for brands and their consumers. Our comprehensive advertising platform seamlessly integrates the capabilities of media, creative, and intelligence to power more than 800 billion impressions and generate more than 300 billion creatives annually, delivering tangible business outcomes for brands and advertisers.
Smartly is the only company in the industry recognized as a Leader in The Forrester Wave: Creative Advertising Technologies with PwC validating the results it delivers for brands. We manage creative and media for 700+ brands worldwide and $6B in ad spend across the largest media platforms, including Facebook, Google, Instagram, Pinterest, Snap, and TikTok. Our end-to-end technology, unmatched access to media platforms and exceptional customer service help Fortune 500 brands to reach and engage consumers and learn what performs best.Smartly is a multinational and diverse team of 750+ Smartlies from 60+ nationalities, working in 13 countries. Together, we want to create and maintain an inclusive environment where everyone feels respected and heard. Our Diversity, Equity & Inclusion approach is at the heart of it.
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
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.
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
Berlin, Berlin, Germany; Helsinki, Uusimaa, Finland
- Equity options, performance-based rewards, competitive compensation, and career development opportunities.
- A flexible hybrid workplace that balances office collaboration with focused remote work. At Smartly we work 3 days a week from the office.
About Smartly
Work authorization
No clear work-authorization passage found. Eligibility is unconfirmed.