Manager of DevOps & Platform Engineering Up to $165,000 Base Salary • Milwaukee, WI Area • Hybrid (3 Days Onsite / 2 Days Remote) Join a global pioneer in industrial machine software and AI automation driving high-veloci…
Software Engineer jobs in Milwaukee, WI
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it grows.
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 software engineer roles
12 shown of 361 · sorted by freshness
Job Description Genesis10 is currently seeking a CI/CD Platform Engineer for a contract position with a Major Financial Services Company... ...to help build and operate a reliable, scalable, and secure software delivery…
businesses and build a more resilient efficient sustainable energy future. Ready to Power a Smarter World with us The Applications Engineer is a technical expert responsible for translating customer and product requireme…
together. We collaborate as a team and celebrate each other’s successes. The Headlines: In the role of Manager, Software Engineering you will be a hands-on, technical expert that will lean in heavily with MCBC’s delivery…
food and dairy industries desalination and various chemical and industrial applications. We are seeking a dedicated Applications Engineer to join our Applied Products team. Under the direction of the AAP Solutions Manage…
learn from mistakes, and rally the team to raise the bar. About This Role: We’re looking for a Technical Lead / Full Stack Engineer to join Novir—someone who can own our technology end-to-end. This is not a pure manageme…
job summary: We are seeking a highly motivated Embedded Software Engineer to join our engineering team focused on developing robust, efficient, and scalable software solutions for embedded controls systems. This role inv…
We are looking for an experienced Platform Engineer / DevOps Engineer to join a team responsible for building, supporting, and improving the cloud infrastructure and engineering platforms used by development teams across…
deliver our clients a competitive edge. Our globally distributed engineering teams focus on adaptable technology and open architecture to... ...Responsibilities: You will work in a fast-paced, financial software developm…
security issues and improve overall security posture.Minimum Qualifications * Bachelor’s degree in computer science, computer engineering, software engineering, information technology, computer information systems, MIS,…
progressing work with minimal day-to-day guidance. Position Summary: We are seeking a self-directed firmware engineer to contribute to embedded software development for MR platforms. The engineer will work across firmwar…
Field Applications Engineer (Fluid Dispensing)Do you want to be part of an organization on the cutting edge of technology?We're looking... ...configurations to be quotedCollects feedback opportunities for hardware and so…
What software engineers earn in Milwaukee
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$48 | $71k–$100k |
| Mid level | $48–$68 | $100k–$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 project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
Applying for software engineer 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.