Seattle, WA

Salary
Posted
Jul 16, 2026
Location
Seattle, WA
Last confirmed open
Jul 21, 2026

What this job asks for AI summary

A data engineering role focused on building and maintaining large-scale data infrastructure within Amazon's talent acquisition technology organization. Day-to-day work involves designing ETL pipelines, architecting data storage solutions, and integrating data from diverse sources using SQL and AWS services. Suited to engineers with a solid background in data modeling, warehousing, and pipeline development who are comfortable shaping both technical strategy and hands-on implementation.

Mid level · 3+ years · National · Full-time

Must have (3)
data modelingETL pipelinesSQL
Nice to have (5)
RedshiftS3EMRLambdaNoSQL

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

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

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

What the occupation pays Median $142,568 (middle half $111,775–$173,013).

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 (6)

No work location is specified in the posting — CBSA and state are left blank. The role appears to be US-based given Amazon's ITA context, but the specific city/office is not stated.

The role title is not given; it is inferred from the responsibilities (data infrastructure, ETL pipelines, data strategy/roadmap) to be a Data Engineer. The SOC was a close call between 15-1243 (Database Architects, reflecting the architectural/pipeline-design emphasis) and 15-1242 (Database Administrators); 15-1243 was chosen because the JD emphasizes designing data architecture and technical roadmaps, not day-to-day database operations.

Seniority is assessed as Mid: the minimum gate is 3+ years and the responsibilities are team-level delivery without explicit org-wide or cross-team architectural authority.

All AWS-specific services (Redshift, S3, Glue, EMR, Kinesis, Firehose, Lambda) and non-relational database experience appear only under 'Preferred Qualifications' and are marked accordingly. 'Firehose' and 'IAM roles and permissions' were consolidated — Firehose is captured under Kinesis context and IAM is an AWS access-control feature rather than a standalone named tool.

No compensation range is provided in the posting.

Ignored 1 non-technology phrase(s) as skills (responsibilities/concepts, not named tools): data engineering.

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 ↗