Posting record
Open 17+ days
- Trace Labs' site dates the posting
- Ghostless first sees this listing
- Last checked: still up
How we know
It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.
Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Trace Labs, so its true age is longer.
Last checked Nov 3, 2026.
How well do you match?
See how much of this posting your resume shows, and what it's missing.
Upload your resumeWhat it asks of you
- Equivalent experience accepted instead of a degree
What the posting discloses
- Pay
- $185k to $245k a year USD
Not stated: Real vacancy, AI screening.
Why these three
Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.
Skills mentioned
About the role
About Trace
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.
The role
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.
What you will do
- 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.
What we're looking for
- 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.
Why Trace Labs
- 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.
Something wrong with this posting?