infrastructure, mobile and desktop clients, and integrations with external applications and AI providers.We’re looking for an exceptional backend engineer who wants substantial ownership of that system: someone with the…
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.
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
6 shown of 72 · sorted by freshness
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…
As a Drupal Developer with Mobomo you will need: Basic Theming Concepts: The candidate should understand the basic concepts of theming in Drupal, including how themes work, what template files are, and how to override de…
Shaping acceptance criteria for testability. Joining product, developers, architects, and designers during refinement to clarify requirements... ...with Postman, REST Assured, or similar tools for validating backend serv…
Job Description LRS Consulting is on the hunt for a .Net Developer to help automate business operations and improve workflow efficiency... ...solutions in Azure. This position is heavily focused on backend development pr…
Senior ERP Developer JOB-10047594 Anticipated Start Date October 12, 2026 Location Kansas City, MO Type of Employment Contract Employer Info Our client is a full-service engineering, architecture, construction, environme…
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.
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 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.