Software Engineer - Data Workflows at Woven by Toyota
Ann Arbor, MI
—
Jul 23, 2026
Ann Arbor, MI
Jul 26, 2026
What this job asks for AI summary
A backend and data engineering role focused on building cloud-native simulation and validation infrastructure for ADAS and autonomous driving software. Day-to-day work involves designing ETL pipelines, data models, APIs, and automated testing systems that process large volumes of real-world and simulated driving data. The role suits engineers with solid Python, SQL, and cloud experience who are comfortable owning features end-to-end and collaborating with cross-functional teams.
Mid level · 3+ years · Bachelor's required · 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
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 (7)
No work location or city is specified in the posting; the CBSA field has been left blank. The role appears to be US-based given the 401k and equal opportunity employer language, but remote vs. on-site is not stated.
The degree requirement states 'Bachelor's or Master's degree' with no 'or equivalent experience' escape clause, so Bachelor's is treated as the minimum hard requirement.
The role sits at the boundary between backend software engineering (15-1252) and data/pipeline engineering (15-1243); the posting leads with 'backend software engineer' and emphasizes APIs and full software lifecycle, so 15-1252 is the primary classification with 15-1243 as the runner-up.
Cloud platform requirement names AWS, Azure, and GCP as interchangeable options with a 1-year minimum; AWS is listed first and used as the primary skill name with the others in alternatives.
DynamoDB is listed under the required 'Technical Expertise' section but framed with 'Familiarity with… such as', indicating it is a soft gate; treated as preferred.
Terraform and microservice/serverless architectures appear under 'Preferred Qualifications' and are marked accordingly.
Seniority is assessed as Mid: the role requires 3+ years of experience and the title carries no level modifier. The responsibilities (mentoring, leading design) skew toward Senior, but the experience floor and title framing support Mid as the more conservative and accurate band.
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.