AWS Software Engineer III-ETL/AI
JPMorgan Chase · Newark, DE
—
Jun 29, 2026
Newark, DE
Jul 21, 2026
What this job asks for AI summary
A mid-level software engineering role on a market data platform team, focused on building and maintaining ETL pipelines and data services on AWS. Day-to-day work involves writing Python or Java code, designing data platform components using services like S3, Redshift, and Lambda, and incorporating AI-assisted development tools. Suits engineers with hands-on AWS data platform experience and an interest in large-scale data processing.
Mid level · 3+ years · National · Full-time
“or” means any one of them counts — you don't need all of them.
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
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $138,970 (middle half $107,524–$175,762).
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)
The job title 'AWS Software Engineer III' maps to a level-III designation, which is treated as Mid-level on the standard career ladder; the 3+ years experience requirement is consistent with that band.
No work location is specified in the posting — the CBSA is left blank. JPMorgan Chase roles of this type are typically on-site at a major hub (e.g., New York, Columbus, or Plano), but the posting does not confirm one.
The role sits at the intersection of software engineering and data platform/ETL work; 15-1243 (Database Architects) is a plausible alternative given the heavy emphasis on data platforms, Redshift, and ETL pipelines, but the primary framing is software development.
Terraform is listed under required qualifications with a softening qualifier ('e.g., Terraform') but is placed firmly in the required section, so it is treated as a hard gate on infrastructure-as-code capability.
AI-assisted development tooling (e.g., GitHub Copilot or equivalent enterprise tools) is called out as a required capability but names no specific product, so no skill entry was emitted for it.
The preferred section explicitly labels items 'best to have', confirming they are not gates.
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.