Salary: $100,000 - 110,000 per year Requirements: We need 3–8 years of professional software engineering experience. We need strong Java development skills grounded in object-oriented programming principles. We need hand…
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.
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 512 · sorted by freshness
the world forward. Built on Lucid’s proprietary technology and software- defined vehicle architecture, our award-winning vehicles bring... ...to choose between performance and sustainability, design and engineering, ambi…
infrastructure. As the digital infrastructure platform within Consor Engineers, a leading North American engineering and advisory firm,... ...Overview We are looking for a versatile generalist Senior Software Engineer, f…
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…
Description As a Full-stack Software Engineer you will support our client's global mobile app deployment ecosystem by helping Android, iOS, Mac, and Chrome app development teams build, test, and deploy applications more…
Description DUTIES : Develops software tools and supports validation of API's using sound, repeatable, industry standard methodologies... ...: Bachelor’s degree in Computer Science, Computer Engineering, Electrical Engin…
Hybrid: This role is categorized as Hybrid/Remote. MI & CA Role: As a Software Engineer on the Software Validation team within the AV organization, you will play a critical role in the development of methods, tools and p…
Robot Software Engineer Posted on 07/28/2026 Location Greater Detroit Description ?? Robot Software Engineer (ROS2 / C++) ?? Wixom, MI | On-Site (Must currently live within commuting distance) Are you passionate about ro…
Role Information: Job Title: Software Engineer Work Location: Fully remote position, home office Employment Type: Full-time Employment Status: Exempt, salaried Visa sponsorship is not available for this position. Must re…
Job Description Job Description Overview We are looking for a skilled Software Engineer to design and deliver scalable, cloud-native microservices within our Connected Services platform. You will own the full software li…
information systems by designing, developing, and installing software solutions. Key Responsibilities: Determines operational... ...and summarizing development and service issues. Accomplishes engineering and organizatio…
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…
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.
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 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.