$99.6k - $166.6k
pursue their dreams. At Ford, you can build more than vehicles. Come build what matters.In this position... The ADAS Software Update Systems Engineer owns the system design, specification, and analysis of software update…
Engineering & IT · Detroit, MI
Software Engineer jobs in Detroit, MI
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.
299
Open roles today
$34–$89/hr
Typical pay range
$119k
Median, full-time
10
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 299 · sorted by freshness
and in how we will influence the future of transportation. Our Software Services team is on the forefront of this work, emboldening... ...move us forward and achieve our mission. The RoleAs a Software Engineering - Site…
successful candidate is expected to report to Austin, TX or Warren, MI three times per week, at minimum.The RoleAs a Mobile Senior Software Engineer, your focus will be on creating cutting-edge mobile applications that p…
responsible for designing, developing, testing and maintaining software applications and products to meet customer needs. They are... ...the software to meet customer requirements. Full-stack software engineering roles,…
Job DescriptionThe Role: General Motors is seeking a software engineering leader to modernize and scale the build systems that support software-defined vehicles. This role will help lead the transition from a legacy Make…
$238.7k - $365.7k
Job DescriptionThe RoleGeneral Motors is seeking a Principal Software Engineer to shape and scale the engineering platforms that build, test, integrate, validate, and deliver embedded software for software-defined vehicl…
Job-ID33138808Reference26-03193Job Title: (Cloud Engineering Engineer 2)About Kyyba:Founded in 1998 and headquartered in Farmington Hills... ...artifacts, manufacturing evidence, service data, and software lifecycle sign…
$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…
seeking a technically strong and highly motivated Design Release Engineer (DRE) to lead the development and launch of external microphone... ..., Acoustics, Systems Engineering, Electrical Engineering, Software, Controls…
hardware and battery systems to intuitive design, intelligent software, and next-generation safety and entertainment features. Every day... ...components or subsystems.This position is a strong fit for an engineer seekin…
$140k - $200k
a real codebase. We aim to finish within a week. The assessment runs in two stages: you'll submit, get real feedback from an engineer on this team, and have time to act on it. Use the tools you use every day. You'll be a…
$140k - $200k
people around the globe work on Speechify in a 100% distributed setting – Speechify has no office. These include frontend and backend engineers, AI research scientists, and others from Amazon, Microsoft, and Google, lead…
02
What software engineers earn in Detroit
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $34–$47 | $70k–$98k |
| Mid level | $47–$67 | $98k–$140k |
| Senior | $65–$89 | $135k–$186k |
Adjusted for the Detroit 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 Detroit?
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.