We are hiring.
Small team, early stage, and a product that is already running on real devices rather than sitting in a deck. There are 4 roles open at the moment, and of those 4, mobile engineering and machine learning are the two that decide whether any of the rest of it matters.
Open roles.
Roles can be full time, part time or contract, and we would much rather shape the arrangement around the right person than lose them to a technicality about hours.
Engineering
Mobile engineer, iOS focus
This is the hardest role on the list, because background execution on iOS is the single constraint the entire product lives or dies on: the app has to keep sampling when it has been backgrounded or killed outright, buffer what it collects while there is no reception at all, and still leave enough battery in the phone to get through a 10-hour shift on a site where nobody has a charger. Android matters just as much commercially and you would own both, but it is iOS that keeps the architecture honest.
Engineering
Backend engineer
You would own ingestion, aggregation and the multi-tenancy that has to hold together when the second and third customers arrive rather than only the first, and you would own the test suite and the deployment pipeline as well. The service is Node and TypeScript on a managed MongoDB cluster, organised feature by feature with a consistent pattern applied across all 11 of them, so what you would be joining is a tidy codebase that needs depth rather than a rescue job that needs a rewrite.
Design
Product designer
There are two users here with very nearly opposite needs, and the product only works if both are served properly rather than one being treated as an afterthought. On one side is a worker who has to understand the app and decide to trust it inside about 30 seconds, standing in full sun with gloves on and one bar of reception. On the other is a site manager who wants the whole day legible in a single glance before the crew starts at six.
Engineering
Artificial intelligence and machine learning engineer
This is the core bet of the whole company, which makes it the role with the most room in it and the least already decided. You would take raw motion data and turn it into a classifier that reliably beats the hand-tuned thresholds the product ships with today, and then build the layer on top of it that reads a weather forecast and works out which crews should start earlier, start later or not start at all. The dataset that would make this possible does not exist anywhere yet.
None of these quite you?
Get in touch anyway. Roles here get shaped around the person, because at this stage the shape of the team is still genuinely open and the right person is worth a great deal more than the right job title. If what you do sits next to one of these descriptions rather than inside it, that is a conversation worth having rather than a reason not to write.
Experience with workforce management, rostering or field service platforms is genuinely useful here, and so is any real insight into how outdoor industries actually run, whether that came from building software for them or from working in them.
We will also be hiring well beyond this list as the pilots turn into customers, and go-to-market in particular, meaning sales, partnerships and customer success, because a product like this one does not sell itself to a site manager who has never heard of it.