Back to jobs

Data Infra Platform Engineer

Pay
Pay not listed
Work setting
On-site — work setting source
Work setup in the employer’s posting: On-Site
From the employer’s posting
Employment
Not stated

What you’ll work on

Full posting
  • Build cloud infrastructure in Terraform as configurable, reusable modules managed through GitOps

  • Deploy, secure, scale and upgrade data systems such as Iceberg, Trino, Kafka, Airflow and databases on Kubernetes

  • Run the catalog, metadata and governance tooling and access policies

  • Build self-service interfaces so teams can provision topics, tables, connections and query access, with docs

  • Define SLOs, write runbooks, lead incident response and run upgrades with no data loss

From the employer’s posting
Build the cloud foundation in Terraform, to a high standard and designed to be configurable
Your focus is on the platform beneath these systems: deploying, securing, scaling, and upgrading them as first-class capabilities
Operate the catalog and metadata layer that makes data discoverable and governed
Build the interfaces that let teams' provision what they need, such as Kafka topics and credentials, Iceberg tables and catalogs
You define and measure the SLIs and SLOs, including data freshness and availability, write the runbooks that make failure recoverable, and lead incident response

What you’ll bring

All qualifications

Core experience

  • Bachelor's degree in computer science, Information Technology or related field.
  • Hands-on experience operating at least one core data system (Kafka, Iceberg/Trino/Spark, or Airflow) as a platform service.
  • Experience running data exploration and visualization tooling such as Grafana, Apache Superset, Elasticsearch, and Kibana.
  • Proficiency in Python and one of Go or Bash, and comfort on Linux.
Qualification wording
Bachelor's degree in computer science, Information Technology or related field.
Hands-on experience operating at least one core data system (Kafka, Iceberg/Trino/Spark, or Airflow) as a platform service.
Experience running data exploration and visualization tooling such as Grafana, Apache Superset, Elasticsearch, and Kibana.
Proficiency in Python and one of Go or Bash, and comfort on Linux.
Education & alternatives
Education - Bachelor's degree in computer science, Information Technology or related field. - Masters degree in Computer Science or Information Technology if applicable
- Bachelor's degree in computer science, Information Technology or related field. - Masters degree in Computer Science or Information Technology if applicable Essential Skills/Experience
Apply at Thales

Posting record

Report an error

Actively hiringFirst seen by us 2 days ago, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 5, 20262 days ago
Recorded sightings
3
Last seen by us
Nov 7, 2026
Employer says posted
Jul 9, 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 2

Early. Similar jobs usually come down between day 6 and day 54.

From 11,511 similar postings that came down. Coming down is not always a hire.

Thales is hiring

26 open jobs

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

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.

  • Bash
  • Python
  • SQL
  • Azure
  • Elasticsearch
  • Grafana
  • Iceberg
  • Kafka
  • Kibana
  • Kubernetes
  • Spark
  • Superset
  • Terraform
  • Trino
  • Airflow
  • Go
