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…
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.
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.
Open data engineer roles
6 shown of 162 · sorted by freshness
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 infras…
experience building automated workflows and low-code solutions using Power Automate and Power Apps including multi-stage approvals data integration with SharePoint and error handling is a plus. Data Governance: Prior exp…
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 detection rul…
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 center d…
GPU. If you'd like to build the world's best AI cloud, join us. *Note: This position requires presence in our Kansas City, MO Data Center 5 days a week; shift work What You'll Do Ensure new server, storage and network in…
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.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For data engineers specifically — generic advice costs you here
State data scale plainly — rows per day, terabytes managed, pipeline counts — because it is the first thing hiring managers scan for.
Name your orchestration, processing, and warehouse tools per role; the modern stack (Airflow, dbt, Snowflake) is a keyword screen.
Highlight reliability outcomes: pipeline failure rates, data freshness SLAs met, incident reductions.
Show cost work if you have it — warehouse spend is a live concern and optimization stories differentiate.
Mention who consumed your data (analysts, ML teams, executives) to show you build for users, not just movement.
Where this role goes
Typical progression
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.