Careers

Build the future of workforce management.

ScanRoster is a small, remote-first team building AI-native workforce management for hospitality. What we ship is used mid-service, on a phone in an apron pocket, ninety seconds before a room fills up. That constraint decides most of what we build and most of how we work.

Introduce yourself What we are building

Remote-firstSmall teamCustomers across time zones

What the work is four inputs · one product

People

The person on shift, not the person who signed the contract.
Workforce

Rosters, cover, breaks, hours and what they cost.
AI

Two jobs it does better than a person at 6am: cover and demand.
Engineering

TypeScript end to end, Postgres underneath, offline when the wifi drops.

What comes out

A shift that gets coveredbefore service
Hours nobody has to argue aboutverified at the door
A pay run that reconcilesfrom the same record

What we are building

One product, from the scan at the door to the pay run

Not a suite, not a platform with modules bolted on. Attendance, rostering, cover, compliance and payroll are one path through one system, which is why nobody here owns a narrow slice of it.

The product

What is live, and what the roadmap is actually about.

AttendanceA rotating QR code, a geofence and a registered device have to agree before a scan counts.
CoverWhen a shift goes uncovered, qualified staff are ranked and asked, instead of a manager working down a group chat.
RosteringShifts shaped around real demand, with the constraints of split shifts and casual contracts built in.
ComplianceCountry rules checked before a roster is published, not after a payroll query.
PayrollVerified hours, overtime and breaks exported in the shape a pay run expects.

The stack

No mystery to it, and no fashion in it either.

Front endNext.js and React in TypeScript, installable as a PWA for the phone in the apron pocket.
APIFastify and Prisma over Postgres, in TypeScript, with row-level security doing tenant isolation in the database rather than in a middleware.
OfflineA scan taken with no signal is queued on the device and flushed by a service worker when there is one.
IntegritySigned rotating tokens, device binding and a server clock that decides, because the device clock is not trusted.
AIRanking and forecasting where search genuinely beats a human under time pressure. Everywhere else it stays plain software.

Why ScanRoster

Four reasons the work here is different

Not benefits and not a culture deck. These are properties of the work itself, and they are the honest reasons somebody would pick this over a larger, calmer product.

AI with a job, not a label

It earns its place in exactly two spots, finding cover for a no-show and shaping shifts around real demand, because those are search problems a person cannot do well at 6am. Deciding what does not get a model is part of the work here.

Problems that bite the same day

A rota that nobody trusts costs a venue a service, not a quarter. You will see the consequence of what you shipped inside a week, from the people living with it, in plain language.

Wide surface, small team

Attendance, rostering, matching, payroll and compliance are one product. You own a path through it end to end rather than a component, and nobody is shielded from the parts that are hard.

Global from the first line

Multi-country compliance, multi-currency payroll and venues in time zones that do not overlap ours are not a later phase. They are constraints on the schema you write this week.

How we work

Three things that are true of every role here

Worth knowing before you write to us, because they are not negotiable and they do not suit everybody.

The product is used, then decided

Features arrive because an operator hit a wall, not because a competitor's brochure had a gap. You will spend real time with the people whose shift depends on what you shipped.

Written, so nobody is behind

Decisions get written down and argued in text. The person who reads them tomorrow, eight time zones away, should not be at a disadvantage to the person who was awake for the call.

Small enough to answer for it

There is no layer between the person who builds something and the person who has to explain it to a customer. Usually they are the same person, and that is the point.

Open positions

What is open right now

This list is generated by nothing. It is the honest state of hiring at a company this size, and it changes.

No open positions right now

We would rather show you an empty list than a list we cannot hire against. There are no live vacancies today, and there is no pipeline you are quietly being added to.

That does not make an introduction a waste of your time. Tell us what you would want to own and what you have built, and it stays on file until a role opens that genuinely fits. These are the areas we expect to need first:

Product engineering Product design Hospitality operations Customer support

Checked 29 August 2026 · this page is updated when that changes

Introduce yourself Meet the team

Get in touch

No role listed is not the same as no interest.

Send us what you have worked on and what you would want to own here. It reaches the people who build the product, and we answer it ourselves.

Contact the team About ScanRoster