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…
Engineering & IT · Kansas City, MO
Backend Developer jobs in Kansas City, 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.
44
Open roles today
$33–$86/hr
Typical pay range
$115k
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 backend developer roles
5 shown of 44 · sorted by freshness
$105k - $140k
Speechify in a 100% distributed setting. These include frontend and backend engineers, AI research scientists, and others from Amazon,... ...Engineers to ensure a seamless handoff from sale to onboarding Develop GTM play…
/PrimeFaces interfaces to Angular single-page applications. Develop and enhance Spring Boot microservices that replace legacy Java... ...applications. Build and maintain secure, scalable REST APIs and backend services. I…
Swiss Lead Programmer Summary Responsible for programming and leading setup activities on multi-axis CNC Swiss lathes to produce high-precision components. Applies advanced knowledge of machining theory, tooling, materia…
SaaS platform built on .NET Core microservices with MS SQL Server backend. Define and own the front-end architecture strategy for a... ...code reviews, troubleshooting, and performance optimization. Develop complex UI mo…
02
What backend developers earn in Kansas City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $33–$45 | $68k–$94k |
| Mid level | $45–$65 | $94k–$136k |
| Senior | $63–$86 | $132k–$179k |
Adjusted for the Kansas City market from national ranges.
03
What employers ask for
The skills these listings keep naming
A server language (Java, Go, Python, C#)API design (REST, gRPC)SQL and schema designCaching and queuesAuthentication and securityDistributed systems basicsDocker and CI/CDObservability and logging
04
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.
05
Resume tips that move the needle
For backend developers specifically — generic advice costs you here
01
State scale where you can: requests per second, data volume, or number of services — it is the fastest way to signal seniority.
02
Name the databases and infrastructure you ran in production, not just languages.
03
Describe reliability work — migrations without downtime, incident reduction, test coverage on critical paths.
04
If you designed an API others consume, say so and note how many teams or clients depend on it.
05
Avoid listing every framework you have touched; two stacks with depth read better than eight without.
06
Where this role goes
Typical progression
01
Junior Backend Developer
02
Backend Developer
03
Senior Backend Developer
04
Staff Engineer
05
Principal Engineer
Ten quiet minutes a day
Applying for backend developer jobs in Kansas City?
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.