Phoenix, AZ

Salary
Posted
Jul 7, 2026
Location
Phoenix, AZ
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A data science role centered on building and deploying pricing models — including demand forecasting, price elasticity, and margin optimization — alongside owning the full experimentation lifecycle (A/B and multivariate testing) and applying causal inference methods. The position also involves developing ML pipelines on Databricks, integrating with MLOps tooling, and collaborating with cross-functional teams. Suited to someone with hands-on production ML experience and a strong statistics background.

Mid level · 3+ years · Phoenix-Mesa-Chandler, AZ · Full-time

Must have (10)
Pythonscikit-learnPyTorchpandasSQLDatabricksMLflowAWS, Azure or GCPA/B testingJavaScript
Nice to have (5)
Optimizely, Statsig or GrowthbookSpark or HadoopDocker or KubernetesAmazon RedshiftAmazon SageMaker

“or” means any one of them counts — you don't need all of them.

Posted 2 times — it's one opening, so apply once.

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

Roughly 25 people in the Phoenix-Mesa-Chandler, AZ area plausibly meet what this posting asks for (data scientists). range 15–35

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What gives you an edge
MLflow8%

Rare in this occupation — lead with these, and say what you built with them.

What won't set you apart
Python88%pandas72%SQL72%JavaScript62%scikit-learn58%A/B testing45%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $117,059 (middle half $87,411–$139,716).

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (7)

The degree requirement is nuanced: the JD states a Master's degree as the primary expectation but explicitly accepts a Bachelor's degree with 5+ years of equivalent professional experience as an alternative — the degree requirement is therefore set to None (equivalent experience accepted in lieu).

The overall experience range is stated as '3-5 years' in the requirements block; the overall years minimum is set to 3 (the lower bound). A separate clause mentions '5+ years' only in the context of the Bachelor's-degree substitution path.

JavaScript is listed in the requirements block alongside Python ('Python (plus experience in JavaScript)'), making it a hard gate despite being secondary; it is marked required accordingly.

AWS-specific sub-services (S3, Redshift, SageMaker) appear in the requirements block as illustrative examples within a broader cloud-platform requirement; they are listed separately as preferred since the JD frames them as 'especially … or similar services', indicating the cloud platform itself (AWS or equivalent) is the gate.

Spark and MLflow appear both in the required Databricks context and in the preferred qualifications; Spark is listed as preferred since the JD's required mention is subsumed under the Databricks requirement, and the preferred section calls it out independently as a big-data framework.

Experimentation platform tools (Optimizely, Statsig, GrowthBook) appear only under Preferred Qualifications.

No compensation figures are provided in the posting.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