help over 40 million people every month, with a team that genuinely cares about the work and each other. AT A GLANCE The Software Engineer is a crucial role within our organization, requiring work in various capacities a…
Software Engineer jobs in Minneapolis, MN
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 913 · sorted by freshness
Pinemarten Networks, a cybersecurity company based in Minneapolis, MN, is hiring an Entry-Level Software Engineer (2 openings). This is a great first software job. You will learn from experienced engineers and ship real…
Cobaltwave Networks, a Salesforce consulting firm based in Minneapolis, MN, is hiring a Software Engineer (3 openings). You will ship features end to end, from the database to the browser, with a small and friendly team.…
Sagebrush Apps, a real estate technology company based in Minneapolis, MN, is hiring a Software Engineer in Test (2 openings). You will help us ship with confidence by building strong automated tests. This is a hybrid ro…
Accurant International Location: Minneapolis, MN (Hybrid) Status: Exempt Salary: $90,000-$120,000 Job Title: Senior Software Engineer Position Description The Senior Software Engineer is responsible for design and develo…
is important to maintain our strong culture, achieve our goals, and thrive as #OneJamf. What you'll do at Jamf: The Software Engineer II is responsible for building the tools required to help organizations succeed with A…
financial institutions. Were looking for people who want more than just a job they want to make a difference! U.S. Bank is seeking a Software Engineer who will contribute toward the success of our technology initiatives…
management network is governed and hardening the environment engineers use to reach devices. Key job responsibilities * Own major... ...its fast and safe. - 4 years of non-internship professional software development exp…
providing innovative healthcare and life science product and service solutions around the globe. Position Summary The Senior Software Engineer will be responsible for the design documentation development and testing of n…
as a series of building blocks to be combined at the speed of software, limited by only the hard constraints of physics and the soft... ...manual testing of new and existing feature sets Work with engineers to define and…
as a series of building blocks to be combined at the speed of software, limited by only the hard constraints of physics and the soft... ...and robustness. Collaborate cross-functionally with other engineering teams to de…
Title : Senior Software Engineer - AI Platforms Location : Minneapolis, MN (Hybrid) Job Type : Contract (6 Months) Compensation : $85 – 100/hr Industry: Manufacturing --- About the Role Our firm is partnering with a glob…
What software engineers earn in Minneapolis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $37–$51 | $76k–$107k |
| Mid level | $51–$74 | $107k–$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 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 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.