Time since we first saw it
Day 98
Up longer than most. Similar jobs usually come down between day 7 and day 56.
From 10,198 similar postings that came down. Coming down is not always a hire.
Location not stated
Open 3 months, first seen by us 98 days agoEmployment type in the employer’s posting: Full-TimeFrom the employer’s posting
A senior individual contributor owning the data science work end to end: deciding what to measure, getting the data, building the models, defending the conclusions.
We are hiring for a sector, not for one narrow problem.
Reconstruct deal P&L across the lifecycle and explain every delta between netback, provisional and final P&L
Forecast provisional costs, demurrage and claim exposure, FX and working capital
Detect anomalies such as invoice lines off contract terms, duplicate invoices and misallocated cost
Build the margin, cost-per-tonne and exposure reporting layer with agreed definitions
Turn vague business problems into research plans and actionable recommendations
A senior individual contributor owning the data science work end to end: deciding what to measure, getting the data, building the models, defending the conclusions. You work directly with traders, deal economists, finance and treasury, and the founders — no account manager in between.
We are hiring for a sector, not for one narrow problem. Assignments come from business stakeholders and they vary; what stays constant is the industry and the independence expected. The team can grow with one or two junior data scientists reporting to you.
P&L reconstruction and margin attribution across the deal lifecycle
Forecasting where it pays on the financial side
Anomaly and fraud detection on financial data
The reporting layer for finance and risk
Turning vague business problems into a research plan
7+ years in data science, with senior ownership of your own workstreams
at least two years of delivered projects in trading, refining, logistics, storage or distribution
Strong Python and SQL, and readiness to work in raw data yourself
Forecasting and time-series modelling on real business data
Experience taking models into production and operating them; close to essential for us
- Working with coding agents, seriously. Agents write most of the code here. Bad agent output in analysis fails silently: a join fans out rows, a `dropna` removes half a population, a future-dated column leaks into features. We hire for verification habits, not speed — row-count and population checks, reconciliation against a number someone already trusts, held-out evaluation, a traceable path from raw data to any figure a decision-maker sees - Strong Python and SQL, and readiness to work in raw data yourself: unfamiliar schemas, undocumented tables, exports never meant for analysis - Forecasting and time-series modelling on real business data
Open 3 monthsWe first saw this posting 98 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 98
Up longer than most. Similar jobs usually come down between day 7 and day 56.
From 10,198 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 recordCheck the employer’s posting for the current role and application details.
Already applied? Track this application
New Data Scientist postings at the employers we follow are down 3% over the last 5 weeks compared with the 5 before.
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.
We file this job under Data Scientist, by the work the posting describes.
Data scientists use statistics and models to answer harder questions, such as whether a change worked, what demand will look like next quarter, or which customers are likely to leave.
Postings usually ask for Python or R, SQL, statistics, experiment design and common machine learning methods.
Unlike an ML engineer, a data scientist's main output is often an analysis or a first model, not software running inside a product.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-2051.
About the role
A senior individual contributor owning the data science work end to end: deciding what to measure, getting the data, building the models, defending the conclusions. You work directly with traders, deal economists, finance and treasury, and the founders — no account manager in between.
We are hiring for a sector, not for one narrow problem. Assignments come from business stakeholders and they vary; what stays constant is the industry and the independence expected. The team can grow with one or two junior data scientists reporting to you.
There is a data engineer and an established data lake, but not every source is organised that way — a meaningful part of the work still starts in raw tables and unprocessed exports.
What the work looks like
The system we are building exists so that anyone involved in a deal can reconstruct the P&L between any two points of the chain, at any moment, on an agreed and versioned allocation basis. That is where the role sits: P&L, cost and financial transactions. Operational data is an input to margin, not a subject of its own.
This is operational deal P&L, reconciled to but not identical with the statutory accounts; the general ledger and month-close stay in the accounting system.
Scope
Requirements
What we offer
How to apply
Share your CV an answer to any of the questions below, at your choice. Applications without answers are not reviewed.
1. A term contract drawn down over several lots was booked at a netback of about $14/t. The final P&L closes at $6/t and nobody can say where the rest went — pricing period, FX, provisional costs replaced by actuals, late demurrage and cost reallocation all have their advocates. How would you approach it, what would you need, and what would you deliver?
2. Give a real case where two systems or two departments reported different numbers for the same P&L, margin or quantity. What were the figures, why did they differ, which one did the business treat as truth, and what did you change?
3. Show a real prompt or task brief you gave an agent for an analysis or a model, and what it produced. Then one case where agent output looked right and was numerically wrong: what was wrong, how you caught it, what check you added.
4. Which systems have you personally pulled data from — CTRM/ETRM, ERP or accounting, invoice and settlement data, bank statements, terminal systems, price feeds? Pick one and tell us something about its data that only someone who has used it would know.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Location not supplied.
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.
We couldn’t identify enough role detail in this saved description to support an AI answer. Read the full posting