become part of a global team of over 50,000 planners, designers, engineers, scientists, digital innovators, program and construction... ...Structural Engineer with experience in hyperscale and colocation data center faci…
Engineering & IT · Kansas City, MO
Data Engineer jobs in Kansas City, MO
Data engineers build the pipelines and warehouses that move data from source systems to the people and models that need it, keeping it fresh, correct, and queryable at scale.
92
Open roles today
$35–$88/hr
Typical pay range
$121k
Median, full-time
2
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 engineer roles
5 shown of 92 · sorted by freshness
satisfaction. We compete on results. THE POSITION The Clinical Analytics Engineer designs, maintains, and improves analytic pipelines, dashboards,... ...decision-making. This role works across R and Python-based data wor…
$55 - $65 per hour
Overview Essmann, a specialist in high-quality custom cabinetry, furniture, and millwork, is seeking a meticulous and insightful Data Analyst to join our team. With a strong reputation for quality craftsmanship and tailo…
everything we do. Who are we? Techwave is a leading global IT and engineering services and solutions company revolutionizing digital... ...'s possible. And we want YOU to be a part of it. Role: Data Analyst Experience: 5…
$50 - $60 per hour
commercial clients, offering innovative solutions to combat indoor and outdoor air pollution. We are seeking a skilled and motivated Data Engineer to join our team and build the data infrastructure that powers our enviro…
02
What data engineers earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $35–$49 | $73k–$102k |
| Mid level | $49–$68 | $102k–$141k |
| Senior | $65–$88 | $136k–$183k |
Adjusted for the Kansas City market from national ranges.
03
What employers ask for
The skills these listings keep naming
SQL and data modelingPython or ScalaAirflow or similar orchestrationSpark or other batch processingWarehouses (Snowflake, BigQuery)dbtStreaming (Kafka)Data quality testingCloud infrastructure
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Design a pipeline that loads data from a production database into a warehouse daily.
Cover extraction strategy, incremental loads versus full refresh, idempotency, and monitoring. Saying how you would backfill after a failure shows real pipeline experience.
How do you handle late-arriving or duplicate data?
Discuss idempotent upserts, watermarks, and dedup keys. This is a daily reality of the job, so a concrete example lands well.
Batch or streaming — how do you decide?
Anchor on the actual freshness requirement and cost. Most 'real-time' asks are fine at minutes; recognizing that is the mature answer.
A stakeholder says the numbers in their dashboard are wrong. Walk me through your debugging.
Trace lineage from the dashboard back to the source, isolating which layer diverged. Showing calm, structured lineage-tracing is the point of the question.
How do you model data for analytics — star schema, wide tables, something else?
Show you know the classic patterns and modern warehouse economics, and that you choose based on query patterns and team skill, not doctrine.
How do you test data pipelines?
Talk about schema and freshness checks, row-count and distribution tests, and tools like dbt tests or Great Expectations — plus alerting when they fail.
Tell me about a pipeline that failed badly and what you changed.
Structure it like an incident review: impact, cause, fix, prevention. Emphasize the durable improvement, such as monitoring or contract enforcement.
05
Resume tips that move the needle
For data engineers specifically — generic advice costs you here
01
State data scale plainly — rows per day, terabytes managed, pipeline counts — because it is the first thing hiring managers scan for.
02
Name your orchestration, processing, and warehouse tools per role; the modern stack (Airflow, dbt, Snowflake) is a keyword screen.
03
Highlight reliability outcomes: pipeline failure rates, data freshness SLAs met, incident reductions.
04
Show cost work if you have it — warehouse spend is a live concern and optimization stories differentiate.
05
Mention who consumed your data (analysts, ML teams, executives) to show you build for users, not just movement.
06
Where this role goes
Typical progression
01
Junior Data Engineer
02
Data Engineer
03
Senior Data Engineer
04
Staff Data Engineer
05
Data Platform Lead
Ten quiet minutes a day
Applying for data engineer 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.