Engineering & IT · Omaha, NE

Data Engineer jobs in Omaha, NE

Data engineers build the pipelines and warehouses that move data from source systems to the people and models that need it, keeping it fresh, correct, and queryable at scale.

29
Open roles today
$35–$86/hr
Typical pay range
$119k
Median, full-time
10
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 data engineer roles

12 shown of 29 · sorted by freshness

Data Engineer 2

HDR · Omaha, NE

further to learn how you could help make great things possible not only in your community, but around the world. In the role of Data Engineer II, we'll count on you to:Build and maintain batch and streaming ingestion pip…

Posted 2d ago
+ Save to tracker View listing

Analytics Engineer 2

HDR · Omaha, NE

your community, but around the world. In the role of Analytics Engineer II, we'll count on you to:Design and develop analytics models aligned... ...with analysts to translate business questions into durable data models.I…

Posted 2d ago
+ Save to tracker View listing

PROJECT - Data Engineer II

Deloitte · Omaha, NE
$71.3k - $140.6k

Position Summary Our Deloitte AI & Engineering team works to transform technology platforms, drive innovation, and help make a significant... ...fuel growth through innovation. Work you'll do As a PROJECT - Data Engineer…

Posted 2d ago
+ Save to tracker View listing

Senior Benefits Analyst

Creighton University · Omaha, NE

mission and strategic initiatives. Key ResponsibilitiesBenefits Program Support and Administration:Support leadership by gathering plan data, analyzing trends, and identifying opportunities for consideration in plan desi…

Posted 3d ago
+ Save to tracker View listing

SQL SERVER DBA Developer

American Unit, Inc. · Omaha, NE

WITH REGULATORY COMPLIANCE LIKE SOX AND CIS. GOOD TO HAVE: SCOM INTERMEDIATE, SCCM INTERMEDIATE, MONTORING AND ALERTING TUNING, DATA ANALYTICS (TABLEAU) EXPERIENCE LEVEL: SME LEVEL, 8 - 10 YEARS OF EXPERIENCE IN SQL SERV…

Posted 3d ago
+ Save to tracker View listing

Cyber Risk Controls Officer

Fiserv · Omaha, NE

Calling all innovators - find your future at Fiserv.We're Fiserv, a global leader in Fintech and payments, and we move money and information in a way that moves the world. We connect financial institutions, corporations,…

Posted 3d ago
+ Save to tracker View listing

Cloud Security Engineer Manager

Deloitte · Omaha, NE
$118.7k - $243.7k

sustainment of zero trust architectures to safeguard critical assets and data against emerging cyber threats.Serve as the subject matter... ...and Firewall Teams, Application Teams, Server Teams, Cloud Engineering Teams…

Posted 3d ago
+ Save to tracker View listing

Sr. Data Engineer

Milan Laser Hair Removal · Omaha, NE

both our clients and our team. As Milan continues to grow, so does the scale and sophistication of the data behind our business. We’re looking for a Senior Data Engineer who can help build the data foundation powering ev…

Posted 1mo ago
+ Save to tracker View listing

Client Service Analyst

Fiserv · Omaha, NE

Calling all innovators – find your future at Fiserv. We’re Fiserv, a global leader in Fintech and payments, and we move money and information in a way that moves the world. We connect financial institutions, corporations…

Posted 7mo ago
+ Save to tracker View listing
02

What data engineers earn in Omaha

Hourly first — that's how the offer arrives

ExperienceHourlyAnnual, full-time
Entry level $35–$48 $72k–$99k
Mid level $48–$66 $99k–$138k
Senior $64–$86 $133k–$179k

Adjusted for the Omaha market from national ranges.

03

What employers ask for

The skills these listings keep naming

SQL and data modelingPython or ScalaAirflow or similar orchestrationSpark or other batch processingWarehouses (Snowflake, BigQuery)dbtStreaming (Kafka)Data quality testingCloud infrastructure
04

Interview questions worth rehearsing

With the thing the interviewer is actually listening for

Design a pipeline that loads data from a production database into a warehouse daily.

Cover extraction strategy, incremental loads versus full refresh, idempotency, and monitoring. Saying how you would backfill after a failure shows real pipeline experience.

How do you handle late-arriving or duplicate data?

Discuss idempotent upserts, watermarks, and dedup keys. This is a daily reality of the job, so a concrete example lands well.

Batch or streaming — how do you decide?

Anchor on the actual freshness requirement and cost. Most 'real-time' asks are fine at minutes; recognizing that is the mature answer.

A stakeholder says the numbers in their dashboard are wrong. Walk me through your debugging.

Trace lineage from the dashboard back to the source, isolating which layer diverged. Showing calm, structured lineage-tracing is the point of the question.

How do you model data for analytics — star schema, wide tables, something else?

Show you know the classic patterns and modern warehouse economics, and that you choose based on query patterns and team skill, not doctrine.

How do you test data pipelines?

Talk about schema and freshness checks, row-count and distribution tests, and tools like dbt tests or Great Expectations — plus alerting when they fail.

Tell me about a pipeline that failed badly and what you changed.

Structure it like an incident review: impact, cause, fix, prevention. Emphasize the durable improvement, such as monitoring or contract enforcement.

05

Resume tips that move the needle

For data engineers specifically — generic advice costs you here

01

State data scale plainly — rows per day, terabytes managed, pipeline counts — because it is the first thing hiring managers scan for.

02

Name your orchestration, processing, and warehouse tools per role; the modern stack (Airflow, dbt, Snowflake) is a keyword screen.

03

Highlight reliability outcomes: pipeline failure rates, data freshness SLAs met, incident reductions.

04

Show cost work if you have it — warehouse spend is a live concern and optimization stories differentiate.

05

Mention who consumed your data (analysts, ML teams, executives) to show you build for users, not just movement.

06

Where this role goes

Typical progression

01 Junior Data Engineer
02 Data Engineer
03 Senior Data Engineer
04 Staff Data Engineer
05 Data Platform Lead
Ten quiet minutes a day

Applying for data 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.

Start with this search No email, no resume, no sign-up. Open your tracker Everything you saved is already there.
29 Data Engineer roles in Omaha Save them into one pipeline Save them into your pipeline
Start free My tracker