Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Veeda Ai

Member of Technical Staff - ML Operations

  • Seen live on Veeda Ai's site today
  • Senior
  • Remote
Pay
Not stated
Location
Toronto
Open for
12+ days
First seen
Oct 23, 2026
Apply on Veeda Ai's site (opens in a new tab)

Posting record

No flags

Open 12+ days

The posting's record, oldest first
  1. Veeda Ai's site dates the posting
  2. Ghostless first sees this listing
  3. 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 Veeda Ai, so its true age is longer.

Last checked Nov 4, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What it asks of you

Bachelor's degree asked for
“Bachelor's degree or equivalent hands-on experience in Computer Science, Engineering, or a related technical field.” (quoted from the posting)

What the posting discloses

Not stated: Pay, 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.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

ABOUT US

Veeda AI is building the next generation of multimodal foundation world models for Physical AI. We're a small, fast-moving team of engineers and researchers from leading AI labs, tackling some of the most challenging problems at the intersection of AI, robotics, and embodied intelligence. If you're excited about pushing the boundaries of what's possible with Physical AI, you'll have the opportunity to make an outsized impact from day one.

RESPONSIBILITIES

  • Experiment Lifecycle Tracking and Tooling: Design, build and deploy tools that own how a run is defined, launched, resumed, and killed. Build and operate experiment databases for code version tracking, data version tracking, reproducibility, and checkpoint ancestry.
  • Inference Fleet Orchestration: Design, build, and operate the serving control plane that accepts large volumes of concurrent client requests and assigns them across inference clusters. Develop cache-aware admission, routing, batching, and scheduling policies that improve cache locality, balance workload, protect tail latency, and keep the fleet highly utilized and reliable. Partner with ML Performance on model runtime, kernel, and per-worker throughput optimization.
  • Model Evaluation in CI: Design, build, and operate automatic model checkpoint evaluation systems on seeded rollout and policy-success suites, run per-change and nightly.
  • Data Pipeline Operations : Design, build, and operate high-performance, fault-tolerant, distributed backend services and event-driven systems for our large scale data processing pipeline.
  • Visualization Platforms: Design, build, and deploy experiment observability and dataset visualization platform( s) that provides interactive data visualization, progress tracking, search, and comparison.
  • End-to-End Ownership: Lead projects through the complete software lifecycle, including technical specs, implementation, CI/CD, on-call support, and production observability.

REQUIREMENTS

  • Bachelor's degree or equivalent hands-on experience in Computer Science, Engineering, or a related technical field.
  • Proficiency in at least one scripting (Python or Bash) and one compiled (Java, Rust, or Go) languages.
  • Experience in shipping production-quality developer tools.
  • Proficient in CICD automations (pipelines, runners, deployment)
  • Experience in building reproducible pipelines end to end, and can say precisely which parts of a training run are bit-reproducible, which are not, and why.
  • One of the following:
  • Proven understanding of event-driven architecture, concurrency models, fault tolerance, and data consistency patterns.
  • Experience building or operating large-scale inference control planes or distributed serving infrastructure, with hands-on work in traffic management, admission control, request scheduling, routing, batching, or cache-aware load balancing; able to reason clearly about cache locality, queueing, tail latency, availability, and fleet utilization.
  • Experience working with multi-node workloads and building around slurm based scheduling systems.
  • Experience working on in-production model evaluation frameworks, in particular regression testing of large multimodal models.

NICE TO HAVE

  • You have run experiment tracking at scale, logging video, 3D, and trajectory artifacts rather than only scalars.
  • You have built evaluation harnesses for generative or embodied models, where quality is a distribution rather than a pass/fail.
  • Full stack development experience with web-based front-end.
  • You have orchestrated ML workflows with Argo Workflows, Flyte, or Ray, and know where each one breaks.
  • You have built GPU-hour attribution that maps cluster spend back to specific experiments and teams.
  • You have contributed to open-source ML tooling, or published on evaluation or reproducibility methodology.

Something wrong with this posting?