Careers

We hire rarely.
When we do, it
changes the company.

There are no open roles today, and we would rather say so at the top of the page than behind a button. The letterbox still works, and a person reads what comes through it.

NO ROLESOPEN TODAYthe slotstill works

What makes it different

It is running at a curb right now.

This isn't a dashboard nobody opens. Valletto is in live valet operations while you're reading this, which changes what counts as a bug.

Time cardPayout

A guest is standing there

A slow retrieval isn't a latency metric. It's somebody waiting in the rain outside a restaurant.

It's somebody's car

A session that loses track of a vehicle is a real BMW in a real garage that nobody can find.

It's somebody's paycheck

Get an overtime rate wrong and a valet is underpaid on Friday. That is not a rounding error to them.

It's somebody's money

Payments settle into operators' own accounts. A billing mistake shows up on a real statement.

The surface

Unusually wide for
a team this size.

Our work connects the arrival lane and the back office. People often work across several parts of the product in a week. Breadth here is the job, not a stretch goal.

In the lane

  • An app for the valet’s iPhone
  • Live Activities on the lock screen
  • An app for Android teams
  • Plate and vehicle recognition

On the web

  • Operator console
  • Admin HQ
  • Partner portal
  • Guest checkout and resident portal

Underneath

  • Reliable service throughout a shift
  • Current information across locations
  • Payments and payouts
  • Consistent pricing across the operation

All of it is live. None of it is a side project.

Native apps for the lane
Web tools for the office
One shared pricing model

How we work

Written down, shipped often,
AI-native for real.

Not a manifesto. Just the parts that would actually change your day.

IMPROVEMENT · a clearer check-in+++++reviewed by a personStand 2 · on shiftTicket 42Acura TLX · parkedTicket 43Ford Bronco · requestedRetrievethis pageincluded

Written down, not discussed

Decisions land in documents and commit messages. Why a thing is shaped the way it is gets written down where the next person will hit it, so the reasoning outlives whoever wrote it.

Learn from the people using it

We listen to operators, test our work, and follow through when something needs to improve.

You'll ship in week one

You will work on something operators need, with clear ownership and help from the people who know the product.

Who you would be writing to

Their names are
already on this site.

Real faces, real profiles, and no careers portal in between. There is no recruiter here to get past, because there is no recruiter here.

Equity, early. Small team, early stage. We'll tell you the actual numbers in the first conversation rather than after four rounds.

If you want to be first in line

Send something
you built.

Not a CV summary of it. The thing itself, and a paragraph on what was hard about it and what you'd do differently. That tells us more in two minutes than a screening call does in thirty.

  • A repo, a shipped app, a teardown, a post. Anything you actually made
  • What broke, and what you changed because of it
  • Which part of the surface above you'd want to own

If there's a fit, you'll hear back from a person. If there isn't, you'll still hear back.

A real person reads it. No tracking number, no portal.