Where the posting names them
- Operational maturity: defining SLOs, incident response, and safe upgrades with no data loss. - Proficiency in Python and one of Go or Bash, and comfort on Linux. - The conviction that infrastructure is code: version-controlled, reviewed, tested, and secured.
Desirable Skills/Experience - Working knowledge of SQL and data modelling. Valued but not required; the role centres on the infrastructure, not the data itself. - Depth in Azure services (AKS, ADLS Gen2, AI Foundry, Key Vault, Entra ID, Private Endpoints).
- Working knowledge of SQL and data modelling. Valued but not required; the role centres on the infrastructure, not the data itself. - Depth in Azure services (AKS, ADLS Gen2, AI Foundry, Key Vault, Entra ID, Private Endpoints). - Kafka and Strimzi, including topics, schema, and credential management.
- Hands-on experience operating at least one core data system (Kafka, Iceberg/Trino/Spark, or Airflow) as a platform service. - Experience running data exploration and visualization tooling such as Grafana, Apache Superset, Elasticsearch, and Kibana. - Solid infrastructure-as-code (Terraform or OpenTofu) and GitOps delivery (FluxCD or Argo CD).
Data platform engineering on Kubernetes - Build and operate the infrastructure that runs the data platform: a lakehouse on Apache Iceberg with a Polaris catalog and Trino, event streaming on Kafka, orchestration with Airflow, and managed databases such as CloudNativePG, all on object storage (ADLS Gen2). Your focus is on the platform beneath these systems: deploying, securing, scaling, and upgrading them as first-class capabilities, with the multi-tenancy, RBAC, governance, and FinOps that keep a shared platform healthy. - Deep expertise in how data is modelled or processed is not required. A working understanding of how these systems are used is highly desirable, but the core of the job is keeping the infrastructure reliable, secure, and available.
Data self-service - Build the interfaces that let teams' provision what they need, such as Kafka topics and credentials, Iceberg tables and catalogs, Airflow connections, namespaces, and query access, without the platform team becoming a bottleneck. The goal is a platform that scales through self-service rather than manual requests, with capabilities maturing toward self-served or provided by default. You document these paths as you build them, so runbooks and guides are part of the deliverable. Operate and keep it reliable
- Strong, hands-on production of Kubernetes, including operating stateful, distributed systems (databases, brokers, query engines) and resolving issues under pressure. - Hands-on experience operating at least one core data system (Kafka, Iceberg/Trino/Spark, or Airflow) as a platform service. - Experience running data exploration and visualization tooling such as Grafana, Apache Superset, Elasticsearch, and Kibana.
- Depth in Azure services (AKS, ADLS Gen2, AI Foundry, Key Vault, Entra ID, Private Endpoints). - Kafka and Strimzi, including topics, schema, and credential management. - Lakehouse and query engines: Iceberg, Polaris, Trino, and Spark on object storage.
- You treat infrastructure as code as software: small, composable modules with the versioning, review, and testing that make them reliable and reusable. The desired state lives in Git, the platform reconciles to it through GitOps, and drift is detected rather than discovered. Data platform engineering on Kubernetes - Build and operate the infrastructure that runs the data platform: a lakehouse on Apache Iceberg with a Polaris catalog and Trino, event streaming on Kafka, orchestration with Airflow, and managed databases such as CloudNativePG, all on object storage (ADLS Gen2). Your focus is on the platform beneath these systems: deploying, securing, scaling, and upgrading them as first-class capabilities, with the multi-tenancy, RBAC, governance, and FinOps that keep a shared platform healthy.
- Several years building platform or data-platform capabilities end to end, production-grade, self-service solutions (three to five years is a useful guide). - Strong, hands-on production of Kubernetes, including operating stateful, distributed systems (databases, brokers, query engines) and resolving issues under pressure. - Hands-on experience operating at least one core data system (Kafka, Iceberg/Trino/Spark, or Airflow) as a platform service.
- Metadata and governance: DataHub, lineage, classification, and catalog RBAC. - Managed databases on Kubernetes (CloudNativePG or similar). - Building or operating an internal developer or data platform.
- Kafka and Strimzi, including topics, schema, and credential management. - Lakehouse and query engines: Iceberg, Polaris, Trino, and Spark on object storage. - Airflow, including providers and connection management.
Cloud infrastructure as code - Build the cloud foundation in Terraform, to a high standard and designed to be configurable, so the platform can provision clusters of different profiles (front-facing, data-oriented, developer-oriented) from the same well-factored code. - You treat infrastructure as code as software: small, composable modules with the versioning, review, and testing that make them reliable and reusable. The desired state lives in Git, the platform reconciles to it through GitOps, and drift is detected rather than discovered.
- Experience running data exploration and visualization tooling such as Grafana, Apache Superset, Elasticsearch, and Kibana. - Solid infrastructure-as-code (Terraform or OpenTofu) and GitOps delivery (FluxCD or Argo CD). - A working command of CI/CD pipelines and release strategy (GitLab, or equivalent).

Your next step

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

Applying through Phenom

  • Phenom runs the employer’s careers site, but the application itself usually runs on another system, often Workday or Taleo. The advice for that system applies once you click Apply.

Already applied? Track this application

Demand for Data Engineer roles

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

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of October 26. The fewest in a week was 839, the most 1,314, and the latest week had 1,079.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 5 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.

Job description

View original posting ↗

Location: Singapore, Singapore

Thales is a global technology leader trusted by governments, institutions, and enterprises to tackle their most demanding challenges. From quantum applications and artificial intelligence to cybersecurity and 6G innovation, our solutions empower critical decisions rooted in human intelligence. Operating at the forefront of aerospace and space, cybersecurity and digital identity, we’re driven by a mission to build a future we can all trust.

In Singapore, Thales has been a trusted partner since 1973, originally focused on aerospace activities in the Asia-Pacific region. With 2,000 employees across three local sites, we deliver cutting-edge solutions across aerospace (including air traffic management), defence and security, and digital identity and cybersecurity sectors. Together, we’re shaping the future by enabling customers to make pivotal decisions that safeguard communities and power progress.

Responsibilities

