Tidewater Networks, an e-commerce platform based in Minneapolis, MN, is hiring a Data Engineer. You will build the pipelines and models that turn raw data into answers the whole company trusts. This is a hybrid role, wit…
Data Scientist jobs in Minneapolis, MN
Data scientists turn raw data into decisions and products, using statistics, experimentation, and machine learning to answer questions the business could not otherwise settle.
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 scientist roles
11 shown of 1,403 · sorted by freshness
Architect to join our thriving Technology and Experience Practice. This is an excellent opportunity to work with clients developing Big Data strategy and roadmaps, while gaining exposure to a variety of industries includ…
Are you ready to make an impact? West Monroe is seeking a Senior Data Engineer to join our Data & AI practice. In this role, you will design, build, and optimize modern cloud data platforms that enable advanced analytics…
We are looking for professionals with strong expertise in Data Science, Experimentation, Python, SQL/BigQuery, Design of Experiments... .... Section Details Job Title Data Scientist Job Type Contract Client Location...
colleagues and communities thrive in an ever-changing world. For additional information visit us at . Job Description Role: DataBricks Data Engineer Location: Minneapolis MN (3 Days onsite/week) Job Summary: The Azure Da…
Role: Ovatives client delivery team gets clients live on EMRge and keeps their experience strong after launch. Were hiring a Lead Data & Software Engineer to be the teams technical leader. You set the technical strategy…
partner with our customers to consistently provide a successful working relationship as a high-performance team. We are adding Data Engineers to influence the direction of data modernization for our customers. We are loo…
and related frameworks to ensure smooth adoption new applications and minimize transition risks." Mandatory Skills: DataBricks - Data Engineering . Experience: 5-8 Years . The expected compensation for this role ranges f…
Thursday, work onsite with your colleagues. Fridays, choose your work location, balancing what your work requires. We are looking for a Data Developer with deep, hands-on Azure data expertise to own and evolve the data f…
As a Data Engineer II here at Honeywell Aerospace, you will play an essential role in developing and refining data pipelines that facilitate the accurate and efficient flow of information across various systems. Your eff…
Snowflake Sr. Data/ AI Engineer Position Description This position is based in our CGI Minneapolis office and is a billable, client-facing consulting role. CGI is looking for an experienced Senior Snowflake Data and AI E…
What data scientists earn in Minneapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $39–$54 | $82k–$112k |
| Mid level | $54–$74 | $112k–$153k |
| Senior | $71–$98 | $148k–$204k |
Adjusted for the Minneapolis 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
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.
Resume tips that move the needle
For data scientists specifically — generic advice costs you here
Lead every bullet with the business result — revenue, retention, cost — and put the method second.
Specify your stack concretely: Python libraries, SQL dialects, experimentation platforms, and any production ML experience.
Distinguish shipped work from research; 'model serving 2M users' and 'notebook analysis' are different claims.
Keep one or two public projects or publications linkable, tailored to the industry you are targeting.
Name the size and kind of data you worked with — event streams, tabular, text — so teams can map you to their problems.
Where this role goes
Typical progression
Applying for data scientist 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.