Data Engineer

We are looking for a Data Engineer to build and run the pipelines and data models behind our core data platform — the centralized data layer that serves global energy traders and analysts in real time. This is a hands-on delivery role. You will write the Python that moves market and fundamental data from source through to the analysts, applications, and AI systems that consume it, and you will support what you ship. Python is the core skill, but it is not the whole job. We are standing up a Snowflake warehouse, migrating legacy pipelines onto a Prefect-based framework, and consolidating how the platform stores and exposes data. The work reaches across more of the stack than pipeline code alone.

This is a hands-on delivery role. You will write the Python that moves market and fundamental data from source through to the analysts, applications, and AI systems that consume it, and you will support what you ship. Python is the core skill, but it is not the whole job. We are standing up a Snowflake warehouse, migrating legacy pipelines onto a Prefect-based framework, and consolidating how the platform stores and exposes data. The work reaches across more of the stack than pipeline code alone. The platform is polyglot by design: streaming, caching, timeseries, relational, and warehouse technologies each doing what they are good at. You will build to the established patterns across that stack, and we expect you to understand why each technology sits where it does.

What You Will Do - Build, test, and operate production data pipelines in Python on our modern pipeline framework, orchestrated with Prefect - Build and maintain warehouse models in Snowflake using dbt — clean, tested, documented, and cost-aware

- 3+ years of hands-on data engineering experience building and operating production data pipelines - Strong Python — clean, tested, maintainable code, not scripts that happen to run. Fluency with pandas and the wider data-handling ecosystem - SQL depth — you can model, query, and tune, and you know what makes a query expensive before you run it

- Strong Python — clean, tested, maintainable code, not scripts that happen to run. Fluency with pandas and the wider data-handling ecosystem - SQL depth — you can model, query, and tune, and you know what makes a query expensive before you run it - Snowflake or a comparable cloud warehouse — dimensional modeling, performance tuning, and cost-aware design. dbt experience is a strong plus

- Implement data quality, freshness, and reconciliation checks so problems surface before users find them - Use AWS data services where our platform patterns call for them - Support what you ship — monitoring and alerting on your components, and investigating when something breaks

- Sound engineering fundamentals — object-oriented design, design patterns, testing, code review, and version control as habits rather than requirements - Working knowledge of AWS data services and how to compose them into something reliable - A build-to-operate mindset — monitoring, alerting, and failure recovery are part of how you design, not something added later

- Build, test, and operate production data pipelines in Python on our modern pipeline framework, orchestrated with Prefect - Build and maintain warehouse models in Snowflake using dbt — clean, tested, documented, and cost-aware - Migrate legacy pipelines and Oracle-based components onto current frameworks and standards, retiring technical debt as you go

- SQL depth — you can model, query, and tune, and you know what makes a query expensive before you run it - Snowflake or a comparable cloud warehouse — dimensional modeling, performance tuning, and cost-aware design. dbt experience is a strong plus - Breadth across data technologies — streaming, caching, timeseries, relational, and warehouse, with a view on where each belongs. Kafka, Redis, InfluxDB, Oracle, and Snowflake are what we run; comparable exposure matters more than an exact match

- Clear communication — you can explain a technical trade-off to an analyst, and turn a vague request into the right set of questions - Terraform, Docker, or API development (FastAPI, Flask) exposure is welcome — we use all three - Experience in financial services, commodities, or energy trading data is a plus; the data volume, latency requirements, and stakes are real

- Migrate legacy pipelines and Oracle-based components onto current frameworks and standards, retiring technical debt as you go - Work across the platform stack — Kafka, Redis, InfluxDB, Oracle, and Snowflake — building to the established pattern for each rather than reaching for the tool you already know - Acquire data from external sources — vendor APIs, files, feeds, and web sources — and land it reliably

- Snowflake or a comparable cloud warehouse — dimensional modeling, performance tuning, and cost-aware design. dbt experience is a strong plus - Breadth across data technologies — streaming, caching, timeseries, relational, and warehouse, with a view on where each belongs. Kafka, Redis, InfluxDB, Oracle, and Snowflake are what we run; comparable exposure matters more than an exact match - Pipeline orchestration experience — Prefect preferred; Airflow, Dagster, or similar considered

- You own several production data components outright and they run reliably with minimal intervention - Warehouse models you built in Snowflake are in active use by analysts and downstream applications - A meaningful share of the legacy pipelines you inherited have been migrated onto the current framework and standards

- Breadth across data technologies — streaming, caching, timeseries, relational, and warehouse, with a view on where each belongs. Kafka, Redis, InfluxDB, Oracle, and Snowflake are what we run; comparable exposure matters more than an exact match - Pipeline orchestration experience — Prefect preferred; Airflow, Dagster, or similar considered - Sound engineering fundamentals — object-oriented design, design patterns, testing, code review, and version control as habits rather than requirements