Pay
$166K–$237K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,537 postings in the last year. Stated ranges, not salaries paid.
United States · Remote · NYC · United States
Live, first seen by us 43 days agoLocation type: RemoteFrom the employer’s posting
Employment type: Full-timeFrom the employer’s posting
Department: EngineeringFrom the employer’s posting
Own models end to end: data, training, evaluation, and deployment
Build training pipelines for large multimodal datasets (video, sensors, language)
Get models into production with the Head of Engineering and CV team and keep improving them
Start with the simplest approach that works, then improve it
Build the tooling needed while moving between different problems
Own models end to end: data, training, evaluation, and deployment into our annotation pipeline.
Build training pipelines for large, multimodal datasets, including video, sensor streams, and language.
Partner with our Head of Engineering and the CV team to get models into production and keep them improving.
Start with the simplest approach that works, then make it better.
Move quickly between very different problems, and build the tooling you need along the way.
Will you now or in the future require visa sponsorship for employment in the United States?From the employer’s application form
We capture how humans actually interact with the physical world, at scale, and we build the ML systems that make every hour of that data more valuable.
In the employer’s words · Read in context
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
$166K–$237K is typical
The middle half of what similar US postings state. This one doesn’t list pay.
From 1,537 postings in the last year. Stated ranges, not salaries paid.
Day 43
Similar jobs usually come down between day 7 and day 76.
From 6,389 similar postings that came down. Coming down is not always a hire.
1 open job
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 industry of hands-on experience training deep learning models on real-world data, at a company, startup, or national lab. Earlier in your career is okay if your track record shows it. - Strong proficiency in Python and a modern deep learning framework such as PyTorch or JAX. - A solid grounding in ML fundamentals, including architectures, optimization, loss design, and evaluation.
Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.
Already applied? Track this application
Trace Labs is building the data infrastructure for physical AI.
Physical AI has the potential to transform how work gets done in the real world, from robotics to embodied systems that can see, move, and interact with their environment. But today, progress is held back by one big gap: there’s no scalable way to collect high-quality, real-world training data. Frontier robotics models are trained on far less data than language models, because there’s no “internet of robotics data.”
Trace exists to change that. We capture how humans actually interact with the physical world, at scale, and we build the ML systems that make every hour of that data more valuable.
We’re an early, deeply technical team. We move fast, we care about quality, and we believe the teams with the best data will build the best robots.
This role sits between ML engineering and research. You’ll bring strong ML engineering skills, a research mindset, and deep learning fundamentals to the hardest problems we see coming at Trace, then ship the answers into production.
You’ll work closely with our computer vision team, but this role is broader and more product-focused. You won’t live on one type of data. One month you might be working with sensor signals, the next with hand tracking video, the next with language. What matters is getting a high-quality model working fast and putting it to use.
We care much more about what you’ve built and shipped than where you’ve published. If you’re earlier in your career but have a clear track record of moving fast and owning hard problems, we want to talk.
Own models end to end: data, training, evaluation, and deployment into our annotation pipeline.
Build training pipelines for large, multimodal datasets, including video, sensor streams, and language.
Partner with our Head of Engineering and the CV team to get models into production and keep them improving.
Start with the simplest approach that works, then make it better. Pull from recent papers when they help you ship, not as the end goal.
Move quickly between very different problems, and build the tooling you need along the way.
A BS in Computer Science, Electrical Engineering, Mathematics, Aerospace, or a related field, or equivalent practical experience. An MS is a plus, not a must.
2+ years of industry of hands-on experience training deep learning models on real-world data, at a company, startup, or national lab. Earlier in your career is okay if your track record shows it.
Strong proficiency in Python and a modern deep learning framework such as PyTorch or JAX.
A solid grounding in ML fundamentals, including architectures, optimization, loss design, and evaluation.
Comfort with messy, real-world data such as video, time series, or sensor streams.
An extraordinary bias toward shipping. You go from idea to working model fast, and you make good calls under uncertainty.
High agency. You find the problem, own it, and get it done without waiting to be told.
Range. You’re excited to work across different kinds of data and problems, not just one narrow specialty.
A foundational problem. The data layer for physical AI is still being defined. You’ll help define it.
Data at scale from day one. We have the resources to collect it. Your job is to make it count.
Real ownership. Your models ship into production and directly shape what our data can do.
Room to grow. Go deeper into ML, take on bigger systems, or both.
New ML Engineer postings at the employers we follow are down 4% 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 ML Engineer, by the work the posting describes.
ML engineers put machine learning models into products. They write the code that trains, ships, serves and monitors models so a recommendation or prediction works for real users.
Postings ask for strong Python and software engineering, a framework such as PyTorch, cloud services, and more and more often experience with large language models.
A data scientist often works out which model to build; an ML engineer makes it run reliably in production.
The government has no code for ML engineers, so these figures are for the closest group, computer and information research scientists.
Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1221.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
No pay amount identified in the saved description.
United States
Working pattern and location restrictions need checking in the full posting.
No clear work-authorization passage found. Eligibility is unconfirmed.