- Workplace
- Hybrid
- Type
- Full-time
- Level
- Senior
- Salary
- $239K – $280K/yr
In this role, you will:
-
Build and maintain the Behavior Evaluation data pipelines (PySpark/zspark medallion architecture on Databricks, EMR Serverless and Airflow) that produce weekly per-geofence estimates.
-
Turn the statistical method (sampling, triage weights, mileage sharing, projections) into tested, reproducible code with checks that fail loudly when the data is bad.
-
Build tools that cut the manual work in each weekly run.
-
Work with cross functional stakeholders so the methodology is applied consistently in code and in clearance reports.
-
Help adapt to new release methodologies and new geofences.
Qualifications:
-
7 - 9 Years of experience or 5+ years with a strong data-platform track record
-
Expert Python, with production experience in PySpark/Spark and Pandas
-
Experience designing scalable batch data pipelines: orchestration, Delta/lakehouse tables, idempotent backfills
-
Solid grounding in applied statistics: sampling, weighting, estimators, confidence intervals
-
Strong testing and CI habits for data code
Bonus Qualifications:
-
Experience with autonomous-vehicle simulation, safety metrics or triage workflows
-
Experience putting ML models into production in a data pipeline
-
Experience with Databricks and AWS (EMR Serverless, S3)
JobsPing insights
Our own analysis of this role, based on every open job we track. Updated daily.
Salary benchmark
Software Engineering roles in United States · 1084 posted USD salaries
This role's midpoint is about 11% above the median for comparable listings. How to negotiate
How in-demand these skills are
Share of all open roles on JobsPing that ask for each skill
- Python23% · 2,143
- Machine Learning19.5% · 1,822
- AWS14.9% · 1,387
- Spark7.1% · 662
Zoox right now
- Open roles
- 241
- Remote
- 0%
- New this week
- 17
Skills they ask for most: Machine Learning, Python, C++, LLM / GenAI.
How to stand out for this role
- Lead your resume bullets with shipped outcomes: latency cut, revenue moved, incidents reduced.
- Link one repository or project that uses this job’s main stack, and make sure its README explains what you built.
- Mirror the posting’s exact tool names (e.g. “PostgreSQL”, “Next.js”) for skills you genuinely have.
- Prepare one story about a production bug you debugged end-to-end; it comes up in almost every loop.