<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Azure Databricks Engineer - Huxley Associates RSS Feed</title>
    <link>https://jobs.co.uk/job/azure-databricks-engineer-huxley-associates--bfea269b-a68a-4d23-aa06-52e479713713</link>
    <description>RSS feed for Azure Databricks Engineer at Huxley Associates.</description>
    <language>en-gb</language>
    <lastBuildDate>Fri, 01 May 2026 09:19:53 GMT</lastBuildDate>
    <item>
      <title>Azure Databricks Engineer - Huxley Associates</title>
      <link>https://jobs.co.uk/job/azure-databricks-engineer-huxley-associates--bfea269b-a68a-4d23-aa06-52e479713713</link>
      <guid>https://jobs.co.uk/job/azure-databricks-engineer-huxley-associates--bfea269b-a68a-4d23-aa06-52e479713713</guid>
      <pubDate>Tue, 07 Apr 2026 23:00:00 GMT</pubDate>
      <description>Location: City of London | Salary: &amp;pound;140000 - &amp;pound;160000/annum | Type: Permanent | This is a rare opportunity to apply serious data engineering in a domain where latency, correctness, and reliability carry direct commercial weight.  * Requirements  * 6+ years data engineering in production environments; Python expertise - idiomatic, well-tested, production-grade code, not notebook scripts  * ETL/ELT pipeline design and implementation at scale; orchestration with Airflow, Prefect, or equivalent; reliability-first mindset including backfill, retry, and exactly-once semantics  * Azure data platform - Azure Data Factory, Azure Databricks, Azure Synapse Analytics, Azure Data Lake Storage; infrastructure as code for data workloads (Terraform or Bicep)  * Databricks - Delta Lake, Unity Catalog, job cluster vs interactive cluster trade-offs, cost-aware compute management, Spark job optimisation  * Relational databases: PostgreSQL at production scale - query optimisation, indexing strategies, table partitioning, replication, schema design for both OLTP and analytical workloads  * MongoDB - document modelling, aggregation pipelines, indexing strategy, replica sets; clear judgment on when document vs relational storage is the right architectural call  * Containerisation: Do...</description>
      <category>Permanent</category>
    </item>
  </channel>
</rss>