ETL Engineer – Java Spring Batch
Eliassen Group · Nashville, TN
$52–$57/hrfrom the description
Jul 24, 2026
Nashville, TN
Jul 26, 2026
What this job asks for AI summary
A contract role focused on migrating legacy Informatica workflows to Java Spring Batch as part of a large-scale modernization effort in the financial services sector. Day-to-day work involves analyzing existing ETL processes, rebuilding them as modern batch pipelines, and developing data transformation and validation logic. The role suits an experienced Java/Spring Batch engineer comfortable with AWS, CI/CD tooling, and Agile delivery.
Senior level · 6+ years · Remote · Contract
“or” means any one of them counts — you don't need all of them.
Posted 14 times — it's one opening, so apply once.
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 170 people nationally plausibly meet what this posting asks for (database architects). range 100–250
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
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 $142,568 (middle half $111,775–$173,013). 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 (7)
This role sits at the boundary between ETL/data pipeline architecture (15-1243) and Java software development (15-1252). The primary deliverable is building and migrating batch data pipelines, but the dominant tooling is Java Spring Batch — a software development framework — making the SOC call genuinely ambiguous. 15-1243 was chosen because the core mission is designing and delivering ETL/data integration solutions; 15-1252 is the close runner-up.
Jenkins and Artifactory are listed together as CI/CD tools in the requirements section. They serve different functions (build orchestration vs. artifact management) but are presented as a paired requirement; each is emitted separately and cross-listed as an alternative to reflect the joint framing.
AWS is listed as preferred within the requirements section ('preferably AWS'), but it appears under the hard-requirements block alongside specific services (ECS, ECR, EC2). It is marked required because the section placement gates the capability; 'preferably AWS' signals the named cloud is interchangeable, not that cloud experience itself is optional.
Informatica experience is explicitly called 'preferred' in the requirements section and is marked accordingly.
Python, GitHub Copilot, and enterprise scheduling/orchestration tools appear under a clearly labeled 'Preferred' section.
The posting requires W2 engagement only; the rate of $52–$57/hr W2 is stated explicitly.
Posting is for a contract engagement — the market benchmarks below price full-time roles, so read the comp comparison with that in mind.
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.