Open Roles

We're a small team with a specific problem.

If you've worked on real-time robotics perception, ROS 2 middleware, or logistics automation software — and you want to own a meaningful chunk of a hard problem — we'd like to talk.

Open positions

Robotics Perception Engineer
Austin, TX Full-time
C++ and Python proficiency; production-grade code in both
ROS 2 middleware experience; familiarity with Nav2 stack
LiDAR point cloud processing — sensor fusion, background subtraction, object tracking

Own the perception pipeline: sensor fusion, object classification, trajectory prediction. You'll be the primary maintainer of MV Perceive and drive the roadmap for new obstacle classes.

Apply via email
Robotics Software Engineer — Planning
Austin, TX Full-time
C++ with emphasis on real-time performance and deterministic behavior
Motion planning algorithms — A*, RRT, or similar graph search backgrounds
Robotics background — hands-on with real robot platforms, not just simulation

Own MV Plan: the modified A* planner, timing constraint solver, and risk tolerance configuration. You'll be working at the intersection of path planning and real-world operational constraints.

Apply via email
Integration Engineer
Austin, TX or Remote Full-time
Python — REST API development, MQTT, data transformation pipelines
ROS 2 basics — you don't need to be a robotics expert but need to read and write ROS 2 nodes
Experience integrating with fleet management or WMS systems a strong plus

Own MV Bridge: the REST and MQTT adapters, WMS connectors, and fleet API integrations. You'll be the person customers talk to when they need a new integration tested and shipped.

Apply via email

Why Mobvynt

You'll work on real robot deployments — not simulations. The code you write runs on AMRs in live warehouse environments. When you fix a classification bug, it shows up in the deployment logs within weeks.
The team is small enough that your code runs in production this quarter. There's no sprint backlog six months deep between you and the robots. You'll see your work deployed.
We're self-funded and growing at our own pace. No runway pressure, no pivot risk. We're building a software product that solves a specific problem well — and we intend to keep doing it.
Austin is a real robotics engineering community — active ROS community, UT robotics program, and a dense cluster of logistics automation operators and AMR companies. It's a good place to do this work.

How to apply

No ATS portal. Email [email protected] with the role name and two paragraphs: what you've built, and what problem you want to work on. We read everything. Short applications that are specific beat long applications that are generic.

[email protected]