Mobile (React Native) do?You will be responsible for designing, developing, and maintaining cross-platform mobile applications for iOS... ...maintainable application development.Collaborate with Product, UX/UI, Backend E…
Backend Developer jobs in Omaha, NE
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
11 shown of 16 · sorted by freshness
Job Title: Guidewire BillingCenter Developer Location: Omaha, NE (Hybrid, 3Days/week Onsite) – Locals preferred Duration: 12-18 months Contract MOI: Phone/Video (MSTeams) Visa: GC/USC Recruiter Additional notes: Prioriti…
Nebraska. Interns will work on meaningful engineering projects, collaborate with cross-functional teams, and gain practical experience developing innovative technology solutions that support customers around the world. D…
Position: SME. Java Fullstack Developer Location: Omaha, NE (100% Onsite) Job type: Contract Exp Level: Min 15+ Years. STANDARD SKILLSET ROLE: JAVA FULL STACK DEVELOPER MUST HAVE: JAVA 8/17, SPRING BOOT, LINUX INTERMEDIA…
Job Title: Java Lead Developer Location: Omaha, NE (5days onsite / Week) Duration: long term Type: Contract W2 Experience... ...Job Description: We are seeking a highly skilled Java Backend Developer with strong DevOps e…
policies, and UDR matrices-strictly via modular, repeatable Terraform templates. ~ State & Configuration Governance: Implement secure backend state management, drift detection mechanisms, and policy-as-code validations (…
senior level engineers and/or designers. They will also work with client managers and the national business class to identify and develop specific technical expertise and will attend training and seminars focused on furt…
Technology US (DT - US) helps power Deloitte’s success, which serves many of the world’s largest, most respected organizations. We develop and deploy cutting-edge internal and go-to-market solutions that help Deloitte op…
processes.-Conduct architecture, solution, and code reviews to ensure alignment with enterprise standards and quality expectations.- Develop reusable integration frameworks, templates, and shared components that reduce d…
Java Developer Location: Omaha (Local Candidates Only) Interview Mode: Video Call (VC) / Client preference noted for local/F2F readiness Note: While the table indicates VC, per your requirement, local candidates who can…
Job Title: .NET Backend Developer – ERP & Integration Focus Location: Omaha, NE Experience Level: 4+ years Pay rate : $32.00/hr. on W2 Job Description: We are seeking a skilled .NET Backend Developer with experience in b…
What backend developers earn in Omaha
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 Omaha 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 Omaha?
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.