and giving our consultants room to grow, lead, and build. The Role We are looking for a technically skilled and motivated Data Engineer with 7-12 years of experience to join our growing Data & Analytics team. In this rol…
Engineering & IT · Minneapolis, MN
Data Engineer jobs in Minneapolis, MN
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.
290
Open roles today
$38–$96/hr
Typical pay range
$132k
Median, full-time
5
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
12 shown of 290 · sorted by freshness
DataDrive, Minnesota-based, is seeking an Analytics Engineer to own and evolve the full analytics stack. You will build pipelines, transform data into reliable models, and develop Tableau dashboards for client delivery.…
$87.05k - $130.57k
As a Data Engineer, you will have the unique opportunity to design and establish a modern data engineering function within our organization. You will take the lead in building the data infrastructure that enables analyti…
Kforce has a client in Minneapolis, MN that is seeking a hybrid Mid-Level Data Engineer to join their team. Summary: The client is looking for a Mid-Level Data Engineer that can hit the ground running with a growing team…
Job Description Job Description Senior Data Engineer – Microsoft Fabric & Power BI Location: Vadnais Heights, MN - Hybrid What is IP Corporation? IP Corporation is a privately held, family-owned chemical manufacturing or…
collaboration.ai. About the Role You'll build the agentic systems and data pipelines behind NetworkOS's AI capabilities: production agent... ...so every workflow has measurable quality, cost, and latency Engineer data pi…
Job Title: Senior Data Engineer Location Remote, but interviews or laptop pickup must occur at one of the following locations: San Francisco, Arlington, VA, Denver, CO, Atlanta, GA, Chicago, Boston, NYC, Houston, Miami,…
~ You can't wait to get out of bed in the morning & get on with your day Overview We're looking for a Senior Data Platform Engineer to lead the design, implementation, and evolution of our data platform infrastructure. Y…
Data Engineer Richfield, MN 55423 (Local - Hybrid 2 Days/Week) 12+ Months Contract Project Description: You will be part of the Myads reporting team responsible for building the measurement, reporting, and insights platf…
$85k - $130k
and always bringing the outside, future focused perspective to our clients. Position Summary: We are looking for a Software Engineer, Data to join our growing technology team. This is a hands-on, data-focused engineering…
About the Role Does the idea of playing a significant role in data platform operations oversight, content expertise, and structure... ...your name written all over it! We are seeking a Data Operations Engineer to join ou…
$72k - $134k
*Securian Financial Groups internal position title is Data Engineering Sr Analyst. Position Summary: Securian Financial is looking for a curious and motivated Data Engineer who’s excited to use data and technology to sol…
02
What data engineers earn in Minneapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $38–$53 | $80k–$110k |
| Mid level | $53–$74 | $110k–$153k |
| Senior | $71–$96 | $148k–$199k |
Adjusted for the Minneapolis 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 Minneapolis?
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.