Job Posting Autopsy — T-Mobile Senior Data Scientist | Brian Curry

Series: Weekly Data Science Job Posting Review Company: T-Mobile | Posted Title: Senior Data Scientist | Diagnosed Title: Senior ML Engineer / Applied Scientist (Hybrid)

Overview

T-Mobile is hiring a “Senior Data Scientist” at a base range of $106,000–$191,100. The posting describes a role that spans the full data science lifecycle — from problem framing through production deployment — and asks for collaboration with engineering on ML pipelines, big data architecture experience, and deep learning expertise.

On paper, this is a data science role. In practice, the responsibilities and required skills tell a different story.

1. Role Identity Test

I mapped each stated responsibility and required skill to one of four standard role archetypes: Data Scientist (DS), ML Engineer (MLE), Data Engineer (DE), and Data Analyst (DA). The breakdown:

Predictive modeling and statistical techniques → Data Scientist. Core DS activity.
Deploying and improving models in production → ML Engineer. Production deployment is engineering.
ML pipelines and production-ready models → ML Engineer. Pipeline work is infrastructure.
Big data architecture — Hadoop, Hive, Spark, Kafka → Data Engineer. This is data engineering tooling.
Deep learning model development → ML Engineer / Applied ML. Specialized engineering.
Business translation and actionable recommendations → Data Scientist. Stakeholder-facing analysis.
Data visualization and communication → Data Analyst / DS. Reporting and storytelling.
Mentorship, code review, best practices → Senior (role-agnostic). Leadership function.

Estimated role composition:

Data Scientist: ~35%
ML Engineer: ~30%
Data Engineer: ~15%
Data Analyst / Leadership: ~20%

Diagnosis: This is a hybrid role. Roughly one-third of the job is actual data science (hypothesis testing, statistical modeling, business translation). Another third is ML engineering (production deployment, pipeline work, deep learning). The remainder is split between data engineering infrastructure and senior leadership duties. The title “Senior Data Scientist” undersells the engineering expectations and oversells the analytical focus.

2. Skill Breadth Score

The posting lists 11 distinct technical skill areas as required or preferred:

Predictive modeling
Deep learning
Python
R
SQL
Hadoop
Hive
Spark
Kafka
Data visualization
Mathematics (calculus, linear algebra, statistics, probability)

Benchmark: A focused senior data scientist role typically requires 5–8 core skills. This posting lists 11, spanning three distinct technical domains (statistical modeling, ML engineering, and distributed systems). A candidate who is genuinely strong across all of these is not a data scientist — they’re a full-stack ML practitioner, and they command compensation well above the top of this range.

Breadth score: 11/8 — exceeds focused-role threshold by 37%.

3. Red Flag Inventory

Flag 1: Title–Responsibility Mismatch — CONFIRMED

The posting itself reveals the mismatch. In the Knowledge, Skills and Abilities section, the first line reads:

“4–7 years Proven experience in predictive modeling, data science, and analysis in an ML engineer or data scientist role building and deploying ML models”

T-Mobile knows this role straddles two job families. They named it “Data Scientist” anyway. This matters because it affects who applies. Experienced ML engineers scanning for “ML Engineer” titles will skip this listing. Data scientists who apply expecting analytical work will encounter significant production engineering responsibilities they didn’t sign up for.

Flag 2: Unicorn Posting — CONFIRMED

The posting requires simultaneous expertise in statistical modeling, deep learning, big data architecture (Hadoop/Spark/Kafka), production ML deployment, data visualization, and executive communication. Each of these is a specialization that takes years to develop. Requiring all of them in a single candidate at 4–7 years of experience suggests the team is understaffed and looking for one hire to cover gaps across multiple functions.

Flag 3: Data Engineering Disguised as Data Science — CONFIRMED

The requirement for 2–4 years of experience with “big data architecture and pipeline, Hadoop, Hive, Spark, Kafka” is not a data science requirement. It’s a data engineering requirement. A data scientist should be able to use Spark for large-scale analysis. Requiring architectural experience with Kafka and Hadoop suggests the hire will be responsible for building or maintaining data infrastructure — work that belongs to a separate role with separate expertise.

Flag 4: Missing Core Data Science Activities — CONFIRMED

The posting makes no mention of:

Experimentation design or A/B testing
Causal inference
Hypothesis testing methodology
Research or literature review
Stakeholder discovery or problem scoping methodology

