Engineering & IT · Kansas City, MO

Data Scientist jobs in Kansas City, MO

Data scientists turn raw data into decisions and products, using statistics, experimentation, and machine learning to answer questions the business could not otherwise settle.

821
Open roles today
$36–$90/hr
Typical pay range
$122k
Median, full-time
4
Fresh in this list

No email, no resume, no sign-up. Save any listing below and you start anonymously.

You're signed in. Saving a listing drops it straight into your pipeline.

01

Open data scientist roles

4 shown of 821 · sorted by freshness

Data Engineer - Business Intelligence (Remote)

hal1009hlli · Kansas City, MO · Full-time

Help shape how Hallmark uses data to make better decisions. As a BI Engineer, you’ll transform complex enterprise data into trusted, accessible analytics. Using Power BI, Microsoft Fabric, Snowflake, SQL, and AI-assisted…

Posted 2d ago
+ Save to tracker View listing

Senior Data Center Engineer - Kansas City

DigitalOcean · Kansas City, MO
$106k - $130k

while learning, having fun, and making a profound difference for the dreamers and builders in the world. We are looking for a Senior Data Center Engineer who is passionate about building and scaling reliable data center…

Posted 4d ago
+ Save to tracker View listing

Forward Deployed Data Engineer

tenex · Kansas City, MO · Full-time

embody it, prioritizing the irreplaceable collaboration and community of in-person work. About the Role As a Forward Deployed Data Engineer — SIEM/SOAR, you build the content that powers TENEX's MDR delivery. From detect…

Posted 1w ago
+ Save to tracker View listing

Senior Director, Data Center Engineering

lightedge · Kansas City, MO · Full-time

then LightEdge can offer you a dynamic corporate environment built on teamwork and personal responsibility. The Senior Director, Data Center Engineering serves as the senior technical authority for the company’s data cen…

Posted 1w ago
+ Save to tracker View listing
02

What data scientists earn in Kansas City

Hourly first — that's how the offer arrives

ExperienceHourlyAnnual, full-time
Entry level $36–$50 $75k–$103k
Mid level $50–$68 $103k–$141k
Senior $65–$90 $136k–$188k

Adjusted for the Kansas City market from national ranges.

03

What employers ask for

The skills these listings keep naming

Python (pandas, scikit-learn)SQLStatistics and A/B testingMachine learning fundamentalsData visualizationExperiment designCommunicating with stakeholdersDomain and product sense
04

Interview questions worth rehearsing

With the thing the interviewer is actually listening for

Walk me through a data project that changed a decision.

Structure it as question, approach, finding, action. Projects that ended in a decision — even 'we did not launch' — beat technically impressive analyses that went nowhere.

How would you design an A/B test for a new feature?

Cover the metric, randomization unit, sample size, and duration, plus a pitfall like peeking or interference. Practical rigor is what is being tested.

Your model performs well offline but poorly in production. Why might that be?

Discuss train/serve skew, data leakage, distribution shift, and feedback loops. Listing several plausible causes and how you would check each is the strong answer.

Explain p-values or confidence intervals to a non-technical stakeholder.

Use plain language and a concrete scenario, and resist overstating certainty. They are testing whether your statistics survive translation.

How do you handle missing or messy data?

First ask why it is missing — the mechanism matters more than the imputation method. Then discuss options and how the choice affects conclusions.

When would you not use machine learning for a problem?

When a rule, a query, or a simple heuristic wins on cost and interpretability. Knowing when ML is overkill signals maturity.

How do you decide which metric a team should optimize?

Talk about proxy versus true goals, gameability, and counter-metrics. A story about a metric that backfired is very effective here.

05

Resume tips that move the needle

For data scientists specifically — generic advice costs you here

01

Lead every bullet with the business result — revenue, retention, cost — and put the method second.

02

Specify your stack concretely: Python libraries, SQL dialects, experimentation platforms, and any production ML experience.

03

Distinguish shipped work from research; 'model serving 2M users' and 'notebook analysis' are different claims.

04

Keep one or two public projects or publications linkable, tailored to the industry you are targeting.

05

Name the size and kind of data you worked with — event streams, tabular, text — so teams can map you to their problems.

06

Where this role goes

Typical progression

01 Junior Data Scientist
02 Data Scientist
03 Senior Data Scientist
04 Staff Data Scientist
05 Head of Data Science
Ten quiet minutes a day

Applying for data scientist jobs in Kansas City?

Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.

Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.

Start with this search No email, no resume, no sign-up. Open your tracker Everything you saved is already there.
821 Data Scientist roles in Kansas City Save them into one pipeline Save them into your pipeline
Start free My tracker