$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…
Engineering & IT · Salt Lake City, UT
Data Engineer jobs in Salt Lake City, UT
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.
62
Open roles today
$38–$97/hr
Typical pay range
$133k
Median, full-time
11
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 62 · sorted by freshness
Divisional Overview:The Risk Division is a team of specialists charged with managing the firm's credit, market, liquidity, operational and insurance risk. Whether assessing the creditworthiness of the firm's counterparti…
$167k - $203k
Premises), SIP (Session Initiation Protocol) trunks, number porting, sites, and Edge configuration· Build integrations using Genesys Cloud Data Actions, the Platform API (Application Programming Interface), AppFoundry ap…
$120k - $155k
States; preference given to candidates near an Eide Bailly location. Work Arrangement: Remote A Day in the Life The Cloud Senior Engineer is responsible for supporting complex engineering initiatives across the Microsoft…
If you're as passionate about your future as we are, join our team.KPMG is currently seeking an Associate Director, AI Application Engineer to join our Digital Nexus Technology organization.Responsibilities:Lead a team o…
We are looking for a Data Engineer to help design and enhance data solutions that support reliable reporting and analytics in Salt Lake City, Utah. This role focuses on building scalable data pipelines, shaping well-stru…
$77k - $202k
context and how it is changing.Use reflection to develop self awareness, enhance strengths and address development areas.Interpret data to inform insights and recommendations.Uphold and reinforce professional and technic…
process improvement across the revenue organization, implementing scalable solutions that enhance operational effectiveness.• Maintain data governance standards by promoting reporting accuracy, process compliance, and st…
$105k - $131.33k
generation projects that enable large-load customers—including data centers—to access reliable, scalable energy as part of integrated... ...strategy while collaborating with industry experts across engineering, developme…
$122k - $145k
acceptance criteria* Create process maps that demonstrate a client’s business workflows to assist in stakeholder alignment* Capture data, reporting, security, and user experience needs at a functional level* Validate req…
timely progression, and proactively identifying and escalating delays or risks.Prepare, review, and validate client documentation and data inputs, ensuring completeness, accuracy, and adherence to operational controls an…
$79.6k - $139.3k
Senior Data Engineer (Databricks & Cloud Analytics) Position Description Are you passionate about building modern data platforms that enable organizations to make smarter, faster decisions? Do you thrive on solving compl…
02
What data engineers earn in Salt Lake City
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $38–$53 | $80k–$111k |
| Mid level | $53–$74 | $111k–$154k |
| Senior | $72–$97 | $149k–$201k |
Adjusted for the Salt Lake 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 Salt Lake 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.