Pay
$127K–$189K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,448 postings in the last year. Stated ranges, not salaries paid.
San Francisco · San Francisco, California, United States
Actively hiring, first seen by us 3 days agoLocation type: On-siteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: SoftwareFrom the employer’s posting
Own the data platform end to end, from on-device capture to training-ready shards
Balance codecs, compression, and storage tiers so 1080p30 video stays affordable to collect
Build uploads that survive bad networks, with buffering, batching, retries, and visible drop rates
Own dataset packaging, versioning, and delivery to external research customers
Get new devices onto one ingest contract with Shenzhen firmware teams
Own the data platform end-to-end: on-device capture, upload under flaky bandwidth, object storage, training-ready shards
Compression, codecs, and storage-tier trade-offs so 1080p30 hours stay cheap enough to keep collecting
Upload that survives bad networks: on-device buffering, batching, retries, a drop rate you can actually see
Own dataset packaging, versioning, and delivery to external research customers
Work with Shenzhen firmware so new devices speak one ingest contract, not a custom path per SKU
From the employer’s posting.
Build AI is the data hyperscaler for Physical AI.
In the employer’s words · Read in context · Company website ↗
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$127K–$189K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 2,448 postings in the last year. Stated ranges, not salaries paid.
Day 3
Early. Similar jobs usually come down between day 6 and day 56.
From 14,770 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.
- That kind of data path: Tesla Autopilot, Waymo, Cruise, Zoox, Nuro, Samsara, Verkada, Netflix encoding, YouTube ingest, Scale, or Eventual/Daft. Demo-scale ETL is not this job - Strong software engineering. Python and at least one systems language. Linux - You measure cost and throughput, not whether the demo uploaded
- Pose, multi-camera, or other large media besides video - Cloud (AWS or GCP), orchestration (Kubernetes, Airflow, Temporal), or IaC - Dataset management or annotation tooling
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Build AI is the data hyperscaler for Physical AI. We're vertically integrated across hardware, manufacturing, logistics, collection, and model training to scale the physical labor dataset orders of magnitude faster than anyone in the world.
We’re hiring a lead for the data platform: camera on a worker to training-ready datasets, and out to research customers. Collection is monocular 1920×1080p 30fps in the wild, targeting 100M hours. The roles we mean: Tesla Autopilot, Waymo, Cruise, Zoox, Nuro, Samsara, Verkada, Netflix encoding, YouTube ingest, Scale, Eventual/Daft. This is not a warehouse, analytics, or generic backend seat.
Own the data platform end-to-end: on-device capture, upload under flaky bandwidth, object storage, training-ready shards
Compression, codecs, and storage-tier trade-offs so 1080p30 hours stay cheap enough to keep collecting
Upload that survives bad networks: on-device buffering, batching, retries, a drop rate you can actually see
Object storage and training-shard formats. The hard problem is petabyte-scale media, not a warehouse
Own dataset packaging, versioning, and delivery to external research customers
Work with Shenzhen firmware so new devices speak one ingest contract, not a custom path per SKU
Make health, cost, and drop rate obvious as we add sites and countries
You have owned a production media or sensor data path at real scale: object storage at petabyte scale, video codecs and compression, upload under flaky bandwidth, or training-shard / dataset formats
That kind of data path: Tesla Autopilot, Waymo, Cruise, Zoox, Nuro, Samsara, Verkada, Netflix encoding, YouTube ingest, Scale, or Eventual/Daft. Demo-scale ETL is not this job
Strong software engineering. Python and at least one systems language. Linux
You measure cost and throughput, not whether the demo uploaded
You want to scale in-the-wild physical-labor video, not run a generic data org
Pose, multi-camera, or other large media besides video
Cloud (AWS or GCP), orchestration (Kubernetes, Airflow, Temporal), or IaC
Dataset management or annotation tooling
You have shipped dataset delivery to external research or training customers
Competitive pay
Medical, dental, and vision packages with generous premium coverage
$500 per month credit for waiving medical benefits
Housing subsidy of $2k per month for those living within walking distance of the office
Relocation support for those moving to San Francisco (Financial District) or Shenzhen (Nanshan)
Various wellness benefits covering fitness, mental health, and more
Daily lunch and dinner in our office
Unlimited compute budget subject to ROI justification
Unlimited Codex and Claude credits
Travel
Build believes in the Bitter Lesson. By taking a general approach of learning from humans, our addressable market is all physical labor.
We are a fully in-person team in San Francisco (Financial District) and Shenzhen (Nanshan), and greatly value engineering skills. We do not have boundaries between engineering and research, and we expect all of our technical staff to contribute to both and work across disciplines as needed.
Build AI is an equal opportunity employer. We review every application. If you do not meet every bullet, still apply. Questions: research@build.ai
New Data Engineer postings at the employers we follow are up 13% 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.
San Francisco, California, United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.