Pay
$127K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,383 postings in the last year. Stated ranges, not salaries paid.
Palo Alto · Palo Alto, California, United States
Open 5 months, first seen by us 161 days agoLocation type: On-siteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: Software EngineeringFrom the employer’s posting
Build and scale ingestion pipelines for high-volume, high-dimensional sensor data
Build and maintain data quality and curation systems, including manual review and auto-labeling
Contribute to storage and retrieval design, including formats, versioning and lineage
Build and operate distributed batch and streaming processing infrastructure
Debug production issues in live data pipelines, such as corruption and schema drift
Build and scale ingestion pipelines for high-volume, high-dimensional sensor data.
Build and maintain data quality and curation systems, including both manual review workflows and auto-labeling.
Contribute to storage and retrieval design for large-scale multimodal datasets, including format choices and versioning/lineage.
Build and operate distributed processing infrastructure (batch and streaming).
Debug production issues in live data pipelines — data corruption, schema drift, backpressure, and failures that only show up at scale.
Will you require immigration sponsorship now or in the future?From the employer’s application form
2+ years of software engineering experience, with some exposure to data pipelines, data engineering, or backend systems.
Experience with at least one distributed data processing framework (e.g., Spark, Ray, Dask, or Flink), or strong fundamentals and willingness to ramp up quickly.
Familiarity with data storage concepts — object storage, data lake table formats, and warehouse vs. lake tradeoffs.
Experience with workflow orchestration tools (e.g., Airflow, Dagster, Prefect) is a plus.
Experience with streaming ingestion for high-volume, near-real-time data is a plus.
Experience building automated data quality/curation systems (statistical filtering, anomaly detection, deduplication, or using ML models in an annotation/filtering pipeline) is a plus.
Experience with robotics- or embodied-AI-specific data (multi-embodiment datasets, teleoperation/demonstration data, egocentric video) is a plus.
Mind Robotics is building Physical AI for real-world industrial deployment, starting with the factory floor.
In the employer’s words · Read in context · Company website ↗
Open 5 monthsWe first saw this posting 161 days ago and it is still up. Roles open this long are often slow to fill or kept open to collect applications.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$127K–$190K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,383 postings in the last year. Stated ranges, not salaries paid.
Day 161
Up longer than most. Similar jobs usually come down between day 6 and day 56.
From 13,974 similar postings that came down. Coming down is not always a hire.
3 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.
- 2+ years of software engineering experience, with some exposure to data pipelines, data engineering, or backend systems. - Strong programming fundamentals in Python, with the ability to write performant, production-grade data processing code. - Experience with at least one distributed data processing framework (e.g., Spark, Ray, Dask, or Flink), or strong fundamentals and willingness to ramp up quickly.
- Clear communicator who collaborates well with research/modeling partners and more senior teammates. - Experience with workflow orchestration tools (e.g., Airflow, Dagster, Prefect) is a plus. - Experience with streaming ingestion for high-volume, near-real-time data is a plus.
- Strong programming fundamentals in Python, with the ability to write performant, production-grade data processing code. - Experience with at least one distributed data processing framework (e.g., Spark, Ray, Dask, or Flink), or strong fundamentals and willingness to ramp up quickly. - Familiarity with data storage concepts — object storage, data lake table formats, and warehouse vs. lake tradeoffs.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Mind Robotics is building Physical AI for real-world industrial deployment, starting with the factory floor. We believe the hardest problems in AI are solved when researchers and engineers are hands-on with the physical world every day - and we're looking for people who are passionate about robotics, value ownership, and are excited to tackle difficult problems. Join us if you want to move beyond digital intelligence and put intelligence into motion.
Mind Robotics is building robots that learn from real-world experience. That starts with a data engine: the pipelines and infrastructure that turn raw, messy, multimodal sensor streams from robots and human demonstrations into high-quality, well-curated training data at scale.
As a Data Infrastructure Engineer, you'll build and operate the pipelines that turn raw sensor and demonstration data into training-ready datasets — from ingestion off real robots and capture devices, through processing and quality filtering, to the dataloaders that feed model training. The systems work today; your job is to build within the architecture, take ownership of specific pipelines and services, and help harden the system as it scales.
Build and scale ingestion pipelines for high-volume, high-dimensional sensor data.
Build and maintain data quality and curation systems, including both manual review workflows and auto-labeling.
Contribute to storage and retrieval design for large-scale multimodal datasets, including format choices and versioning/lineage.
Build and operate distributed processing infrastructure (batch and streaming).
Debug production issues in live data pipelines — data corruption, schema drift, backpressure, and failures that only show up at scale.
Work with modeling/research partners to understand data quality, format, and structure needs, and translate them into working pipelines.
Participate in design and code review across the data infrastructure stack.
2+ years of software engineering experience, with some exposure to data pipelines, data engineering, or backend systems.
Strong programming fundamentals in Python, with the ability to write performant, production-grade data processing code.
Experience with at least one distributed data processing framework (e.g., Spark, Ray, Dask, or Flink), or strong fundamentals and willingness to ramp up quickly.
Familiarity with data storage concepts — object storage, data lake table formats, and warehouse vs. lake tradeoffs.
Bias for ownership: you've taken features or systems from prototype to production.
Clear communicator who collaborates well with research/modeling partners and more senior teammates.
Experience with workflow orchestration tools (e.g., Airflow, Dagster, Prefect) is a plus.
Experience with streaming ingestion for high-volume, near-real-time data is a plus.
Experience building automated data quality/curation systems (statistical filtering, anomaly detection, deduplication, or using ML models in an annotation/filtering pipeline) is a plus.
Experience with robotics- or embodied-AI-specific data (multi-embodiment datasets, teleoperation/demonstration data, egocentric video) is a plus.
New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 weeks.
Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.
We file this job under Data Engineer, by the work the posting describes.
Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.
Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.
An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.
The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
Palo Alto, California, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.