Forward Deployed Data Engineer About the Role DataSQRL is hiring a Forward Deployed Data Engineer to embed with one of our enterprise customers and own the success of their data implementation end to end. This role combi…
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.
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 data engineer roles
12 shown of 1,072 · sorted by freshness
You’ll Do Design, develop, and maintain ETL processes and data pipelines to move and transform data efficiently across systems... ...What You Bring 3–7+ years of experience in data engineering or related fields. St…
Job Description Databricks DBRX, Snowflake, Data Engineering, Data Lake, Data Modeling, Data Pipelines Roles & Responsibilities Design and maintain scalable data pipeline architectures to ensure efficient data processing…
Are you ready to make an impact? West Monroe is seeking a talented Data Engineer to join our Data Engineering & Analytics team. In this role, you will collaborate with our clients to address their most complex needs, wor…
Are you ready to make an impact? West Monroe is seeking a Senior Data Engineer to join our Data & AI practice. In this role, you will design, build, and optimize modern cloud data platforms that enable advanced analytics…
our strategies. Driven by a passion for developing scalable data infrastructures capable of handling billions of transactions and... ...technical capabilities and the customer experience. As a Data Engineer in our team,…
SENIOR DATA ENGINEER (No Visa Transfers or Sponsorships Available) About Tillster Headquartered in the USA, Tillster is the global leader in digital ordering and customer engagement solutions. For over a decade we have d…
whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems. Job Description As a Data Engineer, you will be a memb…
Are you a data engineer who thrives on solving ambiguous, high-impact problems at scale? Do you enjoy building data solutions that teams across an organization rely on every day? If so, this role offers the chance to own…
see it in full. How you'll make impact Our Strategic Data team builds the data foundations that support business intelligence... ...security, and lifecycle management. Work with Data Platform Engineers and Product Manage…
we’re the people who keep the cloud running. We support all AWS data centers and all of the servers, storage, networking, power, and... ...You’ll join a diverse team of software, hardware, and network engineers, supply c…
a whole. Our team is a quickly growing group of committed researchers, engineers, policy experts, and business leaders working together to build beneficial AI systems. About the role As a Data Engineer on the Data Scienc…
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.
What employers ask for
The skills these listings keep naming
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.
Resume tips that move the needle
For data engineers specifically — generic advice costs you here
State data scale plainly — rows per day, terabytes managed, pipeline counts — because it is the first thing hiring managers scan for.
Name your orchestration, processing, and warehouse tools per role; the modern stack (Airflow, dbt, Snowflake) is a keyword screen.
Highlight reliability outcomes: pipeline failure rates, data freshness SLAs met, incident reductions.
Show cost work if you have it — warehouse spend is a live concern and optimization stories differentiate.
Mention who consumed your data (analysts, ML teams, executives) to show you build for users, not just movement.
Where this role goes
Typical progression
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.