$68.88k - $133.34k
world a better place. Join our team today and start building your career with a worldwide leader. Job Information The Software Engineer is responsible for designing, developing, and optimizing scalable, reliable full-sta…
Engineering & IT · Minneapolis, MN
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.
518
Open roles today
$37–$98/hr
Typical pay range
$130k
Median, full-time
11
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 software engineer roles
12 shown of 518 · sorted by freshness
writing test automation) and/or standard developer. Looking for strong core engineering skills.Can you please confirm your top 3 skills sets required?Experience in development and verification of software products, in an…
$111.61k - $131.3k
maintainability.Collaborate with business, product, operations, and engineering teams to deliver high-quality solutions using Agile and Scrum... ...relevant experiencePreferred Skills & Experience8+ years of software eng…
$167k - $203k
Who You’ll Work WithAs a Genesys Consultant or Senior Consultant on Slalom's Contact Center Modernization team, you will design, configure, and deliver Genesys Cloud CX solutions for enterprise clients. You will be a han…
$120k - $155k
location. Work Arrangement: Remote A Day in the Life The Cloud Senior Engineer is responsible for supporting complex engineering initiatives... ..., or a related field required.4+ years of experience in software engineer…
and services that improve everyday life while supporting businesses, communities, and economies worldwide. Position: Software Dev Engineer II Location: Minneapolis,MN Duration: 6 Months Job Type: Temporary Assignment Wor…
$115k - $225k
remaining days of the week.ABOUT THE TEAMThe Core Platform and AI Engineering team at Parametric is responsible for enhancing the quality... ...for supporting their success.ABOUT THE ROLEThe Principal Software Engineer,…
$122.4k - $183.6k
growth and cross-functional collaboration as we work together to engineer the extraordinary. The person in this role will work from the... ...Medtronic facility located in Mounds View, Minnesota. As a Senior Software Dev…
$149.51k - $176.1k
things, learn new skills and discover what you excel at—all from Day One.Job DescriptionU.S. Bank is seeking a full-time Senior Software Engineer (Multiple openings) in Hopkins, MN.Essential Responsibilities:Design, deve…
$110.7k - $218.3k
Position Summary Salesforce Life Sciences Cloud Senior ConsultantDeloitte's Sales & Service practice partners with the world's leading life sciences companies to reimagine how their commercial, medical, and field organiz…
$116.2k - $229.1k
Position Summary AI & Engineering/ EaaS - DevOps Engineer IIIBuild and scale modern DevOps capabilities that help clients accelerate... ...and operational improvement to help organizations strengthen software delivery pe…
$87.69k - $107.18k
Title : Software Engineer | Level II Location : Minneapolis, MN Job Type : Permanent/ Direct-Hire Compensation : $87,691 - $107,177 Annually Industry: Manufacturing --- About the Role Our client, a global leader in the m…
02
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.
03
What employers ask for
The skills these listings keep naming
Data structures and algorithmsSystem designGit and code reviewTesting and debuggingSQL and databasesAPIs and integrationCloud fundamentals (AWS/GCP/Azure)Clear written communicationCross-team collaboration
04
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.
05
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
01
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
02
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
03
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
04
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
05
Keep the tech list honest; anything on the resume is fair game in the interview.
06
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
06
Where this role goes
Typical progression
01
Junior Software Engineer
02
Software Engineer
03
Senior Software Engineer
04
Staff Engineer
05
Principal Engineer
Ten quiet minutes a day
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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.