A leading tech services firm is looking for a Kubernetes Container Platform Engineer to architect and implement container services platforms. The role involves integration with CI/CD pipelines and enhancing automation. C…
Software Engineer jobs in Omaha, NE
Software engineers design, build, and maintain the applications and systems behind modern products. The work spans writing code, reviewing designs, and keeping software reliable as it 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 software engineer roles
12 shown of 176 · sorted by freshness
Position: Cloud Data Engineer Mid-level Location: Omaha, NE Job type: Contract MUST HAVE: SNOWFLAKE - STRONG HANDS-ON EXPERIENCE WITH SNOWFLAKE: SQL DEVELOPMENT, WAREHOUSING CONCEPTS, AND WORKLOAD MANAGEMENT PYTHON - SPE…
Overview Are you an engineer with a passion for leadership, proven engineering experience, and a drive to mentor others while advancing... ...and hands-on experience with CI/CD pipelines to automate the software developm…
Lead the architecture and technical direction of a modern enterprise application Mentor and develop a growing team of software engineers Work with modern technologies including Kotlin, Spring Boot, React, AWS, Kubernetes…
Job Description Job Description Software Engineer (React / Spring Boot) | Up to $120,000 | Hybrid | Direct Hire What Matters Most Competitive salary up to $120,000 , based on experience Hybrid work schedule with regular…
management system (CMS) and rendering infrastructure to the technologies that determine how Gallup appears in search engines and AI answer engines. As a software engineer on the Consumer Engagement team, you'll modernize…
Job Description Job Description Director – Software Engineering | $190 ,000 - $210 ,000 Per Year | Direct Hire What Matters Most Competitive Pay of $190,000 - $210,000 per year based on experience Schedule: Flexible Hybr…
2026 Employee Engagement Survey Results (yes, we use our own software) : · 97% response rate · 83% overall favorability... ...-functional team, working with developers, designers, Quality Engineers and product owners to…
Responsibilities include analyze and understand simulation software discrepancies and change requirements, develop conceptual solutions... ..., determine the cause, and apply iterative systems engineering processes to re…
Job Description Job Description Software Developer | $45 - $55 per hour | Hybrid Contract What Matters Most ~ Competitive Pay... ...team success, and builds a strong foundation in modern software engineering practices. R…
Description Job Description At Aviture, we’re a team of builders—creating mission-critical software that empowers our customers and makes a real impact. We’re looking for a senior-level engineer who thrives on solving co…
Job Description What is Aviture? Aviture provides custom software solutions for clients, acting as a business partner and technical... ...in someone’s life. We’re a team made up of designers, engineers, developers, and i…
What software engineers earn in Omaha
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $33–$47 | $69k–$97k |
| Mid level | $47–$66 | $97k–$138k |
| Senior | $64–$88 | $133k–$184k |
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
Walk me through a project you built and the technical decisions behind it.
Pick one project and go deep. Explain the tradeoffs you weighed, not just the stack you used, and name one thing you would do differently now.
How would you design a URL shortener (or similar small system)?
Start with requirements and rough scale before drawing boxes. Interviewers care more about how you reason through storage, uniqueness, and reads versus writes than a perfect answer.
Tell me about the hardest bug you have debugged.
Describe your process: how you reproduced it, narrowed the cause, and confirmed the fix. A methodical story beats a dramatic one.
How do you decide when code is good enough to ship?
Talk about tests, review, and risk relative to the change. Showing judgment about tradeoffs matters more than claiming perfection.
Describe a time you disagreed with a teammate about a technical approach.
Show that you argued from evidence, listened, and committed to the outcome. Avoid stories where the point is simply that you were right.
How do you approach learning an unfamiliar codebase?
Mention concrete tactics: reading tests, tracing a request end to end, making a small safe change first. This signals you can become productive quickly.
What would you do if a production incident happened right before a deadline?
Prioritize stabilizing production and communicating early. Interviewers want calm triage, not heroics.
Resume tips that move the needle
For software engineers specifically — generic advice costs you here
Name the languages and frameworks per role or project, not just in a skills block, so screeners can match you to the stack.
Quantify outcomes in engineering terms: latency reduced, error rate cut, deploy time shortened, users served.
Link to a GitHub profile or portfolio only if the pinned work is recent and readable.
Describe your role on team projects precisely — 'built the payments service' reads very differently from 'worked on payments'.
Keep the tech list honest; anything on the resume is fair game in the interview.
For senior roles, show scope: systems owned, engineers mentored, decisions driven.
Where this role goes
Typical progression
Applying for software engineer 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.