Job seeker
Working at Hybot
Hybot does not advertise vacancies it has not opened. This page explains how we hire, what the work involves and how to send a speculative application. If a role is open it will be described here with its location and closing date; if nothing is listed, nothing is open, and a speculative note is still worth sending.
No listings you cannot apply to
Some companies keep evergreen job adverts running to harvest CVs. We do not. If a role is open, it will be on this page with its location and closing date. If nothing is listed, nothing is open — and that is information, not an oversight.
A speculative application is still worth sending, and the section below says what makes one easy to act on.
What the work actually is
Software that moves physical machines around rooms containing members of the public. That has some specific consequences for what your week looks like.
Integration across robot vendors. There is an abstraction layer with per-vendor adapters behind it. Adapters are where the reality lives: inconsistent APIs, partial state, and hardware that has its own opinion about what just happened.
Real-time state. Robot position and status are broadcast over WebSocket as they change, not polled. Anything that is late is wrong.
Tooling for people under pressure. The staff interface is used mid-service by somebody carrying something. It is not a dashboard to be admired; it is a control surface to be jabbed at while distracted.
Failures that only happen on one floor. Real venues produce bugs that do not reproduce anywhere else. Being comfortable with that is close to a job requirement.
How to send a speculative application
Be specific. The applications that get a real reply have three things:
- What you want to work on — a problem area, not a job title.
- Something you have built, fixed or shipped that we can look at.
- Where you are, and whether that is negotiable.
Send it through the contact page and say it is an application. We read them, and we will answer.
How hiring works here
A conversation about what you have actually done. A technical discussion grounded in problems from this domain rather than algorithm puzzles. A conversation about how you work with other people. We will tell you the shape and the rough timeline at the start.
Whether a particular role can be done remotely depends on the role — some of this genuinely requires you to be near a robot — and we will say so in the role rather than advertising flexibility we then withdraw.
Where to go next
Other audiences: developers, investors, operators.
Frequently asked questions
Are there open roles right now?
- If a role is open it appears on this page with a real location and a real closing date. If you see no listing, there is no vacancy. We do not post roles to collect applications, because it wastes the applicant's time and tells you something unflattering about the company.
Is a speculative application worth sending?
- Yes, if it is specific. Tell us what you want to work on and show us something you have built or fixed. A general note asking whether anything is available is much harder to act on than a short message about a particular problem you want to solve.
What does the work actually involve?
- Software that controls physical machines in places where members of the public are standing. That means integration work across robot vendors, real-time state, operational tooling for people under time pressure, and debugging problems that only reproduce on a particular floor.
What is the hiring process?
- A conversation about what you have done, a technical discussion grounded in real problems rather than puzzles, and a conversation about how you work with others. We will tell you the shape and rough timeline at the start rather than leaving you guessing.
Do you hire remotely?
- It depends on the role, because some of this work needs you physically near a robot. We will be clear about that in any specific role rather than advertising flexibility in general and withdrawing it at offer stage.
Where this fits
This page is part of Hybot for every audience. If you are working through the topic in order, these are the neighbouring pages.
Build on Hybot: the developer's view
A REST and WebSocket API over a real robot fleet: dispatch to a point of interest, create tasks, stream live state, and integrate with a vendor-agnostic robot layer.
Hybot for investors
What Hybot is, what has actually been built, and what we will not claim. An honest starting point for an investor conversation rather than a pitch deck in web form.
Service robots for business operators
For the person who has to justify the spend: what a Hybot deployment actually involves, what we can measure, and the questions to ask before you sign anything.
The next step from here
One conversation, routed to the person who can answer it rather than to a general inbox.