Time since we first saw it
Day 3
Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
Employment type in the employer’s posting: FULL_TIMEFrom the employer’s posting
Ingest OPC UA, historian, IoT, LIMS, alarm and P&ID data into the Lakehouse
Map signals to physical processes using tags, units and hierarchies
Build real-time streaming and batch ingestion pipelines into the Lakehouse
Detect schema changes and signal drift, and keep audit lineage across pipelines
Build training and low-latency inference data pipelines for AI workloads
Ingest from OPC UA servers, process historians, IoT sensors, LIMS systems, alarms/events, and P&IDs.
Map signals to their physical processes (tags, units, hierarchies)
Build pipelines that handle real-time streaming and batch ingestion into the Lakehouse.
Detect and manage schema changes, signal drift, and inconsistencies acrosstime.
Build and maintaindual pipelines: Training→ large-scale historical data prep for time-series + LLM training. Inference→ low-latency, real-time pipelines
Deep expertise in PostgreSQL (partitioning, indexing, query optimisation, storage design).
Strong proficiency in Python for data processing, scripting, and pipeline orchestration.
Hands-on experience with AWS (EKS, S3, EBS, IAM, KMS, CloudWatch, etc.)for secure and scalable data pipelines.
Proven ability to work with Databricks and PySpark for large-scale distributed data processing.
Familiarity with time-series industrial data (control systems, DCS/SCADA logs, process historians).
Experience in unstructured data sync and management within hybrid cloud/on-prem environments.
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
Similar jobs usually come down between day 3 and day 42.
From 633 similar postings that came down. Coming down is not always a hire.
3 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.
- Deep expertise in PostgreSQL (partitioning, indexing, query optimisation, storage design). - Strong proficiency in Python for data processing, scripting, and pipeline orchestration. - Hands-on experience with AWS (EKS, S3, EBS, IAM, KMS, CloudWatch, etc.)for secure and scalable data pipelines.
The Role As our Data Engineer, you’ll architect and maintain pipelines that make high-frequency time-series, lab, and historian data into a scalable Lakehouse architecture, usable for both deep learning models and real-time LLMs. You’ll be working across AWS (EKS, S3, EBS, KMS, CloudWatch) and Databricks/PySpark, ensuring data is contextualised, synchronised, and optimised for both deep learning models and real-time LLM workloads. This isn’t a traditional ETL role, you’ll be solving problems at the intersection of control systems, industrial data engineering, and AI enablement.
- Strong proficiency in Python for data processing, scripting, and pipeline orchestration. - Hands-on experience with AWS (EKS, S3, EBS, IAM, KMS, CloudWatch, etc.)for secure and scalable data pipelines. - Proven ability to work with Databricks and PySpark for large-scale distributed data processing.
- Build pipelines that handle real-time streaming and batch ingestion into the Lakehouse. - Manage synchronisation between historian archives, unstructured files, and AWS storage (S3/EBS). - Orchestrate Databricks Lakeflow/Connectors for integrating data into Lakebase/Lakehouse.
- Detect and manage schema changes, signal drift, and inconsistencies acrosstime. - Implement lineage and audit trails across Spark/Databricks and AWS pipelines. 4. Data Preparation for AI
- Optimise pipelines for both fast analytical queries and high-efficiency model training. - Deploy and manage data pipelines in AWS EKS (Kubernetes) with persisten tEBS-backed storage. What Success Looks Like
- Hands-on experience with AWS (EKS, S3, EBS, IAM, KMS, CloudWatch, etc.)for secure and scalable data pipelines. - Proven ability to work with Databricks and PySpark for large-scale distributed data processing. - Familiarity with time-series industrial data (control systems, DCS/SCADA logs, process historians).
- Manage synchronisation between historian archives, unstructured files, and AWS storage (S3/EBS). - Orchestrate Databricks Lakeflow/Connectors for integrating data into Lakebase/Lakehouse. - Handle secure, high-throughput transfers between historian archives and sandbox/live environments.
- Bonus: Experience working as a data engineer in oil and gas or energy environments - Bonus: Knowledge of streaming frameworks (Kafka, Flink, Spark Streaming) or MLOps stacks for data versioning and lineage. Core Responsibilities
Technical Requirements - Deep expertise in PostgreSQL (partitioning, indexing, query optimisation, storage design). - Strong proficiency in Python for data processing, scripting, and pipeline orchestration.
Complete your application on appliedcomputing.teamtailor.com. The employer’s form will show what is required.
Already applied? Track this application
Applied Computing was founded in 2023 to build Orbital, a physics-informed foundation model for energy operations. We’re live across oil and gas, refineries, and petrochemicals, working towards our mission: sustainable
abundance for a growing planet.
The hydrocarbon industry keeps the world running. But its complexity has left operators tied to legacy systems, making critical decisions on less than 10% of available data. We built Orbital to change that. It’s a foundation model built specifically for energy that lets companies use AI at scale, harnessing all of their operational
data and optimising in real time for any metric. Decisions get faster, operations get safer, and carbon intensity falls.
We’ve raised over $32 million, including one of the largest seed rounds for an
AI company in the UK. We’re just getting started
The Role
As our Data Engineer, you’ll architect and maintain pipelines that make high-frequency time-series, lab, and historian data into a scalable Lakehouse architecture, usable for both deep learning models and real-time LLMs. You’ll be working across AWS (EKS, S3, EBS, KMS, CloudWatch) and Databricks/PySpark, ensuring data is contextualised, synchronised, and optimised for both deep learning models and real-time LLM workloads.
This isn’t a traditional ETL role, you’ll be solving problems at the intersection of control systems, industrial data engineering, and AI enablement.
Technical Requirements
Deep expertise in PostgreSQL (partitioning, indexing, query optimisation, storage design).
Strong proficiency in Python for data processing, scripting, and pipeline orchestration.
Hands-on experience with AWS (EKS, S3, EBS, IAM, KMS, CloudWatch, etc.)for secure and scalable data pipelines.
Proven ability to work with Databricks and PySpark for large-scale distributed data processing.
Familiarity with time-series industrial data (control systems, DCS/SCADA logs, process historians).
Experience in unstructured data sync and management within hybrid cloud/on-prem environments.
Bonus: Experience working as a data engineer in oil and gas or energy environments
Bonus: Knowledge of streaming frameworks (Kafka, Flink, Spark Streaming) or MLOps stacks for data versioning and lineage.
Core Responsibilities
1. Ingest & Contextualise Data
Ingest from OPC UA servers, process historians, IoT sensors, LIMS systems, alarms/events, and P&IDs.
Map signals to their physical processes (tags, units, hierarchies) for interpretability in AI pipelines.
2. Data Movement & Accessibility
Build pipelines that handle real-time streaming and batch ingestion into the Lakehouse.
Manage synchronisation between historian archives, unstructured files, and AWS storage (S3/EBS).
Orchestrate Databricks Lakeflow/Connectors for integrating data into Lakebase/Lakehouse.
Handle secure, high-throughput transfers between historian archives and sandbox/live environments.
3. Change Tracking & Integrity
Detect and manage schema changes, signal drift, and inconsistencies acrosstime.
Implement lineage and audit trails across Spark/Databricks and AWS pipelines.
4. Data Preparation for AI
Build and maintaindual pipelines:
Training→ large-scale historical data prep for time-series + LLM training.
Inference→ low-latency, real-time pipelines for anomaly detection, optimisation, and LLM search.
Support heterogeneous AI workloads (time-series forecasting and retrieval-augmented LLMs).
5. Database Performance & Optimisation
Tune PostgreSQLand sparkfor high-throughput time-series workloads (partitioning, indexing, query optimisation).
Optimise pipelines for both fast analytical queries and high-efficiency model training.
Deploy and manage data pipelines in AWS EKS (Kubernetes) with persisten tEBS-backed storage.
What Success Looks Like
Live data streams are contextualised,queryable, and AI-ready.
Schema changes and signal drift are detected and handled without breaking downstream workflows.
Training and inference pipelines run smoothly in parallel, optimised for scale and latency.
New Forward Deployed Engineer postings at the employers we follow are up 225% 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 Forward Deployed Engineer, by the work the posting describes.
Forward deployed engineers are placed with their employer's customers: they learn a customer's problem and write the code that makes the employer's product solve it inside the customer's own systems.
Postings ask for strong software engineering, most often in Python, ease with customers and their executives, often travel, and in about three of four cases work with large language models or AI agents.
An AI engineer or data engineer builds for their own employer's product team; a forward deployed engineer does similar work inside a customer. We give this role to every posting whose title says forward deployed.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
London, GB
- Familiarity with time-series industrial data (control systems, DCS/SCADA logs, process historians). - Experience in unstructured data sync and management within hybrid cloud/on-prem environments. - Bonus: Experience working as a data engineer in oil and gas or energy environments
No clear work-authorization passage found. Eligibility is unconfirmed.