By Pablo Revale

The Hire That Doesn’t Exist

Your hotel tech role has been open five months. It isn’t the salary. The market is short of something you can’t write into a job description.

July 31, 2026 · 6 Minutes

THE REQ THAT WON’T CLOSE

A VP of Marketing at a management company told me her senior full-stack role had been open since February. Good candidates. Strong CVs. Not one of them had shipped anything that touched a property management system. She raised the band twice. The role is still open. This is not the labor shortage the industry talks about. AHLA reports 65% of surveyed hotels running staffing shortages, and the WTTC projects a hospitality workforce shortfall of 8.6 million people by 2035, but those numbers describe housekeeping, front desk, and food and beverage. The technology version is narrower and worse. Skift found in 2026 that travel carries the widest AI skills gap of any major sector, driven partly by how few people the industry hires to guide technical change. You are not competing with other hotels for this person. You are competing with fintech, with logistics, with every vertical that pays more and ships against a cleaner data model.

WHAT YOU’RE ACTUALLY SHORT OF

Developers are not scarce. Developers with hospitality encoded in them are. The difference shows up in practice. A senior engineer joining your team has to learn that availability, rates, and inventory move as one message and not three. That your PMS is the source of truth for the folio and almost never for rate. That the CRS owns rate and the channel manager only mirrors it. That parity is a contractual constraint expressed in code. They have to learn that a reservation message is not a create, it is an upsert with an idempotency key, because the same message will arrive twice and the second one must not produce a second booking. That a group block is not thirty reservations. That extending a stay at a different rate does something specific to a folio. None of that is on a CV, and none of it is teachable in a sprint. In our experience a competent senior needs four to six months before they stop making decisions that pass code review and are wrong in a hotel. You pay full salary for that window, and you pay it while the season you were building for goes past.

THE 63% THAT EXPLAINS THE JOB POST

Skift Research’s Hotel Technology Priorities 2025 found that 63% of hotel technology budgets still go to maintaining legacy systems, many of them not AI compatible and unable to support complex data integration. Around 30% of IT budget reaches new implementations, while 86% of hoteliers say they plan to increase technology investment. Read those three numbers together and the job post makes sense. You are not hiring someone to build greenfield. You are hiring someone to build new revenue surface on top of a stack whose integration points were never designed to carry it. Deloitte found 54% of hoteliers believe the technology available to them cannot meet what guests now expect. That is the room you are asking a new hire to walk into on day one, usually without a systems diagram, because nobody ever drew one.

THE KNOWLEDGE ISN’T IN THE PERSON. IT’S IN THE SEQUENCE.

Here is what almost nobody scopes when the answer is a hire. The first thing a new engineer does is archaeology. Which system owns rate today. Which integration is actually a nightly CSV that someone renamed to look like an API. Which of the four places a guest email is stored is the one marketing sends from. That work is unbudgeted and produces no shippable output, so it reads as a slow start rather than as the necessary first deliverable. Then, when that person leaves, the map leaves with them, because it lived in their head instead of in a repository. A single senior hire concentrates all of your domain knowledge into one employment relationship. That is a reasonable bet for a company whose product is software. For a hotel group whose product is a stay, it is an odd place to put the risk.

THE NIGHT AUDIT PROBLEM

The second unscoped item is when hotel software actually fails. A generic engineer tests on a Tuesday afternoon and sees green. Hotel state changes at night audit, and that is where the interesting defects live: the rollover that posts a room charge to a folio which closed a second earlier, the stay spanning a daylight saving change that now reports a length of stay of zero, the month end that runs while a channel manager retry is still in flight. None of those reproduce in a normal QA pass, because a normal QA pass does not know to advance the business date. A second constraint follows from it. You cannot roll back a reservation. In most software a bad deploy is a revert. In hospitality, a bad deploy has already sent a confirmation to a guest who is now standing at a front desk, and the compensating action is human.

WHAT WE DO INSTEAD

Unique Vacations, the company behind Sandals and Beaches, was running two separate apps, one iOS and one Android, so every feature was built twice. We visited the properties, migrated both into a single React Native product with a rebuilt UX, and put the new codebase into production in under four months across 19 properties in 9 countries. It now carries around 16,000 daily user interactions. We did not learn what a folio was during that project. We released it by ramping a small segment of traffic and increasing it while watching performance and feedback, because the alternative on a guest facing app at that volume is not a rollback, it is a support queue. On their website, the platform was not the only deliverable. We migrated more than 500 pages to a headless CMS with about 100 coded components, on a site serving over a million monthly users, then trained their marketing team to ship content without us. That last part is what answers the hiring problem. The point of bringing in an outside team is that your team ends up able to do the work, with the map written down, not that you swap one dependency for another.

IF THE ROLE IS STILL OPEN

The fastest path to shipping is usually not a better job post. Send us the systems you have and what you are trying to launch. We will tell you what we would build, what we would not, and what your own team should own by the end of it.