Careers
Working at Hyrcan-Tech
There is no advertised vacancy list here. Rather than publish roles that do not exist, this page describes the work honestly — robot integration, fleet software, venue-facing interfaces and deployment — and accepts speculative applications against it. A message showing what you have built beats a form.
The four kinds of work
These are the areas the product is actually built from. They are described here so a speculative application can name one rather than guess at what we need.
Robot integration
- Making a physical robot from a third-party manufacturer behave like an ordinary participant in the task queue: state, position, battery, errors and command acknowledgement, behind one abstraction so the rest of the system never learns which vendor built it.
Fleet and platform software
- The assignment loop that re-scores the queue every two seconds against priority, distance and battery; the heartbeat monitoring that tells us a site has gone quiet; and staged rollout so one project takes a release before the estate does.
Venue-facing interfaces
- The screens staff use every shift and the surfaces guests touch — kiosk ordering, table QR menus, on-robot surveys. These are judged on whether a busy person can use them without training, which is a harder constraint than it sounds.
Deployment and operations
- Surveying a venue, aligning a floor plan to the robot's own map, configuring points of interest, training staff, and being the person who works out why a robot stops at the same doorway every time.
How hiring works here
A conversation about what you have built, a technical discussion grounded in the actual system rather than in puzzles, and a conversation about the work you would own. We do not run timed exercises against problems the team has never had to solve.
The honest caveat: this is a small team building a physical product, so hiring happens when a gap becomes unavoidable rather than on a schedule. A speculative application is read when it arrives and remembered when a gap appears.
If you want to understand the system before applying, the developer-facing page describes the architecture and the platform overview explains the three layers you would be working inside.
Frequently asked questions
Why are no open roles listed?
- Because none are currently advertised, and listing invented vacancies to appear larger is both dishonest and, in structured data, a policy violation. When a real role opens with a real location and start date, it will be listed properly.
Is a speculative application actually read?
- Yes, and in a team this size it is the normal route in. What makes one useful is specificity: which of the areas below you want to work on, and evidence of something comparable you have already built or run.
What should I send instead of a CV?
- Something inspectable. A repository, a system you can explain in detail, or a deployment you personally got working. For this kind of work that demonstrates far more than a list of technologies on a document.
Do you hire for deployment roles as well as engineering?
- The deployment work — surveying venues, aligning floor plans, training staff, diagnosing live sites — is a distinct discipline from writing the software, and it is at least as decisive in whether a customer succeeds. Both are described below.
Send a speculative application
Name the area you want to work on and show something you built. That is more useful than any form we could put here.