Sr. Data Scientist
Company websitemarianaminerals.com (Mariana Minerals, opens in new tab)
Base salary $140K to $173K
Employer-published annual base salary, USD. Advertised base range in San Francisco, CA +2 more
You apply on the employer's own site. Six Figure Work does not handle applications.
- LocationSan Francisco, CA +2 more
- WorkplaceOn-site
- Status at last checkSource accepting applications when checked
- Last checked (2 h ago) · observed since
All places named
- San Francisco, CA
- Houston, TX
- Ann Arbor, MI
About this job
About Mariana Minerals
Mariana Minerals is a software-first, vertically integrated minerals company on a mission to supply the critical minerals powering modern energy, AI, and defense technologies. We’re reimagining the minerals supply chain by combining deep industry expertise with advanced software, automation, and data-driven decision-making.
The Role
We're hiring a Senior Data Scientist to be the person who makes those numbers trustworthy and legible. You'll own
Mariana Minerals ie statistics: how we measure recovery and throughput, how we know a process change actually worked, how much of a swing is signal and how much is assay noise, and what the reporting layer says when an operator or an executive opens it.
This is not an ML modeling role and not a data engineering role. Our MLEs build the models and our data engineers move the data. You bring statistical rigor and clear reporting to a company generating more data than it currently knows how to interpret, and you make sure the conclusions people draw from it are the right ones.
What You'll Do
Design and analyze plant trials and experiments — DOE, sample sizing, control selection, and the analysis that says whether a process change did what it was supposed to do and at what confidence.
Own the definitions of the metrics the business runs on: recovery, grade, throughput, yield, uptime, unit cost. Decide what each one means, make the definition consistent across teams, and defend it when someone wants to compute it differently.
Build and own the reporting and analytics layer — the recurring reporting, the dashboards, and the self-serve tooling that lets operators, engineers, and business leads answer their own questions.
Quantify uncertainty honestly: sampling error, assay variability, instrument drift, measurement system analysis.
Apply statistical process control and capability analysis to plant operations — know when a process has actually shifted versus when it's a normal excursion.
Run the deep-dive analyses that don't have a home: why last month's recovery dropped, what's driving cost variance, which of these three suppliers is actually better, whether this correlation is real.
Do forecasting and estimation for production, cost, and capacity planning — applied statistics that informs commitments, not research models.
Partner with the Technical Product Manager for Data & Analytics Platform on what the reporting and analytics stack needs next, and be a demanding internal customer of the data platform when the data isn't fit for purpose.
Raise the analytical bar across the company: review other people's analyses, catch the flawed comparison before it reaches a decision meeting, and teach the teams around you enough statistics to stop making the same mistake twice.
Write findings up so they're actually used — a clear memo a non-statistician can act on, not a notebook that needs you in the room.
How You'll Operate
Rigor with a deadline: You know the difference between the analysis worth another week and the one that's good enough to decide on today, and you say which is which.
Skeptical by default: You ask how the data was collected before you analyze it, and you're the person who notices the sensor was miscalibrated for three weeks.
Structure from ambiguity: Turn a vague business question into a well-posed statistical one, get the data you need, and own the answer end to end.
Explicit about confidence: Communicate uncertainty in a way that helps people decide, rather than hedging so heavily the analysis becomes useless.
Ecosystem fluency: Understand where your data comes from, what the models and simulators downstream do with it, and where the reporting layer sits relative to the platform underneath it.
What We're Looking For
Must have
3–6+ years in data science, statistics, analytics, or a quantitative research role where you owned analyses that drove real decisions
Deep applied statistics: experimental design, hypothesis testing, regression, uncertainty quantification — and the judgment to know which tool fits the question and which assumption you just violated
Strong SQL and Python (pandas, statsmodels, scipy) — enough to get your own data, run your own analysis, and produce your own reporting without waiting on someone else
Track record building reporting and dashboards people actually use, with the product sense to know what belongs on a dashboard versus in a memo
Ability to work with messy, real-world measurement data — missing values, inconsistent sampling, instrument error — and be clear about what it can and can't support
Exceptional written communication; much of this job is making a technical finding land with operators, engineers, and executives
Comfort being the statistical authority in the room
Nice to have
Background in mining, metallurgy, chemicals, energy, manufacturing, or other heavy industry — especially metallurgical accounting, mass balance reconciliation, or sampling theory
Experience with statistical process control, or measurement system analysis
Experience with BI and analytics tooling (Hex, Looker, or embedded analytics) and an opinion about how to deploy them
Degree in statistics, chemical engineering, chemistry, operations research, economics, or a related quantitative field
Experience building an analytics function at a company where one didn't exist yet
Working fluency with LLM-assisted analysis and where it genuinely speeds up analytical work versus where it quietly introduces errors
Why This Role
Most senior data scientist roles are one of two things: a modeling role wearing an analytics title, or a dashboard-request queue. This is neither. You own how a physical, capital-intensive business measures itself, at the moment those measurements move from spreadsheets and tribal knowledge into something supported and shared. At Mariana, you don't need to validate product-market fit, because we are the market: if you find something real in the data, the people who can act on it are down the hall.
Our culture is built on four principles:
Everyone Gets Home Safe. We never put speed or cost ahead of people.
Extreme Ownership. We take full responsibility for outcomes, relentlessly driving toward solutions.
Engineer Out Requirements, then Automate. We simplify, optimize, and then automate for scale.
Share Your Legos. We collaborate openly, share knowledge, and empower each other to build bigger, better solutions.
Join us as we build the future of responsible mineral sourcing and supply!
Source: Mariana Minerals on Ashby · View original posting (opens in new tab)
Pay in context
This role's base floor ($140,000) is above 17% of the 4,273 Software Engineering roles in California listed on this site; 100 others list the same floor. Their median floor is $176,362; the middle half runs from $149,100 to $204,000.
Only jobs on this site count, and each one publishes a base salary of $100,000 or more, so this compares six-figure jobs with each other, not with the whole market. Computed Nov 6, 2026.
This listingSr. Data Scientist$140K to $173K
Sr./Staff Mechanical Engineer$140K to $175K
Machine Learning Engineer (Autonomy)$140K to $180K
Sr. Software Engineer, Autonomy$140K to $200K
Sr. Software Engineer, Infrastructure$140K to $200K
Mine Planner$140K to $175K
Staff Mechanical Engineer$140K to $190K
Chart as a table
| Role | Published base |
|---|---|
| Sr. Data Scientist (this listing) | $140K - $173K |
| Sr./Staff Mechanical Engineer | $140K - $175K |
| Machine Learning Engineer (Autonomy) | $140K - $180K |
| Sr. Software Engineer, Autonomy | $140K - $200K |
| Sr. Software Engineer, Infrastructure | $140K - $200K |
| Mine Planner | $140K - $175K |
| Staff Mechanical Engineer | $140K - $190K |
Observed changes
- Began meeting the published-salary criteria
- First observed on the employer's board
- Observed since
- Employer-stated posting date
- 2026-09-23
Where this pay comes from
Location as the employer wrote it: San Francisco HQ • Houston, TX • Ann Arbor, MI
USD 140,000 – 173,000 · 1 YEAR · Salary
- Method
- Structured pay field published by the employer
- Checked
- Rule set
- us-base-v2
The employer's job board publishes this pay as a dedicated data field. We read the field directly; no interpretation was needed.
What we verified
- The pay figures come from the employer's own listing, quoted exactly above.
- The pay is an annual base salary in US dollars with a minimum of at least $100,000.
- The role was publicly listed on the employer's job board when last checked.
We do not verify what the employer will actually offer, whether the employer is still recruiting for the role, or anything beyond what the employer published. Full methodology.
