building production-grade AI and data-driven applications ~ Strong backend engineering expertise and hands-on experience with advanced... ...is highly preferred Responsibilities: ~ Design and develop Retrieval-Augmented…
Backend Developer jobs in Detroit, MI
Backend developers build the server-side logic, APIs, and data layers that applications run on. The job is designing services that stay correct, fast, and secure as usage 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 backend developer roles
12 shown of 67 · sorted by freshness
experiences, and works with Architecture, iOS and Android Engineering, Backend Engineering, Data, Design, and Go-to-Market to deliver... ...merchandising experiences, and resolve tradeoffs between them.Lead and develop p…
build, and deliver trusted market-leading technology products in a secure, stable, scalable way in the Force.com platform. Design and develop critical technology solutions across multiple technical areas to support the o…
We made history and now we work to transform the future - for our customers, our communities and our families. You'll see your work on the road every day, helping people move freely and pursue their dreams. At Ford, you…
integrations, user-facing capabilities, and platform observability. The developer will receive technical direction from senior engineers and... ...guidance of senior engineers. • Build and integrate REST APIs, backend se…
platforms will be instrumental in crafting user-friendly and feature-rich applications for various mobile devices. What You’ll Do Developing mobile application using React Native framework. Developing application program…
complex engineering and operational challenges. You will identify opportunities to strengthen system resilience, improve processes, and develop scalable solutions, using data and technical expertise to influence decision…
Make an impact with NTT DATAJoin a company that is pushing the boundaries of what is possible. We are renowned for our technical excellence and leading innovations, and for making a difference to our clients and society.…
Racing is where our story began.In 1901, Henry Ford climbed into a car he built himself—"Sweepstakes"—and beat America's most famous driver. He wasn't a racer, but he had to win. He did. Ford Motor Company was born from…
Job-ID32758162Reference26-02463 Employees in this job function are responsible for designing, developing, testing and maintaining software applications and products to meet customer needs. They are involved in the entire…
process, please direct your inquiries to the Global Call Center (GCC) at ****@*****.***. Recruiting tips From developing a stand out resume to putting your best foot forward in the interview, we want you to feel prepared…
middleware services using Java, Spring Boot, microservices, REST, SOAP, OData, RFCs, BAPIs, IDocs, Kafka, and Google Cloud Pub/Sub. Develop and support SAP BTP and SAP Integration Suite solutions that connect SAP applica…
What backend developers earn in Detroit
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $32–$45 | $67k–$93k |
| Mid level | $45–$65 | $93k–$135k |
| Senior | $62–$85 | $130k–$177k |
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
Design an API for a feature like comments or notifications.
Clarify requirements, then cover endpoints, data model, pagination, and error handling. Mentioning versioning and rate limits shows production experience.
How would you find and fix a slow database query?
Walk through reading the query plan, checking indexes, and considering caching or denormalization. Ground it in a query you actually fixed.
How do you keep two services consistent when both need to update data?
Discuss transactions, idempotency, and eventual consistency with outbox or saga patterns. Acknowledge tradeoffs rather than promising perfect consistency.
What do you monitor on a service you own?
Name the basics — latency, error rate, saturation — plus business-level signals. Bonus points for talking about alerts you tuned to reduce noise.
Tell me about a production incident you handled.
Structure it: detection, mitigation, root cause, prevention. Emphasize what changed afterward, not just the firefight.
How do you approach securing an API?
Cover authentication, authorization, input validation, and secrets handling. Naming OWASP-style risks concretely is enough; you are not expected to be a security engineer.
When would you choose a message queue over a direct call?
Talk about decoupling, retries, and absorbing spikes, and be honest about the added complexity of async debugging.
Resume tips that move the needle
For backend developers specifically — generic advice costs you here
State scale where you can: requests per second, data volume, or number of services — it is the fastest way to signal seniority.
Name the databases and infrastructure you ran in production, not just languages.
Describe reliability work — migrations without downtime, incident reduction, test coverage on critical paths.
If you designed an API others consume, say so and note how many teams or clients depend on it.
Avoid listing every framework you have touched; two stacks with depth read better than eight without.
Where this role goes
Typical progression
Applying for backend developer 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.