Hiring

Build the runtime for robots in public spaces.

We're hiring across the engineering stack — perception, robotics, platform, and forward-deployed. Senior in one area, curious about the rest. Real roles, real customers, real pipeline. Open positions are listed below.

01 · Where we hire

Four areas. Senior in one, curious about the rest.

We don't post role-by-role descriptions because the shape of each hire depends on who shows up. If your work fits one of these areas and you're ready to move fast, write to us.

A · Perception & ML

Perception & Machine Learning

You build models that handle real cameras, real lighting, real motion. You've worked on representations that survive distribution shift, not just benchmarks. You can read a foundation-model paper on Friday and ship a small variant by Monday.

VLM / VLA Computer vision Real-time inference Edge deployment
B · Robotics & Field Systems

Robotics & Field Systems

You've shipped software onto a moving robot and watched it handle a sidewalk, a lobby, or a doorway it had never seen before. You think in sensors, latency budgets, and failure recovery. You can debug a perception bug from a video clip and a log file.

ROS / ROS2 Sensor fusion Field debugging SLAM / nav
C · Platform & Infrastructure

Platform & Infrastructure

You've built data and inference pipelines that hold up across thousands of robots and millions of frames. You care about the boring problems: observability, replay, evaluation harnesses, deployment safety. You believe infrastructure is product.

Distributed systems Data pipelines Eval & observability Deploy safety
D · Forward-Deployed Engineering

Forward-Deployed Engineering

You're an engineer who's comfortable inside a customer's operations as much as a codebase. You ride along, you watch fleets fail, you write the integration that turns a pilot into production. You've done this at one company; you want to do it at a better one.

Customer integration Fleet operations Onsite work Pilot → prod
02 · How we work

Small team. Real customers. Fast feedback loops.

03 · Be honest with yourself

This team is a great fit for some engineers and a bad one for others.

We'd rather you self-select out now than three months in. Read both columns. If the left feels like home and the right feels like friction, write to us.

You'll thrive if

  • You like shipping software that runs on a real robot at a real customer's site by the end of the quarter.
  • You read a paper because you want to use it, not cite it.
  • You've built things that broke in the field, and you came back smarter.
  • You have a strong opinion about an existing approach in robotics or perception — and you can defend it.
  • You want equity that means something at exit, and you're prepared to wait a few years for it.

You'll struggle if

  • You want a clearly scoped role with a 30-60-90 plan handed to you.
  • You prefer research over shipping. We love research, but we're a company.
  • You want every problem solved on a whiteboard before code is written.
  • You need formal job titles, fixed teams, and a stable org chart before quarter two.
  • You're allergic to talking to customers, debugging in the field, or sitting in a van for three hours watching a fleet operate.

Ready? See open roles.

Every role we're hiring for, every one we're closing soon. Apply through our applicant tracking system — we read every application and we respond within a week.

View open roles
Don't see your role? Tell us anyway →