customers' requirements and the highest quality standards. As part of this, you will work with all the stakeholders, from architects and Backend Leads to customers, understanding their requirements and supporting them, g…
Backend Developer jobs in St. Louis, MO
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 99 · sorted by freshness
Overview Build Software that Supports Critical National Security Missions. Join Esri`s Professional Services team and develop the backend services, APIs, integrations, and data capabilities that power mission-critical ge…
you are passionate about technology and eager to take on new challenges we encourage you to apply and join our team. Full Stack Developer IT Service Delivery World Wide Technology (WWT) is a global systems integrator and…
Reinventing Geospatial (RGi) is a leading expert in geospatial solutions for Defense, Intelligence, and Federal clients. We enhance situational awareness for soldiers and analysts by integrating software development with…
work onsite three days per week. We are seeking a Full Stack Developer with strong Python and JavaScript expertise to design, build,... ...environment. A full-stack developer commonly owns user interfaces, backend APIs,…
solutions to complex business and technical problems and to troubleshoot effectively under pressure. Comfortable mentoring other developers and helping identify tasks for others. Experience leading a small project or wor…
versions. # Practical experience with Spring Boot and Spring MVC. # Experience designing and developing REST APIs and microservices. # Hands-on Python experience for backend development, automation, or integrations. # Ex…
deployments. You will: Design and implement secure scalable backend systems for Public Sector customers, leveraging Scale's modern... ..., programming languages, and databases. Experience with developing & delivering sof…
customer sites, from prototype to stable production. Build robust backend systems and data integrations that connect customer... ...of all applicants. About Us: At Scale, our mission is to develop reliable AI systems for…
Job Title: Senior Full-Stack Developer( Java / Microservices / DevOps) Location: St Louis, MO (Onsite) Duration: 12 months Job Summary We are seeking a highly skilled andversatile Full-Stack Developer to design, build, a…
sessions and technical workshops with stakeholders. • Design and develop cloud native applications using modern application development frameworks and services. • Design and implement scalable backend services, APIs, and…
This position must be performed on-site, hybrid in St. Louis, MO. Join a team responsible for designing and delivering cloud-based applications that support complex business processes and data driven decision making. Thi…
What backend developers earn in St. Louis
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $32–$44 | $66k–$92k |
| Mid level | $44–$64 | $92k–$133k |
| Senior | $62–$84 | $129k–$175k |
Adjusted for the St. Louis 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 St. Louis?
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.