What Do Hotel Receptionist Interviews Actually Test?

Who's actually in the room

For an independent hotel or a small group, you're usually talking to the Front Office Manager or the General Manager directly — sometimes both, sometimes in one sitting. In a branded chain (Marriott, IHG, Hilton, Accor), the first stage is often an HR or Talent Acquisition screen, followed by a second interview with the Front Office Manager or Duty Manager who will actually be your line manager. Budget and limited-service properties tend to compress this into one meeting because there's no separate HR function on site.

The person interviewing you almost always still works or has recently worked the desk themselves. This matters: vague answers get noticed immediately, because they know exactly what a normal Tuesday afternoon at check-in looks like and what a genuinely difficult one looks like.

The practical bit: what gets tested beyond conversation

Many hotels — especially anything above budget tier — build a practical element into the process, even if it's informal. This can take a few forms:

• A mock check-in or check-out, sometimes at an actual PMS terminal if you claim system experience. If you've listed Opera (Oracle Hospitality), Opera Cloud, Protel, RoomMaster, Mews or Cloudbeds on your CV, expect to be asked to walk through a booking, a rate change, or a folio split, not just asked whether you "know" the system. Saying you're "familiar with Opera" when you've only seen it over someone's shoulder falls apart in about thirty seconds at the keyboard.
• A role-play scenario, usually delivered as "I'm going to be a guest, you're on the desk." Common setups: a guest arrives with no reservation on a sold-out night; a guest insists they booked a king room and the system shows a twin; a guest wants to check out but disputes a minibar charge; a non-English-speaking guest at a busy check-in. These aren't testing whether you're polite. They're testing sequence and judgement — do you check the PMS before you argue, do you involve the duty manager at the right moment, do you offer a resolution before the guest has to ask for one.
• A phone or switchboard simulation, particularly for hotels where reception also handles the main line and internal transfers. They're listening for whether you can take a message accurately, transfer correctly, and not lose a caller mid-transfer.
• A cash/float question, sometimes practical, sometimes verbal: how you reconcile a float at shift change, what you do if it's short, how you handle a card that's declined at checkout. If the hotel takes PCI compliance seriously (most branded properties do, because of card data handling audits), they may ask directly how you'd handle a guest reading their card number aloud at the desk versus using the terminal.

If a hotel skips all of this and only asks generic questions, it's worth noting — it can mean a lower-scrutiny operation, or it can just mean the interviewer trusts the CV and references to do that work instead.

The questions that are really testing something

A few questions come up constantly in front-desk interviews, and each one is standing in for something specific:

"Walk me through what you'd do with a guest who arrives and their room isn't ready." This is testing whether you understand the mechanics of housekeeping status codes (dirty, clean, inspected) and whether you know to offer a concrete alternative — luggage storage, a drink at the bar, an accurate time estimate — rather than just apologising. A shallow answer stops at "I'd apologise and explain it won't be long." A real answer names what you'd actually check first: the housekeeping board, whether an upgrade is available, whether the guest has a flight or event to work around.

"Tell me about a time you had to deal with an overbooking." This is one of the most occupation-specific scenarios there is, and it separates people who've actually worked a busy desk from people who haven't. A shallow answer is "I found the guest another room." A real answer talks about walking the guest to a sister or partner property, who authorises that (usually the duty manager, not the receptionist alone), what compensation policy applies, and how you handle the guest's frustration while that's being arranged — because overbooking situations are rarely resolved in under ten minutes and the interviewer knows that.

"How do you handle upselling at check-in?" Hotels with any commercial pressure — which is most of them — care about this because upgrade and late-checkout revenue is tracked, sometimes per receptionist, sometimes as a team target. A shallow answer is "I always try to upsell." A real answer describes reading the guest first: someone arriving for a one-night business stay is a different upsell conversation from a couple on their anniversary, and pushing the same script at both is what gets upselling switched off as a KPI in the first place.

"What would you do if the PMS went down during a full check-in queue?" This tests whether you know the manual fallback — paper registration cards, a manual key allocation log, checking ID and payment by hand — and whether you know when to call it up the chain rather than freelancing a workaround. Anyone who's worked a system outage during a conference check-in has a specific story here. Anyone who hasn't tends to say "I'd stay calm," which answers a question nobody asked.

"Tell me about a guest complaint you couldn't resolve yourself." This one is deliberately about escalation, not resolution. Hotels want to know you understand the line between what a receptionist can authorise — a room change, a late checkout, a small comp like breakfast — and what needs the duty manager or GM, such as a refund, a rate dispute, or anything involving a repeat complainer. Claiming you resolved everything yourself, every time, reads as either inexperience or a receptionist who overrides management authority, and neither is what they're hiring for.

What a shallow answer sounds like from the inside

Someone who's run a front desk can hear the difference within a sentence or two. Shallow answers tend to:

• Describe the feeling ("I stayed calm and professional") without describing the sequence (check the system, offer options, involve the duty manager, follow up).
• Talk about guest service in the abstract — "I always put the guest first" — rather than naming a specific tool, code, policy, or person involved. Real front-desk work runs on specifics: rate codes, housekeeping statuses, no-show policy cut-off times, who holds signing authority for comps.
• Avoid naming what they'd do when something goes wrong, because most of the honest answer involves admitting a limit — "I don't have authority to refund that, I'd get the duty manager" — and shallow answers try to sound capable of everything instead.
• Skip shift-pattern reality. Reception in most hotels runs early, late, and often a night audit shift with different responsibilities (balancing the day's transactions, running the audit report, prepping the breakfast handover). A candidate who talks about the job as if it's one uniform shift, with no mention of handover notes or shift-to-shift continuity, usually hasn't done nights.

What to do before you go in

If the advert names a specific PMS, get in front of a demo or training video for it before the interview — not to bluff fluency, but so you can talk about the actual screens and fields rather than the brand name alone. Have two or three real scenarios ready — an overbooking, a walked guest, a difficult check-out — with the actual sequence of what you did, who you involved, and what the outcome was, not just how it felt. If you're moving from an independent property to a branded chain or vice versa, be ready to explain the difference in systems and standards plainly; interviewers in this trade ask about it because the operational gap is real, not because it's a box to tick.

jobmarket.pro reads the advert and your work history together and drafts an application that puts the PMS, property type, and shift pattern the employer actually asked for in the right place on the page, without inventing experience you don't have.