Seattle, WA

Salary
$132,100–$178,800from the description
Posted
Jul 14, 2026
Location
Seattle, WA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A data engineering role focused on designing and building large-scale data and ML infrastructure to support generative AI applications. Day-to-day work involves implementing ETL/ELT pipelines, data modeling, and integrating data systems with AWS services, in close collaboration with applied scientists and data scientists. Suited to engineers with hands-on experience managing high-volume data structures for analytics and business intelligence.

Mid level · 3+ years · Seattle-Tacoma-Bellevue, WA · Bachelor's required · Full-time

Must have (5)
data modelingETL/ELTSQLOracleOLAP
Nice to have (4)
AWS RedshiftAWS S3AWS EMRNoSQL

We read this from the posting text with AI. Skim the description below before ruling yourself out.

How this req sits in the market our data

Roughly 75 people in the Seattle-Tacoma-Bellevue, WA area plausibly meet what this posting asks for (database architects). range 30–120

Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.

What won't set you apart
SQL90%data modeling72%Oracle42%

Most people in this occupation already list these. Still required — just not what gets you shortlisted.

What the occupation pays Median $107,748 (middle half $104,212–$164,448). This posting is about at that midpoint.

Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.

Why we read it this way (8)

The role sits between data/pipeline architecture (15-1243) and general software development (15-1252) — it emphasizes building ETL/ELT pipelines, data structures, and ML infrastructure, which leans toward 15-1243, but the GenAI/ML infrastructure framing and 'technical leadership' language add software-engineering weight.

The JD states two overlapping experience gates: '3+ years of data engineering experience' and '3+ years of non-internship data engineering experience' — both point to the same 3-year floor, used as the overall years minimum.

The '1+ years' requirement is scoped to a specific set of technologies (ETL/ELT, OLAP, data modeling, SQL, Oracle) rather than overall experience, so it is captured as a per-technology gate rather than a separate role-level floor.

Oracle is listed as a hard gate under Basic Qualifications alongside SQL and OLAP; it may reflect legacy stack context rather than a true rejection criterion, but section placement requires treating it as required.

All AWS-specific services (Redshift, S3, Glue, EMR, Kinesis, Firehose, Lambda) and non-relational database experience appear only under Preferred Qualifications.

Firehose (Amazon Kinesis Data Firehose) is a sub-service of Kinesis and is consolidated under the Kinesis skill rather than emitted separately.

The title carries no seniority level word; the title states no level. The 3-year minimum and scope of responsibilities support a Mid-level classification.

Compensation is quoted as a base salary range for Seattle, WA; the posting notes that sign-on payments and RSUs are also part of the package.

Read the full posting

The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.

Apply

Apply on employer site ↗