Kforce has an enterprise client seeking a Software Development Engineer II in Minneapolis, MN. Duties: ~ Build automation tools for Warehouses that help associates with how, where, and what to work ~ Basic solutions on t…
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.
665
Open roles today
$37–$98/hr
Typical pay range
$130k
Median, full-time
2
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 665 · sorted by freshness
$96.3k - $154.4k
regarding any recruiting communications or Kapitus' recruiting process in general should email ****@*****.*** As an AWS Software Engineer II at Kapitus, you will play a pivotal role in driving impactful solutions for int…
$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…
$95k - $125k
Job Description Job Description Salary: $95,000 - $125,000 Role: Software Development Engineer (SDE) II Job Type:Full-time Years of Experience:2+ Work Arrangement:On-site, in-office (this is not a remote or hybrid positi…
$50 - $70 per hour
Job Description Job Description Job Title: Sr Embedded Software Engineer The Embedded Software Engineer will lead firmware design, implementation, and testing across the full product lifecycle. This role owns firmware ar…
technology staff as well as Digital Transformation Services for all American Corporations. We are currently seeking a Sr. MDM Software Engineer for our client in the Financial Services domain. We value our professionals,…
$90k - $120k
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…
the-art IPG lasers into turn-key systems to be used in the semiconductor, medical and other industries. We are seeking a Senior Software Engineer to join the Material Processing Systems Group in the development of advanc…
Software Engineer Richfield, MN 55423 (Hybrid 2 Days/Week) 12+ Months Contract Position Summary/Job Description: We are looking for a Software Engineer to help plan and execute major platform features and capabilities. I…
$85k - $130k
proactivity and always bringing the outside, future focused perspective to our clients. Position Summary: We are looking for a Software Engineer, Data to join our growing technology team. This is a hands-on, data-focused…
$97.5k - $150.6k
backend services and APIs using Azure, AWS, or GCP to support software distribution, secure access, diagnostics, telemetry-adjacent workflows... ...architecture, structured programming fundamentals, and robust engineerin…
$117k - $158k
on the SmartThings Hub platform, ensuring a seamless, interoperable ecosystem for millions of users worldwide. As a Senior Software Engineer, you will lead the design and execution of the full software lifecycle, moving…
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.