$80 - $85 per hour
Job Description Job Description Data Engineer Location: Seattle, WA Onsite Flexibility: Hybrid Contract Details Position Type: Contract Contract Duration: 3 months Pay Rate: $80.00 $85.00 / Hour (USD) Hours per Week: 40…
Engineering & IT · Seattle, WA
Data Engineer jobs in Seattle, WA
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.
510
Open roles today
$47–$117/hr
Typical pay range
$161k
Median, full-time
5
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 510 · sorted by freshness
We are seeking a Snowflake Data Analyst/ Engineer with strong expertise in Snowflake, SQL, and data pipeline validation. The ideal candidate will be responsible for designing and optimizing data models, validating data p…
A leading cloud services provider seeks a Data Center Engineer to deploy, maintain, and scale data center infrastructure. Responsibilities include troubleshooting hardware issues, mentoring junior engineers, and supporti…
$128k - $161k
while learning, having fun, and making a profound difference for the dreamers and builders in the world. At DigitalOcean, Data Center Engineers play a critical role in building and operating the physical infrastructure t…
With offices in Bozeman, MT and Seattle, WA, we are a team of engineers and technologists from Boeing, Airbus, Aurora, and beyond. We are... ...company. You will work closely with machine learning and data engineering te…
$52.79 - $81.94 per hour
Role summary Data Engineer I is responsible for designing and developing modern, data-centric applications that support clinical and operational workflows across the healthcare system. These solutions leverage cloud tech…
$197k - $270.6k
in on this mission. If you are too, let's talk. The Technology, Data, and Intelligence Team Okta is the leading independent... ...The Technology, Data, and Intelligence (TDI) organization is the engine that powers Okta's…
$197k - $270.6k
in on this mission. If you are too, let's talk. The Technology, Data, and Intelligence Team Okta is the leading independent... ...The Technology, Data, and Intelligence (TDI) organization is the engine that powers Okta's…
$140k - $185k
We are supporting our client on a search for a Senior Data Engineer who will be the technical owner of a modern data platform. This is a high-trust seat reporting to the head of data with real budget, real ownership, and…
Job Description Job Description We are looking for a Senior Data Engineer to join our growing data platform team. You will own the design, build, and reliability of our cloud-native data lakehouse — from raw ingestion th…
$171.9k - $221k
ABOUT THIS ROLE LVT's AI systems are only as good as the data behind them. As we move toward Physical AI, the binding constraint... ...architecture to the data flywheel. We are seeking a Staff Data Engineer to own that f…
Job Description Job Description Job Summary We are seeking a highly skilled and motivated Data Engineer to join our growing data team. The Data Engineer will be responsible for designing, building, and maintaining robust…
02
What data engineers earn in Seattle
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $47–$65 | $98k–$135k |
| Mid level | $65–$90 | $135k–$188k |
| Senior | $87–$117 | $181k–$244k |
Adjusted for the Seattle 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 Seattle?
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.