$104k - $208k
bachelors degree, either completed or currently in progress. We prefer prior experience as a Software Developer, Coder, Software Engineer, or Programmer. We can only offer this opportunity to candidates located in the US…
Engineering & IT · Oklahoma City, OK
Data Engineer jobs in Oklahoma City, OK
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.
45
Open roles today
$33–$84/hr
Typical pay range
$115k
Median, full-time
6
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 45 · sorted by freshness
Group (LDG) is an award-winning, employee-owned Architecture, Engineering, and Consulting Firm. Guided by our core values, we’re expanding... ...design projects. This position is responsible for the design of data/ voice…
processes that run it. That work changes the operating model an engineering organization runs on, the ways of working underneath it, and... ...We combine our strength in technology and leadership in cloud, data and AI wi…
Principle SecOps & Observability Engineer, (Clearance Secret or Top Secret) CO, AL, OK, TXThis role has been designed as 'Hybrid' with a... .... We help companies connect, protect, analyze, and act on their data and appl…
leaders in helping drive that change, with strong ecosystem relationships. We combine our strength in technology and leadership in cloud, data and AI with unmatched industry experience, functional expertise and global de…
A Manufacturing/ distribution company is looking for a Data Engineer with 3 + years of experience to join a dynamic team in Oklahoma City, Oklahoma. In this role, you will play a crucial part in designing and maintaining…
$50 - $70 per hour
Job Title: Senior Data Engineer Location: Oklahoma City, OK Pay: $50 - $70 / Hour Work Schedule: Hybrid — 4 days onsite and 1 day remote initially Benefits: This position is eligible for medical, dental, vision, and 401(…
$100k - $200k
Job Title: Sr. Data Developer Industry : Energy / Oil & Gas Location (city, state): Oklahoma City, OK Assignment Type:... ...analytics initiatives. Work cross-functionally with IT, data engineering, and field staff to en…
$90k - $100k
Opportunity to support a mission-driven healthcare services organization Strategic role focused on business analysis, enterprise data strategy, and data visualization initiatives Partner with leadership and multiple busi…
$80k - $90k
between internal business teams, external partners, and technology stakeholders. This highly visible role combines business analysis, data analytics, reporting, process improvement, partner management, and workflow optim…
$110k - $125k
Role: Senior Database Engineer Position Type: Contract-to-Hire Location: Oklahoma City (Hybrid) Pay Rate Range: $110,0... ...client is seeking a Senior Database Engineer to join a growing data and business intelligence t…
Database Architect / Administrator We’re looking for someone to join our team with at least five years of experience in relational databases and a minimum of two years of experience in SQL Server. Essential duties and re…
02
What data engineers earn in Oklahoma City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $33–$46 | $69k–$96k |
| Mid level | $46–$64 | $96k–$134k |
| Senior | $62–$84 | $129k–$174k |
Adjusted for the Oklahoma City 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 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.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.