Job Summary E-Logic Inc. is seeking a Senior Software Developer to support the development testing implementation validation and optimization of software applications and analytical tools supporting the IRS RAAS Statisti…
Backend Developer jobs in Oklahoma City, OK
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
10 shown of 25 · sorted by freshness
experience.About the PositionOilfield Tracking Services (OTS) develops software for oilfield operators and transportation companies, including... ..., and third-party integrations.We're seeking a senior, backend- focused…
using Elastic Security (SIEM/XDR) Design, deploy, and maintain the Elastic Stack (Elasticsearch, Logstash, Beats, Kibana) Develop and tune detection rules, dashboards, and alerting workflows Conduct threat hunting and ad…
looking for a Principal AI Engineer to guide a distributed team of developers in building modern, scalable, and AI-integrated software... .../ML models in a production environment.A strong background in backend or full-s…
design test data and deployment timing Must have: More than 5 relevant years of IT experience including 5 years of experience developing web applications Minimum Bachelors in Computer/Engineering/Aviation. A Masters degr…
the FAAs security authorization needs Must have: More than 8 relevant years of IT experience including 8 years of experience developing mobile applications Minimum Bachelors in Computer/Engineering/Aviation. A Masters de…
Job Title: Training and Syllabus Developer Job Category: Training Time Type: Full time Minimum Clearance Required to Start: Top Secret Employee Type: Regular Percentage of Travel Required: Up to 25% Type of Travel: Conti…
world connect with God every day. The YouVersion Software Engineer is primarily responsible for developing software for various YouVersion projects and products, focusing on backend API development, mobile development, o…
At Life.Church, our Digital Product team builds technology that helps people take their next step in their faith journey. As a Senior Software Engineer, you’ll design and build solutions that support the systems and plat…
thought leader in graphs and solve our customers’ high-value problems beyond traditional data solutions. What Success Looks Like: - Developing and honing subject matter expertise to effectively discern and understand the…
What backend developers earn in Oklahoma City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $31–$43 | $64k–$89k |
| Mid level | $43–$62 | $89k–$129k |
| Senior | $60–$81 | $125k–$169k |
Adjusted for the Oklahoma 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 Oklahoma 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.