Johnson Controls International plc. is an equal employment opportunity and affirmative action employer and all qualified applicants will receive consideration for employment without regard to race color religion sex nati…
Data Scientist jobs in Milwaukee, WI
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 552 · sorted by freshness
Time Off ~ Medical, Dental, and Vision - Eligible f irst day of the month following hire date. JOIN A TOP WORKPLACE - DATA INTEGRATION ENGINEER The Data Integration Engineer is a detail-oriented, systems-minded professio…
and we hire people who actually get it. THE ROLE The future of AI is being built right now — and the humans labeling the data are the ones making it possible. NoGigiddy is hiring Data Annotators to help train the next ge…
Summary The Data Quality Analyst is responsible for maintaining the accuracy integrity and completeness of case management data within the Probation Automated Case Tracking System (PACTS360). The position analyzes databa…
design planning delivery and operation of all AWS global other words were the people who keep the cloud running. We support all AWS data centers and all of the servers storage networking power and cooling equipment that…
product configurations and commercial solutions. This role supports the development configuration launch and lifecycle management of Data Center Generator products while working closely with Engineering Sales Project Man…
real-world solutions, join us and unleash your potential as a change catalyst. Who We’re Looking For We’re excited to add a Data Engineer to our Cloud, Data & AI Solutions Team. In this role, you’ll work with a team of c…
Job Description: The Data Engineer at Northwestern Mutual Life Insurance Company in Milwaukee WI will design and build scalable data pipelines and data models using Big Data technologies. Ingest transform and load struct…
information systems and business processes to develop, publish, and maintain key performance indicators, analytical capabilities, and data products that support our customer care program. You will work closely with the D…
Performance Analyst working in Milwaukee, WI , you will be part of the Supply Chain Digital Enablement Team . You will leverage data, analytics, and technology to develop key performance indicators, reporting capabilitie…
WEC Business Services LLC Job Responsibilities * Establishes and implements appropriate standards and criteria for data security requirements * Design, develop, deploy and manage enterprise data security solutions includ…
What data scientists earn in Milwaukee
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $37–$50 | $76k–$104k |
| Mid level | $50–$68 | $104k–$142k |
| Senior | $66–$91 | $138k–$190k |
Adjusted for the Milwaukee 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 Milwaukee?
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.