These are defining activities of senior data science work. Their absence, combined with the heavy emphasis on production ML and pipeline work, reinforces the diagnosis that this is primarily an engineering role wearing a data science title.

Flag 5: Compensation Range Spread — NOTED

The base pay range of $106,000–$191,100 represents an 80% spread from floor to ceiling. Wide ranges are common at large companies with location-based pay bands, but an 80% spread also suggests the role could be filled at significantly different seniority levels — which raises questions about whether the actual scope of work has been clearly defined.

Flag 6: Scope Creep Clause — NOTED

“Also responsible for other duties/projects as assigned by business management as needed” is standard corporate language, but in the context of an already broad role, it signals that the boundary of this job is undefined. For a posting that already spans three technical domains, this is worth flagging.

4. What’s Missing vs. What’s Overrepresented

Present and expected: Statistical modeling and inference, business problem framing, stakeholder communication, mentorship.

Missing entirely: Experimentation / A/B testing, causal inference.

Present but not typically expected in a DS role: Production ML deployment (overweight), big data infrastructure, deep learning, pipeline engineering.

5. Compensation Analysis

Posted range: $106,000–$191,100 base + 15% bonus target

Total compensation estimate: $121,900–$219,765 (base + bonus at target)

Market Benchmarks (2026)

Senior Data Scientist (national):

Glassdoor: $191K–$287K total (25th–75th percentile)
ZipRecruiter: $118K–$167K (25th–75th percentile)
PayScale: $107K–$172K base

Senior ML Engineer (national):

Glassdoor: $169K–$269K total (25th–75th percentile)
PayScale: ~$164K base median

T-Mobile Senior Data Scientist (reported):

Levels.fyi: $110K–$215K total, median ~$164K
Glassdoor: $175K–$240K total estimated

Analysis

The posted base range of $106K–$191K is below the national median for senior data scientist roles on Glassdoor ($232K average total pay) and significantly below the Glassdoor 25th percentile for senior ML engineers ($169K total). When you factor in that this role demands ML engineering, data engineering, and data science expertise simultaneously, the compensation does not match the skill breadth being requested.

However, the range aligns reasonably well with T-Mobile’s own internal comp data. Levels.fyi reports a median total compensation of ~$164K for T-Mobile senior data scientists, and Glassdoor estimates $175K–$240K total. The posted range, plus the 15% bonus target and T-Mobile’s annual stock grants (mentioned in the benefits section), likely lands candidates in the $160K–$220K total comp neighborhood — which is internally consistent but below external market rates for the actual skill set demanded.

The 80% spread between floor ($106K) and ceiling ($191K) is also notable. This typically signals either wide geographic pay bands or that the role could be filled at significantly different experience levels. For context, the posting asks for 4–7 years of experience — a relatively narrow band that doesn’t justify an 80% range spread.

Comp verdict: The pay is competitive for a senior data scientist at a large telecom. It is below market for a senior ML engineer with production deployment, big data architecture, and deep learning experience — which is what the role actually requires. A candidate with the full unicorn profile described in this posting could command $200K–$270K+ total compensation at companies that correctly title and compensate ML engineering roles.

6. The Verdict

What T-Mobile titled this: Senior Data Scientist

What this actually is: A Senior Applied ML Engineer with some analytical responsibilities and significant infrastructure expectations. Approximately 35% of the role maps to data science, 45% maps to ML/data engineering, and 20% is senior leadership work.

Who this role is actually for: A candidate with a strong engineering backbone who can also do statistical analysis — not the other way around. If you’re a data scientist who thrives on experimentation design, causal inference, and deep analytical work, this role will likely frustrate you with its infrastructure and deployment demands. If you’re an ML engineer who enjoys the modeling side and wants to work closer to business stakeholders, this could be a good fit — just know the title won’t accurately reflect your day-to-day.

Bottom line: The posting is not dishonest, but it is mislabeled. T-Mobile appears to need a versatile ML practitioner who can operate across the stack — from data infrastructure to production models to business communication. That’s a legitimate need. But calling it “Data Scientist” misrepresents the work and will attract the wrong candidate pool.

Job Posting Autopsy is a weekly series that applies structured analysis to data science job listings. The goal is not to mock employers but to help candidates make informed decisions — and to push the industry toward more honest role descriptions. Have a posting you’d like reviewed? Drop it in the comments.

Job Posting Autopsy — T-Mobile Senior Data Scientist