Cloud infrastructure as code

  • Build the cloud foundation in Terraform, to a high standard and designed to be configurable, so the platform can provision clusters of different profiles (front-facing, data-oriented, developer-oriented) from the same well-factored code.
  • You treat infrastructure as code as software: small, composable modules with the versioning, review, and testing that make them reliable and reusable. The desired state lives in Git, the platform reconciles to it through GitOps, and drift is detected rather than discovered.

Data platform engineering on Kubernetes

  • Build and operate the infrastructure that runs the data platform: a lakehouse on Apache Iceberg with a Polaris catalog and Trino, event streaming on Kafka, orchestration with Airflow, and managed databases such as CloudNativePG, all on object storage (ADLS Gen2). Your focus is on the platform beneath these systems: deploying, securing, scaling, and upgrading them as first-class capabilities, with the multi-tenancy, RBAC, governance, and FinOps that keep a shared platform healthy.
  • Deep expertise in how data is modelled or processed is not required. A working understanding of how these systems are used is highly desirable, but the core of the job is keeping the infrastructure reliable, secure, and available.

Data governance and metadata

  • Operate the catalog and metadata layer that makes data discoverable and governed for cataloguing, lineage, and classification, and Polaris for catalog-level access. You enforce the conventions and controls that keep data well managed, such as naming standards, access policies, and retention. This is infrastructure and policy work: you run the tooling and the guardrails, without owning the meaning of the data.

Data self-service

  • Build the interfaces that let teams' provision what they need, such as Kafka topics and credentials, Iceberg tables and catalogs, Airflow connections, namespaces, and query access, without the platform team becoming a bottleneck. The goal is a platform that scales through self-service rather than manual requests, with capabilities maturing toward self-served or provided by default. You document these paths as you build them, so runbooks and guides are part of the deliverable.

Operate and keep it reliable

  • Own the data platform at runtime, not just at provisioning. You define and measure the SLIs and SLOs, including data freshness and availability, write the runbooks that make failure recoverable, and lead incident response when the platform degrades or data stops flowing. You run lifecycle work such as cluster, broker, and engine upgrades with no data loss and minimal disruption, and trace failures to root cause.

REQUIREMENTS:

Education

  • Bachelor's degree in computer science, Information Technology or related field.
  • Masters degree in Computer Science or Information Technology if applicable

Essential Skills/Experience

  • Several years building platform or data-platform capabilities end to end, production-grade, self-service solutions (three to five years is a useful guide).
  • Strong, hands-on production of Kubernetes, including operating stateful, distributed systems (databases, brokers, query engines) and resolving issues under pressure.
  • Hands-on experience operating at least one core data system (Kafka, Iceberg/Trino/Spark, or Airflow) as a platform service.
  • Experience running data exploration and visualization tooling such as Grafana, Apache Superset, Elasticsearch, and Kibana.
  • Solid infrastructure-as-code (Terraform or OpenTofu) and GitOps delivery (FluxCD or Argo CD).
  • A working command of CI/CD pipelines and release strategy (GitLab, or equivalent).
  • A sound grasp of cloud-native security: least privilege, network segmentation, secrets management, identity, and supply-chain integrity.
  • Operational maturity: defining SLOs, incident response, and safe upgrades with no data loss.
  • Proficiency in Python and one of Go or Bash, and comfort on Linux.
  • The conviction that infrastructure is code: version-controlled, reviewed, tested, and secured.

Desirable Skills/Experience

  • Working knowledge of SQL and data modelling. Valued but not required; the role centres on the infrastructure, not the data itself.
  • Depth in Azure services (AKS, ADLS Gen2, AI Foundry, Key Vault, Entra ID, Private Endpoints).
  • Kafka and Strimzi, including topics, schema, and credential management.
  • Lakehouse and query engines: Iceberg, Polaris, Trino, and Spark on object storage.
  • Airflow, including providers and connection management.
  • Metadata and governance: DataHub, lineage, classification, and catalog RBAC.
  • Managed databases on Kubernetes (CloudNativePG or similar).
  • Building or operating an internal developer or data platform.

Essential / Desirable Traits

  • You see systems end to end and resist thinking in silos.
  • You treat the platform as a product: you measure adoption and let evidence, not assumption, guide what to build, harden, or retire.
  • You have learning agility, flexibility, and initiative.
  • You are comfortable in an agile team, engaging directly with the developers you serve.
  • You hold your convictions with humility, welcome feedback, and stay resilient.

At Thales, we’re committed to fostering a workplace where respect, trust, collaboration, and passion drive everything we do. Here, you’ll feel empowered to bring your best self, thrive in a supportive culture, and love the work you do. Join us, and be part of a team reimagining technology to create solutions that truly make a difference – for a safer, greener, and more inclusive world.

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

Singapore, Singapore

Working pattern and location restrictions need checking in the full posting.

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.