Design Engineer

Do you have experience in Robotics?, * A user-testing instinct. You set up tests cheaply, observe carefully, and update your views based on what you see.

• A preference for prototyping over speccing. You would rather build the thing than describe it.
• Strong frontend skills in React. You can ship a usable, accessible interface on your own.
• Comfort working alongside engineers without becoming one. Design judgment remains your centre of gravity.

Nice to have

• Experience designing for robotics, teleoperation, real-time systems, or other operator-in-the-loop products.
• Familiarity with API or backend integration, enough to wire your prototypes to real data.
• Experience with WebXR or other immersive interface work.
• A maker streak: side projects, hardware tinkering, or anything you built because you wanted it to exist.

We are looking for a Design Engineer to own our teleoperation and operator-facing interfaces from end to end. That means working from sketches and flows, through a working React prototype, into user tests with real operators, and onto the version that ships. You think in terms of interactions and tasks rather than tickets, and you would rather put a rough thing in someone's hands than ship a polished thing nobody uses. This is a different kind of hire from the rest of our team: a designer who codes, rather than an engineer who dabbles in design. Show and tell is part of the job. We demo organically every one to two weeks, and we hire for people who naturally build toward something visible. You will be part of a fast-growing cutting-edge robotics and AI team looking towards developing solutions to real world problems. What you'll do * Own the design of our teleoperation, data-collection, and operator interfaces, including flows, interactions, and visual language. * Prototype your designs in React (or whatever is faster) and ship the ones that work. You will not hand off to engineering for this surface; you are the engineer for it. * Run user tests with operators and customers. Iterate quickly based on what you observe rather than what people say. * Push back on requirements when the right answer is a different interface than the one specified. * Help shape what we build next. If a workflow is painful, you should be the person who notices and proposes the fix.